How to Build a Logistics App in Nigeria: Shipments, Trips, Fleet and Billing

Logistics app versus delivery app: which one do you need?

The two are often confused, and building the wrong one is expensive.

If your business is closer to the left column, the guide to building a delivery app in Nigeria is the right starting point. If it is closer to the right, continue here. Some businesses (a cargo consolidator that also does last-mile drops in Lagos) need both, and should build the logistics core first with a delivery module later.

The modules of a logistics app

The marked modules form a workable version one for most haulage and cargo businesses. The customer portal and advanced analytics come once the operations data is reliable.

Roles and what each one needs

• Operations or dispatch: the trip board (which vehicles are where, on which trips, with which loads), consignment queue, driver assignment, exception handling.
• Drivers: a simple app in plain language with large buttons: today's trip, stops in order, consignments to deliver, photograph the signed waybill, log an expense, call the office.
• Loading and warehouse staff: for consolidators, a screen to receive consignments, scan or tag them, and confirm loading onto a trip.
• Finance: expense reconciliation, invoicing, payment matching, statements, driver advances.
• Customers: booking, tracking, documents, invoices, queries, through a portal or a WhatsApp link.
• Management: utilisation, profitability per route and vehicle, outstanding receivables, compliance expiries.

Permissions should be role-based from the start; the driver must not see customer rates, and a customer must not see another customer's consignments.

The two lifecycles: consignments and trips

A logistics app tracks two things that move separately. Consignment lifecycle: booked → received at depot (for consolidators) → loaded onto trip → in transit → delivered (with proof) → invoiced → paid, with side paths for partial delivery, damage, return to depot and cancellation. Trip lifecycle: planned → vehicle and driver assigned → loaded → departed → checkpoints or waypoints → arrived → unloaded → expenses reconciled → closed, with side paths for breakdown, diversion and delay. A trip carries many consignments; a consignment may, for multi-leg journeys, be carried by more than one trip. Modelling this correctly is the core of the backend, and it is why a spreadsheet stops working: it cannot hold both lifecycles and their relationship. Write both lifecycles down with the rules for each transition before the build starts.

Tracking options: driver phone, telematics or both

Most businesses should start with driver-phone tracking inside the driver app, because the app is needed anyway for status, documents and expenses. Add telematics for high-value vehicles or cargo where independent tracking justifies the cost. If a telematics provider is already in place, ask for API access so the logistics app can show positions on the same trip board rather than in a separate system.

Trip expenses and the road money problem

Fuel, tolls, loading fees, road expenses and driver allowances are where haulage businesses lose control. The app should handle the full cycle:

• Advance: the office records the advance given to the driver for a trip, by cash or transfer.
• Expense capture: the driver logs each expense in the app with amount, category, location and a photo of the receipt where one exists, offline if necessary.
• Reconciliation: at trip close, finance compares advance, logged expenses and returned cash, and approves or queries items.
• Standard costs: the system holds expected fuel and expense ranges per route and flags trips that exceed them.
• Reports: cost per trip and per kilometre by route, vehicle and driver.

Expenses that cannot be receipted will always exist on Nigerian roads. The point is not to eliminate them but to record them at the moment they happen, with a location and time, so patterns become visible and disputes become rare.

How to build a logistics app: twelve steps

1. Map the current operation: how a shipment is booked, how trips are planned, what the waybill looks like, how money moves, what causes disputes. Interview drivers and finance, not only management.
2. Choose version-one modules from the table above; resist adding the customer portal until operations data is reliable.
3. Define the consignment and trip lifecycles with transition rules.
4. Design the pricing logic: by route, tonnage, volume, vehicle type or negotiated customer rates, with surcharges and how quotes become bookings.
5. Design the data model: customers, consignments, trips, vehicles, drivers, expenses, invoices, documents, positions.
6. Build the backend and operations dashboard first. The trip board is the screen operations staff will live in; get it right with them.
7. Build the driver app for Android with offline capture, low data use, large controls and plain language, in the languages your drivers actually use.
8. Build finance functions: expenses, advances, reconciliation, invoicing, statements, and an export to the accounting software already in use.
9. Add tracking: phone-based first; telematics integration where justified.
10. Add notifications: WhatsApp template messages or SMS to customers at departure, arrival and delivery, using the WhatsApp Business Platform.
11. Pilot on one route or one depot for a full month, running the paper process alongside. Reconcile the two to find gaps.
12. Roll out, train and measure: utilisation, cost per kilometre, invoice-to-payment time, disputes, against the baseline.

