> ## Documentation Index
> Fetch the complete documentation index at: https://help.tapp.shop/llms.txt
> Use this file to discover all available pages before exploring further.

# View a table visit

> Review the seated party, expected end, upcoming booking, and orders for the active visit.

Open a table’s details to see who is seated, when the visit is expected to end, and which orders belong to it. Check the current party separately from the next booking before making a service decision.

## Who can do this?

Owners, Managers, and Staff can view table details for their shop.

## Where

In the web app, open **Live floor** and select a table. Its details panel shows the table name and current state. The mobile app also provides table details with a different layout.

## Read the visit details

1. Confirm the shop and table name. Check the room and capacity so you do not act on a similarly named table elsewhere.
2. Read **Currently seated** for the active party, seating time, and expected end. A walk-in may have a general label rather than a named guest.
3. Read **Next booking** separately. In the web panel, this shows the next upcoming pending or confirmed reservation found among today’s loaded bookings for this table. It excludes bookings whose start time has already passed, and does not summarize every future reservation.
4. Review the table details. **Allergens noted** displays ordinary booking notes: from the seated booking when loaded, otherwise the next booking. Check which party the notes concern. **None today** means no notes were found here; it does not confirm that the current party has no allergies.
5. Open the linked booking where offered if you need to verify its contact details or change the planned visit.

Some visits have no expected end displayed. When present, it is a planning time. An overdue visit remains active until the team closes it. A reservation time alone does not establish that the guest has been seated.

## Review orders

The order cards show orders linked to the current active visit, excluding cancelled orders. They are not a full history of orders ever placed at this table. The order list does not refresh on the same timer as the floor status. Reload the page to check recent changes from another device. Review each order’s items, amount, and status separately; an amount shown on a card does not itself mean it is paid.

Use the available order actions when you need to continue service. **Add order to table** starts a fresh order for the active visit and clears the current basket, so finish or safely leave other order work first. Use **Extend time** or **Close table** for the visit itself.

## Platform and market notes

In the mobile map, tap a table to open its visit or press and hold to show its available actions. Tables under **Unplaced** work the same way. Search and status filters fade nonmatching map tables; you can still open them. Small table shapes may omit the timer or seat count, so open the details to check. The web panel uses your computer’s local date and time for today’s bookings and upcoming visits. Check its time zone against the shop, especially when working remotely, and check each order’s currency. One active visit can occupy several tables. Opening another member table can show the same visit, so avoid repeating an action from each table.

## Troubleshooting

If the panel shows the table as free, another team member may already have closed the visit. Refresh before acting. The panel loads at most 200 shop orders before selecting those for this visit. If an expected order is absent, check order history and its table connection rather than creating another order immediately. Use **Bookings** for dates beyond today, missing reservations, or a complete list. The web panel loads at most 1,000 of today’s pending and confirmed bookings, so its empty next-booking section is not a complete availability check.

## Related articles

* [Extend a table visit](/en/live-floor/extend-table-session)
* [Manage an order from the floor](/en/live-floor/manage-order-from-live-floor)
* [Search and filter bookings](/en/bookings/search-and-filter-bookings)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.