Restaurant customer database from bookings, orders and the till

Aug 22
4 min read

Updated: 4 days ago

Introduction

A restaurant sees the same faces every week and knows almost nothing about them. Meanwhile the delivery platform that takes a commission on each order knows exactly who they are.

The asymmetry is the problem. Building your own record of customers is what makes it possible to fill a quiet shift without paying someone else for access to your own diners.

1. A restaurant customer database is assembled from sources you already have

You do not need a new system. You need to consolidate what is already being collected in three or four places.

Online bookings hold names, contact details, party sizes and dates. Your own online ordering holds addresses and order history. A loyalty scheme holds frequency. Event and catering enquiries hold the highest-value contacts in the business.

Each of those already exists in isolation. The work is bringing them into one place with consistent fields.

2. Keep the fields that change what you would do

Restraint here is what keeps the record usable.

Name, one contact method, first visit date, last visit date, number of visits, average spend, and one notes field for anything genuinely useful — dietary requirements, usual order, a preferred table, that they come with children.

Add consent status and how it was obtained. Skip anything you would never act on; a database with twenty fields gets maintained for a month.

3. Own the delivery platform relationship where you can

The uncomfortable structural issue in this vertical.

Platforms generally do not hand over customer details, so delivery-only customers are not yours in any durable sense. The available responses are partial and worth doing anyway.

Include something in the packaging that invites direct ordering next time — a card with a code, a reason to come to your own site. It converts a modest percentage, and those customers arrive commission-free from then on.

4. Capture details at the door as well as online

In-person customers are the majority in most venues and the least recorded.

The realistic mechanisms: the loyalty signup, the wifi login, a card left with the bill, or simply asking when taking a phone booking and writing it down properly.

Phone bookings are the most commonly wasted opportunity. Someone gives you their name and number, it goes on a paper sheet, and it is discarded at the end of the week.

5. Record consent honestly and separately

Having someone's details because they booked a table is not permission to send them marketing.

Ask explicitly, once, with a clear statement of what you will send and how often. Record the date and the method. Keep the marketing list distinct from the operational booking records.

This is both a legal requirement in most places and a practical one — a list built on assumed consent produces complaints and unsubscribes that damage deliverability for everyone else.

6. Use it for the three things it is actually good at

A database earns its keep on a small number of uses.

Filling known quiet shifts, by messaging people who live nearby and have visited on weekdays. Winning back customers who have not been for noticeably longer than their own usual gap. And recognising regulars — the notes field is what lets staff greet someone properly and remember their order.

That third use is not measurable and is frequently the most valuable, because it is the reason people become regulars in the first place.

7. Keep it clean, or it decays into uselessness

Restaurant data degrades quickly: people move, numbers change, addresses are mistyped at a busy till.

Agree one identifier — usually a phone number — and merge duplicates against it. Standardise how sources are recorded so you can count them. Remove addresses that bounce repeatedly.

A quarterly tidy is enough, and it should be a named person's job. Without it you will have four records for your best customer and no idea they are your best customer.

8. Protect it, because it is customer data

The obligation that comes with holding this.

Keep it in a business-owned account rather than on a personal device, restrict access to the people who need it, and do not export copies to laptops and phones.

Know what you would do if it were lost or exposed, and delete what you no longer use. A restaurant customer list is exactly the kind of data people expect to be handled carefully, and the reputational cost of mishandling it in a local market is high.

Conclusion

Consolidate bookings, your own online orders, loyalty and enquiry records into one place with a small set of fields you would actually act on.

Convert delivery customers to direct ordering where you can, capture phone and in-person details properly, record consent separately and honestly, use it to fill quiet shifts, win back lapsed diners and recognise regulars, tidy it quarterly against one identifier, and hold it securely in a business-owned account.