How to change reservation booking mode
Move one materialised service occurrence between manual reservation handling and automatic optimisation. In the observed app surface, managers reactivate automatic mode from a Manual, open, non-past occurrence with optimisation configured.
In this article
Booking mode is set per materialised service occurrence. Manual mode keeps reservation handling under the team's control; automatic mode asks Antylogic to calculate the operating options for that occurrence again.
This guide focuses on the visible Harbor Soho workflow: open the occurrence, use `Pasar a modo automatico`, and confirm the same occurrence returns to `Automatico` without changing the recurring service series.
Before you start
- Work in the correct organisation and location context, such as Harbor Demo Group / Harbor Soho.
- Use a reservation occurrence that already exists and can be opened from the reservations calendar or `/:orgId/:locationId/reservations/:occurrenceId`.
- To view the detail screen, the user needs `reservation:manage` or `reservation:view`; to use the visible action menu item, the user needs `reservation:manage`.
- To switch an occurrence to automatic mode, the user or automation also needs `reservation-automatic:use`.
- For the visible automatic-mode action to appear, the occurrence must be Manual, open, not on a past day, and have optimisation configured from the occurrence or event payload.
Instructions
- 1.
Open the occurrence
From the reservations calendar, open the service occurrence you need to manage. In the GB demo, this is a Harbor Soho occurrence for the Soho lunch service, such as the one containing the Liam Scott reservation.
- 2.
Check eligibility
Confirm that the mode badge shows Manual, the occurrence is still open for reservations, the day is not in the past, and optimisation is configured. If one of those checks fails, the automatic-mode action is intentionally hidden.
- 3.
Open the action menu
Open the detail screen menu labelled `Configuraciones`. With the right permissions and occurrence state, the menu shows `Pasar a modo automatico`.
- 4.
Reactivate automatic mode
Choose `Pasar a modo automatico`. The app saves the mode change first, then starts a forced optimisation run for the same occurrence so availability and assignments can refresh.
- 5.
Confirm the result
After the refresh, check that the same occurrence shows the `Automatico` badge and that the reservation context is still present. The UI shows the automatic-mode toast only after the mode update and forced run complete successfully.
Validations and limits
- `Pasar a modo automatico` is visible only when the current mode is Manual, the occurrence is open, an optimisation configuration is available, and the occurrence is not in the past.
- The visible menu action requires `reservation:manage`. The backend accepts `reservation:manage` or `optimization:manage`, and switching to `automatic` also requires `reservation-automatic:use`.
- The mode endpoint accepts only `automatic` or `manual` as requested values; `waiting_list` can be derived internally but is not selectable through this action.
- The change applies to one materialised service occurrence only, not to the recurring service series or base calendar event.
- The observed detail menu does not provide a direct action to switch an Automatic occurrence back to Manual; Manual mode can be set through the supported API or appear after other operational flows.
- Changing booking mode does not change the occurrence acceptance state. Opening or completing reservations belongs to a separate action.
- The mode update and the forced optimisation run are separate calls. If the run fails after the mode update, the mode may already have been saved.
Expected result
The occurrence is restored to automatic booking for that service only. Reservation context refreshes, and Antylogic synchronises optimisation and waitlist state according to the final booking mode.