The short answer
Choose a documented PMS-to-lock connection for your exact model and plan, configure property mapping and message timing, then test a booking from code creation through door delivery. Include changed dates, cancellation and a fallback check. Our recommended checklist follows the documented limits; we have not performed these tests ourselves.
Check the whole connection, not just the brand
RemoteLock’s North America catalog includes Schlage Encode Deadbolt and Encode Plus, but exact SKUs, required bridges, your PMS interface and subscription entitlement still need confirmation. OwnerRez describes capability as a combination of PMS, hardware and connecting software. New RemoteLock connections are no longer offered through Hospitable’s documented integration; existing configured users may continue, and a replacement is unconfirmed.
Set property mapping and code messages deliberately
OwnerRez documents RemoteLock mapping in OwnerRez and permits one lock system per property. Configure code-generation timing and include the documented code field in your guest-message template. Our checklist: confirm which door each mapping controls and arrange messages after the appropriate code-generation step. Documentation of a request alone does not prove the lock received it.
Test booking changes and cancellation for your model
OwnerRez documents changed-date and cancellation handling for supported programmable RemoteLock locks. It gives different rules for ResortLock algorithmic codes: they cannot be canceled and date changes require a new code. It also notes an Igloo stay longer than 28 days requires shorter reservations. Our checklist: test these cases on your actual configuration before promising automatic handling.
Treat cleaner schedules as a separate requirement
RemoteLock Access Users without a schedule get 24/7 access. Recurring user and guest schedules vary by model; Schlage Encode’s documented recurring scheduling supports users but not guests. That distinction does not mean stay start/end credentials are unavailable. Verify the cleaner access window independently of the guest workflow.
Check delivery and plan a model-specific fallback
RemoteLock’s API distinguishes pending, synced and failed delivery states. Its FAQ describes valid credentials already stored on compatible, powered locks working without internet; remote changes and audits require connectivity. Offline codes do not bypass dead batteries. Our checklist: confirm your model’s fallback method and who can respond locally, then test a normal arrival and a connectivity interruption before relying on the setup. We have not tested outage behavior.
Common questions
Does a generated code prove the door is ready?
No. RemoteLock’s API documents separate pending, synced and failed delivery states. Confirm the code reached the intended device rather than relying only on creation in the software. API capability also does not establish your plan entitlement.
Will every booking change keep the same code?
Do not assume that. OwnerRez documents different behavior by model and interface; ResortLock algorithmic date changes require a new code, and those codes cannot be canceled.