How Nigerian Businesses Can Prepare for Mobile Commerce

Readiness is not a purchase. A business can own an attractive website, an Instagram following and a payment link and still be unprepared, because the orders arrive faster than the stock system, the delivery promises are informal, and nobody can say which products people look at and abandon.
What follows is a sequence rather than a wish list. Each step is scoped so that a small team can complete it, and each one is chosen because skipping it causes a specific, predictable failure later. If you want the market context first — the channels, the payment behaviours and the constraints — read Mobile Commerce in Nigeria alongside this.
What "ready for mobile commerce" actually means
Score your business honestly against the six readiness areas before deciding what to spend on. The lowest score is where your money should go first, regardless of which area is most interesting.
| Readiness area | Not ready | Partly ready | Ready |
|---|---|---|---|
| Technical | Site slow or not usable on a phone | Responsive but heavy | Fast on mobile data, secure, maintained |
| Product content | One photo, one-line description | Photos but no specifications | Photos, specifications, sizing, stock, delivery time |
| Payments | One method, manual confirmation | Card only | Card and transfer, auto-reconciled, failures handled |
| Delivery | Quoted informally in chat | Fees known internally | Published zones, fees and timelines you meet |
| Operations | Orders live in one person's phone | Spreadsheet, reactive | Defined order flow, stock accuracy, response targets |
| Data | No analytics, no customer list | Analytics installed, unused | Funnel tracked, customer database owned by the business |
A useful reframing: mobile commerce readiness is mostly operational readiness with a technical component, not a technical project with operational side effects.
Get the technical foundation right
Test on the devices your customers actually use
Borrow a mid-range Android phone, switch off Wi-Fi, and complete a purchase yourself. Time each page. Note every point where you hesitate. This single exercise usually produces a better task list than any audit tool.
Reduce page weight
Compress and resize every product image, remove unused plugins and third-party scripts, and avoid autoplay video. On a mobile-data connection, weight is the main determinant of whether a page is seen at all.
Fix the fundamentals
- HTTPS active, with no browser warning.
- Hosting appropriate to your traffic, with a plan for peak periods such as December.
- Tap targets large enough for a thumb, no horizontal scrolling, forms that fit a phone screen.
- No pop-up before the visitor has seen a product.
- Automatic backups running, with a restore that has actually been tested.
Decide what you are building on
If your current platform can support your catalogue, payment methods and delivery logic, improve it. Replace it only when it genuinely blocks those things. A migration undertaken for cosmetic reasons consumes the budget that content and payments needed.
Get product information and content ready
The mobile product page has to do the work a salesperson does in a shop. Prepare content in bulk before you touch design.
- Photograph every product properly. Three to five images: front, detail, in use or worn for scale, and one per colour variant. Consistent background, good light.
- Write real descriptions. Material, dimensions, capacity, what is included, warranty, care instructions, who it suits.
- Add sizing where relevant. Actual measurements, not just S/M/L.
- Standardise product names. One convention, applied across the catalogue, so search and reporting both work.
- State stock status accurately. Accepting orders for items you do not have creates refunds and complaints.
- Put delivery timing on the product page. By zone, in working days.
- Write the policies. Returns, refunds, exchanges, privacy. Plain language, published, linked in the footer.
- Prepare a short FAQ. Authenticity, sizing, delivery, payment methods and returns answer most pre-purchase messages.
Content preparation is the least glamorous step and usually the one with the largest effect on conversion, because it removes the reason customers stop to ask.
Get payments ready
Support the way your customers already pay, and make each route reconcilable without manual detective work.
- Open a business bank account and register the business. Payment providers require verified business details; Corporate Affairs Commission registration is normally a prerequisite rather than an afterthought.
- Set up a payment provider. Paystack, Flutterwave, Interswitch and similar providers handle cards, transfers and often USSD. Confirm current fees and settlement timelines directly with the provider.
- Enable dedicated virtual accounts for transfers. This is the single most valuable operational upgrade for Nigerian sellers, because each payment matches an order automatically.
- Handle failures explicitly. Show pending status honestly, keep the order recoverable, and give the buyer a route to complete payment.
- Decide your payment-on-delivery policy. If you offer it, define the area, the order-value limit and what happens on rejection. If you do not, say so on the product page.
- Send confirmations. Order number on screen plus a message the buyer can keep reduces "did it go through" traffic substantially.
- Reconcile daily. Match settlements to orders every day while volumes are small enough for the habit to form.
Get delivery and fulfilment ready
Mobile buyers decide on the basis of delivery information before they decide on price.
- Define zones. For example: within Lagos mainland, Lagos island, Abuja, other South-West states, other states. Assign a fee and a working-day range to each.
- Choose partners deliberately. Intra-city riders and courier firms such as GIG Logistics, Kwik or Sendbox suit different weights, distances and value profiles. Have a second option for peak periods.
- Solve addresses. Nigerian addresses often need landmarks and a phone number that will be answered. Capture both at checkout.
- Publish honest timelines. Under-promising and delivering early builds repeat custom; the reverse does the opposite.
- Decide packaging. Damage in transit is a recurring source of returns and refunds.
- Plan returns physically. Where do returned items go, who inspects them, how quickly is the refund processed?
- Agree tracking. Even a simple status the customer can check reduces support load.
Get your team and operations ready
Volume exposes whatever process you did not write down.
- Write the order flow. Order received, payment confirmed, stock allocated, packed, dispatched, delivered, closed. Assign a name to each step.
- Set response targets. Decide what "fast" means for WhatsApp and social messages during working hours and publish your hours.
- Move customer conversations to a business-owned number. Use the WhatsApp Business App or, where you need automation and multiple agents, the WhatsApp Business Platform. Conversations on a staff member's personal number leave when they do.
- Keep stock accurate. Whether in a spreadsheet or an inventory system, a single source of truth prevents overselling.
- Train for exceptions. Wrong item, part payment, customer unreachable, item out of stock after ordering. These are the cases that damage reputation.
- Plan for peaks. December, Black Friday-style promotions and viral posts create volume spikes. Know your capacity in orders per day and what you will do above it.
- Protect access. Store, payment, domain and social accounts registered to the business, with recovery on the owner's email and phone.
Get your customer data and measurement ready
- Install analytics and track the funnel. Sessions, product views, add to cart, checkout start, order complete. Without this you cannot tell a traffic problem from a checkout problem.
- Build a customer database you own. Name, phone, email where given, order history, delivery zone. Exported from your store or kept in a simple CRM. Followers are not a database.
- Capture consent properly. If you intend to send marketing messages, ask at the point of collection and keep the record. The Nigeria Data Protection Act 2023 applies to the personal data you are collecting; confirm current obligations with the Nigeria Data Protection Commission.
- Review a weekly number. Completed orders, average order value, delivery time and support response time are enough to begin with.
- Watch what customers search for. Terms that return no results tell you what to stock or what to rename.
A 90-day readiness plan
Indicative sequencing for a small team. Adjust to your starting point, and do not skip the measurement step in month one, because it tells you whether the rest worked.
| Period | Focus | Output |
|---|---|---|
| Weeks 1–2 | Diagnosis | Mobile audit on a real phone, analytics installed, baseline numbers recorded |
| Weeks 3–4 | Technical | Images compressed, scripts trimmed, HTTPS and backups confirmed |
| Weeks 5–6 | Content | Top 20 products fully documented with photos, specifications and sizing |
| Weeks 7–8 | Payments | Provider live, virtual accounts enabled, failure handling and confirmations tested |
| Weeks 9–10 | Delivery | Zones, fees and timelines published; partners confirmed; returns process written |
| Weeks 11–12 | Operations and data | Order flow documented, response targets set, customer database exported, weekly review started |
At the end of the quarter, compare completed orders and average order value with the baseline you recorded in week one. That comparison, not the appearance of the site, tells you whether you are ready.
Example (hypothetical): an Ibadan home goods business
Example (hypothetical): a home goods business in Ibadan sells cookware, storage and small appliances through Instagram and a WhatsApp catalogue, taking twenty to thirty orders a week. The owner wants to sell nationally and plans to commission an app.
A readiness review suggests the app is the wrong first purchase. The business has no product photographs at consistent quality, no written specifications, no delivery pricing beyond "we will check and tell you", and no record of which customers bought what. Two staff answer messages from their personal phones. Payments arrive as transfers to a business account, matched manually against a notebook.
The sequence that fits: photograph and document the fifty best-selling items; build a mobile-first store on a standard e-commerce platform; enable card and transfer payment with dedicated virtual accounts so reconciliation stops being manual; publish zone-based delivery fees covering Ibadan, Lagos, Abuja and other states; move conversations to one business WhatsApp number with a catalogue linked to the store; export the existing customer list into a simple database; and start a weekly review of orders, average order value and delivery time.
If, after two quarters, a meaningful share of customers are buying more than once a month, an app becomes a defensible next investment. Before that, it would be a more expensive way to reach the same customers.
What readiness costs
Indicative 2026 ranges; actual quotes vary with scope, catalogue size, vendor and exchange rate. Separate the one-off work from the recurring commitments, and compare two or three written quotations on identical scope.
| Readiness item | Indicative one-off | Indicative recurring |
|---|---|---|
| Mobile audit and analytics setup | ₦80,000–₦300,000 | — |
| Image compression and product content across a catalogue | ₦100,000–₦500,000 | — |
| Mobile-first business website | ₦150,000–₦2,500,000 | — |
| E-commerce store with payments and delivery logic | ₦400,000–₦3,500,000+ | — |
| Payment integration and virtual accounts | ₦150,000–₦600,000 | Provider transaction fees |
| Domain and hosting | — | ₦23,000–₦150,000 per year combined |
| Maintenance, updates and backups | — | ₦20,000–₦150,000 per month |
| WhatsApp Business Platform messaging | Setup within the build | Usage-based, priced in USD |
| Inventory or order management software | ₦0–₦2,000,000+ depending on build or subscription | Subscription where applicable |
A business with a working site and honest delivery can often complete meaningful readiness work for less than the cost of one month of moderate ad spend.
Mistakes to avoid while preparing
- Buying an app before the fundamentals work. An app amplifies whatever experience you already have, including a thin product page.
- Rebuilding the website when the problem is content. Diagnose before you commission.
- Launching promotions before delivery is ready. A successful campaign into an unprepared operation produces refunds and complaints that outlast the sales.
- Offering payment on delivery with no policy. Without an area limit, a value limit and a rejection process, it becomes an expensive default.
- Keeping customer conversations on personal phones. The relationship and the history leave with the staff member.
- Skipping the baseline. Without numbers from week one, you will argue about impressions rather than results.
- Ignoring consent. Bulk messaging people who never opted in produces blocks, complaints and avoidable exposure under the NDPA 2023.
- Treating readiness as a project with an end date. Catalogue, delivery and content need continuous maintenance, and the weekly review is where that happens.
Conclusion
Preparing for mobile commerce is a sequence, not a shopping list. Diagnose on a real phone, record a baseline, then fix the technical weight, complete the product content, add the payment methods your customers actually use, publish delivery terms you can keep, write down the order process, and build a customer database and a weekly number you review. Do those in order and the question of whether to build an app answers itself with data rather than ambition. Do them out of order and you will buy technology that sits on top of an operation that cannot use it.
If you want help turning a readiness gap into a working store, Linestech can audit your current mobile experience, implement the payment and delivery logic Nigerian buyers expect, and build the order and customer records your team needs as volume grows.
Frequently asked questions
How long does it take a small Nigerian business to get ready for mobile commerce?
A focused small team can complete the core work in about 90 days: diagnosis and measurement first, then technical fixes, product content, payments, delivery and operations. Businesses with a large catalogue or complex fulfilment take longer, mostly because of photography and product documentation rather than development time.
What should we do first if the budget is small?
Measurement and product content. Installing analytics costs little and tells you where buyers leave; compressing images and writing proper product descriptions costs time rather than money and usually produces the largest change in completed orders. Payment options come next, because each missing method excludes a group of buyers.
Do we need to stop selling on WhatsApp and Instagram?
No. Keep them, but connect them to something you own. Use them for discovery and conversation, link to product pages that carry full information, and make sure every order produces a record in your own database. The risk is not using these channels; it is having no asset outside them.
How do we handle customers who do not trust paying before delivery?
Offer an alternative with limits rather than either refusing or accepting everything. Common approaches include payment on delivery only within a defined area, only below a certain order value, or only after a first successful prepaid order. Publish the policy, and strengthen trust signals: registered business name, physical address, business account, clear returns policy and genuine reviews.
Is a mobile app part of readiness?
Rarely at the start. An app suits businesses with genuine repeat purchase, loyalty mechanics or an operational need such as driver or vendor tools. Preparing for mobile commerce means making the phone experience of your existing channels work; the app decision should be made later, using data from that experience.
How do we prepare for December and other peak periods?
Check hosting capacity, confirm stock levels and lead times with suppliers, agree extra delivery capacity with partners, set realistic delivery windows on the product page, prepare message templates for common questions, and decide the maximum orders per day you can fulfil properly. It is better to cap promotions than to take orders you cannot deliver.
What does a business need in place before a payment provider will approve it?
Requirements vary by provider, but typically a registered business, a business bank account, identity documents for directors or owners, and website details including your policies. Confirm the current requirements directly with the provider before you plan a launch date around them.
How do we know when we are actually ready?
Place a complete test order yourself from a phone on mobile data, as a stranger would: find a product through search or a link, read enough to decide, pay by both card and transfer, receive a confirmation, receive a delivery within the window you published, and then find that order in your own records. If every step works without a staff member intervening, you are ready.
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.


