Online restaurant reservations: how they work and how to handle no-shows
A booking is not just a line in a notebook. It means a specific table, chosen on the floor plan, with its time and party size. This guide shows how restaurant reservations work and how to handle no-shows, with steps you can apply.
How it works (short answer)
- The booking is entered in the reservations module, with the date, the time and the party size.
- On the floor plan you see which tables are free and which are reserved at that time.
- You choose on the floor plan a table of the right size for the party.
- The booking appears on the chosen table, with its time and party size.
- Before service, you check the day’s bookings on the floor plan.
What helps handle no-shows
- Confirming the booking with the guest and a reminder before the booked time, done by your team, for example by phone.
- Tell the guest how to cancel in good time, so they free the table instead of vanishing.
- A clear cancellation policy for large parties and busy evenings, if you have one.
- A cancellation policy written clearly and shown before the booking is confirmed.
- You confirm the evening's bookings by phone or message on the day.
- Different policies for guests who often fail to show, decided by you.
Table: reservation channels
Where bookings come from and what to track on each channel
| Channel | What works well | The main risk |
|---|---|---|
| Phone | Special requests and large parties | It gets lost if the host does not enter it in the system immediately |
| Website form | Bookings that come directly from guests | Overbooking, if it does not check the floor plan |
| Social media and messaging | A younger audience and last-minute bookings | Unfinished conversations, with no phone number |
| Third-party platforms | Visibility with new guests | Commission and guest data that does not stay with you |
| Walk-in | Fills the gaps left by cancellations | Blocks reserved tables if the list is not up to date |
A practical example, with your own figures
Hypothetical example: a 60-seat restaurant, two seatings a night and 25 bookings a night. If some guests do not show up, tables stay empty and those seats cannot be sold again that evening.
Work it out with your own figures: the number of empty tables per evening, multiplied by your average check, then by the evenings in a month. The result shows what a single cause costs you.
Confirming bookings in time, a clear cancellation policy and noting the empty tables after each service are things you can track yourself, month by month. Compare the figures from one month to the next.
What you need to know legally
- The name, phone number and email in a booking are personal data: keep them only as long as you need them for the reservation and guest history (EU Reg. 2016/679).
- A reminder for an existing booking is not marketing; promotional messages require separate consent.
- The cancellation policy must be communicated before the booking is confirmed — informing the consumer in advance is mandatory (OG 21/1992).
- The fiscal document is issued for the amount actually collected, through the electronic fiscal cash register (OUG 28/1999).
Common mistakes
- Confirming a booking by seat count instead of by table — then discovering you have no free table for 6.
- Sending one confirmation and nothing afterwards, so a guest who forgot gets no signal at all.
- Not noting anywhere the guests who did not show up, so you repeat the same mistake next time.
- Not stating the cancellation policy before confirming — that is both a legal risk and a lost booking.
- Not noticing in time the tables freed by cancellations, so a table stays empty until 21:00.
How 4restaurants.net helps
- The floor plan shows which table is free and which is booked at a given time.
- The time slots on each table show when the table frees up.
- Group bookings sit on the same floor plan, with party size and time.
- Reservations, the floor plan and orders are in the same application.