Enable public table preferences
Control whether Harbor Soho's public booking journey asks guests for table preferences before checking availability. When the setting is off, the public flow skips that step and preference fields are ignored.
In this article
Public table preferences let guests say how they would like to be seated without changing the restaurant's own assignment rules. The setting lives in the Public web configuration for the location and only controls the Preferences step; it does not publish or unpublish the public booking page.
For Harbor Soho, enabling the setting adds No preference, Zone and Table type choices before time selection. Disabling it removes that step, resets any previous preference choice and keeps availability and reservation creation free of table preference fields.
Before you start
- An authenticated operator session with an organisation and Harbor Soho selected.
- Harbor Soho can be loaded from the location settings page.
- The location has automatic reservations available, so the Public web tab is visible.
- The operator has `location:view` or `location:manage` to open the settings screen.
- The operator has `location:manage` to change `Permitir preferencias de mesa`.
- To verify the guest-facing effect, Harbor Soho has `public_booking_enabled=true`, automatic reservations available and at least one public service with a floor plan.
Instructions
- 1.
Open the Public web settings
Go to Reservations, open the Public web tab for Harbor Soho, or open `/:orgId/:locationId/location/optimization-configs?tab=public-booking` directly. If automatic reservations are not available for the location, this tab is not shown.
- 2.
Check the table preference state
Find `Permitir preferencias de mesa`. A missing or null value is treated as enabled; only an explicit `false` value disables public table preferences.
- 3.
Turn preferences on or off
Use the toggle to change the setting. View-only operators can see the setting but cannot change it, and the toggle stays disabled while the save request is in progress.
- 4.
Verify the guest booking step
Open Harbor Soho's public booking route. With preferences enabled, guests can choose No preference, Zone or Table type before checking available times.
- 5.
Check the disabled behaviour
When preferences are disabled, the public booking journey moves on without the Preferences step. Availability and reservation creation continue without `preferred_table_ids`, `table_type_id` or `table_type_mode`.
Validations and limits
- The settings screen can be opened with `location:view` or `location:manage`; saving requires `location:manage`.
- The Public web tab is hidden when `reservation-automatic:use` is unavailable for the location.
- The app only sends the update after the selected location is loaded and the operator can manage it.
- A successful save shows `Preferencias habilitadas` or `Preferencias deshabilitadas`; a failed save shows an error instead.
- Zone preferences convert selected zones into `preferred_table_ids` from the floor plan.
- Table type preferences send `table_type_id` with `table_type_mode: "preferred"`.
- If the floor plan cannot load, the guest can continue with No preference.
- When the setting is disabled, the backend ignores table preference fields even if a client sends them directly.
- The implemented public booking route is `/:orgId/:locationId/booking`; `/:orgId/:locationId/reservar` is supported as an alias.
Expected result
Harbor Soho's public booking flow either includes the Preferences step and passes allowed table preferences into availability and reservation creation, or skips the step and proceeds without table preference fields while public booking publication remains controlled by `public_booking_enabled`.