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

# Manage booking status

> Confirm, deny, mark no-show, or archive a booking using only supported status transitions.

Status communicates the operational state of a booking and controls whether tables remain reserved. Use the action shown for the current state; the API rejects transitions outside its allowed sequence.

## 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. Open the booking detail panel and verify guest, date, time, and current status.
2. For **Pending**, choose **Confirm** to accept or cancel to **Deny**. Guest-created bookings start Pending and require staff action.
3. For **Confirmed**, choose **Mark no show** when the guest did not arrive, or cancel to archive the booking.
4. A **No show** booking may return to Confirmed or be archived. A Denied booking may be archived. Archived is terminal in the current model.
5. After updating, verify list/calendar status and Live Floor table availability. No-show and archived bookings are treated as freed for floor assignment.

## 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 an action is absent, the current status may not support it. Do not attempt an undocumented transition through repeated edits.
* Use no-show only for the attendance outcome. Use archive/cancel for a booking that should no longer be active; the distinction affects reporting and floor context.

## Related articles

* [Use booking calendar and list views](/en/bookings/use-calendar-and-list-views)
* [Start an order from a booking](/en/bookings/start-order-from-booking)