The Coordination Problem Hiding Inside Nigerian Logistics

A parcel leaves a hub in Lagos at 7am. Assigned to a delivery partner — one of several third-party last-mile operators the courier uses to cover areas outside their direct network. The driver picks it up. The hub logs the handover. The driver begins his route.

At 11am, a customer calls to ask where their parcel is.

The contact centre agent checks the system. The system shows the parcel was dispatched to a delivery partner at 7am. What the system cannot show is where the parcel is right now. The delivery partner does not update the courier's system in real time. The driver does not have a device broadcasting his location. The only way to know where the parcel is at 11am is to call the delivery partner, who calls the driver, who checks and calls back.

The customer is told: we will update you shortly.

This is the coordination problem inside Nigerian logistics. And like most of the operational problems I write about, it is not a technology problem. It is a structural problem that technology cannot fix until the structure is understood.

The ecosystem most people outside logistics do not see

Nigerian courier and logistics companies do not deliver everything themselves.

The major players — established courier companies, tech-driven last-mile operators, freight specialists — operate networks that extend far beyond their direct capacity through partnerships with smaller operators, agents, and independent contractors. This exists for obvious reasons. Nigeria is a geographically complex market. Road infrastructure is inconsistent. Traffic in Lagos alone makes predictable ETAs a work of fiction. Building a fully owned delivery network that covers every corridor is capital-intensive and operationally demanding.

So they partner. Scale without proportional overhead.

The tradeoff is coordination.

When a parcel moves within the courier's own network, they control the information flow. When it crosses into a partner's hands, the information gap opens. The courier knows when it left. The customer knows when it was supposed to arrive. What happens in between — where the parcel is, whether delivery was attempted, why it failed if it did — lives in a space that neither party can see clearly.

That gap is where the problems live.

What coordination actually looks like on the ground

The tools for managing partner relationships in Nigerian logistics are, in most cases, WhatsApp groups, phone calls, and end-of-day reconciliation meetings.

A hub manager coordinates with delivery partners through a WhatsApp group. Dispatch instructions go out in the morning. Updates come back when drivers report in — which is inconsistent, because reporting is an additional task on top of the primary task of actually delivering. Exceptions — failed deliveries, address problems, customer unavailable — come through the same channel, mixed in with everything else in the thread.

At the end of the day, the hub manager reconciles what went out against what came back. The gaps — parcels dispatched but not delivered and not returned — require individual follow-up calls. Some resolve quickly. Some take days. Some require the partner to trace back through their own records, which may be just as informal as the courier's.

Meanwhile, the customer is still waiting.

What this actually costs

The visible cost is the failed delivery. The parcel that did not arrive. The customer complaint. The refund. This is the number that gets measured, reported, and acted on in operations reviews.

The invisible cost is larger.

Every phone call chasing a delivery status is time a hub manager is not spending on the next dispatch. Every manual reconciliation is an hour that cannot be invested elsewhere. Every failed delivery that requires re-delivery doubles the cost of serving that customer. Every customer who received no update during the delivery window is a customer who is less likely to ship again.

These costs are diffuse. They do not appear as a line item anywhere. They show up as lower margins, higher customer acquisition costs to replace the customers who churned quietly, and operations teams that are permanently reactive — always managing the last problem, never building toward the next state.

The number is real. It just does not announce itself.

Why it is not as simple as "just fix it"

The coordination gap persists not because nobody has noticed. Everyone has noticed.

It persists because fixing it requires changing behaviour across an ecosystem of independent actors who each have their own constraints and their own logic.

A major courier can invest in better tracking systems. But if their delivery partners — independent operators with thin margins and minimal technology infrastructure — cannot feed data into those systems, the tracking stays incomplete. Partial visibility is better than none. It does not answer the customer's question at 11am.

And the partners are not being stubborn. They are running operations with real constraints. Adopting a new system means training, devices, data costs, and time. For a small delivery contractor managing fifteen drivers across three routes, the overhead of a new coordination tool is not theoretical. It is a real cost on top of an already thin operation, even if the tool would ultimately help them.

This is the part that gets missed when people come in with software pitches. They are solving for the courier's visibility problem without asking what it costs the partner to provide it. The incentive structures are not aligned. The solution that looks obvious from the outside collapses when it meets the partner's actual situation.

The question worth asking

Across every conversation I have had with logistics operators in Nigeria, the coordination problem surfaces in different forms but with consistent structure. Information that should flow between parties does not. The gap gets filled by manual communication. The manual communication is never quite enough.

The most useful question is not which technology solves this.

It is: at what specific point in the delivery process does the information gap open, what would it actually take to close it, and who in the ecosystem would need to change their behaviour — and what would make that change worth it to them — for the closure to stick?

That is a harder question than it sounds. It is also the only question that leads somewhere real.

***

Part of an ongoing look at how Nigerian organizations actually operate — not how they say they do.