Edit Reservation

In this article

Before you start

• The operator is signed in with Harbor Demo Group and Harbor Soho selected.
• The target service occurrence is public and reachable from the reservations calendar or the reservation occurrence deep link; internal services are not valid reservation edit targets.
• The occurrence contains the reservation to edit, for example Liam Scott in the Soho lunch service.
• The role has `reservation:view` to load the occurrence and `reservation:manage` to open and save the editor.
• Customer lookup data is available, with `customer:manage` granted when the save creates or updates customer details.
• A floor layout is available when the edit includes preferred, required or assigned tables.

Instructions

1. 1.

   Open the service occurrence

   Open the target reservation occurrence from the calendar or direct link. Confirm that the Harbor Soho service context, reservation list or board and table assignment context are loaded before editing.

2. 2.

   Open the reservation editor

   Select the Liam Scott row, card or edit action. The editor opens with customer name, customer phone, party size, start time, duration, read-only status and the inferred table mode.

3. 3.

   Update guest and booking details

   Correct the guest name, phone, party size, time or duration. Keep the contact fields complete and party size positive before saving. Time and duration are snapped to the configured service slot interval.

4. 4.

   Choose table handling

   Leave the table mode as indifferent when any table is acceptable. Choose preferred, required or assign when the reservation needs specific table choices, then select one or more current-layout tables.

5. 5.

   Save the reservation

   Choose Save. Antylogic validates the visible fields, saves the reservation update, creates or updates the linked customer when needed, refreshes the occurrence data and closes the editor after a successful save.

6. 6.

   Confirm manual handling when required

   If automatic optimisation cannot validate the edited reservation or table distribution, confirm Save and switch to manual only when the operator accepts manual handling for that occurrence. Cancelling the prompt leaves the pending edit incomplete.

Validations and limits

• Customer name, customer phone and a positive party size are required before the save is sent.
• For normal reservations, start time and duration are editable, snapped to the slot interval and bounded by the duration rules up to 480 minutes.
• When the table mode is not indifferent, at least one selected table must exist in the current layout.
• Preferred mode saves preferred table IDs, required mode saves restricted table IDs and assign mode saves manual table IDs.
• Waitlist reservations cannot keep manual table assignments, and the editor does not expose a general status selector.
• Reservation and customer persistence are separate calls; a customer update failure after the reservation save does not roll back the reservation update.
• Manual confirmation is a retry of the same update with `confirm_manual_mode: true`, not a separate endpoint.

Expected result

The occurrence detail refreshes with the edited reservation, updated linked customer details when applicable and the selected table handling. If manual confirmation was accepted, the automatic occurrence moves into manual handling for that saved change.