The short answer
Rezervem Experience can catalogue paid hotel extras such as transfers, cakes and spa services and track the related orders. Rezervem Stay supports the digital guest journey, Hospitality focuses on tasks and requests, PMS handles rooms and accommodation, and POS handles orders at service points. Together they do not automatically create a room-folio posting.
A resort guest requests a cake in the room, a spa visit the next day and refreshments by the pool. To the guest this is one stay; to the team it involves different records for the purchased product, room eligibility, service preparation and settlement.
A hotel guest requests three different extra services
The cake purchase has been recorded correctly, but nobody has assigned a kitchen task. The guest assumes the hotel has everything under control because payment was made. The order still needs a verified route to the team responsible for delivery.
Confusing a catalogue order with a PMS charge or a completed Hospitality task can lead to missed service, incorrect folio balances and avoidable complaints. Having all products licensed does not by itself prove that the integrations are in operation.
Five checks across rooms, tasks and service orders
Follow the operational, financial and guest-facing details as separate checks so that no stage is assumed to be complete.
- Define each extra as a product and eligible variant in Experience.
- Confirm the authoritative room and accommodation data in PMS.
- Test the specific guest touchpoints enabled within Stay.
- Verify the staff task flow in Hospitality and service-station orders in POS.
- Reconcile payment, delivery, cancellations and any supported folio posting.
How Experience relates to Stay, Hospitality, PMS and POS
Experience keeps the sold item's catalogue and order records. Stay connects appropriate guest interactions, Hospitality tracks operational work, PMS owns accommodation, and POS manages QR or service-point ordering. The systems may share context through approved integrations, but their records and responsibilities remain distinct.
Test the particular hotel's modules, user roles, channels, release versions and supported connectors before promising automatic task creation, inventory allocation or room charges. A service request that exists in one product should be confirmed in the destination workflow.
FAQ: Does Experience manage room bookings?
No. Room inventory and stay records belong to the PMS.
FAQ: Does every Experience purchase create a task?
Not automatically. That requires a supported, verified operational workflow.
FAQ: Are POS service orders identical to Experience purchases?
No. They represent separate catalogue and ordering responsibilities.
