Dormakaba Oracode offline locks are compatible with Guesty Locks Manager (GLM), allowing you to create and manage temporary access codes for your guests. These locks operate differently than other lock providers due to their offline nature. This article outlines the requirements and considerations to help you successfully manage your Dormakaba locks through GLM.
Requirements for getting started
- Dormakaba Oracode subscription: You'll need an active subscription to connect your locks to Guesty Locks Manager.
- Seam approval: Your setup requires approval from Seam. Your locks will appear in the GLM interface once approved.
- One property link: Each Dormakaba Oracode lock can only be linked to one property.
- Matching time zones: The lock and listing time zones must match to ensure proper code generation.
Considerations for code generation
Time slot synchronization
The default check-in and check-out times of your listing must align with the programmed slots of your Dormakaba Oracode devices:
|
Scenario |
Device slot time |
Reservation time |
Code generation result |
|---|---|---|---|
|
Example 1 |
14:00 - 10:00 |
15:00 - 11:00 |
✗ GLM will not create a code |
|
Example 2 |
14:00 - 12:00 |
14:00 - 12:00 |
✓ GLM will create a code |
|
Example 3 |
14:00 - 12:00 |
15:15 - 11:00 (including ETA/ETD) |
✗ GLM will not create a code |
For successful code generation, ensure your reservation times (including any ETA/ETD adjustments) fall completely within the device's programmed time slot.
GLM code settings impact
Your GLM Code Settings, including ETA/ETD buffers, affect which slot is used.
For example, a 30-minute ETA/ETD buffer will require a slot of 13:30 - 12:30 even if the device slot and listing check-in/out are 14:00 - 12:00.
Limitations
- No check-in time updates: Changing a guest's ETA/ETD will generate a new code (if a suitable time slot is available) instead of updating the existing one. We recommend sending automated messages with codes close to arrival to avoid lockouts.
- One code at a time: Only one code can be active at a time:
- If code A is created for March 1st to 10th and code B is created for March 5th to 13th, code A stops working after code B is used for the first time. If time and date are overlapping the code B will be used first time.
- Codes with different user levels (team member vs. guest) can overlap without issues. However, overlapping codes within the same user level will cause the newer code to override the existing one. For example, if you create a "Guest Stay" code for Jan 1-5 and another for Jan 12-19, both will work as scheduled. But if you create a third "Guest Stay" code for Jan 10-15, it will deactivate the Jan 12-19 code.
- Additional restrictions:
- No activity logs
- No common doors support
- No code refreshing capability
- No remote lock/unlock functionality
- Offline locks don’t support guest backup codes
- All codes must have an expiration date (maximum duration: one year)
Best practices
- Carefully align your listing's check-in/check-out times with the programmed slots of your Dormakaba devices to ensure successful code generation.
- Consider your GLM Code Settings, especially ETA/ETD buffers, as they directly impact slot selection.
- Have a backup plan for guest access (such as team member codes) in case of timing conflicts or reservation changes.
- Plan your guest communication carefully to provide clear access instructions and avoid confusion.
By understanding these guidelines, you can effectively leverage Dormakaba Oracode locks within your Guesty property management workflow while minimizing potential access issues for your guests.