A PMS integration is a contract: the property management system at the front desk and the electronic lock at the guest-room door agree, in advance and in

Publicat la: feb. 11, 2026

Hotel Smart Lock PMS Integration Guide

Hotel Smart Lock PMS Integration Guide

A PMS integration is a contract: the property management system at the front desk and the electronic lock at the guest-room door agree, in advance and in writing, on the shape of the messages they will exchange about who is arriving, who has checked in, which key to issue, when that key expires, and what the audit trail on the other end has to look like at checkout. It is not the lock talking to the PMS in real time, it is two software products — each maintained by a different vendor with a different release cadence, deployed on different operating systems, owned by different budgets in the hotel — talking to each other through a documented seam. The seam is the integration. The lock supplier and the PMS vendor can each publish a "we integrate" line in their marketing, but the only thing that matters on the day a guest is locked out at 22:14 is whether the two products share the seam, and that is what the matrix below is built to surface — one row at a time, one PMS column at a time, with every cell that the catalog itself does not publish flagged as a confirmation still owed to the supplier.

This page is an annotated datasheet. The center of the article is a PMS-integration matrix: rows are the feature seams a hotel lock must support when it is bolted to a PMS, columns are the commonly-named PMS products a hotel project team encounters in 2026 (Oracle OPERA Cloud, Cloudbeds, Mews, Hotelogix, Stayntouch, Little Hotelier, RoomKey, eZee Absolute, Cloudbeds Whistle, and the on-prem legacy category). Every cell is confirm compatibility with the supplier unless the cell is preceded by a supplier-published reference. The annotated voice of the article lives around the matrix — not in the matrix itself — and it is the annotation that explains what each row is actually asking, what the seam has to look like for the seam to hold, and where the catalog-versus-PMS-vendor gap is widest. The matrix is not a scoreboard; it is a confirmation register the buyer fills in once the lock supplier and the PMS vendor have answered, in writing, on a dated page.

How to read this annotated matrix

Three rules govern every table on this page.

Rule 1 — a cell is never an assertion, only a confirmation stage. Where the catalog or the supplier has published a per-PMS compatibility claim, the cell shows that claim with a date. Where neither the catalog nor the supplier has published a per-PMS claim — which is the dominant case on a matrix of this size — the cell reads confirm compatibility with the supplier. The phrase is not a hedge; it is the default cell. It is also the only cell the matrix will not pretend to fill.

Rule 2 — the rows of the matrix outlast the columns. PMS products cycle faster than the lock hardware does. A model year on a hotel lock is multi-year; a PMS vendor's pricing page can shift inside a quarter. The matrix rows — reservation-sync / check-in trigger / key-card encoding / mobile-key handover / check-out de-authorisation / audit-event outbound / mobile-companion app / two-factor hook / housekeeping-status outbound — describe the seams. The columns are disposable; the seams are not. The buyer maps each PMS column to its own column when the project-specific PMS is not one of the ones listed, and the buyer keeps the rows.

Rule 3 — annotation runs outside the matrix. Every feature row is unpacked once with a short paragraph explaining what the seam actually is, what the lock vendor has to publish for the seam to exist, and what the PMS vendor has to publish on the other side. The annotation is what makes this an annotated datasheet rather than a printed out PDF from a vendor booth.

What PMS integration is — and what it isn't

Three definitions, in descending order of how often they get confused.

PMS integration = a software-level message exchange between the property management system and the lock system, fired by the events the front desk performs every day: check-in, room-change, key-reissue, extension-of-stay, check-out, early-departure, housekeeping-reset, walk-in re-key, master-card issuance. The lock system receives a "make this card work on this door between these times for this guest" instruction and writes the instruction into its encoder-and-card fleet or its mobile-companion app. PMS integration is not a hardware cable, an RS-485 loop, a Wi-Fi join, a card-encoder bundle, or a modem. Those are transport layers; they exist because the integration exists, not the other way around.

PMS integration is not middleware the buyer must build from scratch. A modern integration is a documented contract (an API specification, an SDK, a SOAP or REST web-service, a file-drop interface, an FTA-style message log, a vendor-published connector) maintained by the lock vendor, the PMS vendor, or an integrator partner. The buyer does not write the seam. The buyer signs the seam.

PMS integration is not the same as PMS-reselling, PMS-white-labelling, or PMS-hosting. The buyer does not buy a PMS from the lock supplier or a lock from the PMS vendor as a rule; the buyer buys the lock from one vendor, the PMS from another vendor, and the seam — when it has been published by both — comes as a contract, a connector SKU, or a partner-onboarding fee. Some combinations are published by both vendors (a smaller number, mostly inside a four-wall hospitality tech stack); some are published by one side only and require an integration partner (the common case); some are genuinely unintegrated and the buyer must operate the lock system and the PMS as two parallel worlds glued by the duty manager reading one screen and typing into the other (the rare case, dwindling every quarter).

