How to connect table bookings to visits and revenue
Guide menu and contents
Link a booking to attendance using an internal ID, date and venue. Add revenue and known source. Keep cancellations, no-shows and walk-ins separate so one party does not appear as several sales.
Agree what each record represents
An enquiry can become a booking. One booking can become one seated table, several covers and one or more bills. Record the ID, service date, venue, status and number of arrivals. Link the bill only through a process staff can follow.
Agree what counts as a cancellation or no-show and how to handle moves and split bills. Use service date for occupancy and enquiry date for response metrics.
Reconcile a short period
| Source | Fields |
|---|---|
| Ads and website | Link, source, event and period. |
| Reservations | ID, date, venue, status and covers. |
| Till | Time, internal transaction ID and revenue. |
Start with one week and one venue. Allow for unknown and unmatched records. Similar timestamps alone do not identify the same party.
Resolve duplicates and walk-ins
When someone books on the site and messages on WhatsApp, check the shared log before entering another booking. Keep cancelled records separate from the final visit. Include walk-ins in occupancy and leave them out of booking conversion.
Keep contact details out of advertising reports. Use aggregates or internal IDs and limit access to guest-linked records.
Report the quality of the join
Report total visits, visits with a booking, known sources and exceptions. Say how much is missing. If many confirmed tables never become visits, start with statuses and reminders. When the join is reliable, compare source contribution with cost.
Sources
Want a team to help market your restaurant?
Use this guide to make the changes yourself. If you want help finding where you’re losing diners and turning the plan into action, OliveMKTG can connect your website, menu, Google profile, content and ads to measurable table bookings.
Talk to us about restaurant marketing