Define the entitlement rule before checking guests in
Breakfast may be included for some rooms, paid separately for others or restricted by occupancy and date. A room number identifies the booking context but should not, by itself, decide whether a meal is included.
Document how partial arrivals, additional guests and repeated attempts at entry should be handled, so staff do not depend on a printed list or individual memory.
Use live room and entitlement lookup
With a supported Guest Access setup and an accessible property data source, the staff member searches by room number or guest name to see the relevant stay and breakfast entitlement.
Because a live search needs an internet connection, verify the room record and arriving party size before recording the check-in. The server makes the final entitlement decision.
Treat extra and outside guests separately
If more guests arrive than the entitlement permits, stop and confirm the applicable paid or complimentary policy. Do not mark an extra meal as included just to speed up the queue.
Visitors who are not staying at the property need a separate admission or payment rule. The tool should support the front-desk decision rather than silently authorizing every arrival.
Understand the offline limitation
Guest Access can queue some check-in actions after a network failure and attempt to sync them later. However room and entitlement searches do not operate offline, so new lookups still require connectivity.
A queued check-in can later be rejected by the server, and the current staff app has limitations in presenting permanently rejected queued items. Define a manual exception and reconciliation procedure for the breakfast shift.
Review the morning's exceptions
After service, reconcile included, paid, complimentary and extra admissions against the actual entitlement records available to your property. Review check-ins delayed by connectivity and any rejected syncs.
Use these patterns to improve staffing and guest communication. Explore Hospitality and confirm Guest Access integration requirements before deployment.
