Reception and guest journey

What should I test before connecting smart locks to my PMS?

Check what happens at the door when a booking changes. Use eight guest scenarios to agree acceptance criteria with your PMS and access-control suppliers before rollout.

Quick answer

Test the complete journey from reservation change to guest message to physical door. Confirm when access starts and ends, what happens after extensions, room moves and cancellations, and how staff help during failures. Use authorised test bookings and unoccupied rooms. Record both successful entry and refused entry, then approve the connection only when the results and backup procedures meet your agreed requirements.

Agree the access rules before testing

Use this hotel PMS smart lock integration test with the exact lock model, firmware, gateway and connector proposed for your property. Ask both suppliers to confirm supported actions, required guest details, UK availability, subscriptions and setup responsibilities in writing.

Define which event creates a credential, which event activates it, and which event removes access. Completing an online form, sending a key and authorising entry are separate checks. For example, GuestCompass documents check-in as the trigger for its RoomRaccoon connection; completing online check-in alone does not issue a digital key in that documented workflow.

  • Map each physical room and permitted entrance to the correct reservation; include a door the guest must never open.
  • Agree local access times, the Europe/London time zone and a test across the GMT/BST clock change.
  • Define a maximum acceptable update delay with the suppliers. Distinguish a message being sent from the lock applying the change.

Run these eight guest scenarios

The outcomes below are acceptance requirements to agree, not promises about any particular integration. Test on unoccupied rooms with authorised staff and a working backup access method.

Eight-scenario room-access acceptance matrix
Guest scenarioTest actionExpected access result
1. Scheduled arrivalIssue the credential; try entry before and at the agreed 15:00 start.Entry is refused before 15:00 and permitted from 15:00 at the assigned room and authorised entrance only.
2. Normal departureTry the same credential immediately before and at the 11:00 expiry.It works before 11:00 and stops at the agreed expiry, including relevant shared doors.
3. Stay extensionExtend departure before the original expiry and deliver any replacement credential.Access continues past the old deadline, ends at the new one and matches the message received.
4. Room moveMove the test guest from room 4 to room 7; check both doors.Room 7 works by the agreed handover time; room 4 stops working. Any transfer overlap is explicitly authorised and time-limited.
5. CancellationCancel after a credential has been issued; test it again.The cancelled credential cannot admit the guest after the agreed revocation deadline. A cancellation email alone is insufficient.
6. Next guest, same roomCreate the next stay and try both guests’ credentials.The departing guest has no access; the arriving guest gains access only within their own authorised window.
7. Guest cannot use the keyTest an undelivered message and, separately, an unavailable guest phone.An authorised staff member verifies the booking and supplies the approved alternative without granting wider access.
8. Connection or device failureWith the installer, test connection loss and a lock power/battery fault separately.Behaviour matches the documented failure mode; staff can assist. Pending changes are reconciled after recovery without restoring cancelled access.

Repeat relevant scenarios for every deployed credential type and hardware configuration. Record actual results, elapsed time, pass/fail, owner and retest date.

Verify the result at the door

Keep a test record with reservation reference, room, PMS event time, connector acknowledgement, guest-message arrival and physical access result. Avoid recording usable PINs or active key links. A successful API response is evidence of processing, not proof of the door’s final state.

Illustrative example

A fictional 12-room inn agrees a two-minute maximum for room-move updates. This is its test threshold, not a supplier performance claim.

  1. 14:00: change room

    Reception moves the test booking from room 4 to room 7. No access overlap is authorised.

  2. 14:01: check both doors

    Room 7 opens, but room 4 still opens. Record the partial result.

  3. 14:02: assess the deadline

    Room 4 still opens. Mark the test failed, investigate revocation and retest before rollout.

Prove the backup route before sign-off

Test an already-issued key separately from creating, extending or revoking one during an outage. A working existing key does not prove that updates can reach the lock. If cancellation cannot take effect while disconnected, record that limitation and agree a supplier-approved response before accepting the system.

The backup should name the responsible person, an accessible contact route and an authorised access method, such as an installer-approved spare key or locally issued credential where supported. Rehearse it with someone who did not configure the connection.

Hold rollout for unresolved access failures. Wrong-room entry, access beyond the agreed expiry, unconfirmed revocation or an unusable backup require correction and retesting. After recovery, reconcile pending changes against current bookings and check that old credentials remain invalid.

Use the results to assess RoomRaccoon

The UK hotel software integrations directory includes Room Key & Guest Access. Use your completed matrix to assess a proposed connection. A directory listing does not establish its supported actions, hardware compatibility or update behaviour.

RoomRaccoon’s hotel property management system supports reservation management and automated guest emails. Access delivery still depends on the chosen partner and configuration. Its TTLock documentation, for example, specifies PIN-compatible devices and configuration-dependent delivery. Confirm the current UK package, any upgrade or partner fees, and each required workflow separately.

Bring your lock model, access timings and completed matrix. Ask: “Can we demonstrate a room move and cancellation on this configuration, including failed updates and the backup route?”

Discuss your room-access integrations

Questions before you approve the connection

Is a PMS demonstration enough?

It helps establish supported workflows. Final acceptance also needs the proposed hardware, representative doors and guest delivery route. Record any behaviour that was demonstrated only in software.

Should early check-out remove access immediately?

Agree the rule explicitly. Test changing the reservation to checked-out before its scheduled end and verify when access actually stops, including shared entrances.

What if a workflow needs manual intervention?

Document the action, authorised role, deadline and evidence of completion. It is acceptable only if your staffing and access policy can reliably support it; mark it as manual in the matrix.

Sources and verification

Checked on 10 November 2026. The matrix is a proposed acceptance checklist; it does not report tests performed on a live lock installation.