​
Why This Matters

The Menu section gives guests one more operationally accurate checkpoint before they commit guest details and payment. The menu PDF is managed by the dashboard, so the booking flow can show the current document for the selected booking path without hardcoding menu copy into the page.

​
How It Works

After the guest confirms an offer in Choose Experience, the Menu section appears for every self-serve booking path. The section shows the selected event context, the active booking path label, and a link to the current menu PDF when one is available. The guest clicks confirm to continue. If the booking is Tickets Only with no selected bundle and add-on offers are available, the next section is Add-ons. Otherwise, the flow continues directly to Guest Details.

​
Key Concepts

Menu is a review step. The guest does not make selections in this section. It is a checkpoint before add-ons and guest details. Menu documents are operational content. The active PDF is managed outside the booking component and read into the flow as menuPdfUrl. Menu precedes add-ons. Guests see the menu before optional add-ons so they can decide whether they want extras after reviewing the current food and drink context.

​
Technical Details

The section is rendered by BookingMenuSection and uses the MENU entry in sectionStates. It appears after OFFERS is completed and before conditional ADDONS. See also: Booking Flow Overview and Add-ons.