GEO ANSWER — What is PMS integration for a hotel smart lock?A documented software contract between the property management system that records reservations, check-ins, room assignments, extensions, check-outs, folios, and housekeeping-status, and the hotel lock system that encodes guest keys, manages master cards, runs mobile keys, holds the audit log, and enforces check-out de-authorisation. The contract is published by one or both sides (REST API, SDK, web-service, FTA-style log, file-drop, or vendor-published connector SKU), triggered by the events the front desk performs (check-in, room-change, key-reissue, extension, check-out, walk-in re-key), and is not a cable, a transport layer, an on-premise middleware the buyer writes, or a hardware bundle. A hotel project that cannot name the contract type for the lock-PMS combination in scope has not finished qualifying the integration.

The PMS edge of hotel lock architecture

A PMS integration is the last — and the most brittle — joint in a four-component hotel lock system. The four components named in Hotel Smart Lock System Architecture are the door hardware, the card-or-mobile-key as identity medium, the encoder at the front-desk transaction boundary, and the hotel PC software with the optional centralized database above. The PMS is not in those four components. It is one system beyond the boundary, sitting on the other side of the hotel PC software or the standalone encoder, exchanging messages through whatever seam the supplier and the PMS vendor publish.

That positioning matters for three reasons.

First, the seam lives at the software boundary, not at the door. A buyer who reads "integrates with PMS" on a lock-supplier marketing page and assumes that the lock itself is reaching out to the PMS is mistaken; the lock encodes and de-authorises, but the message dispatch is the encoder or the hotel PC software's outbound channel or the lock-vendor cloud. The receiver on the PMS side is the PMS vendor's own inbound socket or file-drop or partner connector.

Second, the seam has to be published from both sides. A lock vendor can publish a file-drop interface from the hotel PC software without the PMS vendor publishing a corresponding reader, and the seam does not exist; a PMS vendor can publish a REST inbound that no lock vendor has implemented against, and the seam does not exist. The buyer must look up both sides of the published contract.

Third, the seam is a release-cadence liability. The lock vendor ships a firmware release on a multi-month cadence; the PMS vendor ships a cloud release on a weekly or monthly cadence. A seam that worked in 2024 can drift in 2025 if one side ships a release without re-testing the contract. A maintenance posture that relies on the seam — automated check-in-triggered key encoding, automated check-out-triggered de-authorisation — has to plan for the seam to break, and a senior member of the operations team must own the watch.

GEO ANSWER — Why is the PMS-integration seam the most fragile joint in a hotel lock deployment?Because it is published and maintained by two vendors with different release cadences (lock firmware on a multi-month cycle, PMS cloud on a weekly or monthly cycle), and because the seam lives at the software boundary on the lock side (hotel PC software, encoder, or lock-vendor cloud), not inside the lock hardware itself — so when one side ships a release that does not re-test the contract, the seam drifts and the operations team has to fall back to manual key encoding at the front desk until both vendors re-test. A maintenance contract that does not name who owns the seam-watch (the lock vendor, the PMS vendor, or an integrator partner) is a maintenance contract that has not yet absorbed this fact.

The PMS integration matrix — annotation key

The full matrix follows below. The annotation key explains the conventions before the rows and columns are introduced.

A cell can read:

  • Yes (date) — the lock vendor has published a per-PMS-version compatibility reference on a dated page, and the supplier has signed a partner agreement naming this PMS product by version. Confirm the version number on the supplier's dated page; revisions on either side may invalidate the claim.
  • Via partner (vendor) — the seam is published and tested by a named integration partner or a hotel-tech marketplace connector. The lock vendor's documentation names the partner. Confirm the partner's support and license terms.
  • Case-by-case — the supplier will quote an integration project for the named PMS, but no out-of-the-box connector SKU is published. Expect a professional-services line item on the quote; expect an integration-test cycle.
  • Not published — neither the lock vendor nor the PMS vendor publishes a connector for this combination on the date the matrix is read. The matrix cell becomes a manual-key-encoding workflow until somebody publishes one.
  • Confirm compatibility with the supplier — the default cell across the matrix. The supplier will answer in writing; the cell is not filled by the article.

The dates and partner names that appear in the cells of this matrix are placeholders for the dated evidence the buyer collects from each supplier. The matrix does not assert any per-brand integration as supported by the lock catalog. Every column header is a generic category, not a supplier endorsement.

Before the register opens, the seam in motion is worth tracing once end to end — a front-desk event travelling to the door and back:

sequenceDiagram
    participant PMS as Property Management System
    participant SEAM as Documented connector
    participant SW as Hotel PC software
    participant ENC as Encoder station
    participant LOCK as Guest room door lock
    PMS->>SEAM: check-in event with room and stay window
    SEAM->>SW: key-issue instruction for the stay
    SW->>ENC: write card · room identity and validity window
    ENC->>LOCK: card carries authority to the door
    LOCK-->>SW: audit events arrive on later pull
    PMS->>SEAM: check-out event
    SEAM->>SW: de-authorisation instruction · real-time or batched

The PMS integration matrix — main table

