Table reservations and the restaurant floor plan

The most expensive mistake a restaurant can make is booking the same table to two different guests on a Friday night: one waits at the door while the other gets an apology. Table reservations and floor plan management treat a table as a resource and a time slot as a unit of capacity, so the system itself blocks that clash instead of catching it later.

Why a double booking can’t be solved with a warning

In most reservation notebooks — or a shared spreadsheet — two people can write the same table down for the same time, and the system, at best, notices afterwards. What’s actually needed is for the second entry to be refused the moment it’s created, not flagged with a warning. Saying “be careful” without locking the table and time slot on one resource just guarantees the same mistake comes back during the next rush.

A floor plan is a map, not a list

Keeping reservations as a plain list of names and times hides which table is which size, and which section it’s in — garden, indoor, smoking area. A floor plan holds every table with its capacity and location; when a party of six arrives, the system suggests one table with the right capacity, or tables that can be combined, instead of two separate two-tops.

Deposits and event bookings

A section of the floor set aside for a birthday party or a private event carries a different commitment than an ordinary table booking: a deposit is taken, a cancellation policy is set. When that kind of booking shares the same capacity lock as ordinary table reservations, the same section can’t be handed to an event and a walk-in guest at once.

Waitlist and no-shows

When the floor is full, putting a guest on a waitlist instead of turning them away lets you catch the first table that clears without losing the booking; the next person on the list gets called the moment a table opens up early. Just as important as the booking itself is recording a no-show; a given guest’s repeat no-show history can factor into whether a deposit gets requested for a busy night. Without a waitlist and no-show record, a floor that looks full might actually be quietly carrying a few empty tables that only get noticed when staff physically check.

Tied to the customer record

A reservation shouldn’t be a record disconnected from the guest behind it: how many times they’ve visited, which table they prefer, whether there’s an allergy or a note worth remembering — all of that belongs on the reservation screen. A reservation linked to the customer record makes a regular feel recognised; a disconnected notebook asks the same questions from scratch every time.

Example

For Friday at 8pm, a four-top in the garden section gets called in by two different guests: the first call comes in at 2:12pm, the second at 2:15pm. With a capacity lock in place, the first booking holds the table instantly; the 2:15pm request comes back as “unavailable” for that table, and staff offer the second guest a different table at 8:30pm or an equivalent indoor table. Without a lock, both bookings get written down, and the clash only surfaces at 7:50pm, with both parties standing at the door.

How it works in Rotenta

1. In Reservations, every table is set up on the floor plan with its own capacity and section (garden/indoor).
2. Once a reservation is created, the system refuses a second confirmation for the same table and time window; the second request comes back as unavailable, and staff offer an alternative table or time.
3. For event or group bookings, the deposit amount and cancellation terms are noted on the same record; the section shares the same capacity lock as ordinary tables.
4. The reservation links to the guest’s card in Customers; past visits and notes appear on the same screen.
5. Confirmations and reminders go out as in-app notifications through Core notifications.

More detail on the reservation engine itself lives on the reservations module page. For the other criteria worth checking before you buy, see our guide to choosing cafe and restaurant software; for the order and till flow, read bringing online orders and the till into one flow. Our cafe and restaurant software hub has a broader overview of the sector.

Frequently asked questions

What happens if two staff members try to book the same table at once?

The second attempt is refused; the system marks the table as unavailable and staff have to offer an alternative table or time. The clash is blocked at the moment of booking, not discovered later.

Can tables be combined on the floor plan?

Yes, tables that can be pushed together for a larger party are defined as a combination on the floor plan and held as a single reservation.

What happens if a deposit-paying reservation is cancelled?

The cancellation policy is noted on the reservation record; the deposit status and any refund are tracked on the same record.

Does reservation history show up on the customer’s card?

Yes, a guest’s past reservations, preferred table and any notes appear on their own customer card.

Can we log phone reservations in the system too?

Yes, the channel — phone, walk-in, online — is recorded on the reservation itself, so you can report on where bookings come from. Get in touch to talk through setup.