Why PMS Integration Matters for Smart Access
Without a PMS integration, issuing a mobile key is a manual process. Staff receive a booking notification, log into the access control dashboard, create a credential, set the validity dates, and send it to the guest. For a 100-room hotel doing 70% occupancy, that's roughly 70 manual key-creation tasks per day — each one a potential point of failure.
A proper PMS integration eliminates all of those steps. The reservation data flows automatically from your booking engine to the access platform, which generates and delivers the digital key without any human intervention. The guest receives their key before they arrive. The front desk doesn't touch it.
The Technical Flow: Booking to Door-Open
Here's what happens in a well-integrated system:
Step 1: Reservation Created
A guest books via your website, an OTA (Booking.com, Expedia), or your front desk. The PMS records the reservation with check-in date, checkout date, room assignment, and guest contact details.
Step 2: Webhook or Polling
The PMS sends a webhook (a real-time notification) to the access control platform, or the platform polls the PMS at regular intervals. Webhooks are preferable — they're faster and create less load on both systems. The notification contains the reservation ID, dates, room number, and guest email or phone.
Step 3: Credential Generation
The access platform creates a time-bound digital key. The key is valid from 3pm on check-in day to 11am on checkout day (or whatever your property's times are). It grants access to the assigned room plus any common areas the guest should be able to enter — lobby, lift, gym, pool.
Step 4: Delivery
The credential is sent to the guest via their preferred channel: Apple Wallet, Google Wallet, a branded guest app, or a simple web link. The guest taps "Add to Wallet" and they're done.
Step 5: Stay Management
If the guest extends their stay, changes rooms, or checks out early, the PMS sends an update. The access platform adjusts the credential in real time — no staff involvement required. At checkout, the key is revoked automatically.
What Makes a Good Integration
Not all PMS integrations are created equal. The critical differences:
Real-time vs. Batch: Some integrations sync every 15 or 30 minutes. That's fine for reporting but terrible for access control. If a guest checks in at 3:01pm and the sync runs at 3:15pm, they're standing in the corridor for 14 minutes. Real-time webhooks solve this.
Two-way vs. One-way: A one-way integration pushes booking data from PMS to access platform. A two-way integration also pushes access events back — so the PMS knows when a guest actually entered their room for the first time (useful for housekeeping triggers and revenue management).
Room move handling: Guests get reassigned rooms. A good integration detects the room change in the PMS and automatically revokes the old key and issues a new one. A bad integration requires staff to manually update the access system.
Group bookings: Conference blocks, wedding parties, tour groups — these create dozens of reservations simultaneously. The integration needs to handle bulk credential creation without choking or creating duplicate keys.
The Most Common PMS Platforms
The hotel industry runs on a fragmented tech stack. The major PMS platforms you'll encounter include Oracle Opera (dominant in large chains), Mews (fast-growing in independent and boutique hotels), Cloudbeds (popular with hostels and smaller properties), Apaleo (API-first, popular with tech-forward operators), and RMS (strong in Asia-Pacific).
PassLane maintains certified integrations with 50+ PMS platforms, covering the vast majority of the market. The integration is typically configured in under an hour — API keys exchanged, property mapped, and test credentials issued.
What Breaks and Why
The most common integration failures aren't technical — they're operational:
Dirty PMS data: Room numbers that don't match between the PMS and the lock system. Guest records with no email or phone number (so the key can't be delivered). Reservations created without room assignments.
PMS updates and migrations: When a hotel upgrades their PMS version or migrates to a new platform, integrations can break silently. The access platform keeps polling an endpoint that no longer exists. Keys stop being issued but no alert fires.
Timezone mismatches: A surprisingly common problem. The PMS stores dates in UTC, the access platform interprets them as local time, and guests get keys that expire 10 hours early.
A good access platform builds monitoring for all of these scenarios and alerts staff before a guest is affected.
Choosing the Right Setup for Your Property
If you're evaluating smart access platforms, the PMS integration should be the first thing you test — not the last. Ask for a live demo with your specific PMS. Check whether the integration supports real-time webhooks, two-way data flow, and automatic room-move handling. And ask how many properties are running that specific PMS integration in production.
The PassLane platform was built API-first specifically because integration quality determines the entire guest experience. Request a demo to see how it connects to your existing tech stack.
