Topic

Goal: guests pay a weekday price or a weekend price for the same kind of visit — without two separate booking pages.

Build it

Start from a normal booking procedure (people → time → place → hold → price → pay → sync). Then branch the pricing part:

1. Two price positions — add two Add position steps (or two orderables on one step with conditions): e.g. “Weekday table fee” and “Weekend table fee”.
2. Execution conditions — enable the weekday position only when the selected slot is Mon–Fri; enable the weekend position only for Sat–Sun (or your weekend definition). Conditions usually look at the timeframe the guest already picked.
3. Matching Pay now — if totals or payment methods differ, use two Pay now steps with the same day conditions. Often one Pay now is enough if only the positions change.
4. Optional extra fields — weekend-only Require input (e.g. special notes) with the same weekend condition.
5. Test both paths — book a Friday and a Saturday; confirm Today and the invoice amounts.

Template to copy

Classic occupancy — use as the base procedure, then add the weekday/weekend branches on pricing (and Pay now if needed).

API

• Add position to order
• Pay now
• Require input