Dietary requirements are a small detail that becomes a big problem at scale. At 200 guests you might have thirty different needs — vegan, gluten-free, nut allergies, halal, kosher, plus the couple's specific requests — and every one has to reach the caterer accurately, mapped to the right table. Get it wrong and someone has nothing to eat at their own friend's wedding.
Per-guest needs that aggregate into a kitchen sheet, connected to seating and the live list.
Open Mezze — freeDietary needs live on each guest and flow into the kitchen sheet, aggregated with a per-table breakdown the caterer can actually use — total vegan meals, and which table they are at. Because it is connected to seating and the live guest list, a late RSVP or a moved guest updates the kitchen sheet automatically.
They aggregate into a kitchen sheet with totals and a per-table breakdown the caterer can use.
Because dietary data is connected to seating, moving the guest moves their meal in the kitchen sheet.
Yes — the kitchen sheet updates from the live guest list, so a late change is reflected.