How Much Does It Cost to Build a Delivery App in Nigeria?
Delivery app cost tiers in Nigeria (2026)
For a Nigerian business, delivery app costs fall into three tiers set by how many sides the system serves and whether tracking is live. A single business delivering its own goods with manual dispatch sits at the bottom; a multi-hub logistics platform sits at the top.
| Tier | Indicative 2026 range | Typical scope | Who it suits |
|---|---|---|---|
| Simple: own-business delivery | ₦3,000,000–₦8,000,000 | Customer ordering app or WhatsApp orders, basic rider app with job list and proof of delivery, status updates, manual dispatch on a web screen | Restaurants, pharmacies, retailers delivering their own orders |
| Standard: delivery platform | ₦8,000,000–₦25,000,000 | Customer app, rider app with live GPS, dispatch dashboard with auto-assignment, zone or distance pricing, gateway payments, notifications, ratings | Dispatch companies, intra-city logistics, food delivery in one city |
| Full: logistics platform | ₦25,000,000–₦50,000,000+ | Multiple hubs, route optimisation, merchant portal and API, wallets and cash reconciliation, fleet management, analytics | Multi-city logistics firms, e-commerce fulfilment operators |
Indicative 2026 ranges; actual quotes vary with scope, vendor and exchange rate.
Why a delivery app costs more than it looks: three products
A delivery app is three connected products on one backend, and each has its own screens, logic and testing. Quotes that price "the app" without naming the rider app and the dispatch dashboard are pricing a third of the system.
| Customer app | Rider app | Dispatch dashboard (web) |
|---|---|---|
| Create order, set pickup and drop-off | Accept or reject jobs, see route | Order queue and assignment (manual or automatic) |
| Fee estimate before confirming | Navigation handoff to Google Maps | Live map of riders and orders |
| Pay by card, transfer, USSD or cash | Status updates: picked up, en route, delivered | Pricing rules, zones and surcharges |
| Live tracking and ETA | Proof of delivery: photo, signature, OTP | Rider onboarding, documents and shifts |
| Notifications and support chat | Earnings, cash collected, settlement | Cash reconciliation and payouts |
| Ratings and order history | Offline queue for poor coverage | Reports, disputes and customer support |
The rider app is where cheap builds fail. It must work on entry-level Android phones, keep running with the screen off, survive network drops, and use as little battery and data as possible while sending location. That is more demanding engineering than the customer app.
What determines the cost of a delivery app?
The cost of a delivery app in Nigeria is driven by live tracking, maps and routing, the pricing engine, proof of delivery, payments including cash, notifications, the number of hubs and cities, merchant and B2B features, and rider management. Each is a separate scope decision.
- Live tracking. Real-time location from riders to customers and dispatch needs a persistent connection (websockets or a real-time service) and battery-aware location logic. It roughly doubles the backend complexity compared with status-only updates.
- Maps and routing. Address search, distance calculation, ETA and navigation typically use Google Maps Platform or an alternative such as Mapbox. Integration is moderate work; usage is a recurring USD cost. Adding Google Maps to a mobile app is covered in its own guide.
- Pricing engine. Flat fee is trivial; zone-to-zone tables are simple; distance and time-based pricing with surcharges for weight, rain, night and fuel changes is a module.
- Proof of delivery. Photo, signature or OTP at handover, with time and location captured, as described in the guide to building a mobile app with camera features.
- Payments and cash. Gateway integration for prepaid orders is standard. Cash on delivery adds rider cash tracking, daily reconciliation and settlement logic that many quotes omit.
- Notifications. Push for app users, SMS or WhatsApp for customers who have not installed the app, and rider alerts that cut through a phone in a pocket.
- Hubs and cities. Multi-hub sorting, intercity legs and city-specific pricing multiply configuration and reporting.
- Merchant and B2B features. A portal or API for e-commerce merchants to book deliveries in bulk, with invoicing, is a product of its own.
- Rider management. Onboarding with documents, guarantor records, shifts, performance and earnings statements.
- Automatic assignment. Nearest-available-rider logic with fallbacks is moderate; batching and route optimisation across many stops is advanced.
Line-by-line cost breakdown of a standard build
The table below shows how a standard-tier platform of about ₦15,000,000 might divide. Use it to spot quotations where the rider app or the dashboard is priced as an afterthought.
| Component | Typical share | Indicative amount on a ₦15,000,000 project | What it covers |
|---|---|---|---|
| Discovery and operations mapping | 5–8% | ₦750,000–₦1,200,000 | Zones, pricing rules, dispatch process, rider policy |
| UI/UX design (three products) | 10–12% | ₦1,500,000–₦1,800,000 | Customer, rider and dashboard screens |
| Customer app | 15–18% | ₦2,250,000–₦2,700,000 | Ordering, fee estimate, tracking, payments |
| Rider app | 15–18% | ₦2,250,000–₦2,700,000 | Jobs, location service, proof of delivery, earnings, offline queue |
| Backend and real-time services | 18–22% | ₦2,700,000–₦3,300,000 | APIs, assignment logic, live location, pricing engine |
| Dispatch dashboard | 10–12% | ₦1,500,000–₦1,800,000 | Live map, assignment, riders, cash reconciliation, reports |
| Maps and payment integration | 5–7% | ₦750,000–₦1,050,000 | Maps SDKs, gateway, webhooks |
| Testing and QA | 8–10% | ₦1,200,000–₦1,500,000 | Field testing with real riders, device and network testing |
| Publishing and project management | 5–7% | ₦750,000–₦1,050,000 | Two store listings, coordination, change control |
Indicative shares for a standard-tier build; allocations vary by vendor and scope. Field testing with actual riders on actual routes is the line most often missing, and it is the one that finds the battery, GPS and offline problems before customers do.
Recurring costs: maps, messaging, hosting and riders
Delivery apps have higher running costs than most business apps because location, maps and messaging are metered. Budget these separately from the build and review them monthly.
| Recurring item | Indicative 2026 cost | Notes |
|---|---|---|
| Maps platform usage | USD, billed per request with monthly allowances | Address search, distance and ETA calls add up; verify current Google Maps Platform or Mapbox pricing |
| Real-time backend hosting | ₦300,000–₦1,500,000+ per year | Persistent connections and location writes need more capacity than a catalogue app |
| SMS and WhatsApp messages | Per message or per conversation | Order confirmations and rider alerts to non-app users |
| Push notifications | Free tier to modest USD | Firebase Cloud Messaging commonly used |
| Payment gateway fees | Percentage per transaction | Check current gateway pricing |
| Maintenance and support | 15–25% of build cost per year | Three products means more to maintain |
| Rider devices and data | Per rider | Company phones or data allowances if riders use their own |
| App store accounts | Apple US$99 per year; Google US$25 once (historically) | Verify current fees |
Indicative 2026 figures; verify current pricing with each provider. Two design choices shape the maps bill: how often the rider app sends location (every few seconds versus every 30 seconds) and whether the customer app requests ETAs continuously or on demand. Ongoing costs are covered further in the guide to app maintenance cost in Nigeria.
Example (hypothetical): a restaurant's own delivery versus a dispatch startup
Example (hypothetical): two businesses in Port Harcourt and Lagos both say they need "a delivery app". Their scope, and their tier, differ. A restaurant group in Port Harcourt delivers from three outlets within a few kilometres. Orders arrive on WhatsApp and Instagram; the group employs six riders. It needs a rider app with a job list, navigation handoff, status updates and a delivery photo, status notifications to customers by SMS, and a simple web screen where each outlet assigns jobs. No live map for customers, no in-app ordering yet. Simple tier, indicatively ₦4,000,000–₦7,000,000, with modest recurring costs because there is no continuous tracking. A dispatch startup in Lagos wants to serve small online sellers across the mainland and island. It needs a customer app with fee estimates, a merchant web portal for bulk bookings, a rider app with live location and proof of delivery, automatic assignment to the nearest rider, zone-based pricing with surcharges, gateway payments plus cash on delivery with reconciliation, and a dispatch dashboard with a live map. Standard tier, indicatively ₦15,000,000–₦25,000,000, with maps, messaging and real-time hosting as significant monthly items. Neither figure is a quote. They show that the same phrase, "delivery app", describes systems that differ several times over in cost, and that the difference is operational scope rather than screens.
What changes the cost in Nigeria
For a Nigerian delivery business, five local factors move the cost: landmark-based addressing and traffic, cash on delivery, rider device quality and churn, the data and battery cost of tracking, and safety and regulatory constraints on how riders move. Each adds scope that overseas templates do not include.
- Addresses and traffic. Customers describe locations by landmarks; map pins are often wrong. The app needs pin adjustment, landmark notes and a rider call button, and ETAs must allow for Lagos traffic rather than trusting map estimates.
- Cash on delivery. Widely expected and operationally heavy. Rider cash balances, daily settlement and limits on cash per rider are a full module, not a checkbox.
- Rider devices. Riders carry entry-level Android phones with weak GPS and small batteries. Location logic must be battery-aware, the app small, and everything testable on those devices.
- Data cost. Continuous location uploads consume data riders pay for unless the business does. Send location efficiently and let dispatch adjust frequency.
- Rider churn. Fast onboarding with document capture and guarantor records, and instant deactivation, matter more than in markets with stable fleets.
- Movement restrictions and safety. Restrictions on commercial motorcycles in parts of Lagos and other cities affect routing and vehicle types; verify current rules in each city you operate in. Rider safety features such as an SOS button and trip sharing are cheap to add and worth including.
- Fuel price changes. The pricing engine should let the business change rates and surcharges without a developer.
- Data protection. Customer addresses and rider location history are personal data under the NDPA 2023; restrict access by role and set retention periods. Verify obligations with the NDPC or an adviser.
How to reduce the cost without a worse product
- Phase it. Launch with WhatsApp or web ordering plus a rider app and a web dispatch screen; add the customer app once volume justifies it.
- Status tracking before live maps. "Picked up, en route, delivered" with an ETA satisfies most customers at a fraction of the cost of a live map.
- Zone pricing before distance pricing. A table of zones and fees is cheap and predictable.
- Polling before websockets. Refreshing rider location every 30 seconds is far cheaper to build and run than a full real-time layer, and adequate for many operations.
- One city first. Multi-hub logic can wait until you have a second hub.
- Use a courier API instead of your own riders if delivery is not your core business; the guide to building a logistics app in Nigeria covers when to own the fleet.
- Web dashboard, not a third mobile app, for dispatchers and managers.
- Do not cut field testing, the rider app's offline behaviour or cash reconciliation. Those savings return as losses.
How to compare quotations
Send every vendor the same written scope and compare against this checklist before comparing totals. Quotation comparison checklist
- All three products named and priced: customer app (or web ordering), rider app, dispatch dashboard
- Live tracking specified (real-time or interval) and the location update frequency stated
- Maps provider named and estimated monthly usage cost stated
- Pricing engine scope: flat, zones, distance and time, surcharges editable by staff
- Payment methods listed, including cash on delivery and rider cash reconciliation if needed
- Proof of delivery method: photo, signature, OTP
- Automatic assignment logic described, or manual assignment stated
- Notifications: push, SMS, WhatsApp, and who pays per-message fees
- Field testing with real riders on entry-level Android phones included
- Store publishing for both apps under your own accounts
- Source code and account ownership in writing
- Warranty period and monthly maintenance rate
- Assumed exchange rate and date for USD items
- Milestone-based payment schedule
The guide to reviewing an app development proposal and the guide to what should be included in an app development contract cover the wider procurement steps.
Mistakes that inflate the bill
- Pricing "an app" and discovering the rider app and dashboard later. The most common overrun in delivery projects.
- Live tracking everywhere from day one. It raises build cost and monthly maps and hosting bills before volume exists.
- Ignoring cash on delivery in scope. Reconciliation gets built in a hurry after riders and cash go missing.
- Testing on Wi-Fi in the office. The rider app's real problems appear on the road, on cheap phones, with the screen off.
- Distance-based pricing with no manual override. Every fuel price change becomes a developer request.
- No offline queue in the rider app. Deliveries completed out of coverage are lost or duplicated.
- Skipping rider onboarding and deactivation tooling. Churn turns into a security problem.
- Not budgeting for maps usage. The monthly USD bill arrives after launch and surprises the finance team.
Conclusion
A delivery app in Nigeria costs what its three sides and its tracking model demand. Decide whether you are building your own delivery operation or a platform, choose interval tracking and zone pricing until volume justifies more, scope cash on delivery and rider onboarding properly, and budget for the metered running costs of maps, messaging and real-time hosting. Compare quotations only against a written scope that names all three products, and protect the field-testing line, because the rider app is where delivery businesses win or lose. If you want a realistic scope and indicative quote for a delivery app based on your fleet, cities and pricing model, Linestech builds customer, rider and dispatch systems for Nigerian delivery and logistics businesses and can review your requirements before you commit.
Frequently asked questions
Do I need a separate rider app?
Yes, if riders are doing more than receiving a WhatsApp message. Job acceptance, navigation, status updates, proof of delivery, earnings and an offline queue need a dedicated app built for entry-level Android phones. It can be very simple at first, but merging rider functions into the customer app produces a confusing product that neither audience likes.
How much does live tracking add to the cost?
Real-time tracking with a live map for customers and dispatch typically adds a meaningful share of the backend and rider app work, often several million naira on a standard build, plus higher monthly hosting and maps costs. Interval-based tracking (location every 30–60 seconds) delivers most of the operational benefit at far lower build and running cost.
Can the app handle cash on delivery?
Yes, but it must be scoped as a module: rider cash balance per shift, cash limits, daily settlement, discrepancies and reports. Many quotations treat cash as a payment option label and omit reconciliation, which is where losses occur. Ask specifically how rider cash is tracked and settled.
What does Google Maps cost for a delivery app?
Google Maps Platform bills per request across services such as address autocomplete, distance calculation and map loads, with monthly allowances; pricing changes, so verify the current schedule and estimate usage from your expected orders. Design choices such as caching distances for common zones and limiting continuous ETA refreshes keep the bill manageable.
Can I start with WhatsApp orders and only a rider app?
Yes, and for many restaurants, pharmacies and retailers it is the right first phase. A rider app with job list, navigation, status updates and proof of delivery, plus a simple web dispatch screen, indicatively sits at ₦3,000,000–₦6,000,000. Customer-facing ordering and tracking can be added on the same backend later.
Does building for more cities cost much more?
The technology cost rises moderately: city-specific zones, pricing, hubs and reporting, and intercity legs if you connect cities. The larger costs are operational, since each city needs riders, supervision and support. Build the first version with city as a configuration setting so expansion does not require re-engineering.
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.
