Pilot: How do Dormakaba Oracode locks work with Guesty Locks Manager?

Requirements

• You must have an active subscription to connect your locks to Guesty Locks Manager.
• Seam must approve your setup. Locks appear in the Guesty after approval.
• Link each lock to only one property.
• Ensure lock and property time zones match for accurate code generation.
• Align device slot times with reservation times.

Connect Dormakaba to Guesty

Identify each site you want to connect to Seam and follow the steps below.

Step by step:

1. Log in to your Oracode Live account.

   Note your site name, located in the upper-right corner of the Oracode Live portal.

   

2. Contact Dormakaba Oracode Support to connect your sites to Seam. You can use the following email template:

   Please connect the following sites to the Seam Access Token: {Insert Site Name} {Insert Site Name}

3. Wait for email approval from Dormakaba.
4. Once approved, sign in to your Guesty account.
5. In the top navigation bar, click the mode selector and select Operations mode.
6. Click Field operations and select Locks manager.
7. In the top-right corner, click Add provider and select Dormakaba Oracode.
8. Click Continue.
9. Follow the prompts to enter your lock provider credentials.

Allow a few moments for the locks to import to Guesty. You will see the locks listed once the process is complete.

Match time slots and reservation times

The default check-in and check-out times of your listing must align with the programmed slots of your Dormakaba Oracode devices:

Ensure reservation times, including any ETA or ETD adjustments, fall completely within the programmed time slot. Review your Guesty Locks Manager code settings carefully, as ETA or ETD buffers impact which slot the system uses.

Limitations

• Guesty Locks Manager treats all Dormakaba locks as offline through Seam. Online features, such as real-time updates or remote management, aren't supported.
• Changing a guest's ETA or ETD generates a new code instead of updating the existing one. Send automated messages with codes close to arrival to avoid lockouts.

• Only one code can be active at a time. If you create a second code that overlaps the first, the newer code overrides the existing one once used.

  • Codes for different user levels, such as a team member and a guest, can overlap without issues.
  • Overlapping codes within the same user level cause the newer code to override the existing one.

  For example: If you create code A for March 1 to 10 and code B for March 5 to 13, code A stops working after code B is used for the first time. Because the dates overlap, code B is prioritized.

• Offline locks don't support activity logs, common doors support, code refreshing, remote functionality, or guest backup codes.
• All codes must have an expiration date with a maximum duration of one year.