Reservations & tables
The floor plan, bookings and table requests
See which tables are seated, which are waiting for the bill and which are booked for later. The host, the floor staff and the till all work from the same floor plan.
Select a table and turn it: seat, bill, clear. Badges are guest requests sent from the QR menu. Names and times are illustrative.
Selected table
T6
- Seats
- 6
- Party
- Birthday · 6
- Time
- Seated 19:15
3 guest requests open, sent from the QR menu at the table.
Where it works: Dining room
Walk the whole restaurantBookings that can’t overlap
Staff take bookings by phone or at the door, for a table and a time. Each booking holds the table for its duration (90 minutes unless you change it), and the server refuses any booking that overlaps, even when two people enter bookings on two devices at the same moment.
- 1Bookings per branch, with party size, phone and notes.
- 2Linked to the guest record when there is one, so you can see a regular’s history.
- 3The overlap check runs when a booking is created and every time it is edited.
Tonight · Main floor
Illustrative data- T34 seatsKarki · 418:20 · seatedGurung · 321:00 · confirmed
- T54 seatsTamang · 217:30 · completedShrestha · 420:00 · confirmed20:45 · refused
- T66 seatsBirthday · 619:15 · seated
- T72 seatsRai · 218:00 · no-showThapa · 221:30 · pending
- T88 seatsOffice dinner · 820:30 · confirmed
A 20:45 booking for T5 would collide with the Shrestha party still at the table until 21:30. The server refuses it: so two people on two devices can’t both promise the same table.
From booking to a cleared table
A booking moves from pending to confirmed, seated and completed. Cancellations and no-shows are kept as statuses rather than deleted, so you can still see them the next day.
Table status changes during service (available, occupied, reserved, billing), so the host sees the current state of the floor. When a guest asks for the bill from the table’s QR code, the request appears against that table on staff screens.
A booking’s life
- 01
Pending
- 02
Confirmed
- 03
Seated
- 04
Completed
Cancelled
Before arrival. The table frees for rebooking.
No-show
Recorded against the booking, not quietly deleted.
How it connects
What a table is connected to
A table holds its current order, the QR code guests scan, its bookings and any guest requests. The host, floor staff, kitchen and till all see the same table record.
Feeds in
- Staff bookingsPhone and walk-up reservations
- QR at the tableGuest orders and requests
- Guest self-bookingPlannedBook from your website
Reservations & tables
Floor plan, table status, bookings with overlap checking, and guest requests from the table.
Reservations and table features
Bookings use the same tables and guest records as the rest of DataRestro. Planned means not built yet.
- Available
- Available
- Partial
- Partial
- Planned
- Planned
Floor plan
AvailableTables with shape, seats and position, grouped by floor.
Table status
AvailableAvailable, occupied, reserved or billing, updated as service moves.
Staff reservations
AvailableParty, time, duration, table, phone and notes, per branch.
Double-booking protection
AvailableOverlapping bookings on a table are refused on the server.
Booking statuses
AvailablePending, confirmed, seated, completed, cancelled, no-show.
Guest requests
AvailableCall waiter, request bill, water or assistance from the table QR.
Table QR codes
AvailableA unique code per table for ordering and requests.
Guest self-booking
PlannedBook from your restaurant website.
Deposits
PlannedHold a booking with a deposit for large parties.
Waitlist
PlannedQueue walk-ins and message them when a table frees.
Opening hours for bookings
PlannedBookings limited to the hours you set.
Reservation questions
Can guests book online?
How do guest requests reach the floor?
How long does a booking hold a table?
Do you have a waitlist?
Try the demo
A sample restaurant in your browser. Take an order, send it to the kitchen, mark it ready and take payment. No account needed.