Room first or date first? The booking flow that fits your venue
Two ways to guide parents in the widget. Choose based on a few similar rooms or many with different character.
In a venue with two or three very different rooms (small vs large, princess theme vs disco), many families think “I want room X” first. With similar rooms, the natural question is “which Saturdays are free?”.
The widget can follow room first or date first. Neither is universally better — there is a better fit for your building.
Date first (recommended when…)
- Rooms are comparable in price and size.
- The bottleneck is the Saturday, not choosing a room.
- You want to fill slots before selling the premium room.
The parent sees the calendar, picks a day, then an available room that day.
Room first (recommended when…)
- Each room is a distinct product (brand, capacity, fixed décor).
- Marketing pushes one room (“party in the castle”).
- Prices and packages vary a lot by room.
The parent picks a room, then sees dates for that room.
Mistakes when the flow is wrong
- Date first with a confusing room catalogue → abandonment at step 2.
- Room first with only one useful room → useless extra step.
Run one test booking with real parents (or staff as a customer) and count where they drop off.
Consistency with the rest
The flow should align with packages by age, catering and visible final price.
In FastCore you configure this from the business flow panel — no coding.