Skip to main content
A booking table represents a physical table used by bookings, allocation, live floor, and table-aware POS flows. Its capacity and party-size range are separate values and should match the shop’s real operation.

​
Who can do this?

Owners and Managers can use the described parts. Only Owners and Managers have configuration write access; Staff access remains read-only or operational. API authorization is authoritative.

​
Where

Open Settings → Rooms & tables. Add a table from a room, from the unassigned area, or from a room’s overflow menu. Select Edit on a table card to change it.

​
Steps

  1. Enter a unique table name and choose 1–50 seats.
  2. Set minimum and maximum party size from 1–50; maximum must not be below minimum.
  3. Assign a room or leave the table unassigned.
  4. Choose booking priority from Highest to Lowest, or Offline when the table must be excluded from online allocation.
  5. Save and verify the card’s capacity, party range, room, priority, and online state.

​
Platform notes

The API restricts creates, updates, reordering, and deletes to Owner or Manager. Staff can read tables for bookings and operations. Deleting removes combined-table membership automatically, but the API returns a conflict when active future bookings in Pending, Confirmed, or No-show still reference the table.

​
Market notes

The same table fields apply in GB and DE. Capacity is not a legal occupancy calculation, and the interface does not translate merchant-entered table names. Set values according to the actual venue and local operating practice.

​
Troubleshooting

If Save is disabled, check the name, 1–50 bounds, and party range. A delete conflict means future active bookings must be reviewed and reassigned or resolved first; do not bypass the protection. If the table appears missing, clear search and room filters and inspect Unassigned.