Being on the property does not grant room rights
Overnight hotel guests and day visitors can use some of the same facilities, but they do not share room and meal entitlements. Rezervem Stay is the stay-linked guest channel; other Rezervem products can serve separately eligible visitors. Resort restaurants, spas and beaches can serve overnight and day guests. Being physically at the hotel does not establish that a visitor occupies a room or has a meal entitlement.
Distinguish access for accommodation-linked services from access to public and independently purchased services, so one guest's room information is not exposed.
Classify services by access category
Some actions require an active stay, such as charging a meal to the room or using a package benefit. Others can be sold as standalone day-use packages.
General directions, public menus and opening hours may be shown without requesting room information. Define rights per action, not by forcing everyone to complete the same form.
Ask for the right information at the right moment?
Displaying a restaurant menu does not need a room number. Processing a refund may require verifying who owns the original payment.
A room-account charge needs proper verification of the active accommodation and charging authority. A day visitor paying independently is a separate collection flow.
Do not carry rights between visitor types
A guest may visit for a day and stay overnight a month later. Historical guest contact does not entitle an old day-use session to access the newly assigned room.
Check property, identity, dates and active permissions when a visitor's role changes. An old QR link or shared token must not permit unauthorised charging.
How Rezervem products divide the responsibilities?
Stay is the stay-related guest journey; Experience owns available saleable services and their orders, while Pay handles collections.
Manager handles dining reservations and QR Order manages service-point orders. Confirm actual supported access and payment flows for each hotel.
