Serein.
← All articles

Restaurant Customer Database: What to Keep and How

Restaurant Customer Database: What to Keep and How

Restaurant host checking guest records before service

A restaurant customer database is the single record of who your guests are, how they book and what they like, built up from every reservation, walk-in and message. The best ones are small and accurate: a name, a way to reach the guest, a visit history and a few notes your team will use on the next visit. This guide covers what to store, where the data comes from, which Danish rules apply and how to turn it into better service.

Getsereingetserein.dkKeep Guest Records Ready for ServiceSerein stores guest contact details, visit history, tags and private notes, with data export and erasure for GDPR.Explore guest records

TL;DR

  • Start with identity (name, phone or email) and visit history. Add preferences over time, not all at once.
  • Your reservation system is the best source because every booking, whether online, by phone or walk-in, lands in one profile.
  • In Denmark, marketing to guests needs a legal basis. Consent must be voluntary, specific, informed and unambiguous, and asked separately from your privacy policy.
  • Keep notes factual and useful for service. Be careful with health or allergy details.
  • Measure it: how many first-time guests come back within three months is the number that tells you whether it works.

Table of Contents

What a restaurant guest database actually is

It is not a spreadsheet of email addresses for newsletters. It is a living guest record that answers three questions before the guest walks in: who is this, have they been here before, and is there anything we should know?

For a small restaurant, that can be the difference between greeting a regular by name and asking for a surname you have heard five times. For a manager, it is the difference between guessing who is arriving at 19:00 and knowing.

There is research behind the idea. A 2010 study of RFID-based restaurant systems found that integrating database technology allowed proactive, customer-centric service, which raised service quality and revenue. The technology in that study is dated, but the principle holds: when the system remembers, the staff can focus on the guest.

The database also helps behind the scenes. Sales and order patterns can guide staffing levels, food waste and operational efficiency, as long as the data is clean enough to trust.

What to store about each guest

The temptation is to collect everything. Resist it. One industry guide advises operators to establish identity first and enrich profiles over time, because collecting too much too early produces gaps, errors and guests who feel interrogated.

A practical structure has four layers:

Layer Examples Why it earns its place
Identity Name, phone, email, language Lets you confirm, remind and recognize the guest
Visit history Dates, party size, status (arrived, seated, completed, no-show) Shows who is a regular and who keeps missing bookings
Preferences Favorite table, seating requests, drinks, occasions Lets staff personalize without asking again
Consent and permissions Marketing consent, medium, date given Keeps you on the right side of the law

An affinect guide describes essential guest data in similar terms: identity, behavioral data such as visit frequency, transactional data such as spend, and preference information.

Danish restaurant groups publish their own policies, and they show what is typical. Sovino’s guest data policy lists name, email, phone number and booking history for bookings, plus language settings for app users. Streckers’ policy is broader and may include address, date of birth, purchase history and survey data. A single independent restaurant rarely needs that much. If you will never use a date of birth, do not ask for it.

Notes: useful, but handle with care

Private notes are where a guest database becomes personal: “prefers the window table”, “celebrating an anniversary”, “always arrives ten minutes late”. Keep them factual and professional, because a guest has the right to see what you hold about them.

Health information is a different matter. Sovino’s policy tells guests who want to share dietary restrictions, health information or accommodation needs to contact the restaurant directly, and notes can include seating requests. A sensible house rule: record what the kitchen and floor need to act on (“no nuts”) and nothing more. If you are unsure whether a note about a guest’s health is appropriate to store, ask your data protection adviser or check with the Danish Data Protection Authority, Datatilsynet.

Where the data comes from

Guests reach you through many doors, and each one should feed the same record. Danish policies list table bookings, event enquiries, website cookies and social media, and Sovino names bookings made online, by phone, in person, by email, social media or text message.

