How to set table mode on a reservation

In this article

Before you start

• Open a service occurrence such as Harbor Soho's Soho lunch service at /:orgId/:locationId/reservations/:occurrenceId.
• Have reservation:view to load the occurrence, reservations, assignments and layout.
• Have reservation:manage to create, edit and save the reservation; customer:manage is also needed when the save creates or updates the customer.
• Use an occurrence that resolves to a layout with tables. Without a layout, the table selector is disabled.
• Fill customer name, customer phone and party size before saving, even when the only change is table mode.

Instructions

1. 1.

   Open the service occurrence

   Go to the reservation detail page for the service occurrence and wait for the reservations list, table board, assignments and layout to load.

2. 2.

   Open the reservation editor

   Create a reservation or edit an existing one, such as Liam Scott in the Harbor Soho demo. The editor resolves the current table mode from the reservation fields and table assignments.

3. 3.

   Choose the table mode

   Use Table mode to choose Indifferent, Preference, Required or Assign tables. Indifferent keeps the booking flexible; Preference and Required record table intent; Assign tables locks a fixed manual assignment.

4. 4.

   Select tables when required

   For Preference, Required or Assign tables, open Tables and select one or more tables from the loaded floor plan, such as C1, C2 or C3 in Harbor Soho.

5. 5.

   Save the reservation

   Save after checking the customer details and party size. Indifferent clears table lists; Preference saves preferred tables; Required saves restricted tables; Assign tables saves fixed manual assignments.

6. 6.

   Confirm manual mode if prompted

   If an automatic open service cannot validate the table change, use Save and switch to manual only when the operator accepts that this change may move the occurrence into manual handling.

7. 7.

   Check the refreshed service view

   After saving, confirm that the reservation row and table board reflect the selected mode and tables after the occurrence, customers and assignments reload.

Validations and limits

• Customer name and customer phone are required before save.
• Party size must be a number greater than zero.
• Any mode other than Indifferent must have at least one valid selected table.
• Selected table IDs are deduplicated and ignored if they do not belong to the loaded layout.
• Assign tables is not offered for waitlist reservations, and waitlist or cancelled reservations clear assignments in backend handling.
• There is no separate persisted tableMode field; the editor derives the mode from assignment_mode, preferred tables, restricted tables and current table assignments.
• In the current implementation, Preference and Required also send the selected tables as table_ids, so table assignments are refreshed as well as the preferred or restricted fields.
• If the optimiser requires manual confirmation, the retry sends confirm_manual_mode: true after the operator chooses Save and switch to manual.

Expected result

The reservation keeps the selected table intent, the table assignment records are updated where the current implementation submits table_ids, and the service view reloads with the latest reservation and assignment state.