Assign an optimisation configuration to a service
Use the Optimisation field on a public Harbor Soho service to keep table assignment in Manual mode or connect the service to an optimisation configuration for automatic assignment.
In this article
Manual mode is the default and is a valid operating choice. It saves the service without `optimization_config_id`, so new occurrences remain manual.
Choosing a non-system optimisation configuration stores `optimization_config_id` on the service payload. New or refreshed occurrences can then use automatic booking mode and the optimisation runtime.
Before you start
- Harbor Demo Group and Harbor Soho are selected.
- The service form is opened with `kind=service` from create service or edit service.
- The operator can manage services. Read-only service access is not enough to edit.
- To choose anything other than Manual mode, the operator can view optimisation configurations and the runtime has at least one non-system configuration in location or organisation scope.
- Saving a selected configuration requires automatic reservation use permission.
- When editing, use a service occurrence that has not already started.
Instructions
- 1.
Open the service form
Open Create service or edit Soho lunch service. Stay on the Info tab, where the public service details and the Optimisation field are managed.
- 2.
Keep optimisation on public services
Use the field only for public services. If the service is switched to Internal, layout, catalogue and Optimisation are hidden and the service is saved without an optimisation configuration.
- 3.
Choose the mode
Open Optimisation. Leave Manual mode selected when staff should assign tables manually, or choose an available location or organisation configuration for automatic optimisation.
- 4.
Save the service
Create sends the service bundle create request; edit sends the service bundle update request. Manual mode omits `optimization_config_id`; a selected configuration saves that ID in the service payload.
- 5.
Set recurring scope
For recurring services, choose whether the change applies only to the selected service or to future services. Past snapshots preserve the optimisation configuration they used.
Validations and limits
- Public services require a layout and catalogue before saving; `optimizationConfigId` itself is optional.
- Manual mode is explicit and default. The form does not auto-select the default optimisation configuration.
- System optimisation configurations are not offered in the service selector.
- A non-empty `optimization_config_id` must be a UUID, cannot refer to a system configuration and requires `reservation-automatic:use`.
- A future occurrence with active reservations can reject the change if the selected configuration cannot produce a valid solution.
Expected result
The public service either remains in Manual mode or stores an optimisation configuration for automatic assignment on new or refreshed occurrences.