Turn special requests into clearly priced services.
When a guest requests a tasting menu, celebration cake or transfer, your team needs clear choices, prices and service terms. Experience manages those offers as products; Manager handles reservations and Pay handles eligible payments.
A special request should be more than a reservation note.
Whether a guest chooses a cake or a special menu, everyone should understand which option was ordered, what it costs and what the team needs to prepare.
- 01Which product option was sold?
- 02Where and when is it available?
- 03What is prepaid versus due at the venue?
- 04Was the code redeemed or refunded?
Experience owns the catalog and experience-order records. Manager handles restaurant reservations, Pay handles payment and Connect handles permitted messaging.
Give every service a clear offer and price.
Organize tasting menus, cakes, transfers and table arrangements into categories, products and sellable options. Manage eligible venues, prices, inclusions, exclusions, galleries, dietary labels and descriptions in supported guest languages.
Show what is prepaid and what remains due on site.
Set each product price, with venue-specific pricing where needed. For eligible product payment requests, Rezervem Pay collects the upfront amount and records any balance due at the venue. Your team can distinguish a sent payment link from a completed payment.
Keep add-ons and each guest's menu choice with the reservation.
In Manager, staff can add Experience items that meet the venue, date, meal period and party-size rules. In supported panel deployments, guest-menu products can be assigned to individual guest rows on a reservation. À la carte choices appear when permitted by the venue's service settings and tasting-menu rules; guests who have yet to choose remain visible. Products added later by staff are recorded as payable-at-venue orders. Manager handles table capacity and Experience handles sales conditions.
Choose where and when each service can be sold.
Product-linked payment requests and staff-added reservation items are two supported sales paths. For reservation add-ons, venue, date, meal period and party-size rules are checked. The scope of other guest-facing sales channels depends on the venue's enabled setup.
Keep orders, payments and service fulfilment clear.
Track Experience orders and payment status. Eligible sales fulfilled through redemption codes without a reservation generate codes that staff can look up and redeem. Reservation-linked orders do not generate separate redemption codes. For refunds, check the payment and any redemption record together.
Define the offer. Sell it when eligible. Track delivery.
Keep every step from offer to service clear for your team.
Plan menus, reservations and service together.
See how the team can coordinate guest choices, table allocations, payments and preparations.
Common questions.
Tasting menus, cakes, decorations, transfers and other add-on services as product options where supported.
Staff can add eligible items to a restaurant reservation; these are currently payable at the venue.
No. Product payment requests can collect a predefined prepaid portion; Manager staff-added items are currently payable at the venue.
No. Codes apply to eligible voucher-based orders; reservation-linked fulfilment works differently.
No. Experience controls where and when an item can be sold, while Manager handles tables and reservations. Your team separately checks the seats allocated to the event against bookings and orders.
Product-linked Rezervem Pay payment requests and staff-added items in Manager are supported. Other guest-facing purchase channels depend on the venue's enabled setup and available rollout.
Experience guides
Practical steps for the Experience catalog.
Experience articles
How experiences and add-on sales work.
Make your add-on services easier to understand and sell.
Plan your product catalog, reservation add-ons and payment options with us.