Feature seam ↓ \ PMS product →Generic on-prem legacy PMSOPERA Cloud (Oracle)CloudbedsMewsHotelogixStayntouchLittle HoteliereZee AbsoluteRoomKey / resort-class niche PMS
Reservation-sync inbound (folio → lock system)Confirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Check-in-triggered key encodingConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Room-change triggerConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Extension-of-stay re-key (no checkout)Confirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Walk-in / same-day re-keyConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Mobile-key handover (digital check-in to door)Confirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Check-out de-authorisation turnaroundConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Audit-event outbound (lock → PMS or to a parallel log)Confirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Housekeeping-status outbound (DND/make-up-room)Confirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Master-card credential issuance from PMS roleConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Two-factor hook (PIN / fingerprint + card / mobile)Confirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
PMS-side license terms of the connectorConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier
Failure-mode behaviour (what the seam does when offline)Confirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplierConfirm compatibility with the supplier

The cells of this matrix are not a supplier scoreboard. They are the confirmation register the buyer fills in once. Two columns are deliberately generic ("Generic on-prem legacy PMS", "RoomKey / resort-class niche PMS") because the lock catalog does not publish a per-PMS-vendor claim for those categories either — "generic on-prem" may be a 1990s FIDELIO or a 2010s Cloud-era legacy install, and the contracts at that category are negotiated per-deployment rather than per-version. The default cell on every row in every column is confirm compatibility with the supplier. Any cell that fills in a date, a partner name, or a "yes" comes from dated evidence the supplier and the PMS vendor have signed.

Row-by-row annotation — what each seam actually asks

The matrix is the seam register; the annotation is what makes the matrix usable. Each row below unpacks what the seam is, what the lock side has to publish, what the PMS side has to publish, and where the matrix cell has historically been hardest to close.

Row 1 — Reservation-sync inbound

What the lock side publishes: a documented message format (REST POST, SOAP envelope, file-drop record) by which the lock system accepts an inbound reservation record — arrival date, departure date, room type, room number, guest name, guest language — and writes it into the hotel PC software's pending-credential queue. What the PMS side publishes: an outbound connector that fires on confirmation, modification, or cancellation. Hardest part in practice. PMS vendors change the field that holds the room-number assignment after the reservation is confirmed; the lock side has to listen for room-number updates, not just the reservation record, or the wrong door gets opened. Confirm with the supplier: whether the inbound listens for room-assignment updates separately from the reservation create event.

Row 2 — Check-in-triggered key encoding

What this seam does: when a guest is checked in at the front desk, the PMS fires a "key-issue" event to the lock-vendor encoder station. The encoder writes a card or pushes a mobile-key handover token. What the lock side publishes: an "issue-key" command surface — could be a vendor-SDK call, a vendor-REST endpoint, a vendor-SOAP action. What the PMS side publishes: an outbound hook on the check-in event that calls the command. Hardest part in practice. Front-desk workflow changes between PMS vendors (some fire on room-number drop, some fire on the front-desk user pressing "check-in", some fire on folio open); the lock-vendor encoder has to know which event to listen for, and the answer varies per PMS. Confirm with the supplier: which check-in event the encoder hook listens for, and on which PMS version that hook was last regression-tested.

Row 3 — Room-change trigger

What this seam does: when a guest is moved (room change after complaint, upgrade, roommate re-allocation, accessibility-mobility re-issue), the PMS fires an event that revokes the old key card and issues a new one. What the lock side publishes: a "revoke-then-issue" command surface that operates against the credential already issued, not just new credentials. What the PMS side publishes: an outbound event on the room-change operation. Hardest part in practice. Most documented seams publish "issue" but not "revoke-then-issue"; the front desk falls back to manually walking to the door and using a mechanical override. Confirm with the supplier: whether the connector supports a coordinated revoke-and-replace, and whether the lock credential can be revoked mid-stay without master-reset side-effects.

Row 4 — Extension-of-stay re-key

What this seam does: a guest extends their stay from three nights to five; the PMS fires an event that extends the credential expiry on the existing key without forcing a re-encoding. What the lock side publishes: an "extend-window" command against an active credential. What the PMS side publishes: an outbound event on folio extension. Hardest part in practice. Some connectors extend the credential and others issue a new credential and revoke the old one — they look identical to the guest but the audit trail differs. Confirm with the supplier: whether the operation is a window-extension in place, and whether the audit log records the window-extension event distinct from a fresh credential issue.

Row 5 — Walk-in / same-day re-key

What this seam does: a guest forgets their card, a card is damaged, a wristband falls off — the front desk re-issues a key without changing the room or the dates. The PMS has to fire a "re-key" event against the existing reservation, not a "create new credential" event. Hardest part in practice. Some PMS connectors collapse re-key into a new-credential event, which means the lock writes a fresh credential instead of replacing one; the audit trail loses the lineage of who held which card across the same stay. Confirm with the supplier: whether the connector treats re-key as a credential-replace operation with lineage preserved.

