# Building an E-Commerce Platform for the Nigerian Market: Logistics, Payments, and Trust
TL;DR: Winning ecommerce in Nigeria isn't a UI problem — it's a logistics, payments-redundancy, and trust-engineering problem, and your platform architecture has to be built around all three from day one.
Nigeria's online retail market is already worth an estimated $9–9.5 billion in 2025, and forecasts put it above $16–18 billion by 2030–2031 at a compound growth rate north of 12% a year (Mordor Intelligence, Research and Markets). WorldPay projects that by 2026, roughly 13% of Nigeria's total retail sales will happen online, with mobile devices driving 77% of that shopping activity and smartphones already accounting for over 82% of transactions. That's a large, mobile-first, fast-growing market — and also one where the standard Shopify-clone playbook from the US or Europe breaks in predictable ways.
Having built commerce and logistics-adjacent software for clients operating across Nigeria and neighboring markets, we've found the technical decisions that actually determine whether a Nigerian ecommerce platform succeeds cluster into three areas: how you handle money, how you handle delivery, and how you convince a first-time buyer to trust a screen. This post walks through each.
1. Payments: design for redundancy, not for a single "best" gateway
Unlike markets where one or two processors dominate, Nigerian ecommerce runs on a handful of genuinely strong, competing payment rails, and building your checkout around just one is a reliability mistake, not just a business one.
- Paystack — acquired by Stripe in 2020, used by over 60,000 Nigerian businesses including Domino's and Bolt, and generally the strongest default for developer experience and card/bank-transfer success rates (BNO News).
- Flutterwave — pan-African reach across 30+ countries, powers Uber and PiggyVest locally, and is the natural choice if the platform needs to expand beyond Nigeria into Ghana, Kenya, or francophone West Africa.
- Interswitch — the incumbent, running since 2002, still critical for card-scheme processing, bank integrations, and government/utility-adjacent payment flows.
The pattern we implement for clients is a payment orchestration layer: an abstraction inside the checkout service that can route a transaction to a primary processor and automatically fail over to a secondary one if the first times out or declines — which happens more often here than in mature markets, given intermittent bank connectivity and NIBSS switch congestion at peak periods. This is exactly the kind of integration-heavy, non-templated backend work that off-the-shelf ecommerce platforms handle poorly, and where a custom software build earns its cost back quickly — you're not fighting a plugin's assumptions about a single gateway.
Two other payment realities to design for:
- Bank transfer and USSD are not edge cases. A large share of Nigerian shoppers still prefer paying via bank transfer or USSD codes over card entry, partly from card fraud caution, partly from lower card penetration outside major cities. Your checkout flow needs first-class support for transfer-and-confirm flows, not just a card form with a transfer option buried in a dropdown.
- KYC is now a real, regulated cost. Under CBN's tiered KYC framework, wallets and higher-limit accounts require both BVN (Bank Verification Number) and NIN (National Identification Number) verification via NIBSS/NIMC, with a March 2026 circular introducing baseline standards for automated AML/KYC systems for fintechs, PSPs, and mobile money operators (compliance deadline March 2028) (Techpoint Africa, Dojah). If your platform holds a wallet, processes marketplace payouts to sellers, or offers buy-now-pay-later, this isn't optional middleware — it needs to be part of the initial data model.
2. Logistics: cash-on-delivery, addressing, and the last mile
This is where most imported ecommerce templates fail outright.
Cash-on-delivery (COD) still dominates. Across Sub-Saharan Africa, COD accounts for an estimated 60–85% of ecommerce transactions (eTrade for All), and Nigeria is no exception — trust in prepaying an unfamiliar online seller is still low enough that COD is the conversion-maximizing default, not a fallback option. That has direct architectural consequences:
- Order state machines need a distinct "payment pending — collect on delivery" status, separate from paid/unpaid, with reconciliation workflows for riders who are carrying and remitting physical cash.
- Failed-delivery handling matters more than in prepaid markets: a customer not being home when COD is the payment method means the delivery and the payment both fail, so retry logic needs to trigger both a redelivery attempt and a payment reminder.
- Increasingly, platforms convert COD into an electronic settlement at the door — the rider or agent takes a card tap, transfer confirmation, or QR payment instead of cash — which reduces fraud and rider safety risk (cash-carrying riders are a real robbery target) and speeds up merchant cash cycles.
Addressing is a genuine technical problem, not a data-entry nuisance. Nigeria doesn't have the kind of ubiquitous, standardized street addressing that most Western ecommerce platforms assume — NIPOST's own national addressing standard has existed since 2017, but coverage and adoption outside commercial districts is inconsistent, and locating a residential address in Lagos frequently still involves phone calls and landmark descriptions rather than a clean geocode (Quartz Africa). NIPOST has partnered with what3words to try to close this gap. In practice, this means your platform's checkout should:
- Capture a landmark/description field alongside the structured address, not instead of it.
- Support pin-drop map selection (Google Maps or what3words) rather than relying purely on free-text address parsing.
- Store delivery notes per-order, not just per-customer, since "nearest landmark" guidance often changes trip to trip.
Courier integration should be multi-carrier from the start. Firms like GIG Logistics (aiming for coverage across all 36 states plus the FCT) anchor last-mile delivery in the major cities, but coverage, pricing, and reliability vary sharply by state and by whether the destination is urban or peri-urban. A resilient platform integrates a courier abstraction layer — similar in spirit to the payment orchestration layer — so operations can shift volume between GIG, Kwik, or a regional courier by lane, rather than being locked into a single carrier's API and coverage map.
3. Trust: the layer that decides whether checkout happens at all
Payments and logistics get you to a working system. Trust is what gets a first-time visitor to actually click "pay." Surveys of Nigerian online shoppers consistently cite fear of non-delivery, receiving substandard or counterfeit goods, and general unfamiliarity with the seller as the top reasons for cart abandonment — not price, not UX friction.
Concrete platform features that move the needle:
| Trust mechanism | What it addresses |
|---|---|
| Verified seller badges / business registration display (CAC number) | "Is this a real business?" |
| Delivery tracking with rider photo + live status | "Will my order actually arrive?" |
| Return/refund policy enforced in-platform, not just written in a footer | "What happens if it's wrong?" |
| Review system with photo proof and verified-purchase tags | "Can I trust the reviews?" |
| Visible NDPA-compliant privacy notice and data handling | "What happens to my BVN/NIN/card data?" |
On that last point: Nigeria's Data Protection Act (NDPA) 2023, now backed by the General Application and Implementation Directive (GAID) issued in March 2025, is actively enforced — the Nigeria Data Protection Commission issued compliance notices to over 1,300 organizations in August 2025 alone, and Multichoice Nigeria was fined ₦766.2 million for data privacy violations in July 2025 (DLA Piper, Templars). Any platform storing customer PII, payment identifiers, or delivery addresses needs a real data map, a documented retention policy, and a 72-hour breach notification process — this is now a compliance requirement with financial teeth, not boilerplate legal text.
Putting it together: what the architecture actually looks like
A production-grade Nigerian ecommerce platform typically needs:
1. A checkout service with orchestrated multi-gateway payment routing (Paystack primary, Flutterwave or Interswitch as failover) plus a first-class COD/pay-on-delivery order state.
2. A fulfillment service with a multi-carrier abstraction, landmark-aware address capture, and rider-level delivery confirmation (photo, signature, or OTP-on-delivery).
3. A trust and compliance layer: seller verification, review moderation, and NDPA-aligned data handling baked into the schema, not bolted on later.
4. Offline-tolerant UX — given inconsistent mobile data quality outside major cities, checkout and order-tracking flows should degrade gracefully on slow or intermittent connections rather than failing outright.
None of this is exotic engineering, but almost none of it comes for free out of a generic ecommerce template, which is why most serious Nigerian ecommerce plays — from established players down to ambitious SME platforms — end up investing in custom-built commerce backends rather than stretching an off-the-shelf storefront past its design assumptions.
FAQ
Do I need both Paystack and Flutterwave, or is one enough?
One is enough to launch, but running a primary/failover pair materially improves checkout success rates, since bank-side outages and NIBSS switch congestion affect processors unevenly at peak times. Most serious platforms add a second gateway within their first year.
Is cash-on-delivery worth supporting given the operational overhead?
Yes, for most consumer categories. COD represents the majority of transactions across the region, and removing it typically costs more in lost conversion than it saves in reconciliation effort — though converting COD to an electronic tap-to-pay at the door captures most of the fraud-reduction benefit without losing the conversion.
How do we handle addresses without a standardized postal system?
Combine structured address fields with a mandatory landmark/description field and a map pin-drop (Google Maps or what3words). Store delivery notes per order rather than assuming a customer's address is static or unambiguous.
What's the single biggest technical mistake companies make building for this market?
Treating it as a UI/localization exercise — translating currency and adding a Nigerian flag to a template built for prepaid-card, standardized-address markets — instead of redesigning the payment state machine, fulfillment workflow, and trust surface around how Nigerian shoppers actually buy.
Sources
- Nigeria E-commerce Market Share, Size & Overview – Mordor Intelligence
- Nigeria E-commerce Market Share Analysis – Research and Markets
- Best Payment Gateways for Businesses in Nigeria in 2025 – BNO News
- CBN Fintech Regulations 2026: Licensing & Compliance Guide – Techpoint Africa
- CBN KYC Requirements for Fintechs in 2026 – Dojah
- Logistics Update Africa: Getting Past the Hurdles to the Last Mile – eTrade for All
- How Better Digital Mapping Will Boost Nigeria's E-commerce – Quartz Africa
- Nigeria: NDPC Issues GAID – Key Compliance Insights – DLA Piper Privacy Matters
- NDPC Issues the NDPA General Application and Implementation Directive 2025 – Templars
- GIG Logistics – Last-Mile Delivery