Per-guest catering in online booking: fewer surprises on party day
Charge menu by number of guests in the same flow as room and package. What the venue gains and what the customer must see.
“We were 18 and the menu was for 12.” At birthday catering, that mismatch costs money or creates tension in the kitchen. If guest count is only confirmed on WhatsApp on Thursday, mistakes are almost inevitable.
Catering in the online booking forces guests (or tiers) to be declared before paying the deposit — and keeps the total aligned with what the kitchen will prepare.
Benefits for the business
- Predictable production: you know how many menus to prepare.
- Consistent billing: dashboard total matches what was charged and what is outstanding.
- Fewer calls like “what would it be if we are 20?”.
What parents must understand
- Whether the price is per person or a closed menu for the group.
- Minimum guests or surcharge per extra child.
- Whether catering is mandatory or optional for that package.
Clarity here avoids the conflict described in clear final price before booking.
How it fits with packages and room
Typical flow: pick date and room → package by age → catering step (if you offer it) → decoration or other extras → deposit.
Everything adds on screen before payment. In FastCore this is part of the party venue engine, not a separate spreadsheet.
If you do not offer catering online yet
You can start with a closed package only (catering included) and open per-guest options later. What matters is that what you promise on the website matches what you configure — without promising steps that are not active.
Catering + packages + deposit in one widget?