How to build a restaurant customer database from your orders

What a restaurant customer database holds

A customer database for a restaurant is a list of guests with one record each. The record answers three questions: who they are, whether you may contact them, and what they order. A spreadsheet of email addresses answers the first. The other two are what make a winback possible, and they come only from orders. The fields below are the ones Appetier's guest groups read, so each one has a job.

• Name, email, and phone. One of the last two is enough to start a record.
• Permission, kept per channel. A guest who ticked the box for email has not agreed to texts, and the record keeps the two apart.
• First order date and last order date. Every group below is a rule on these two.
• Order count, lifetime spend, and average order. Together they separate a regular from a one-time guest.
• Favorites and reorders, from what they put in the cart, not from a survey.
• Diets, dislikes, and allergies the guest saved, so a message never offers a dish they can't eat.
• A birth date, only when the guest gave one. The birthday note skips everyone else.
• The location they order from most, so a two-location group can message each neighborhood on its own.

Where the records come from

Your own checkout is the source. A guest who signs in with the email link Appetier sends gets a record, and every order after that updates it. Marketplaces work differently, by design. DoorDash, Uber Eats, and Grubhub bring you new guests and handle the delivery, and the guest stays inside their app. A marketplace order gives the kitchen what it needs to cook and nothing for your list. Keep the marketplaces for the guests who found you there. Give regulars a direct way to reorder, and the list builds itself from them.

• Checkout on your site and in your apps. Sign-in is a link by email, good for 30 days at one brand, and a signed-in guest reorders from their last 50 orders.
• Loyalty signup. A reward waiting at checkout is the reason most guests hand over an email.
• Reservations and the waitlist. A booking on your own site starts a record before the first order.
• Order updates. Guests who opt in to texts get order updates by text, and that opt-in is stored on the record.
• The console. Staff can add a follow-up date, a VIP flag, and a note from a phone call, and every device sees it.

The guest groups worth having, with the rules

A database earns its keep when it sorts itself. Appetier ships ten groups, each a rule on the fields above. Every new order moves guests between them. The numbers here are the product defaults, and an owner can change any of them. Read them as a starting point that one location can run without a marketing hire.

• New: no past orders yet. The first-order follow-up goes here.
• Returning: at least one order, and the last one within 60 days.
• Recent 7 days: ordered in the last week.
• Frequent 30 days: four or more orders in the last 30 days.
• Winback 30 days: at least one order, and none in the last 30 days. The winback campaign reads this group.
• At risk: last order 30 to 59 days ago. Still reachable with a small nudge.
• Lapsed: last order 60 or more days ago. The lapsed-guest campaign reads this one.
• VIP: five or more orders, $500 or more in lifetime spend, and an average order of $25 or more.
• High spend: two or more orders and $1,000 or more in lifetime spend.
• Big ticket: two or more orders with an average over $40. Loyal 6+ months: six or more orders and 180 days on the list.

Step 1: let guests sign in at checkout

Nothing gets recorded for a guest who checks out as a stranger. The email link is the lowest friction sign-in there is: no password, no app download. Once a guest is signed in, favorites, reorders, and loyalty points give them a reason to stay signed in. Check the storefront on your own phone. If a returning guest can't reorder in a tap, the sign-in isn't earning its place.

• Turn on guest sign-in and loyalty before the first campaign. A list of 40 guests can't be segmented.
• Put the reward where the guest sees it: at checkout, before they pay.
• Leave allergy notes on. A guest who saves an allergy has to accept your allergy notice first, and that record protects both of you.

Step 2: ask for permission, one channel at a time

Permission is the field that decides whether the list is an asset or a liability. Ask for email and text separately, and store the answer per channel. Appetier only sends marketing texts to guests who ticked the box, and every marketing email carries a one-click unsubscribe. A guest who opts out stays out, on every send after that.

• Texts go out between 9 a.m. and 8 p.m., and at most one a day per guest.
• Marketing email leaves from your own domain once it's connected. Until then it comes from Appetier's address.
• A brand with too many bounces or complaints pauses its email until the list is cleaned. Ask for permission the honest way, and that never happens.

Step 3: set the limits before anything sends

Sous is Appetier's AI agent, and it runs four campaigns from this database: the 30-day winback, the lapsed-guest nudge, the first-order follow-up, and the birthday note. Before the first one goes, you set what it may offer. Set the largest discount, the most messages any guest gets in a window, quiet hours, and which channels it may use. Every send is checked against those limits twice, once when it's planned and again when it goes out. You choose how much it does on its own, and one switch pauses all of it.

• A 25% offer against a 15% limit is refused, with the limit as the reason.
• The frequency limit counts the messages you sent by hand too. A guest you texted yesterday is skipped today.
• A message due at 10 p.m. inside quiet hours waits for the morning.
• A sent message can't be pulled back. Read each one before it goes, or let it send inside your limits.

What a winback to this list costs: a worked example

Say a single location has 300 guests in the winback group, with permission to text. Sous writes the message and offers what your limit allows. The 300 texts sit inside the 1,500 marketing texts each location gets a month. So the send itself adds nothing to your bill. Past that allowance a text costs 1¢, and 1,000 marketing emails cost $1.50, only up to a monthly limit you set. Orders that come back land on your own checkout and pay 5% until the fee reaches $199 for the month. We won't guess a return rate for you. The scoreboard shows the real one after the first send.

• 300 texts, inside the allowance: no extra charge.
• Every order that follows pays the Growth rate on its food subtotal, not on tax, tips, or delivery.
• Each Growth location also includes 10,000 marketing emails a month, so an email winback to the same 300 guests is inside the allowance too.
• An owner who never sets a usage limit is never billed past an allowance. The campaign stops instead.

Count the orders that came back, not the opens

A campaign report that shows opens and clicks tells you about the message. A restaurant needs to know about the orders. Appetier credits a campaign with an order only when the guest received that message and ordered inside the window you set. An order 90 hours after a text with a 72 hour window doesn't count. A guest with no recorded delivery doesn't count either, however soon they ordered.

• Only campaigns claim revenue. A fix Sous made to a sold-out item shows the orders that followed as a count, kept apart from campaign revenue.
• The Marketing tab shows the total per campaign, for the ones you wrote and the ones Sous proposed.
• You set how long after a message an order still counts. Shorter windows understate; longer ones flatter. Pick one and keep it.

Restaurant customer database FAQs

• Can I import my existing email list?: You can bring contacts in, but a record with no order history lands in no group but New. The database becomes useful once those guests order on your own checkout.
• Do DoorDash or Uber Eats orders add guests to my database?: No. Those channels keep the guest inside their own apps. Your list grows from your checkout, your apps, and reservations on your own site.
• Does the POS feed the customer database?: Connecting Square, Clover, or Toast keeps prices, hours, and sold-out items matched. Guest records come from direct orders and reservations on Appetier.
• How many guests do I need before a winback makes sense?: Enough that the 30-day group has a few dozen people in it. Below that, read the list by hand and call your regulars.
• Who can see guest contact details?: Owners, admins, and managers in the console. Sous never sees a guest's contact or payment details when you ask it questions.
• What happens to a guest who unsubscribes?: They stay on the record with permission turned off for that channel, and nothing goes to them on it again.

Next steps

See how the groups above turn into campaigns on the restaurant marketing page. Then run the free website audit on your own site. It checks whether guests can sign up at all, and the report shows your restaurant on Appetier.