What changes for Nigerian logistics businesses

• Long, unpredictable roads. Interstate trips can be delayed by road conditions, checkpoints and breakdowns. Status updates should be event-based (departed, checkpoint reached, arrived) with optional position, not a promised ETA.
• Connectivity is intermittent. The driver app must capture everything offline and sync later, and the trip board must show last-known position and time honestly.
• Drivers and phones. Many drivers use basic Android phones and may not be comfortable with dense apps. Large buttons, few screens, voice-friendly notes and local-language labels matter more than features.
• Paper still rules at the customer's gate. A signed physical waybill is what receivers expect. The app should generate a printable waybill and capture a photo of the signed copy rather than trying to abolish paper.
• Fuel price volatility. Standard costs per route need to be adjustable quickly, and quotes should have short validity.
• Credit customers and slow payment. Businesses pay on terms and often late. Invoicing, statements, ageing reports and reminders are as important as tracking.
• Compliance documents. Vehicle papers, driver licences, insurance and goods-in-transit cover expire; the fleet module should hold them with reminders. Verify current regulatory requirements for your operation with the relevant authorities; this article does not provide legal advice.
• Security of cargo data. Where a truck is, what it carries and when it left are sensitive. Restrict who can see live positions and consignment contents, and handle personal data under the Nigeria Data Protection Act 2023, verifying obligations with the Nigeria Data Protection Commission.
• Currency. Hosting, map usage and telematics subscriptions are often priced in US dollars; budget in both currencies.

Example (hypothetical): a Port Harcourt haulage firm with 25 trucks

Consider a haulage company based in Port Harcourt with 25 trucks carrying containers and general cargo to Lagos, Aba, Onitsha and Abuja for around forty business customers on credit terms. This scenario is illustrative and not a client result. The company runs on a whiteboard, paper waybills, WhatsApp groups per route and an accounting package that receives invoices weeks late. The recurring problems: trucks idle in Lagos because nobody knew a return load was available, road expenses that cannot be reconciled, customers disputing delivery dates, and invoices going out late because signed waybills arrive with the driver days later. Version one covers consignments and waybills, the trip board, a driver app (trip details, status at checkpoints, waybill photo at delivery, expense logging with receipts, offline), advances and reconciliation, and invoicing with an export to the accounting package. Phone-based tracking gives the trip board last-known positions. WhatsApp templates notify customers at departure and delivery. The effect the company looks for: invoices issued the same day the waybill photo arrives, expenses reconciled at trip close, and a trip board that shows which trucks will be empty in Lagos tomorrow so that operations can sell return loads. Phase two adds a customer portal for booking and documents, and telematics on the highest-value trucks. Indicative cost for version one sits in the ₦5,000,000–₦15,000,000 band and phase two takes the whole system towards ₦15,000,000–₦30,000,000 (2026 ranges; actual quotes vary with scope, vendor and exchange rate).

What a logistics app costs in Nigeria

As indicative 2026 ranges, with actual quotes varying by scope, vendor and exchange rate:

Telematics hardware and subscriptions are separate from the app budget. Compare two or three written quotations on identical scope, and ask specifically how each vendor handles offline driver capture and the consignment-to-trip relationship, since those are the two areas where cheap builds fail.

Build custom or buy software?

Off-the-shelf transport management and fleet software exists, usually as SaaS priced per vehicle or per user per month in US dollars. It can be the right choice when the business runs a standard operation and can adapt to the software's process. Custom development is justified when:

