Configure Public Booking Warnings
Configure one or more public booking warnings that appear by party size, by selected zone/table type preference, or when the Preferences step opens.
In this article
Public booking warnings let the team explain operational conditions before the guest continues: large groups, weather-dependent terrace service, accessibility notes, or preference restrictions.
Each warning has a title, description, step, colour, optional blocking behaviour, and a rule. In the ES demo, Marea Gran Via includes a blocking large-group warning, a non-blocking Terrace weather warning, and a non-blocking accessibility note shown when Preferences starts.
Before you start
- You are signed in with a selected organisation and location, such as Harbor Demo Group and Harbor Soho in the GB demo runtime.
- Public booking is available for the location and the Public web tab is visible.
- You can view the location settings. To edit and save warnings, your user needs location management permission.
- The location loads successfully and keeps its existing namespace code valid, because saving warnings updates the location settings.
Instructions
- 1.
Open Public Web settings
Open `/:orgId/:locationId/location/optimization-configs?tab=public-booking` and switch to the Public web tab. Warning controls are in Warnings during booking.
- 2.
Add a warning
Press Add warning. The app adds an editable warning card to the list.
- 3.
Define content and behaviour
Enter Title and Description, choose Step and Color, and decide whether Blocking prevents the guest from continuing when the rule matches.
- 4.
Configure the rule
For People, set Show when more than; a threshold of 8 appears for 9 or more guests. For Preferences, choose When to show: when a selected zone/table type matches a name, or as soon as the Preferences step opens.
- 5.
Save warnings
Press Save warnings. On success, the app confirms the save and reloads the saved list into the form.
- 6.
Check the public result
Open `/:orgId/:locationId/booking` or the `/reservar` alias and trigger the configured step. In the ES demo, more than 8 guests blocks the flow, selecting Terrace shows a weather warning, and entering Preferences shows the accessibility note.
Validations and limits
- Each warning requires a title and message before saving.
- Warnings are stored in `public_booking_warnings.items`; the legacy `public_booking_warnings.people` shape is still read for compatibility.
- People rules normalize the threshold to an integer from 1 to 99 and use a strict condition: more than X guests.
- Preference rules support `trigger=selection_match` for selected zone/table type names and `trigger=step_start` for a message shown when the Preferences step opens.
- `selection_match` compares text case-insensitively and accent-insensitively against selected zone and/or table type names. `step_start` does not require a match value.
- If Blocking is enabled and the rule matches, the guest sees the warning and cannot advance from that step until they change the selection.
- Save warnings is disabled when the user cannot manage the location or a save is already pending.
- Because the setting reuses `PUT /api/app/{orgId}/locations/{locationId}`, unrelated location validation such as namespace or country data can still block the save.
- The public booking page shows every active warning matching the current step; it is no longer limited to a single people warning.
Expected result
The location stores warnings in `location.public_booking_warnings.items`, and the public booking page evaluates them in People or Preferences according to their threshold, selected-preference match, or step-start trigger.