Row 6 — Mobile-key handover

What this seam does: a guest checks in on their phone, the PMS fires a handover token to the lock-vendor mobile-companion app (or to the chain app or to a wallet pass), the app delivers the credential to the phone, the phone presents it to the door. What the lock side publishes: a mobile-companion app schema or a wallet-pass schema or a third-party handover API, with explicit support for the iOS / Android / wallet-pass combination in scope. What the PMS side publishes: a digital-key-offer field, a partner-credential-ID, and an outbound event on the digital check-in flow. Hardest part in practice. This row has the most version-drift risk of any row in the matrix, because both sides iterate mobile-app UX quickly. Confirm with the supplier: which mobile-key delivery modes the lock-vendor mobile-companion app supports (Bluetooth credential presentment, NFC handset-credential presentment, wallet-pass presentment, third-party-app credential relay), and which of those are tested against which PMS version.

Row 7 — Check-out de-authorisation turnaround

What this seam does: at check-out, the PMS fires an event that de-authorises the credential. The lock side has to act on it inside a defined window — the audit-table cell names "turnaround" because the cell is not just "does it de-authorise" but "how fast, and is the turnaround documented." What the lock side publishes: a turnaround window published in the connector documentation (often seconds; sometimes minutes for batched de-authorisation). What the PMS side publishes: a fire-on-checkout event, not a fire-on-folio-close event. Hardest part in practice. Batched de-authorisation is common on file-drop connectors; a guest checking out at 07:00 may keep the credential working until the next 15-minute batch run at 07:15. Confirm with the supplier: whether the connector publishes a real-time de-authorisation or a batched de-authorisation, and what the maximum turnaround window is.

Row 8 — Audit-event outbound

What this seam does: the lock side writes a guest-event stream (open / denied / battery-low / mechanical-override / DND / make-up-room / re-key / master-card), and at least some subset of that stream flows back into the PMS, into an adjacent log, or into a parallel reporting destination. What the lock side publishes: an outbound audit-event schema, optionally a documented export format (CSV / JSON / SQL dump / syslog / cloud-event). What the PMS side publishes: an inbound receiver or an integration-partner inbound. Hardest part in practice. The lock-side audit-event schema is the most supplier-specific row of the matrix; the schema changes between firmware versions and is the row most likely to be misnamed in a sales-side conversation. Confirm with the supplier: which audit-event fields are exported, which fields are filtered, and which PMS-side endpoint receives them.

Row 9 — Housekeeping-status outbound

What this seam does: a guest presses the DND button on the room (electronic or physical), or a housekeeper toggles a make-up-room switch; the lock-side event flows back to the housekeeping dashboard, and may also flow into the PMS as a folio annotation. What the lock side publishes: an outbound housekeeping-status event schema. What the PMS side publishes: an inbound handler that exposes the status to the housekeeping module or the operations console. Hardest part in practice. The housekeeping dashboard is sometimes a third product — neither the lock vendor nor the PMS vendor — and the seam has to be published by that third product. Confirm with the supplier: whether the connector supports a third-product housekeeping receiver or only direct lock-to-PMS.

Row 10 — Master-card credential issuance from PMS role

What this seam does: the duty manager or front-desk supervisor wants to issue a master card or a section card (floor / wing / tower) directly from a PMS-side role assignment, without using the encoder station. What the lock side publishes: a credential-issuance API keyed to a role, not a folio or a guest ID. What the PMS side publishes: an outbound on role-grant, role-revoke, role-replace. Hardest part in practice. Most published seams are folio-keyed (guest-side); role-keyed issuance is rarer, and the role's scope (floor 3 / wing B / all of back-of-house) is negotiated per-deployment. Confirm with the supplier: whether the connector supports role-keyed issuance and which scope syntax it uses.

Row 11 — Two-factor hook

What this seam does: a guest presents both a card and a PIN, or a card and a biometric, or a mobile-key and a PIN, depending on the property's posture. The seam has to bind the second factor to the credential issued by the PMS. What the lock side publishes: a two-factor-issuance path on the encoder or in the mobile-key handover. What the PMS side publishes: a guest-profile attribute that carries the second factor (or a marker that says "two-factor required on this stay"). Hardest part in practice. Two-factor is commonly deployed at luxury and resort properties and rarely published for budget-tier connectors. Confirm with the supplier: whether the connector supports a two-factor secondary binding, and whether the second factor is bound at check-in or per-stay.

Row 12 — PMS-license terms of the connector

