How to Build a Customer Database
A useful customer database is not a large spreadsheet of every name, address and phone number the takeaway has ever received. It is a controlled record of people, orders, preferences and permissions that supports cust…

A useful customer database is not a large spreadsheet of every name, address and phone number the takeaway has ever received. It is a controlled record of people, orders, preferences and permissions that supports customer service, analysis and permitted marketing without losing track of where the information came from.
Step 1: define purposes before fields
| Purpose | Typical data | Important boundary |
|---|---|---|
| Fulfil an order | Name, contact, address, order and delivery notes | Do not treat fulfilment data as automatic marketing permission |
| Customer support | Complaint, remedy and communication record | Keep only what is needed to resolve and evidence the issue |
| Loyalty | Account ID, points or stamps, adjustments | Keep a reliable liability and correction trail |
| Analytics | Order, channel, location and timing data | Use appropriate aggregation and explain relevant tracking |
| Direct marketing | Channel preference, source, wording version and date | Apply PECR and UK GDPR rules; honour objection and withdrawal |
Related guides
- Restaurant Marketing and Customer Retention — the main guide for the wider topic.
- Customer Data and Database Management — the broader guide that frames this implementation.
- Customer Segmentation for Takeaways — a closely related operational control to review alongside this page.
- Customer Data Consent for Restaurant Marketing — a closely related operational control to review alongside this page.
Step 2: inventory every source
List the website, app, POS, marketplace, telephone-order tool, loyalty system, email provider, SMS provider and support inbox. For each source, record who controls it, which identifiers it uses, where data is hosted, what can be exported and what happens when the contract ends.
Do not import marketplace customer details into an owned marketing list simply because the data is visible in an order screen. Check the platform agreement and the purpose for which the information was supplied.

Step 3: choose a stable customer key
Email, phone number, address and payment token can all change or be shared. Use a system-generated customer ID where possible and record matching confidence rather than merging records automatically. Provide a way to correct a mistaken merge.
Step 4: store permission as evidence, not a single tick
- Channel: email, SMS, push or another route
- Status: permitted, suppressed, objected, withdrawn or unknown
- Source and date
- Exact or versioned wording shown
- Business and products or services covered
- Reason relied on, including any soft opt-in assessment
- Date and source of later change
A campaign export must apply the current suppression status at send time. A historical opt-in should not override a later objection.
Step 5: minimise and separate sensitive notes
Do not use free-text delivery notes as a marketing profile. Notes may contain access information, health-related details or other personal information that is irrelevant to segmentation. Define retention and access rules for customer-service notes separately from marketing fields.
Step 6: clean the database safely
- Remove obvious test and duplicate records without deleting valid evidence.
- Correct invalid contact formats and mark undeliverable destinations.
- Reconcile suppressions across email, SMS, app and CRM suppliers.
- Review records with unknown origin before marketing use.
- Delete or anonymise data when the retention purpose has ended, while keeping a minimal suppression record where needed to prevent re-contact.
Step 7: test access, export and exit
Use a sample record to test correction, marketing opt-out, subject-access search, deletion or restriction handling and supplier export. Confirm that account closure does not erase unresolved loyalty balances, refunds or legal records prematurely.
Database health measures
- Percentage of records with known provenance
- Suppression consistency across systems
- Duplicate and mistaken-merge rate
- Failed email and invalid-phone rate
- Time to locate and correct a customer's record
- Number of uncontrolled spreadsheets or agency exports
Practical next step: create a source register before importing anything new. Take ten customer records and trace each field back to its system and purpose. If provenance cannot be explained, quarantine the field from marketing use.
Sources and date checked
Guidance checked: 24 July 2026. Recheck official guidance and supplier rules before launch.
Operational, legal and platform requirements can change. Recheck official guidance and supplier documentation before altering a live service.
Related practical guides
Restaurant Marketing and Customer RetentionHow to Run a Direct-Ordering Promotion Without Training Customers to Wait for DiscountsA direct-ordering promotion should demonstrate the value of the owned channel, not redefine the normal price as the amount customers pay only bet…Read guide →
Restaurant Marketing and Customer RetentionHow to Prevent Discount AbuseDiscount abuse should be managed as a cost and control problem, not as a reason to treat every enthusiastic customer as dishonest. The objective …Read guide →
Restaurant Marketing and Customer RetentionHow to Measure Repeat Order RateRepeat-order rate is only meaningful when the customer identity, eligible population and observation period are stated. A percentage without thos…Read guide →
Restaurant Marketing and Customer RetentionEmail Deliverability and ComplianceDeliverability and compliance support each other: wanted, well-governed mail is more likely to reach customers and less likely to produce complai…Read guide →
Restaurant Marketing and Customer RetentionEmail Campaign Types for RestaurantsCampaign type should follow a customer need and an operationally valid reason to contact them. A weekly discount email is not a default requireme…Read guide →
Restaurant Marketing and Customer RetentionDealing with Fake or Unfair ReviewsA review can be inaccurate, abusive or unrelated to a genuine order without being easy to remove. The correct response is to preserve evidence, u…Read guide →Connect customer ordering with operations and profit
Use the wider guide library to check the menu, kitchen, fulfilment, payment and financial implications of each decision.
Browse all practical guides