The usual touchpoints for an independent restaurant:

  • Online booking page. The cleanest source. The guest types their own details, so spelling errors are rare.
  • Phone bookings. Often the weakest link, because details are typed in a hurry or written in a notebook and never transferred.
  • Walk-ins. Easy to skip on a busy night. Capture at least a first name and, if the guest agrees, a phone number.
  • Email and social media enquiries. Event and group requests usually arrive here.
  • Newsletter sign-ups. Separate from bookings, and based on consent.

One industry guide on guest data sources lists reservation systems, online ordering, guest WiFi, point-of-sale and loyalty sign-ups, and argues that the strongest strategies treat these as one unified system rather than isolated tools. For a restaurant with ten to fifty tables, that means one rule: every reservation, however it arrives, ends up in the same guest profile. DataDelivers points to a common failure here: operators who lack a unique guest identifier across their tools end up relying on fragmented, misleading loyalty-only data.

How to build it, step by step

  1. Write down what you will use. For every field, name the moment on the floor or in the office when someone will use it. If you cannot, drop the field.
  2. Pick one home for the data. A reservation system with guest records is better than a notebook, a spreadsheet and a phone full of numbers. Two sources of truth means neither is true.
  3. Capture at the point of booking. Name, phone or email and party size are enough. Ask for the rest later, at the table, where a conversation beats a form.
  4. Tag consistently. Agree a short list of tags with the team (regular, birthday, allergy-aware, press) and stick to it. Fifty tags is the same as none.
  5. Record status honestly. Mark arrivals, no-shows and cancellations as they happen. This is the cheapest way to learn who is reliable.
  6. Clean it monthly. Merge duplicates, fix obvious typos, remove outdated entries.
  7. Train the team. People are the weak point. BDO’s guide for restaurants cites human error as a cause in 88% of modern data breaches, so staff training and clear privacy habits matter as much as the software.

The same guide warns that flawed data leads to poor decisions and urges operators to check incoming data for relevance, completeness, bias and timeliness. In practice: a guest marked “regular” because of one night three years ago is not a regular.

The rules in Denmark: consent, marketing and storage

A customer database holds personal data, so GDPR applies. The practical questions are what you can use the data for and how you ask.

Using data to run the booking

Taking a name and phone number to manage a reservation is part of delivering the service the guest asked for. Confirmations, reminders and a note about a seating request fall naturally under that. Sovino’s policy, for instance, lists booking confirmation, communication about a visit and accommodating requests as uses, and keeps newsletters on a separate consent basis.

Using data for marketing

Marketing is where restaurants slip. Datatilsynet’s guidance on direct marketing says a legal basis is required, and consent must be voluntary, specific, informed and unambiguous, with the request kept separate from the privacy policy. That means a pre-ticked box buried in your booking terms does not work.

The Danish Consumer Ombudsman adds rules for electronic marketing. Consent must name the medium, such as email or SMS, and the product categories, and vague wording like “etc.” does not stretch it. There is a narrow exception: marketing similar products to existing customers can be allowed without new consent if the statutory conditions are met. Check those conditions with the guidance, or an adviser, before relying on it.

A clean approach for a restaurant: a separate, unticked checkbox on the booking page (“Send me news and offers by email”), stored with the date. Reminders about the booking itself are service messages; the newsletter is marketing.

Using data for marketing — overview diagram

Collect little, protect it, delete it

Datatilsynet’s advice on restaurant guest registration during the pandemic is a good model for any collection of contact data: limit it to what is needed, state the purpose, protect it, use it only for that purpose and delete it when it is no longer relevant. That context was infection tracing, so do not copy its specifics, but the habits transfer.

In practice you need a way to export a guest’s data if they ask and a way to erase it. Check also that your software supplier is covered by a data processing agreement and that you can see who its subprocessors are. We publish ours: our data processing agreement, subprocessors and security overview are open for any restaurant to read before signing up. You can also see how guests are informed on our guest privacy page.

Turning records into better service

A database that nobody opens is just a liability. These are the uses that pay off quickly in a small restaurant.

