Skip to main content
A booking becomes an order context after the guest is seated. The supported path runs through Live Floor and the table session, preserving the booking, guest, and table relationship instead of starting an unrelated cart.

​
Who can do this?

Owners, Managers, and Staff may view bookings and perform the operational action in this guide.

​
Where to do it

Use Bookings in the Management web app for list, calendar, and details. Configuration is under Settings → Booking; the operational seating/order handoff is in Live Floor. Mobile has corresponding booking, detail, settings, and floor views.

​
Steps

  1. Confirm the booking and ensure it has an appropriate table assignment for the current visit.
  2. Open Live Floor, find the table showing the upcoming or due booking, and select Seat now.
  3. Open the resulting table session. Verify the currently seated guest, linked booking, table, and expected end.
  4. Choose Add order. Tapp opens POS with the active table session context so the new order can remain linked to that session.
  5. Add items and continue through the normal POS flow. Return to the table session to see its orders and operational state.

​
Platform notes

Management web and mobile use the same booking and status endpoints. The guest web app can create bookings; guest bookings start Pending, while authenticated store staff manage operational bookings. Guest and table assignments are separate links.

​
Market notes

The flow is the same in GB and Germany. Date, time, and calendar labels follow the store market and time zone. Use the displayed local time; a booking stores a local civil date and time. This guide was verified on 17 July 2026. Saved status, API authorization, and server validation of time windows and table occupancy are authoritative.

​
Troubleshooting

  • If the booking is not on the expected table, inspect its assignment and time. Do not start an unrelated POS order as a substitute for a missing session link.
  • If seating or order creation reports a conflict, refresh Live Floor and verify that no active session already occupies the table. Resolve the session or assignment first.