Changing rooms should not erase a guest's booking
A room change should not erase a hotel guest's restaurant reservation, and checkout must end expired access. Rezervem Stay presents bookings using authorised stay context, while Manager and PMS retain their separate records. A guest may be moved because a room needs maintenance while still expecting to dine at the same time with the same party. Restaurant booking ownership should therefore not be identified solely by a room number.
Use the authorised stay and guest relationship as the durable context where supported. Define whether guests can still manage the existing dining booking after the room change and how the correct new room becomes visible.
Set the dining boundary on checkout day
Some resorts stop new restaurant reservations on the evening after departure. Others may allow late checkout or separately purchased day use. These are property policies, not an unrestricted extension of stay eligibility.
Test the old and new occupants of the same room. An expired session must not grant access to the next occupant's dining entitlements or records, including when a tab has been left open.
Define booking ownership across multiple rooms
A family in two rooms may need one restaurant table. The hotel must identify who created the joint booking, who may cancel it, and whether a connected room can withdraw only its own participants.
One possible policy allows only the booking owner to cancel the full reservation, while another room may leave its participation. This is a property decision. Test changes in party size and the staff reservation list together.
Run a clear front-desk and restaurant test
Do not test only a straightforward booking. Verify the expected consequences of changed room assignments, shortened stays, group participation and interrupted PMS access.
- Change the guest's room in the PMS and inspect the linked booking.
- Attempt an action using the former room context.
- Shorten the stay and check future dining eligibility.
- Remove one room from a multi-room party and check the guest list.
- Cancel the full booking and check both capacity and guest screens.
- Simulate a temporary PMS outage and document staff fallback.
What can Stay, Manager and PMS support?
The hotel guest app has room/stay matching and multi-room-related rules, with booking and cancellation actions. Manager manages dining capacity while the PMS is the accommodation source.
The deployed adapter decides which stay changes reach the guest app and how quickly. Test actual room changes and checkout in the property's environment; code-level capability does not prove automatic event handling everywhere. Explore Stay.