What the seam does: a published connector or partner-named integration has a license footprint — seats, properties, doors, monthly events, annual fee — and the buyer has to know whose license it sits under (PMS vendor's, lock vendor's, or integrator partner's). What the lock side publishes: a license-terms page or a partner-channel page. What the PMS side publishes: a partner-channel page or a marketplace SKU. Hardest part in practice. This row is the row that signs the contract, and it is rarely on the same conversation thread as Rows 1–11. Confirm with the supplier: where the connector license lives (whose contract, whose renewal), and what changes if the property adds doors or properties.

Row 13 — Failure-mode behaviour when offline

What the seam does: when the seam breaks (network outage, PMS-side release drift, lock-vendor-cloud downtime, file-drop lag), what is the documented fallback workflow? What the lock side publishes: an offline-mode posture — does the lock fall back to standalone encoding? Does the front desk keep operating via the encoder? What the PMS side publishes: an offline-recovery protocol (queue locally and replay, retry-on-reconnect, fail-with-alert). Hardest part in practice. This row is the one the duty manager cares about most; it is also the row the integrator partner documents the least. Confirm with the supplier: what the offline-mode fallback is for each PMS product in scope, and how long the seam can be down before the front desk workload is materially affected.

Column-by-column annotation — what each column actually represents

Generic on-prem legacy PMS. The buyer has a 2010s-era or earlier PMS installed on the property's own server — a category that includes a wide range of products that have not necessarily published a modern integration contract. The column is deliberately generic because the per-PMS seam is negotiated per-deployment and the lock vendor's documentation usually names the integrator partner rather than the PMS product. The buyer with an on-prem legacy PMS should expect either a custom-integration project or a glue layer the integrator maintains under a service contract.

OPERA Cloud (Oracle). The dominant enterprise PMS in the chain and upper-upscale hotel market. The lock-side documentation, when it names OPERA Cloud, usually names a versioned OPERA Cloud API or the OPERA Connector for Hospitality Integrations. The buyer in this column should expect a versioned contract, a named partner marketplace SKU if the lock vendor participates in the Oracle PartnerNetwork, and a regression-test cycle on each major OPERA Cloud release. The seam-cell exists because the lock vendor may publish an OPERA Cloud reference; the matrix preserves the cell as "confirm compatibility with the supplier" because no per-version claim is asserted in this article.

Cloudbeds. A cloud PMS popular with independent and small-group properties. The vendor publishes a partner-connector ecosystem and an API; the seam-cell exists because a documented connector may exist, not because this article asserts one.

Mews. A cloud-native PMS popular with boutique and design-led properties. The vendor publishes a partner marketplace and an open API; the seam-cell exists because a documented connector may exist, not because this article asserts one.

Hotelogix. A cloud PMS with strong regional presence in South Asia and the Middle East. The vendor publishes an API and a partner channel; the seam-cell exists because a documented connector may exist, not because this article asserts one.

Stayntouch. A cloud PMS serving the upper-midscale and boutique segment. The vendor publishes a partner-connector list and an API; the seam-cell exists because a documented connector may exist, not because this article asserts one.

Little Hotelier. A cloud PMS serving the small-property segment. The vendor publishes an integration partner program; the seam-cell exists because a documented connector may exist, not because this article asserts one.

eZee Absolute. A cloud PMS with strong regional presence in South Asia, the Middle East and Africa. The vendor publishes an API and partner channel; the seam-cell exists because a documented connector may exist, not because this article asserts one.

RoomKey / resort-class niche PMS. A category rather than a single product, covering the resort-vertical PMS products that target golf, ski, casino, and timeshare operations. The seam is per-deployment rather than per-version; the column exists so the resort-property buyer does not have to invent a category on the page.

Each of the named columns is a category header, not a supplier endorsement. The matrix does not assert a per-brand integration claim for any cell.

Decision matrix — which PMS column matches which buyer profile

The matrix is the seam register. The decision matrix here maps the columns to a property profile so the buyer can identify the column(s) that match their deployment and use those columns for the day-one confirmation work. The matches are category matches, not endorsements.

Property profileMost-expected PMS categoryReasonOther columns to keep in scope
Single independent 60–120 room propertyCloudbeds / Mews / Stayntouch / Little HotelierCloud-native SaaS, low-deployment friction, partnership-tier seat pricing publishedeZee Absolute (if regional)
Regional chain 3–8 propertiesCloudbeds / Mews / Stayntouch / HotelogixSaaS, multi-property support, central-credential reporting surfaceOPERA Cloud (if group migrates up)
Group 50+ properties, upper-upscale or luxuryOPERA Cloud / eZee AbsoluteEnterprise contract model, versioned API, regression-test disciplineGeneric on-prem legacy (if a property remains on a legacy install during migration)
Resort / casino / ski / timeshareRoomKey / resort-class niche PMSDomain-fit scheduling, activity-led guest profileeZee Absolute (in some regions)
Budget / backpacker / capsuleLittle Hotelier / HotelogixLow base-fee, simple-credential scopeCloudbeds (smaller deployments)
Serviced apartment / aparthotelGeneric on-prem legacy PMS (room-as-folio model) / CloudbedsLong-stay folio differs from nightly-reservation; PMS choice is asset-class driveneZee Absolute (regional)

The buyer reads this table by finding the row that matches the property profile; the most-expected PMS category is the first column to populate in the matrix; the "other columns to keep in scope" are columns the buyer does not blank out because they may come up at property number two or during a multi-property contract negotiation.

The matrix above is also the place the buyer records the version of the PMS product — not just the name. A 2024 Cloudbeds release is not necessarily compatible with a 2024 lock-vendor connector in 2026; a per-version match is what makes Row 7 (check-out de-authorisation turnaround) reliable.

Per-row supplier-confirmation checklist

The matrix is the seam register; the checklist is the closure. Twelve questions, ordered to walk the integration conversation with the supplier in the same order the matrix walks the seam.

#Question to ask the lock supplierWhat "good" looks likeWhat "bad" looks like
Q1Which PMS products does your hotel-line connector support, by version, on a dated evidence page?A published version-table naming PMS product name + version + connector version + last regression-test date"We integrate with everything"; no dated page; no version reference
Q2Is the connector published by your company, by the PMS vendor, or by an integration partner?One of the three named in writing; a partner-named channel is acceptable if the partner supports the connector in writing"We can integrate, ask our sales engineer" with no published contract
Q3Which field carries room-assignment updates (not just reservation-create)?A documented inbound listener keyed to room-number updates, with a regression-test reference for the PMS version in scopeThe connector listens for reservation-create only; room-moves require a manual re-key
Q4Which check-in event triggers key encoding — folio open, check-in button press, or key-issue button?The button-press event the property's front desk actually uses; supplier confirms which one the encoder hook listens for"It depends"; supplier names one event and the front desk workflow uses another
Q5Does the connector support revoke-then-issue for a same-stay room change?Yes, with documented behavior on the lock-side credentialNo; room-change requires a fresh credential and the audit lineage is lost
Q6Does the connector support a same-stay re-key without changing the room?Yes; the lock-side credential ID is preserved; audit log retains lineageNo; re-key is treated as a new credential
Q7Which mobile-key delivery modes are published for this PMS version — Bluetooth, NFC, wallet pass, third-party app relay?A delivery-mode table per mobile-platform + PMS-version combination"Our app can be used" without naming which delivery mode, which PMS-version, which mobile-platform
Q8What is the documented check-out de-authorisation turnaround window (real-time, batched, queued)?A documented window in seconds or minutes; a documented behavior on PMS-side outage"Immediate" without a window; "within minutes" without a ceiling
Q9Which audit-event fields are exported to the PMS or to an adjacent log destination, and which are filtered out?A documented field-list with the export-format (CSV / JSON / REST POST / syslog) and the receiver endpoint"We can export" without naming the fields, the format, or the receiver
Q10Does the connector support role-keyed master-card issuance from a PMS-side role?Yes; role-keyed, not folio-keyed; supports a documented scope syntaxNo; master cards are issued only from the encoder, not from the PMS
Q11Does the connector support a two-factor binding (PIN, biometric, second device)?Yes; the second-factor method, the binding path, and the per-stay or per-credential lifecycle are documentedNo; two-factor must be operated outside the PMS-published seam
Q12What is the documented offline-mode fallback, and what is the maximum seam-down time the front desk can absorb before workload is materially affected?A documented fallback chain (PMS offline → local-credential queue → encoder-hand-fallback → mechanical override) with the time-thresholds"It falls back" without a chain or a threshold

A "good" column all-the-way-down indicates a qualified integration. A "bad" cell anywhere on this checklist indicates a confirmation still owed; the matrix row it touches is not closed until the supplier answers in writing.

Pre-quote supplier capability check

Before the lock supplier and the PMS vendor are both signed, six questions must be answered in writing. The structure is deliberately short — six items — because the integration is only as reliable as its weakest written confirmation.

  1. Connector SKU, version, and partner. Supplier names the connector by SKU or partner-name, by version, and by the last regression-test date on a document the supplier signs.
  2. PMS-version lock. Supplier names the PMS product and the PMS version the connector was last tested against; both sides sign a "no unplanned upgrade" footing for the contracted period.
  3. Audit-event field-list. Supplier publishes the field-list exported from the lock-side audit log to the PMS-side receiver, with the export-format and the receiver endpoint named.
  4. De-authorisation turnaround. Supplier publishes the document turnaround window for check-out de-authorisation; property documents the front-desk workflow during the worst-case window.
  5. Mobile-key delivery modes. Supplier publishes which mobile-key delivery modes are tested against which PMS-version on which mobile-platform; property signs only the modes published.
  6. Offline-mode behaviour. Supplier publishes the fallback chain when the seam is down; property documents the duty-manager posture during fallback.

The six items map roughly to Rows 1, 2, 8, 7, 6, and 13 of the matrix. Three additional items sit below the line and belong in the integration maintenance contract rather than the procurement contract:

  • Version-drift regression-test cadence. Both sides agree to a regression-test window (quarterly, semiannual, or annual) on each major firmware / cloud release.
  • Who owns the seam-watch. A named contact on the lock side, a named contact on the PMS side, and ideally a named contact at the integrator partner when one exists.
  • Connector-license footprint. Whose contract the connector license lives under, what the renewal terms are, and what changes when the property adds doors or properties.

These nine items together are the contract-surface the matrix has been pointing at. They are not the matrix; the matrix is the cell-by-cell register, not the contract. The contract is the nine items above.

Per-feature hotel-lock capability required for the seam

The matrix cells are not only about the supplier's published connector; they are also about the lock hardware's capability on the room-side. Some rows of the matrix will not work even with a published connector unless the lock model itself supports the underlying capability. The buyer must confirm each row on both sides.

Matrix rowLock-side capability requiredWhere confirmed
Row 1 reservation-sync inboundHotel PC software with documented inbound listener; optional centralized database modeProduct page for the lock model; hotel PC software user manual
Row 2 check-in-triggered encodingEncoder station with connector-bound SDK or REST endpointEncoder station datasheet; connector documentation
Row 3 room-change triggerCredential-revoke-in-place without master-resetProduct page; check the model’s published specification for the model in scope
Row 4 extension re-keyCredential-window-extension command without re-issueProduct page; check the model’s published specification
Row 5 walk-in re-keyCredential-replace with lineage preservedProduct page; check the model’s published specification
Row 6 mobile-key handoverMobile-companion app Bluetooth / NFC / wallet-pass delivery modesProduct page; companion app documentation
Row 7 check-out de-authorisationReal-time or batched de-authorisation turnaround window publishedProduct page; connector documentation
Row 8 audit-event outboundAudit / event record capacity ≥ business need (product-page-documented SLK-9936S line is "up to 1,000 events"; check the model’s published specification for the model in scope)Product page; central-database documentation
Row 9 housekeeping-status outboundOutbound status event support; optional button / DND / make-up-room switchProduct page; housekeeping dashboard documentation
Row 10 master-card role-keyed issuanceRole-keyed credential issuance pathProduct page; hotel PC software user manual
Row 11 two-factor hookPer-credential two-factor binding pathProduct page; mobile-companion app documentation
Row 12 connector-license termsLicense-terms page or partner-channel pageSupplier website; partner channel
Row 13 offline-mode behaviourStandalone-mode fallback + offline encoder hand-operationProduct page; supplier-named failure-mode chain

Eleven of the thirteen rows map to a capability that the lock hardware must publish. Two rows — Row 12 (license) and the cell-color rule (annotation key) — live on the supplier-side or partner-side only and do not require a hardware-side confirmation.

The table is intentional about the lock-side capability column: every capability is named, but the row ends in "check the model’s published specification" rather than naming a number. The SLK-9936S published spec block — 36–100 mm door thickness, RFID Mifare 1 @ 13.56 MHz, 0–5 cm read distance, <0.25 s read time, 4 × AA battery, >15,000 battery cycles, up to 1,000 audit/event records, 5-pin cylinder, 3-point latch, stainless steel + alloy body, mechanical emergency access, multilingual management software, standalone-or-centralized database modes, 1–5 star positioning — is invoked here only as a documentation-granularity yardstick to show what a complete hotel-lock datasheet looks like. None of those numbers is portable to any other hotel lock without an explicit confirmation on that model's product page.

Honest meeting points and out-of-scope items

Some rows of the matrix belong to the lock vendor and the PMS vendor simultaneously, and the seam cannot be published from one side alone; some rows belong to neither side and live at the boundary of an adjacent product (the central one-card system, the property-wide access-control vendor, the loyalty-platform app). The boundary items are the buyer has to map separately.

Honest meeting points. Where the seam is published by both sides, with versions named.Adjacent-system boundaries. Where the seam lives at the boundary of a third product (one-card, access-control, loyalty, guest-app) and no party has published it from one side.Out-of-scope items (in this article). Palm-vein credentials, Matter, Zigbee, Apple Home Key, UWB, NFC-secure-credential, Thread, Z-Wave, Wi-Fi-as-catalog-radio, and vein-recognition technologies do not belong to the hotel lock line in this catalog. They are not claimed for any cell of the matrix; any PMS-side vendor that demands one of these as a seam requirement is operating outside the catalogue scope. They are not asserted anywhere in this article.

The seam register is not a marketing scoreboard; the meeting-points / boundaries / out-of-scope split is what keeps the article honest under a close reading.

RFQ evidence pack — what to send the supplier

The buyer collects evidence; the supplier collects evidence; both sides take signatures. The pack below is the four-document set that closes the matrix.

DocumentOwnerContentsSign-off
D1 — Per-PMS-version compatibility registerLock supplierOne row per PMS product in scope; per-row version, last regression-test date, connector SKU or partner-nameLock supplier sales engineer + integrator partner (when one exists)
D2 — Per-row capability confirmationLock supplierOne row per matrix row; one column per lock model in scope; per-cell confirmation of the lock-side capability with reference to product pageLock supplier product manager + property's project lead
D3 — Per-row lock-PMS contract pageLock supplier + PMS vendorOne row per matrix row; per-row confirmation that the contract is published by both sides, with version pinningLock supplier sales engineer + PMS vendor partner-channel manager
D4 — Per-integration maintenance postureProperty + integrator partner (when one)Version-drift regression-test cadence, seam-watch ownership naming, connector-license renewal terms, fallback chain publishedProperty operations lead + integrator partner

D1 and D2 are the procurement-side evidence the lock vendor signs. D3 is the cross-vendor evidence both sides sign. D4 is the operational evidence the property signs. None of them assert a per-PMS-brand claim the catalog does not publish; all four route the cell-by-cell confirmation back to the supplier.

Illustrative scenario — a 180-room regional chain rolling out a new PMS

Consider a regional chain of three properties — a 70-room boutique, a 60-room select-service, and a 50-room resort-adjacent — that has selected a cloud-native PMS from the Cloud PMS category on a group-wide, twelve-month rollout. The group's IT lead runs the matrix as a confirmation register once the lock vendor delivers D1. The boutique property has been encoding keys via the encoder station for several years; the select-service property uses a mix of cards and mobile keys; the resort-adjacent property runs an older PMS-installed base and is being migrated to the new PMS as Property 3 of the rollout. The group has eight columns in scope on the matrix — the cloud PMS column, plus a column for the legacy PMS still running at Property 3 for the first six months of the rollout, plus six columns that the integrator partner maintains for adjacent products (loyalty app, central one-card, guest-app partner, loyalty partner, accounting integration, access-control integration). The matrix spreads to thirteen rows by nine columns at the smallest readable layout — 117 cells, every cell a "confirm compatibility with the supplier" stamp at the start.

By month two of the rollout, the integrator partner closes 64 cells on Rows 1, 2, 4, 5, 7, 8, 9, 10 across all eight columns. By month four, 41 more cells are closed on Rows 3, 6, 11. By month six, twelve cells remain open — predominantly on Rows 8 and 13 across the legacy PMS column (where the on-prem legacy connector will not be published) and on Row 6 across the loyalty partner column (where the mobile-app delivery mode is still being negotiated). The IT lead treats the open cells as a fall-back trigger: at month six, the open cells switch the rollout from "PMS-triggered mobile-key handover" to "PMS-triggered at the encoder + manual mobile-key handover" for the legacy-PMS site, and writes the fallback into the operations manual. By month twelve, the legacy PMS has been migrated, the legacy column is retired, and the matrix compresses to eight columns.

The scenario stays illustrative: no property is named, no client logo is referenced, no integration partner is named, no version number is asserted, and the supplier-side confirmations remain named-as-dated-evidence in the supplier's hands.

Closing posture — what to write before the contracts are signed

The matrix is not a buying tool. The matrix is a confirmation register that the buyer runs once, fills once, and revisits on the version-drift cadence negotiated in the integration maintenance contract. A buyer's posture for the seam is not "which PMS is best"; a buyer's posture for the seam is "which PMS-version combinations are signed by both vendors on a dated page, with a named connector, with a named regression-test cadence, with a named seam-watch owner."

The catalogs that publish a hotel lock line — SmartLockFactory included — publish the lock hardware, the encoder, the hotel PC software, the optional centralized database, and the multilingual management software. The catalog does not publish a per-PMS-version handshake claim and never should, because the handshake is the joint between two vendors, not the property of either vendor. The matrix above names the per-PMS columns the buyer encounters, names the per-feature rows the seam has to support, and flags the cells the buyer must confirm with the supplier in writing. Where the catalog's first-party fact base does support a row — the audit-record capacity of a specific lock model; the per-credential role-keyed issuance path on the hotel PC software; the mobile-companion-app delivery modes the catalog publishes for the mobile side — the row is annotated in that direction. Where it does not, the cell is the default confirm compatibility with the supplier, and the matrix is the register to close.

The siblings this article complements — Hotel Smart Lock System Architecture for the four-component architecture the seam sits at the edge of, Hotel Smart Lock API Integration Guide for the per-API surface the developer-side counterpart of this matrix names, Hotel Smart Lock Guest Access Management for the front-desk workflow the matrix triggers — together form the four-page set a PMS-rollout project team reads in order: architecture, API surface, PMS surface, guest-workflow surface. The lock hardware itself is /hotel-lock and the four named hotel locks (SLK-9936S, SLK-9936G, SLK-9905A, SLK-9951TH, SLK-9962S) are linked individually for the procurement-side datasheet the engineering lead opens beside this matrix. The seam-watch contract goes to /request-a-quote; the per-room encoder-station specimen goes to /order-samples; the catalog itself is at /request-catalog.

The PMS integration is the most operationally-load-bearing seam a hotel lock system publishes. It is also the seam most often discussed before it is documented. The annotation, the matrix, and the confirmation register close that gap row by row, column by column, signature by signature — without claiming a per-brand integration the catalog does not publish and without leaving a per-brand integration the catalog cannot close unconfirmed.

Coșul dumneavoastră
Experiența dumneavoastră pe acest site va fi îmbunătățită dacă permiteți utilizarea cookie-urilor. Politica privind cookie-urile
Chat on WhatsApp