Skip to main content
Seating a walk-in records both calendar context and real occupancy. Tapp first creates a walk-in booking and then starts an active session on the chosen table or table group.

​
Who can do this?

Owners, Managers, and Staff may operate Live Floor and table sessions. Room, table, and booking configuration remains Owner/Manager-only wherever its API requires that role.

​
Where to do it

In the Management web app, open Rooms and tables → Live Floor. Select a table for its card or session. The Management mobile app provides the same core floor, filter, map, table-action, extension, and session-detail areas.

​
Steps

  1. From Live Floor, select Seat now on a free table or start the walk-in action.
  2. Set party size from 1 to 50 and, optionally, choose or create a guest only when your guest-directory role permits it.
  3. Review Tapp’s suggested free table. Re-select it or choose another suitable table; check seats, room, priority, and any locked members of a combined table.
  4. Confirm the duration, which starts from the store’s standard booking duration unless the flow supplies another allowed value.
  5. Submit once. After success, open the table and verify the active session, walk-in identity, start time, expected end, and linked table set.

​
Platform notes

Web and mobile use the same session endpoints. POS orders are anchored through the session ID. Guest bookings from the guest app can appear as incoming floor bookings, but guests cannot operate Live Floor or sessions.

​
Market notes

The flow is the same in GB and Germany. Live Floor sends a local time reference for the store; bookings and sessions are shown in that local operating time. Currency differences affect orders, not occupancy logic. This reflects the product on 17 July 2026. The active session is authoritative: an elapsed booking window does not end physical occupancy, and only a successful session action changes the table state.

​
Troubleshooting

  • If the table is taken between suggestion and submit, session start returns a conflict. The web flow attempts to archive the just-created walk-in booking so it does not remain as a false hold.
  • A missing suggestion can mean no free table fits the party. Change party/table choice only when operationally correct; do not select an offline or occupied table.