Drink pairings, course upgrades, chef-led add-ons, group venue cross-sell — all captured in the booking flow, before the floor team meets the guest. The right add-on at the right moment, without the awkward upsell-at-the-table conversation.
Drag-and-drop options. Per-experience scoping. Conditional logic. Live in your branded booking page.
For tasting-menu venues, paired bars and chef-led concepts, the booking is the one moment in the guest journey when intent is highest, attention is undivided, and the add-on doesn't feel like a sales pitch. Once they're seated, the conversation shifts to the experience itself — and pushing pairings, upgrades or extras can break the tone venue is built on.
Most reservation platforms treat the booking as a slot grab — name, party size, time, done. They don't give the operator a way to surface a wine pairing, a champagne reception, an additional course or a sister venue. The result is revenue left at the booking page that has to be recovered, awkwardly, on the floor.
There's also a brand cost to upselling at the table. A chef's tasting menu loses something when the server has to recite five upgrade options before service begins. Premium operators want the add-on to be visible, attractive and frictionless — but at booking, not at first course.
Revasi was built to put the upsell where it belongs. Drink pairings, course upgrades, dietary-aware add-ons, group venue cross-sell — all surfaced during the booking flow, configurable per experience, with image, price and name controls so the booking page reads as part of the brand.
These live inside the Cross-Sell & Upgrades tab in your admin. Configure them once, scope them per experience, and the booking page does the rest.
Build full pairing options with image, price and name. Offer alcoholic and non-alcoholic pairings in parallel — the guest picks the right one for them. Reorder with drag-and-drop, swap copy and pricing per experience, and surface only the pairings that match the menu being served that night.
Settings · Cross-sell & upgrades · Drink pairings
Caviar supplement on the tasting menu. Truffle service. Champagne reception on arrival. Birthday cake or anniversary plate. Build any add-on as a configurable option with price, image and description, and toggle which experiences it shows up for.
Settings · Cross-sell & upgrades · Upgrade options
Show a pairing only when the guest has selected the chef's tasting. Hide alcohol upgrades for a halal-flagged booking. Show a private dining add-on only for parties of six or more. Conditional rules use simple pattern matching against built-in or custom fields, with optional cover thresholds.
Settings · Cross-sell & upgrades · Conditional triggers
For hospitality groups, the booking page never dead-ends on a sold-out slot. If the selected venue has no availability for the requested party size or time, sister venues in your group are surfaced inline as alternatives — guests book somewhere in the family rather than bouncing. The same cross-sell continues in branded confirmation emails (bar after dinner, second restaurant, weekend brunch), with custom heading, link text and per-venue toggles.
Settings · Cross-sell & upgrades · Sister venues
5 steps · live for every booking
Add the upsell option in Cross-Sell & Upgrades — name, short-name, price, description, image. Scope it to one or more experiences (tasting menu, chef's table, à la carte). Optionally add a conditional rule, e.g. show only for parties of four or fewer.
The guest sees the option in your branded booking flow at the moment they're selecting time and party size — when intent is highest. Image, price and short description render inline. Drag-and-drop ordering controls which options lead.
Selection is locked into the reservation record. The booking confirmation email reflects the add-ons selected, with totals and any policy text. The kitchen and floor team see the add-ons in the admin reservation listing.
If the selected venue runs out of availability before the booking lands, the flow surfaces sister venues in your group as alternatives — keeping the guest inside the family rather than losing them to a "no times available" dead end. Once the booking confirms, the same cross-sell runs in the confirmation email with a custom heading and link, driving repeat visits to other venues without paid acquisition.
Pairings and add-ons appear on the reservation card, on the listing table, and (optionally) on the floor-plan view. The team preps the right wines, the right courses, the right plate-up — without anyone having to brief the venue manually.
When the upsell happens during booking, the kitchen has time to source, the cellar has time to chill, and the floor team isn't pitching mid-service. The venue runs cleaner, the guest experience is calmer, and the revenue lands without effort.
Revasi · SevenRooms · OpenTable · Chope
| Feature | Revasi | SevenRooms | OpenTable | Chope |
|---|---|---|---|---|
| Drink pairings as first-class booking option | Partial | |||
| Conditional show/hide logic on upsells | Partial | |||
| Per-experience scoping (tasting vs à la carte) | ||||
| Drag-and-drop reorder of options | ||||
| Cross-sell sister venues in confirmation email | Partial | |||
| Sister-venue cross-sell when slot is unavailable | ||||
| Image, name, price per option | Partial |
Compiled from publicly available materials. Features may vary by plan or region.
Anything that sits on top of the base reservation: alcoholic and non-alcoholic drink pairings, course upgrades (caviar, truffle, supplements), chef-led add-ons (chef's greeting, kitchen tour), occasion add-ons (birthday cake, anniversary plate), and group/private-dining surcharges. Each is configured with name, price, image and description.
Yes. Each upsell option can be scoped to specific experiences — so a wine pairing only shows on the tasting menu booking, an à la carte add-on only shows for à la carte, and a private dining surcharge only shows when the private dining room is selected. Scoping is set per option in the admin.
Yes. Conditional triggers let you show or hide an upsell based on what the guest has selected — for example, hide alcohol upgrades when "halal" appears in the dietary field, or only show a private dining add-on for parties of six or more. Triggers use simple pattern matching with optional cover thresholds.
Yes — in two places. When a guest hits an unavailable slot at the selected venue, the booking page automatically surfaces sister venues in your group as alternatives, so they can still book somewhere in the family rather than bouncing. And on every booking confirmation, a configurable cross-sell block in the email promotes sister venues — custom heading, link text, link URL, and per-venue toggles. Both surfaces are styled to match your venue brand.
Yes. Selected add-ons appear on the reservation record in the admin listing, on the reservation detail card, and on the daily activity view. Pairings, supplements and special requests are visible to the team before the guest arrives — which is the point.
Settings › Cross-sell & upgrades. Update the price, swap the image, change the description, reorder by dragging. Changes apply to new bookings immediately; existing bookings keep the price they were quoted at.
Revenue protection
Reconfirmation, reminders and credit-card holds — protect the revenue your upsells just earned.
Service preparation
Conditional dietary fields with halal, vegan and allergy logic — the same engine that powers conditional upsells.
Platform comparison
How Revasi compares against SevenRooms, OpenTable, Chope, TableCheck and Resy on upsell, branding and commission.
Drink pairings, course upgrades and cross-sell live in your branded booking flow on day one.
BALI · JAKARTA · SINGAPORE · KUALA LUMPUR · BANGKOK · & THE REST OF ASIA