Logistics Management Software in Nigeria: From WhatsApp Orders to Proof of Delivery
Logistics companies in Nigeria rarely fail because they lack vehicles. They fail because they lose track of what is where: a parcel picked up in Yaba and last seen at a Surulere hub, a rider holding two days of cash-on-delivery money, a customer waiting for an invoice that nobody can reconcile against 300 waybills. Most operations run on WhatsApp groups, a dispatcher's notebook and an Excel sheet that is updated at night. That works for 30 deliveries a day and collapses at 300.
This article is for owners and operations managers of dispatch and courier companies, e-commerce fulfilment operations, interstate haulage firms and third-party logistics providers. It explains what logistics management software should do, what changes in Nigerian operating conditions, when a ready-made product is enough, and what a custom system costs. Vehicle-focused fleet management and customer-facing delivery tracking are covered in separate guides; this one is about the operational core.
What does logistics management software do?
Logistics management software is the system that follows every shipment from the moment a customer requests a pickup to the moment cash and paperwork are reconciled. It replaces the notebook, the WhatsApp group and the nightly spreadsheet with one record per shipment that every role updates from a phone or a hub computer.
A complete system for a Nigerian logistics operation covers:
- Order intake: shipments created from a customer portal, WhatsApp, an online store integration, a merchant's bulk upload or by a call agent.
- Pricing: zone-based or distance-based rates, weight bands, special handling, customer-specific tariffs.
- Dispatch and routing: assigning shipments to riders, vans or trucks, batching by area, reassignment when a rider is unavailable.
- Hub and manifest management: scanning parcels in and out of hubs, interstate manifests, exceptions for missing items.
- Rider and driver app: task list, navigation, status updates, offline capture, proof of delivery (photo, signature, OTP).
- Customer notifications: SMS or WhatsApp status updates and a tracking link.
- Cash-on-delivery and remittance: recording cash collected per rider, daily remittance reconciliation, merchant payouts.
- Billing: invoices per merchant from delivered shipments, credit terms, statements.
- Reporting: deliveries per rider, on-time rate, failed delivery reasons, revenue per merchant, cost per delivery.
Logistics management, fleet management and tracking software: what is the difference?
The difference between logistics management software, fleet management software and delivery tracking software is what each one treats as the main record.
| Type | Main record | Answers | Typical users |
|---|---|---|---|
| Logistics management software | The shipment | Where is each parcel, who has it, has it been paid and billed? | Dispatchers, hub staff, finance |
| Fleet management software | The vehicle | Where are the vehicles, fuel, maintenance, driver behaviour? | Fleet managers |
| Delivery tracking software | The customer's view | Where is my order and when will it arrive? | Merchants and end customers |
A courier company needs logistics management first; fleet management becomes important once it owns many vehicles; tracking is a customer-facing layer on top of the shipment record. Buying a GPS fleet product and expecting it to run dispatch and billing is a common and expensive mistake.
Which modules does each type of logistics business need?
| Business type | Must have | Add later |
|---|---|---|
| Same-city dispatch (bikes) | Order intake from WhatsApp and merchants, dispatch, rider app with POD, COD reconciliation, merchant billing | Route optimisation, customer app |
| E-commerce fulfilment | Store integrations, warehouse pick and pack, dispatch, returns handling, merchant portal | Inventory for merchants, multi-warehouse |
| Interstate courier | Hub scanning, manifests, exception handling, tracking notifications, agent network management | Air and partner line-haul integration |
| Haulage and trucking | Trip and load management, waybills, driver advances and expenses, customer contracts, invoicing per trip | Telematics integration, fuel management |
| Third-party logistics for FMCG or pharma | Customer contracts and SLAs, order-to-delivery visibility, temperature or handling flags, proof of delivery with documents | Client portal with SLA reporting |
What changes for logistics software in Nigeria
Logistics software in Nigeria typically has to work in conditions that overseas delivery platforms treat as edge cases.
Addresses and navigation
Addresses are often descriptions ("opposite the blue church after the filling station") rather than structured data, and landmarks matter more than street numbers. The system should store free-text directions and a phone number alongside any map pin, allow the rider to call the customer from the app without exposing personal numbers unnecessarily, and let dispatchers correct pins from experience.
Cash-on-delivery and transfers
A large share of e-commerce deliveries are paid on delivery, by cash or by bank transfer to the rider's or company's account. Riders hold money. The software must record the amount collected per shipment, the method, and reconcile each rider's daily remittance against expected collections. Merchant payouts then flow from reconciled collections, not from delivered counts.
Failed deliveries and returns
Customers are unreachable, refuse items, or ask for delivery "tomorrow" repeatedly. Failed-delivery reasons, re-attempt rules and return-to-merchant flows need to be built in, because they drive both cost and merchant disputes.
Connectivity and power
Riders move through areas with poor data coverage, and hub computers face power interruptions. The rider app must capture status and proof of delivery offline and sync later; hub scanning should tolerate a lost connection. Timestamps should be captured on the device to keep the record honest when syncing is delayed.
Traffic and time windows
Lagos and other cities impose unpredictable transit times. Promising exact delivery times is risky; the system should work with windows and communicate delays automatically, and dispatch should batch by corridor rather than by distance alone.
Merchant relationships on WhatsApp and Instagram
Most merchants are small online sellers who send orders on WhatsApp. Order intake that accepts a structured WhatsApp message or a simple merchant portal, and returns a tracking link automatically, is worth more than any advanced routing feature. The WhatsApp Business Platform from Meta enables automated notifications at scale and carries per-message costs.
Trust and proof
Merchants and customers dispute deliveries. Photo proof, OTP confirmation, signature capture and timestamped location at delivery protect the logistics company and settle disputes quickly.
Off-the-shelf delivery software vs custom logistics software
The difference between off-the-shelf delivery software and a custom logistics system is how closely the shipment lifecycle, pricing and money flows match your business. Ready-made delivery management products handle standard same-city dispatch with rider apps and tracking, priced per rider or per delivery, often in US dollars. Custom systems model your hubs, tariffs, COD rules, merchant contracts and integrations exactly, at a higher upfront cost.
Off-the-shelf usually works when:
- You operate in one city with a standard pickup-to-delivery flow.
- COD handling is simple or rare.
- You have fewer than about 20 riders and a handful of merchants.
- You can accept per-delivery or per-rider pricing in US dollars.
Custom development is usually justified when:
- You run hubs, manifests or interstate routes.
- COD reconciliation and merchant payouts are a daily finance process.
- Merchants need portals, API access or store integrations.
- Pricing rules are complex (zones, weight, customer contracts, surcharges).
- Per-delivery SaaS fees at your volume exceed what a build would cost within a year or two.
- You need integrations with accounting, fleet telematics or partner couriers.
How much does logistics management software cost in Nigeria?
For a Nigerian logistics company, the main cost drivers are the number of roles and apps (dispatcher web, rider app, merchant portal, customer tracking), hub and manifest complexity, COD and billing logic, integrations (payments, WhatsApp, online stores, maps), and expected volume. All figures are indicative 2026 ranges; actual quotes vary with scope, vendor and exchange rate.
Subscription costs
Delivery management products typically charge per active rider or per delivery, usually in US dollars, sometimes with a platform fee. At high volume, per-delivery pricing can exceed the cost of ownership of a custom system. Ask for pricing at your current and projected volumes, and check whether COD reconciliation, merchant portals and WhatsApp notifications are included.
Custom build costs
| Scope | Indicative one-off build | Indicative recurring |
|---|---|---|
| Dispatcher web app, rider app with offline POD, basic pricing, COD recording, merchant invoicing | ₦4,000,000–₦9,000,000 | Hosting ₦300,000–₦800,000+ per year plus maintenance |
| Above plus merchant portal, tracking links, WhatsApp/SMS notifications, COD reconciliation and payouts | ₦8,000,000–₦16,000,000 | Maintenance often 15–25% of build per year; messaging and maps usage fees |
| Multi-hub with manifests, interstate, store integrations, customer app, accounting integration | ₦15,000,000–₦40,000,000+ | Support retainer; higher hosting |
Usage-based costs to budget
- Map and geocoding API usage (US dollar-denominated).
- WhatsApp Business Platform and SMS per-message costs.
- Payment gateway fees for merchant payouts and online payments.
- Android devices for riders, or a bring-your-own-device policy with data allowances.
Compare two or three written quotations on the same scope. Ask each vendor how the rider app behaves offline and how COD reconciliation works, because those two areas separate serious logistics software from generic delivery demos.
Example (hypothetical): a dispatch company in Lagos handling 400 parcels a day
Example (hypothetical): a dispatch company based in Ikeja serves about 120 Instagram and WhatsApp merchants with 35 riders and two collection points. Orders arrive as WhatsApp messages, a dispatcher assigns riders in a group chat, riders report deliveries with photos in another group, and COD money is counted each evening. Problems: merchants dispute deliveries and payouts, evening cash counts never match, and adding a third collection point is impossible to coordinate.
The company scopes a custom logistics system in two phases:
Phase one (about three months): merchant portal and structured WhatsApp intake, dispatcher board with rider assignment by zone, rider app with offline status updates, photo and OTP proof of delivery, COD amount capture, and daily rider remittance reconciliation. Indicative build ₦7,000,000–₦10,000,000.
Phase two (about two months): automated tracking links and WhatsApp notifications, merchant statements and payouts from reconciled COD, failed-delivery workflow with re-attempt rules, and management reports on on-time rate and cost per delivery. Indicative build ₦4,000,000–₦6,000,000.
The result is one shipment record from intake to payout, evening reconciliation done per rider in the system, and merchants checking status themselves instead of messaging the dispatcher. The figures are illustrative and the company should compare written quotations on this scope.
How to implement logistics software without stopping operations
The first step is to define your shipment statuses and COD rules on paper, because software can only enforce a process you have actually decided.
- Write the shipment lifecycle. Every status from "requested" to "paid out", who sets it, and what evidence is required.
- Define pricing and COD rules. Zones, weight bands, surcharges; who may hold cash, remittance deadlines, tolerance for shortfalls.
- Choose the route (product or custom) with the checklist below and your volume projections.
- Pilot with a subset. Five riders and ten merchants for two to four weeks while the rest continue on WhatsApp.
- Fix intake first. Make merchants create orders in the portal or structured WhatsApp flow; refuse unstructured orders after a cut-over date.
- Move COD reconciliation into the system and stop the evening manual count; discrepancies become per-rider records.
- Switch off the old groups for operational updates once the pilot riders are stable; keep one for announcements.
- Review weekly for the first two months: failed-delivery reasons, sync issues, rider complaints, merchant disputes.
Logistics software requirements checklist
- Order intake from merchant portal, structured WhatsApp and bulk upload.
- Free-text directions and landmarks stored with each address.
- Zone or distance pricing with customer-specific tariffs.
- Dispatcher board with assignment, batching and reassignment.
- Rider app that works offline and syncs later, with device timestamps.
- Proof of delivery: photo, OTP or signature, and location.
- Failed-delivery reasons, re-attempt rules and return-to-merchant flow.
- COD amount and method per shipment; daily rider remittance reconciliation.
- Merchant invoices and statements from delivered and reconciled shipments.
- Tracking link and automated notifications.
- Hub scanning and manifests if you operate hubs or interstate routes.
- Reports: on-time rate, deliveries per rider, cost per delivery, revenue per merchant.
- Role-based access and audit trail.
- Data export at any time; NDPA 2023 position on customer data.
- Integration options: payments, accounting, online stores, maps, WhatsApp.
Mistakes logistics companies make with software
- Buying fleet GPS and expecting dispatch and billing. Vehicle tracking tells you where the bike is, not who has paid for the parcel.
- Skipping offline support. The first rider in a dead zone will revert to WhatsApp, and the record breaks.
- Leaving COD outside the system. Cash discrepancies are the biggest source of losses and staff disputes; if reconciliation is manual, the software has not solved the business problem.
- Per-delivery SaaS at scale without doing the maths. US dollar fees per delivery at hundreds of deliveries a day can exceed the cost of a build within a year.
- No structured intake. If merchants can still send free-text WhatsApp orders, dispatchers will still retype them and errors continue.
- Ignoring failed deliveries in the design. Re-attempts and returns are where costs and disputes concentrate.
- Launching to all riders at once. A pilot catches app and process problems before they affect every merchant.
Conclusion
Logistics management software in Nigeria should be built around the shipment record and the money that follows it: structured intake, dispatch, an offline-capable rider app with proof of delivery, COD reconciliation per rider and billing from reconciled deliveries. Same-city dispatch companies with modest volume can start with an off-the-shelf delivery product, watching US dollar per-delivery fees as they grow. Hub-based couriers, fulfilment operations and haulage firms usually justify a custom system, indicatively ₦4,000,000–₦25,000,000+ built in phases. Whatever the route, define statuses and COD rules first, pilot with a subset of riders, and retire the WhatsApp groups for operational updates once the system is trusted.
If your dispatch or haulage operation has outgrown WhatsApp groups and spreadsheets, Linestech can scope a logistics management system around your intake, dispatch, proof-of-delivery and reconciliation processes.
Frequently asked questions
Can logistics software take orders directly from WhatsApp?
Yes. A common design is a structured WhatsApp flow on the WhatsApp Business Platform that collects pickup, delivery and item details and creates a shipment automatically, returning a tracking link. Free-text messages still need a human to interpret them, so the aim is to move merchants to the structured flow or a portal.
Do riders need company phones?
Not necessarily. Many companies run a bring-your-own-device policy with a data allowance, which works if the rider app is light, offline-capable and runs on modest Android phones. Company devices make sense when proof-of-delivery photo quality, security or staff turnover justify the cost.
How does COD reconciliation work in logistics software?
Each delivered shipment records the amount collected and the method. At day end, the system shows what each rider should remit; the rider's actual remittance is recorded and any shortfall becomes a per-rider record. Merchant payouts are then generated from reconciled collections rather than from delivery counts.
Is route optimisation worth it in Nigerian cities?
Basic batching by zone and corridor delivers most of the benefit and is easy to implement. Full route optimisation adds map API costs and depends on accurate addresses and live traffic; it becomes valuable at higher volumes per rider and for scheduled van routes rather than ad-hoc bike dispatch.
Can logistics software integrate with merchants' online stores?
Yes, through store platform APIs or plugins, so orders flow in automatically and status flows back. This is most useful for fulfilment operations serving merchants on standard e-commerce platforms; for Instagram-only sellers, the portal or WhatsApp intake is the practical route.
How long does a custom logistics system take to build?
A phased build typically takes three to six months for the operational core (intake, dispatch, rider app, POD, COD, billing) and a further two to four months for portals, notifications, hubs and integrations. Piloting with a subset of riders while the rest continue on the old process keeps operations running throughout.
Sources and further reading
Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.
