·Nigeria, WhatsApp, Pay-on-delivery

Running a Courier Business in Nigeria: WhatsApp, COD, and the Software Gap

A delivery rider on a scooter with an insulated delivery bag riding through a city street

Key takeaways

  • WhatsApp is the default booking channel for many Nigerian courier operators, form or no form.
  • Pay-on-delivery is the norm, not an edge case, and software built around pre-payment fights that.
  • The real cost of this gap is invisible — it looks like customer service, not a missing feature.

Talk to almost any courier or delivery operator in Lagos, or anywhere else in Nigeria, and two things come up immediately: customers book through WhatsApp, and a large share of deliveries are paid for on arrival, not in advance. Neither of these is a quirk to design around — they're the operating environment.

WhatsApp is the booking channel, whether you plan for it or not

Plenty of operators build a booking form, promote it, and still get most of their orders through WhatsApp messages. Customers describe a pickup and drop-off in a chat, sometimes with a photo of the item, and expect a reply — not a redirect to a form.

The operational cost shows up quietly: someone has to read every WhatsApp thread and manually create the order elsewhere. It's invisible in a way that formal software gaps aren't, because it looks like normal customer service rather than a missing feature.

Pay-on-delivery is the default, not the exception

Cash and pay-on-delivery are common in Nigerian courier operations, for reasons that have little to do with which software an operator uses — trust, banking friction, and customer habit all play a role. Software built around pre-payment as the default forces operators to work around it manually: sending account details by hand, chasing confirmation, or accepting the friction of asking customers to pay upfront when they'd rather pay on arrival.

The gap this leaves in generic dispatch software

  • Booking forms that assume the customer will use them, instead of capturing what actually arrives on WhatsApp.
  • Payment flows built around pre-payment, with pay-on-delivery treated as an afterthought or unsupported entirely.
  • Customer notifications sent by app push or email, when the customer is reachable on WhatsApp and nowhere else.

None of this is a reason to avoid dispatch software — it's a reason to be specific about what you need from it. A platform that treats WhatsApp as a first-class booking channel, and pay-on-delivery as a supported flow rather than a workaround, matches how the work already happens instead of asking operators to translate their business into a foreign model.

Traksend was built with this operating environment in mind: a WhatsApp AI assistant that can capture an order directly from a chat, and pay-on-delivery support that sends account details to the customer automatically before the rider arrives.

Ready to see it running in your operation?

Sign up free, or request a demo — no commitment either way.