The booking is the beginning. The integration does the work.
A useful integration turns a reservation into the right permission. A dependable one also handles every change to that reservation.
Map rooms to real doors
The PMS knows a room or property identifier. The access platform knows devices and access groups. The integration must connect the two, including the building entrance, room door and any shared areas the guest is entitled to use.
Treat that mapping as operational configuration, with an owner and a review process. A booking can be accurate while a mistaken mapping still issues access to the wrong door.
Define when access may be released
Reservation creation is not always the right trigger for usable access. Room readiness, required registration or payment steps may come later. Separate credential creation from credential delivery and the time at which it becomes valid.
Ask where each rule lives. If the PMS, guest portal and lock platform all have a check-in time setting, document which one controls the door and how time zones are handled.
Test changes, not just new bookings
A room move should give the guest the new access and remove the old permission as intended. An extension should change the end time. A cancellation should prevent an unused credential from becoming a problem.
Ask the provider how it detects missed updates, retries failed requests and avoids creating duplicate credentials. A dashboard should distinguish a requested action from one confirmed by the downstream system.
Use a small acceptance checklist
Before rollout, walk through a new booking, same-day arrival, date change, room move, cancellation and failed delivery. Repeat the relevant cases with a lock or gateway disconnected. Record who receives an alert and who resolves it.
These are evaluation questions, not a promise that every listed integration supports every workflow. Confirm the capabilities for the exact PMS version, lock model and product plan.
Sources & further reading
Based on official documentation and product descriptions. These are general explanations and evaluation questions; support depends on the specific hardware, provider and configuration.
Explore the provider landscape ↗