Halal, vegan, gluten-free, shellfish allergy, tasting-menu-specific restrictions — captured at booking with conditional follow-ups, scoped per experience, and persisted across visits so your kitchen reads the room before the guest arrives.
Built-in fields. Custom dietary forms. Pattern-based follow-ups. Persistent guest profiles.
For a tasting-menu kitchen, dietary information collected at booking is the difference between a clean service and a re-prep at first course. A guest with a shellfish allergy who selected "no allergies" at booking — because the form was generic and they didn't register their own caveat — becomes a 12-minute scramble at the pass. The course slips. The pacing slips. Service slips.
The standard reservation form makes this worse. A free-text "any dietary requirements?" field captures intent inconsistently — some guests write nothing, some write "vegan", some write three paragraphs about a complex condition. The kitchen reads them differently depending on who's on the pass. The risk surface is wider than it should be.
For halal-certified rooms, the issue is sharper. "No pork" appearing in the dietary field is a yes-or-no signal that should drive whole sections of the menu and the upsell flow — but it has to be detected reliably, not parsed by hand from free text. For tasting-menu venues with multi-course pacing, dietary capture also has to know the cover count: a vegan substitution on a 12-course menu for a 4-top is doable; on a 12-top, it's a different conversation.
Revasi treats dietary information as a structured signal — toggleable per experience, with conditional follow-ups, optional cover thresholds, and a persistent guest profile so the same allergy doesn't need to be re-captured on every visit.
These live alongside the upsell engine in the Cross-Sell & Upgrades tab in admin. Built-in dietary fields are toggleable; custom fields are configurable; conditional logic ties everything together.
Three pre-built fields ship out of the box: dietary restrictions, special occasions, and accommodation needs. Each can be toggled on/off, marked required, scoped per experience, and shown in the confirmation email or the reservation listing — separately from each other.
Customization · Cross-Sell & Upgrades · Built-in Fields
When the dietary field contains a pattern you specify — "halal", "no pork", "vegan", "shellfish" — surface a follow-up field for detail. Optionally apply a cover threshold (e.g., only ask for tasting-menu detail when party size is four or fewer). Triggers run on built-in fields or any custom field you create.
Customization · Cross-Sell & Upgrades · Conditional Triggers
Build your own fields beyond the defaults: a checkbox group for common allergies, a radio group for cuisine adjustments, a dropdown for menu-specific substitutions. Each custom field is scopeable per experience, can be required or optional, and can be marked to show in the confirmation email or the reservation listing.
Customization · Cross-Sell & Upgrades · Custom Fields
Every booking links to a guest profile that retains dietary notes, custom labels (Press, Critic, F&F, allergy-flagged) and free-text notes across visits. When a returning guest books, the team sees prior dietary information on the reservation card immediately — no need to re-capture, no risk of inconsistency.
Customization · Client Profiles · Notes & Labels
5 steps · live for every booking
The booking flow shows the dietary field you've enabled for that experience — built-in or custom, optional or required. A halal-certified room might show only the "dietary restrictions" field; a tasting menu might show that plus a conditional follow-up.
If the guest types "halal", "vegan" or another pattern you've defined, a follow-up field surfaces inline — for example, asking for allergy detail or course-substitution preference. Cover thresholds limit follow-ups to relevant party sizes.
Revasi matches the booking to an existing guest profile by email or phone. If matched, prior dietary notes are linked to the reservation. If new, a profile is created with the dietary information attached.
Fields you've marked as "show in email" appear in the branded confirmation email, so the guest can review and correct before arrival. Internal-only fields stay invisible to the guest but visible to the team.
The reservation listing shows dietary information at-a-glance, with custom labels (allergy-flagged, halal, VIP) badged on the row. The reservation detail card carries full notes plus historical context from prior visits.
Premium kitchens don't want allergy detail at the pass — they want it at booking, captured cleanly, with enough structure that the same word means the same thing every time. Revasi gives you the structure without making the booking form feel like an intake questionnaire.
Revasi · SevenRooms · OpenTable · Chope
| Feature | Revasi | SevenRooms | OpenTable | Chope |
|---|---|---|---|---|
| Built-in dietary, occasion & accommodation fields | Partial | |||
| Conditional follow-up on dietary patterns | Partial | |||
| Per-cover thresholds for tasting menu detail | ||||
| Custom dietary fields per experience | ||||
| Persistent dietary memory across visits | Partial | |||
| Show-in-email and show-in-listing toggles | Partial |
Compiled from publicly available materials. Features may vary by plan or region.
Three built-in fields ship by default — dietary restrictions, special occasions and accommodation. Each is toggleable, can be marked required, and is scopeable per experience. You can also build custom dietary fields (text, checkbox group, radio group, dropdown) and set conditional follow-ups that surface only when the guest types a specific pattern, like "halal" or "shellfish".
Yes. Each dietary field can be scoped per experience — required on the tasting menu, optional on à la carte, hidden on bar bookings. You can also apply a cover threshold to conditional follow-ups, so detail is asked for tables of four or fewer (where substitutions are tractable) and skipped for larger groups.
You define a pattern — for example, "halal|no pork|porkfree" or "vegan|plantbased". When the guest types something matching the pattern in a built-in or custom field, a follow-up field surfaces inline asking for the detail you need. The follow-up can also be hidden when the pattern matches if you prefer reverse logic.
Yes. Every booking links to a persistent guest profile that holds prior dietary notes, internal labels (allergy-flagged, halal, VIP, F&F) and free-text notes. When a returning guest books, the team sees prior dietary context on the reservation card before service — no re-capture, no risk of inconsistency.
Optionally. Each field has a show-in-email toggle and a show-in-listing toggle, controlled separately. You can show the field to the guest in the confirmation email so they can correct it before arrival, while keeping internal-only notes invisible to the guest but visible to the team.
Yes. The built-in dietary field accepts any free-text input, and conditional triggers can be tuned for halal, kosher, religious, allergen or any other pattern relevant to your room. Custom checkbox or radio fields can also be built to capture structured halal/kosher signals if you prefer multiple-choice over free text.
Pre-arrival revenue
The same conditional engine that powers dietary follow-ups also powers upsells — show the right add-on only when it matches the guest profile.
Revenue protection
Reconfirmation, reminders and credit-card holds — keep the dietary detail you captured from going to waste.
Platform comparison
How Revasi compares against SevenRooms, OpenTable, Chope, TableCheck and Resy on dietary, branding and commission.
Free trial. Conditional dietary fields, per-experience scoping and persistent guest profiles live on day one.
BALI · JAKARTA · SINGAPORE · KUALA LUMPUR · BANGKOK