
A hotel lock only becomes useful to reception when the property management system can deliver a credential tied to room, arrival and departure. Integration exists in several generations, from encoder cables to real-time mobile key APIs.
In a hotel, the lock platform and the property management system must agree on who stays in which room, from when until when, and what credential opens it. The traditional architecture is offline-by-design: the PMS sends room and stay data to a front-desk encoder, which writes an RFID keycard for the assigned room and dates; the lock itself never touches the network. A newer architecture delivers mobile keys online, with the PMS or a booking engine triggering a key message through a credential service to a guest phone, sometimes with locks reached through gateways for live revocation. Between those poles sit encoder-connected middlewares, kiosk integrations and unified hospitality platforms. This guide explains the integration models, the role of encoders, common interface styles and the acceptance tests hospitality buyers should run. Supported PMS interfaces and middleware for each hotel lock platform are confirmed in writing per quotation.
| Encoder model | The PMS feeds a front-desk encoder that writes room and date data to an RFID card; locks stay offline and validate the card themselves. |
| Online mobile key | A credential service receives stay data from the PMS and pushes a phone key, often with gateways enabling live updates at the locks. |
| Interface styles | Integrations use vendor middleware, documented APIs or PMS marketplace connectors; raw database access is not a professional integration. |
| Stay lifecycle | Check-in issues, room moves re-issue, early checkout revokes and extensions update validity; every path must be tested end to end. |
| Shared systems | Elevator floors, energy-saving switches, parking and common doors can read the same credential when planned together. |
| Offline resilience | Guest-room locks validate credentials at the door by design, so a PMS or internet outage never blocks a guest holding a valid key. |
| Our policy | We identify the lock platform, encoder family and certified PMS or middleware options per project rather than claiming universal compatibility. |
Encoder-based keycard systems remain the robust default for most hotels; online mobile key suits brands that want digital check-in and can support gateway infrastructure, while mixed deployments keep cards as the universal fallback.
| Property type | Integration approach | Why it fits |
|---|---|---|
| Mid-scale hotel | PMS-linked encoder and RFID keycards | Reliable offline doors, familiar reception workflow. |
| Luxury or lifestyle brand | Mobile key plus cards, gateways on floors | Digital-first guest experience with card fallback. |
| Serviced apartments | Online codes or mobile keys via management software | Remote check-in without a 24-hour desk. |
| Resort or large campus | Lock platform middleware to the PMS estate | Common doors, elevators and rooms on one credential. |
| Small guesthouse | Standalone encoder or app-based issuance | Low infrastructure, simple training, modest budget. |
| Group with multiple PMS brands | Middleware or credential hub architecture | One key service normalizes several PMS interfaces. |
PMS integration reaches beyond the guest-room lock. Elevators, energy-saving units, parking barriers, spas and floor lounges can consume the same stay credential when the lock platform is specified holistically.
| Opening | Typical door | Lock approach |
|---|---|---|
| Guest-room door | Fire-rated timber or steel door with hotel mortise | RFID lock from the PMS-fed encoder, offline validation. |
| Floor elevator | Cabin reader tied to room floor rights | Card or phone enables only the guest floor during the stay. |
| Hotel main entrance | Glass entrance with after-hours control | Guest credential opens perimeter during the stay window. |
| Energy-saving switch | Wall switch inside the guest room | Card insertion arms power; coordinate card format early. |
| Spa or club lounge | Amenity door with scheduled access | Stay package flags drive amenity eligibility in the PMS map. |
| Back of house | Staff doors with master hierarchy | Separate staff key plan issued through the same platform. |
Hospitality integrations fail on assumptions, not on locks. For named platforms we provide the documents below so the hotel IT team, PMS vendor and installer share one reference before cabling begins.
| Component | Typical logic | Notes |
|---|---|---|
| Interface document | How stay data enters the lock platform and its field mapping. | PMS and middleware teams need exact payload definitions. |
| Encoder specification | Encoder model, connection, card format and failover procedure. | Reception must issue keys even if the PMS link is down. |
| Mobile-key flow | Invitation channel, phone requirements and gateway behavior. | Guest support scripts depend on this flow. |
| Lifecycle matrix | Check-in, room move, extension, checkout and no-show handling. | Every case must be proven during acceptance testing. |
| Sub-system list | Elevator, energy switch and common-door compatibility. | Late additions are expensive once cabling is finished. |
No in the dominant hotel design. Traditional RFID guest-room locks are offline: reception encodes room number and stay dates onto a keycard through a PMS-connected encoder, and the lock validates the card by itself with no network connection, so a WAN outage never blocks a guest holding a valid card. Online mobile-key systems deliver phone credentials through a credential service and may use floor gateways for live revocation, but even those platforms typically keep the last valid credential working at the door. This offline resilience is deliberate hospitality engineering. When comparing systems, buyers should ask what happens to issued credentials during a PMS, network or gateway outage; the behavior for each platform is documented in writing per quotation.
Through one of several integration patterns. In the encoder pattern, the PMS prints or encodes via a local encoder module using a vendor driver or middleware, exchanging room, arrival and departure fields at the front desk. In online patterns, the PMS calls a credential-service API when reservation events occur, and the service delivers mobile keys or updates online locks via gateways; larger groups sometimes use a central credential hub that normalizes several PMS brands. Field mapping covers room number, stay dates, guest count flags and amenity rights. Direct database edits are not considered an integration because they bypass validation and support contracts. We provide the interface specification and support the PMS vendor’s technical questions during the project.
Yes on platforms supporting online mobile key: after the reservation is checked in or pre-arrival rules trigger, the PMS or credential service sends an invitation by message or email, the guest installs or opens the required wallet or app, and a key tied to room and dates appears on the phone — enabling true keyless arrival when paired with after-hours entrance rights. Practical conditions apply: supported phone models, gateway coverage at the doors, identity verification policy of the hotel and fallback handling for unsupported devices or dead batteries, which is why most properties keep RFID cards available at the desk. Properties should pilot the complete pre-arrival flow including room moves. Supported mobile-key channels and PMS combinations are confirmed per project in writing.
In an encoder system, reception simply encodes a fresh card for the new room and the old card stops granting the original room because its room and date data no longer matches; lost or old cards can be killed from the lock audit using a replacement card procedure. In online mobile-key systems, the PMS event triggers revocation or re-issue through the credential service, and gateways push the update to locks; without a gateway the change applies at the next sync, which is why gateway coverage matters for live room moves. Early checkout revokes the stay credential immediately online or renders the card invalid by date and room mapping. These lifecycle cases — move, extend, early checkout, no-show and card loss — should all appear in the acceptance test script for the integration.
Yes when the project is specified as one credential system: the same RFID card or mobile credential can carry room rights, floor rights for the elevator reader, after-hours entrance, parking barrier access and energy-saving switch recognition, because each sub-system reads the same encoded data according to its own rules. The catch is coordination: elevator controllers, energy-saving switches, parking systems and locks often come from different vendors, and their card format, timing and connector requirements must be agreed before cabling. Late requests (“can the card also do the spa?”) can require hardware changes. We recommend a one-page credential matrix listing every reader in the building, confirmed against each vendor during the design phase and validated in the site acceptance test.
Send your PMS edition, property layout and preferred credential model with your RFQ. We provide the interface document, encoder and gateway architecture, lifecycle test script and coordination support for elevator and amenity sub-systems.
Request Spec Sheet + QuoteTechnology overviewLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team