Two independent questions need answers
First verify that a guest is authorised for the relevant stay. Then check whether a restaurant can accept the requested party and time. The PMS or approved accommodation source provides one answer; restaurant operations provide the other.
Document which team maintains room assignments, stay dates, meal times, table capacity and booking restrictions. Treating these as one unverified decision can cause both security and operational errors.
Step 1: Verify guest identity and the stay
A room number is not a password. Pair it with the hotel's approved verification information, limit access to the appropriate stay and end access when the guest is no longer eligible.
- Test active, future and completed stays separately.
- Confirm the next occupant of a room cannot see earlier guest bookings.
- Check how a room change preserves the correct stay identity.
- Test incorrect login attempts, shared data and session expiry.
Step 2: Use the property's local calendar
A guest leaving on Saturday morning may not be eligible for dinner that evening. Define the boundary according to hotel policy and local time rather than the time shown by the traveller's phone.
Test overnight flights, early departures, one-night stays and extensions. Determine when a change in the accommodation record should trigger renewed eligibility checks.
Step 3: Apply each restaurant's own rules
Even an eligible guest may find no tables. Confirm meal periods, party limits, repeat-booking restrictions and paid dining terms for each outlet.
A visible time must not be treated as a guaranteed booking. Verify that the confirmed date, time and party size match on both the guest and staff screens; check cancellation and competing requests.
Step 4: Define failures and mismatched records
An unreachable PMS is not proof that a stay does not exist. Do not silently bypass verification; provide the guest with an accurate explanation and a staff-supported fallback.
Test changed rooms, cancelled stays, paid restaurants, full capacity, multiple rooms and PMS timeouts. Record both the message displayed and the actual restaurant reservation outcome.
Keep meal benefits separate from available tables
Meal-package eligibility may originate in the PMS or another approved hotel rule source; restaurant capacity belongs to the booking system. Neither decision proves the other.
Test a guest with an active stay but no remaining dining allowance and a guest with a valid allowance when no tables are free. The staff action and guest explanation differ.
How do Stay, Manager and PMS work together?
Rezervem Stay is the guest interface, Manager owns restaurant bookings, and the PMS supplies the approved stay context. The hotel guest app has room-and-stay-date access and restaurant booking workflows subject to venue setup.
Validate the installed PMS adapter's data coverage, freshness and access policy. Explore Stay, Manager and PMS.
