Skip to content
Mobile Appfor Takeaways Start here
Restaurant Marketing and Customer Retention

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…

3 min readPublished 31 Oct 2026UK-focused practical guide
A dessert and coffee loyalty app in a cafe

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

PurposeTypical dataImportant boundary
Fulfil an orderName, contact, address, order and delivery notesDo not treat fulfilment data as automatic marketing permission
Customer supportComplaint, remedy and communication recordKeep only what is needed to resolve and evidence the issue
LoyaltyAccount ID, points or stamps, adjustmentsKeep a reliable liability and correction trail
AnalyticsOrder, channel, location and timing dataUse appropriate aggregation and explain relevant tracking
Direct marketingChannel preference, source, wording version and dateApply PECR and UK GDPR rules; honour objection and withdrawal

Related guides

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.

A dessert and coffee loyalty app in a cafe
Practical takeaway systems work best when ordering, kitchen operations and customer communication stay connected.

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

  1. Remove obvious test and duplicate records without deleting valid evidence.
  2. Correct invalid contact formats and mark undeliverable destinations.
  3. Reconcile suppressions across email, SMS, app and CRM suppliers.
  4. Review records with unknown origin before marketing use.
  5. 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.

Editorial note

Operational, legal and platform requirements can change. Recheck official guidance and supplier documentation before altering a live service.

Continue reading

Related practical guides

Build the complete picture

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
A mobile takeaway menu surrounded by freshly prepared food