How to Build a Customer Database for an Online Business
Most Nigerian online businesses can name last month's revenue but cannot name their twenty best customers. The orders happened; the memory of who placed them is scattered across a WhatsApp thread, an Instagram inbox, a delivery note and a bank statement. That scatter is the single biggest constraint on repeat sales, because you cannot sell again to someone you cannot find.
A customer database fixes it. It is less technical than it sounds and more valuable than almost anything else a small online business can build.
What a customer database is, and why it is your most valuable asset
A customer database is one structured record per customer, holding who they are, how to reach them, what they have bought, and what they have told you. It is not a marketing list and not a pile of phone contacts. The difference is structure and history.
What it makes possible:
- Selling again to people who already trust you, which costs far less than finding new buyers
- Identifying your best customers, so service and offers can reflect their value
- Noticing when a regular goes quiet, while there is still time to act
- Answering "have they ordered before?" instantly, which changes how customers are treated
- Running meaningful offers to a defined group rather than broadcasting to everyone
- Surviving the loss of an Instagram account, a phone or a WhatsApp number
- Proving to a partner, distributor or lender that you have a real customer base
What it is not: a reason to hoard data. Collecting information you never use creates work, risk and a compliance burden without value.
What to record: the minimum useful fields
Start small. Every extra field is a field someone must fill in and keep accurate.
Essential
- Phone number, in a consistent format, as the primary identifier
- Name, as the customer gives it
- Delivery city or area, plus a landmark
- Channel of first contact: Instagram, WhatsApp, website, referral, walk-in
- Order history: date, items, quantity, amount in naira, payment method
- Order status and delivery outcome
- Consent flag for marketing, with the date and how it was obtained
Useful once you are running well
- Email address, where the customer provides one
- Preferences: sizes, flavours, colours, preferred delivery day
- Notes: allergies, gate code, "always orders for her office"
- Tags: wholesale, corporate, VIP, first-time, problem delivery
- Source of acquisition: which campaign or referrer
- Complaint history and resolution
Avoid unless you genuinely need it
- Date of birth, unless you run birthday offers and will honour them
- Full residential details beyond what delivery requires
- Anything financial beyond payment method and amounts
- Card details, always and without exception. Your payment gateway stores those, not you
Where to capture data across every channel
| Channel | What to capture | How |
|---|---|---|
| Website checkout | Name, phone, delivery address, items, amount, consent tick | Automatically; the order record is the customer record |
| Website enquiry form | Name, phone, what they asked about | Form fields kept to three or four |
| WhatsApp orders | Name, phone, area, items, amount | Staff log it after confirming payment, or a CRM logs it automatically |
| Instagram DMs | Phone and name at the point of quoting | Ask for the number to send a payment link |
| Phone calls | Name, phone, what they wanted | A shared form or sheet at the point of the call |
| Walk-ins or events | Name, phone, what they bought | A simple form on a tablet or a short paper slip entered later |
| Delivery notes | Confirmed address and landmark | Feed corrections back into the record |
| Marketplace sales | Whatever the marketplace releases to you | Often limited; treat marketplace buyers as partially owned |
The principle: the capture must happen where the order happens, as part of confirming the order, not as a separate task someone does later. Tasks done later do not get done.
Where to store it: four options from spreadsheet to custom
| Option | What it is | Good for | Watch out for |
|---|---|---|---|
| Structured spreadsheet | One row per customer, one sheet for orders, shared online | Under a few hundred customers, one or two staff | Breaks with several editors; no reminders; easy to corrupt or leak |
| Online store customer records | The customer and order data your store platform already holds | Businesses selling mainly through their own website | Chat and Instagram orders are missing unless entered manually |
| CRM or WhatsApp-linked CRM | A customer system with tags, notes, reminders and conversation history | Businesses whose orders arrive across several channels | Subscription costs, often in US dollars; import and export quality varies |
| Custom customer system | Software built around your process, integrating store, WhatsApp and payments | Multi-channel sellers, subscription models, wholesale with statements | Higher upfront cost; you fund hosting and maintenance |
The honest sequence for most Nigerian online businesses: spreadsheet, then store records plus disciplined manual entry for chat orders, then a CRM linked to WhatsApp, then custom software only if the business has a genuinely unusual workflow. Export your data at every transition, and never choose a tool you cannot export from.
Keeping it clean: deduplication and phone formats
A database full of duplicates and broken numbers is worse than none, because reports mislead and messages fail.
- Standardise phone numbers on entry. Pick one format and enforce it, converting 0803… and +234803… to the same stored value. Strip spaces and dashes.
- Use the phone number as the key. Names are spelled differently, abbreviated and shared. Numbers are not.
- Deduplicate monthly. Sort by number, merge records, keep the fullest history.
- Validate at the point of entry. Reject numbers with the wrong length, and confirm the number back to the customer in the order confirmation.
- Handle multiple numbers. A customer may order from one number and receive delivery on another. Keep a secondary number field rather than creating a second record.
- Correct addresses after delivery. Riders learn the real landmark; that knowledge belongs in the record.
- Archive, do not delete, inactive customers, unless they ask to be removed, in which case honour it.
- Back up regularly, with a copy outside the primary system, stored securely.
Set a monthly thirty-minute cleaning routine and assign it to a named person. Databases degrade quietly.
Segmentation: four groups that pay for themselves
You do not need sophisticated segmentation. Four groups cover most of the value:
- First-time buyers. Follow up after delivery, ask how it went, and offer a reason to return within a sensible window.
- Repeat customers. Your most valuable group. Recognise them, tell them about new stock first, and never make them queue behind a stranger.
- Lapsed customers. Anyone who has not bought in a period that is long for your category: 45 days for food, 6 months for furniture. A single well-timed message to this group is usually the highest-return activity available.
- Enquired but never bought. Record the objection. A restock, a bundle or a direct answer converts a meaningful share of them.
Two optional extras once these work: wholesale or corporate accounts, who need statements and different terms, and high-value customers, typically your top ten or twenty by lifetime spend, who deserve a personal relationship rather than a campaign.
Consent, privacy and the NDPA 2023
Customer names, phone numbers, addresses and purchase histories are personal data under the Nigeria Data Protection Act 2023, which is overseen by the Nigeria Data Protection Commission. Practical, non-legal guidance:
- Have a lawful basis. Fulfilling an order justifies collecting delivery details. Marketing messages generally require consent.
- Ask clearly and record it. A tick box at checkout or a plain question in chat, with the date and wording stored against the customer.
- Separate transactional from marketing messages. Order confirmations and delivery updates are part of the service; promotional broadcasts are not.
- Honour opt-outs immediately, and make opting out easy.
- Collect only what you use. Minimisation is both good practice and less work.
- Restrict access. Not every staff member needs export rights; departing staff should lose access on the day they leave.
- Secure the storage. Strong passwords, two-factor authentication, restricted admin accounts, encrypted backups.
- Never sell or swap customer lists. It breaches trust and creates compliance exposure.
- Publish a privacy notice on your website explaining what you collect, why, and how long you keep it.
Obligations vary with the scale and nature of your processing, and registration requirements apply to some organisations. Verify your position with current NDPC guidance or a qualified professional. This is a description of the issue, not legal advice.
What changes for Nigerian businesses
Phone number is identity, not email. Build around it. Many customers will never give an email address, and those who do may not read it.
Orders arrive from several channels at once. Instagram DMs, WhatsApp, the website, phone calls and walk-ins all produce customers. A database that only captures website orders will hold a fraction of your business.
WhatsApp is the follow-up channel. Messages there get read. That makes consent and restraint more important, not less, because a blocked number is hard to undo.
Staff turnover moves customer knowledge. When the person who "knows the customers" leaves, an undocumented business loses its memory. Records in a system, not in a handset, protect against this.
Delivery data is customer data. Landmarks, gate instructions and preferred delivery times reduce failed deliveries, which are a real cost in Lagos and other large cities.
Platform risk makes ownership urgent. A restricted Instagram account or a lost SIM removes your access to customers unless you hold the list elsewhere.
Tools priced in dollars need a buffer. CRM subscriptions billed in US dollars move with the exchange rate. Model a weaker naira before committing.
Example (hypothetical): an online bookshop in Abuja
Example (hypothetical): An online bookshop in Abuja sells through a small website and Instagram, roughly 150 orders a month averaging ₦12,000. Website orders hold customer details; Instagram and WhatsApp orders are recorded on delivery notes and in chat. School and library orders arrive by email. Nobody can say how many customers have bought more than once.
What it builds. All customers move into the website platform's customer records, since that is where half the data already lives. Chat orders are entered by the person who confirms payment, using a short form with five fields: number, name, area, items, amount. Phone numbers are standardised. A monthly export feeds a spreadsheet where duplicates are merged and four segments are tagged. School and library buyers get a wholesale tag with contact person and delivery terms.
What changes (illustrative, not a claim). Within a quarter the shop can see that a meaningful group of customers buy two or three times a year, which justifies a termly message about new arrivals in their category. Lapsed buyers from the previous school session become a list worth messaging before the next one. Schools that ordered once are followed up before the term rather than after. None of this required new software beyond what the website already provided; it required a five-field entry habit and a monthly clean.
Build it in ten steps
- Define the minimum fields. Phone, name, area, channel, orders, consent. Nothing else at first.
- Choose one storage location. Whichever you pick, it must export cleanly.
- Import what exists. Website orders, delivery notes, phone contacts, past invoices, chat threads.
- Standardise phone numbers across everything you imported.
- Deduplicate by number and merge histories.
- Set the capture rule: no order is confirmed until the customer record is created or updated. Write it where staff can see it.
- Add consent capture to your checkout and to the chat script, and record it against the customer.
- Tag the four segments and set a schedule for each: post-delivery follow-up, repeat recognition, lapsed outreach, enquiry recovery.
- Assign a monthly clean to a named person: duplicates, failed numbers, address corrections, segment refresh.
- Back up and export monthly, storing a secure copy outside the primary system.
Expect a week to set up and a quarter before the data is complete enough to reveal patterns.
What it costs (indicative)
All figures are indicative 2026 ranges; actual costs vary with vendor, scope and exchange rate. Compare two or three written quotations on identical scope.
| Option | Indicative one-off | Indicative recurring |
|---|---|---|
| Structured spreadsheet | Your time, plus ₦50,000–₦200,000 if someone sets it up and enters historical data | Low-cost office suite subscription |
| Store platform customer records | Included with an existing store; ₦400,000–₦3,500,000+ if you are building the store itself | Hosting and platform fees |
| CRM subscription | ₦50,000–₦300,000 for setup, import and training if outsourced | Often US$20–US$100+ per month equivalent, billed per user |
| WhatsApp-linked CRM | ₦100,000–₦500,000 setup including template approval | Subscription plus WhatsApp Business Platform message fees in US dollars |
| Custom customer system | ₦2,000,000–₦30,000,000+ depending on modules | Hosting ₦150,000–₦800,000+ per year; maintenance often 15–25% of build cost yearly |
For most online businesses under a few thousand customers, the right answer is the first or second row plus discipline. Custom software is justified by unusual workflow, multiple branches or integration needs, not by customer count alone.
Mistakes to avoid
- Keeping customers only in a phone's contacts. Reason: no history, no segments, and one lost device erases the asset.
- Collecting fields nobody uses. Reason: long forms slow orders, and unused data is pure risk.
- Letting staff decide when to log a customer. Reason: inconsistent records make every report untrustworthy.
- Storing card details. Reason: it is unnecessary, since your gateway handles it, and it creates serious exposure.
- Marketing without consent. Reason: customers block the number and it breaches the expectations set by the NDPA 2023.
- Ignoring duplicates. Reason: a customer split across three records looks like three one-time buyers, hiding your best relationships.
- Choosing a tool you cannot export from. Reason: the database is the asset; if you cannot take it with you, you do not own it.
- Broadcasting the same message to everyone. Reason: irrelevant messages train customers to ignore you, which spends trust you will want later.
- Leaving the list unused. Reason: a database that is never messaged, segmented or reviewed is an expense rather than an asset.
Conclusion
A customer database is the difference between an online business that starts from zero every month and one that compounds. Keep the fields few and the capture automatic, key everything on a standardised phone number, store it somewhere you can export from, clean it monthly, and segment into four groups you actually act on. Treat consent seriously under the Nigeria Data Protection Act 2023, both because it is required and because a customer who trusts your messages is worth more than one who mutes them. Start this week with a spreadsheet if that is what you have; the value comes from the habit of recording every order, not from the sophistication of the tool.
If your customers are scattered across chat threads, delivery notes and an Instagram inbox, Linestech can consolidate them into a customer system linked to your website, WhatsApp and payments, so every order adds to an asset you own.
Frequently asked questions
Can I start with a spreadsheet?
Yes, and many successful businesses do. A shared sheet with one row per customer, standardised phone numbers and a linked order sheet works up to a few hundred customers and one or two people. Move on when several staff need to edit at once, when you need reminders, or when finding a customer takes more than a few seconds.
What is the single most important field?
The phone number, stored in a consistent format. It is the identifier Nigerian customers actually have, the way you will reach them, and the key that lets you merge records from Instagram, WhatsApp, the website and walk-ins into one customer.
Do I need consent to message customers about their order?
Order confirmations, payment receipts and delivery updates are part of fulfilling the transaction and are normally expected. Promotional broadcasts are different and generally require consent. Keep the two separate, record when and how consent was given, and honour opt-outs promptly. Verify your position with current NDPC guidance.
How do I get customer details from Instagram orders?
Ask for the phone number at the point of quoting, because you need it to send the payment link and arrange delivery. Log it as part of confirming the order rather than afterwards. Moving the conversation to WhatsApp also gives you a contact you can reach again, with consent.
How often should I clean the database?
Monthly, as a scheduled thirty-minute task owned by one person: merge duplicates, fix broken numbers, apply address corrections from delivery feedback, and refresh segment tags. Quarterly is acceptable for very low volumes; annual cleaning means the data will already be misleading.
What should I do if a customer asks me to delete their data?
Honour the request for marketing purposes immediately and remove them from all promotional lists. You may need to retain transaction records for accounting and tax purposes, so explain clearly what is being removed and what is retained and why. Confirm your obligations with current NDPC guidance or a qualified professional.
Is a CRM worth it for a small online business?
It becomes worth it when orders arrive across several channels, when more than one person handles customers, or when you want reminders and conversation history rather than a static list. Below that, a well-kept spreadsheet or your store's own customer records will do the job for a fraction of the cost.
How do I use the database to increase sales?
Start with lapsed customers, since they already trust you: one relevant message to people who have not bought in a while usually produces the best return available. Then recognise repeat buyers with early access rather than discounts, follow up first-time buyers after delivery, and revisit enquiries that never converted with an answer to their original objection.
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.