• The operation has specific workflows (consolidation depots, multi-leg trips, customer-specific pricing and documents) that generic software handles badly.
• Drivers need an app in plain language with offline capture tuned to Nigerian roads.
• Integrations with existing accounting, telematics or customer systems are essential.
• US-dollar subscriptions for dozens of vehicles and users would exceed the cost of owning the system within a few years.

The article on logistics management software in Nigeria treats the software options in more depth. A middle path is to use SaaS for fleet maintenance while building the custom trip, driver and billing core.

Mistakes to avoid

• Starting with the customer portal. Customers need reliable data; that comes from operations and drivers using the system first.
• A driver app designed like an office tool. Dense screens and English-only jargon lead drivers back to phone calls. Test with real drivers on their own phones.
• No offline mode. A driver app that fails without network will be abandoned on the first trip.
• Modelling trips without consignments, or the reverse. Both lifecycles and their relationship are the backbone; get the data model right early.
• Ignoring finance. Expenses, advances and invoicing are where the money leaks; a tracking-only app does not fix that.
• Telematics before workflow. Knowing where a truck is does not tell you what it carries, what it cost or whether it has been invoiced.
• Abolishing paper waybills. Receivers and checkpoints expect them. Digitise the record and photograph the signature instead.
• No pilot on a single route. A month of parallel running on one route reveals more than any requirements workshop.

Conclusion

A logistics app for a Nigerian haulage, cargo or freight business is built around two lifecycles, consignments and trips, and the modules that serve them: booking, waybills, the trip board, a driver app that works offline, expenses and reconciliation, invoicing, tracking and, later, a customer portal. Build the operations core first, design the driver app for the drivers you actually have, keep paper waybills as photographed evidence rather than abolishing them, and pilot on one route before rolling out. The return comes from visible utilisation, verified expenses and invoices issued the day cargo is delivered. If your operation has outgrown the whiteboard and WhatsApp groups, Linestech can help you map the consignment and trip workflows, choose version-one modules and build a logistics system with a driver app suited to Nigerian roads.

Frequently asked questions

Can the app work with drivers who are not comfortable with technology?

Yes, if it is designed for them: a handful of large buttons, one task per screen, plain language or local-language labels, photo capture instead of typing, and a call-the-office button. Pilot with the least technical drivers, not the most. Many businesses also keep a dispatcher-side option to update a trip on a driver's behalf after a phone call.

Do I need telematics devices on every truck?

No. Start with driver-phone tracking inside the driver app, which is free of hardware and also carries status, documents and expenses. Add telematics units to high-value vehicles or where independent tracking, ignition data or theft recovery justify the hardware and subscription. If units are already installed, integrate their positions into the trip board through the provider's API.

How does the app handle multi-leg journeys and consolidation?

The data model links consignments to trips many-to-many. A consignment received at a depot in Onitsha can be loaded onto one trip to Lagos, unloaded at a hub and loaded onto a different vehicle for final delivery, with its status and proof recorded at each leg. This relationship is the reason a spreadsheet stops working and a proper backend is needed.

Can customers track their cargo without a portal?

Yes. A tracking link sent by WhatsApp or SMS at departure can show consignment status and last-known position without a login. A full customer portal adds booking, documents and invoices and is usually a phase-two addition once operations data is reliable.

How does the logistics app connect to our accounting software?

Most accounting packages accept invoice and payment imports, and many offer an API. The logistics app generates invoices from delivered consignments and exports them, then imports or matches payments so that statements and ageing reports stay consistent. Specify the accounting package in the requirements so that the vendor can confirm the integration route.

What is the difference between a logistics app and fleet management software?

Fleet management software focuses on the vehicles: documents, maintenance, fuel, tyres, driver behaviour and telematics. A logistics app focuses on the work: consignments, trips, drivers' tasks, proof of delivery, expenses and billing. Many businesses need both; the fleet module in a logistics app covers the basics, and dedicated fleet software or telematics can be integrated for deeper vehicle management.

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.

• Nigeria Data Protection Commission (NDPC)
• WhatsApp Business Platform — Meta for Developers
• Core Web Vitals — web.dev