Before service. Scan tonight’s arrivals. Who is a regular? Who has a note? Who has a history of no-shows? Ten minutes of this changes how the host plans the room. Our own thinking on this is in a calmer service starts before the first arrival.

Guest records supporting four stages of restaurant service

At the door. Greet by name. Seat the anniversary couple at the quiet table. Ask the regular whether they want the usual.

At the table. Staff who see a note do not need to ask the guest to repeat an allergy. That is both better hospitality and safer.

After the visit. A short thank-you or a feedback request, sent to guests who agreed to it, keeps the relationship warm. Guidance from Danish restaurant groups lists feedback after the visit among the purposes of guest data.

On the booking rules. If history shows repeated late cancellations, adjust your policy rather than blaming guests. We cover that in writing a booking policy that feels like a welcome.

On the floor plan. Knowing party sizes and habits helps you set tables sensibly, as in our piece on making your floor plan work.

Our view: the database should disappear into service

We built Serein around a simple belief: a guest record should be a by-product of running a good evening, not a second job. If your team has to stop and fill in a CRM form during a Friday rush, they will not do it, and the data will rot.

So we think the record should be built where the work happens. The booking comes in, the guest profile is created or updated. A walk-in is added in seconds. Status changes (arrived, seated, completed, no-show) are made as the evening unfolds, and the history writes itself. Notes are private to your team, and the guest can have their data exported or erased when they ask.

We also think restaurants should resist the pull to turn every guest into a marketing target. The most valuable thing a database does is let you be more attentive. The newsletter can wait until you have asked properly and been told yes.

— Safi

Measuring whether it works

Collecting data is not the goal; changing what you do is. Wonderful Copenhagen’s guide to data in the restaurant industry recommends measuring first-time guests, how many return within three months, purchase frequency, customer lifetime value, campaign effect and guest satisfaction. Its method is a loop: collect and organize, analyze, act, then repeat to check the effect.

For a small restaurant, start with three numbers:

  • Share of bookings from returning guests. Pull it monthly. A rising share means your hospitality is working.
  • Return within three months. Of the guests who came for the first time in a given month, how many came back?
  • No-show rate. If reminders and policy changes work, this falls.

Write the numbers down, change one thing (a reminder, a greeting routine, a booking rule), and look again next quarter. The same guide argues that data pays off when analyzed across sources, not just collected, so compare what the booking records say with what reviews and staff observations tell you.

Serein for restaurant guest records

Serein is web-based reservation and service-management software for independent restaurants, cafés and other table-service venues in Denmark and the EU. Online, phone and walk-in bookings all go into one service view, and each guest has a record with contact details, visit history, tags and private notes, with export and erasure for GDPR. The whole app and the guest booking page work in English and Danish, and guests never need an account.

Plans are billed per restaurant location, per month, with a 14-day free trial: Essential is €39 per month and Service is €69 per month. See the plans and pricing, or look around the live demo first. You can also read about how Serein works for different kinds of restaurants.

FAQ

Do I need guests’ consent to keep their details?

Not to manage their booking: you need the name and contact details to deliver the reservation. Consent comes in when you want to send marketing, and then it must be voluntary, specific, informed and unambiguous and asked separately. For borderline cases, ask a data protection adviser.

What is the minimum I should collect?

A name, one way to reach the guest and the party size are enough to run a booking. Add preferences and notes as you learn them. Collecting too much too early tends to produce incomplete, unreliable records.

Can I use a spreadsheet instead of software?

You can, and many restaurants start that way. The weak points are duplicate entries, no live status, no connection to your booking channels and harder handling of export and erasure requests. Once you take bookings by phone and online, a reservation system with guest records saves time and errors.

How long should I keep guest data?

Only as long as it is relevant to the purpose you stated. Datatilsynet’s guidance stresses deleting data when it is no longer relevant. Set a review rhythm and write your retention period in your privacy information.

Sources

Recommended

Made with BabyLoveGrowth tools