Many Nigerian shoppers still prefer to see the goods before they pay. For an online store, pay on delivery can remove that hesitation and bring in orders that would otherwise be lost at checkout. The catch is that every unpaid order carries a risk: the parcel may never be accepted, the cash may arrive late, and the goods may come back. This guide explains where those losses come from and how to reduce them without turning away the buyers you want.
What pay on delivery does for an online store
Pay on delivery, often called cash on delivery or COD, lets a buyer place an order and pay the rider when the goods arrive. It is a trust tool. A buyer who has never heard of your store can order without sending money first, which is why it often lifts conversion on a checkout page that otherwise has only card payment.
The benefit is real, but it is not free. Your store carries the cost of the delivery attempt whether or not the buyer pays. If you do not manage that cost, a store that looks busy can be losing money on every failed trip.
Where pay on delivery costs you money
Failed deliveries
A buyer who ordered on impulse may not answer the phone on delivery day. Each failed attempt costs a rider's time and fuel, and the parcel travels back. If you pay for each attempt, the order can end up costing more than the margin it earned.
Returns and refused parcels
Some buyers refuse the parcel at the door, especially when the item looks different from the photo or the price has changed. Refused goods need to be collected, inspected, and restocked. Until they are back on your shelf, you have lost the sale and the delivery cost.
Slow cash and messy reconciliation
With prepaid orders, the money arrives before you pack the goods. With cash on delivery, your rider holds the cash and your team has to match it to each order. Late remittances and mismatched amounts make it hard to know what you actually earned that week.
Stock held for orders that never close
If your site reduces stock as soon as a buyer clicks "place order", unpaid orders can lock up items that other customers want. Those items look sold out when they are not. This is a software problem, and it is one of the most common ones we see when stores grow.
How to reduce pay on delivery losses
You do not need to remove pay on delivery to control it. Most of the damage comes from a few specific gaps, and each one can be closed.
- Confirm every order before you dispatch. A short call or message asking the buyer to confirm the address and time weeds out many failed trips. Make it a step in your order process, not something a busy staff member remembers to do.
- Charge for the risk. A small delivery fee on cash orders, or a higher fee for cash than for prepaid, reflects the cost of a failed attempt. Set the rule once and apply it the same way to everyone.
- Offer a prepaid option that is easy to choose. Show card, bank transfer and pay on delivery side by side, and explain the difference in one line. Many buyers switch once they see prepaid is simple and safe.
- Limit cash orders for risky cases. You can restrict pay on delivery to areas where your riders reliably deliver, or to orders below a value you choose.
- Track failed attempts by customer and area. If the same phone number or street keeps failing, flag it. Your data will show you where the losses really sit.
Build checkout so both payment types work properly
The checkout is where most of these problems are either prevented or created. A store that offers pay on delivery and prepaid options usually needs its order system to handle both paths without confusing staff or customers.
Keep order status tied to real payment events
For prepaid orders, your backend should update the order only after the payment provider confirms the payment, usually through a webhook. Do not rely on the buyer's browser saying the payment worked, because the connection can drop after the money has left the account. If your backend is set up this way, a paid order and a stock reduction will always agree. Our backend and API development work covers this kind of payment and order logic in Go, Node.js and Laravel.
Hold stock for the right length of time
For pay on delivery, decide when stock is reserved. Some stores reserve it at confirmation, and release it if the order is not confirmed within a set time. Others reserve it only after dispatch. Either can work, but the rule must be written into the system, not left to staff judgement.
Show payment status everywhere it matters
Your team, your riders and your customers should each see the same status: unpaid, paid, cash collected, remitted, refused or returned. When those labels match across your admin panel and your customer emails, fewer orders fall through the gaps. A custom website or web app built around your payment rules is usually easier to run than a template with the rules bolted on.
When to change your delivery policy
Look at your numbers before you decide. If failed deliveries and refusals cost more than the orders bring in, tighten the rules first: confirmation calls, delivery fees and prepaid incentives. If the problem is concentrated in one area or one product line, limit pay on delivery there instead of removing it everywhere. If your store has outgrown spreadsheets and manual matching, that is a sign the system needs work. Our technical support team can review a store's order and payment flow, find where orders are being lost, and fix the code behind it.
A simple test helps: after each change, track failed delivery rate, refusal rate and time to remit cash for four to six weeks. Keep the changes that improve the numbers and drop the ones that do not.
Frequently asked questions
Should my online store offer pay on delivery at all?
For many stores in Nigeria, offering it is worth it because it removes a major reason buyers leave at checkout. The decision depends on your delivery reliability and margins. Offer it with clear rules, and check the results regularly.
How can I stop buyers from refusing parcels?
Show accurate photos and clear product details, confirm the order before dispatch, and make sure the price on the invoice matches what the buyer saw. Most refusals come from surprises, so reducing surprises reduces refusals.
Is prepaid checkout safer for my store?
Prepaid orders reduce the risk of failed deliveries and cash delays because the money arrives first. They still need correct order status handling, so a paid order and its stock change always match.
Can my current store system handle both payment types?
Many template stores can, but they often handle order status and stock poorly when both are used. If you are seeing mismatched orders or stock errors, a developer should review how payments are recorded before you add more features.
If your store loses money on unpaid orders or your checkout is hard to manage, we can help you map the problem and fix it. Start a project brief or contact Icoweb from Port Harcourt, and we will look at your order and payment flow with you.




