A guide for hotels
What is hotel PMS integration, actually?
A plain-English explanation of what PMS integration means, which systems typically connect to it, and what to check before you sign off a project — from engineers who configure this daily.
The short answer
Your PMS is the source of truth. Integration lets other systems read it.
Your property management system holds the reservation, the guest name, the room number, the room status and the checkout time. Without integration, every other system in the hotel — the TV in the room, the door lock, the phone, the POS at the bar — has no idea any of that exists. Someone at the front desk has to type it in separately, system by system, guest by guest.
PMS integration means those systems can read (and sometimes write back to) the PMS automatically, usually via an API. Guest checks in once, at the front desk, and the room TV welcomes them by name, the door lock is already encoded, and the bar tab is ready to post to their folio — without anyone re-typing anything.
Integration ≠ migration
These get conflated often. A PMS migration replaces the property management system itself. PMS integration connects your existing PMS — whichever one you're on, and whether or not you have any plans to change it — to the other systems in the building.
The platforms
Integration difficulty depends heavily on which PMS you're on.
Oracle Opera / Opera Cloud
Most common in mid-to-large hotels and groups. OHIP for modern API-based integration.
Mews
API-first by design — typically the most straightforward platform to integrate against.
Apaleo
Built around an open API and app marketplace model, similar philosophy to Mews.
Protel
Common across European independents and groups; interface layer varies by version.
What typically integrates
The systems hotels most often connect to the PMS.
IPTV & guest casting
Guest name, room status and checkout time flow from the PMS to the in-room TV for welcome screens, folio display and interactive checkout — the most common PMS integration hotels ask for.
Door locks & key systems
Reservation and checkout events trigger key encoding and access revocation automatically, so front desk isn't manually managing lock software alongside the PMS.
Point of sale
Restaurant, bar and minibar charges post directly to the guest folio rather than being reconciled manually at checkout — reduces both front-desk workload and billing disputes.
VoIP & telephony
Guest name and room status populate the phone system for correct call routing and billing, and checkout automatically clears the extension.
Guest messaging & upsell platforms
Pre-arrival and in-stay messaging platforms pull reservation data from the PMS to trigger the right message at the right point in the guest journey.
Revenue & channel management
Rate and availability data flows both ways between the PMS and channel managers or revenue management systems — usually already in place before we're involved, but worth checking for gaps.
Before you sign off
What to actually check before a PMS integration project is signed off.
The most common failure mode isn't the initial integration going wrong — it's a project being signed off on a successful demo, then breaking quietly weeks or months later when the PMS vendor pushes a routine update or the firmware on the connected system changes. Before sign-off, ask specifically what happens when either side updates: does the integration get retested against new versions, or does nobody find out until a guest complains about a TV that no longer shows their name at check-in?
Ask to see the data flow tested in both directions, not just one. A door lock system that reads checkout data correctly but doesn't reliably write back an access revocation is only half-integrated, and that's exactly the kind of gap that shows up as a security or billing problem rather than an obvious technical failure. The same applies to POS and folio posting — test a real charge posting to a real guest folio before accepting the project as complete, not just a connectivity check between the two systems.
Finally, get written clarity on who's responsible for the integration once the initial project ends. PMS vendors, connected-system vendors and the integrator who did the initial work can each reasonably point at one of the others when something breaks eighteen months later — a genuinely useful sign-off includes a clear answer to "who do we call" before that situation ever comes up, not after.
FAQ
PMS integration — questions we get asked
It means another system — IPTV, door locks, POS, phone system, guest messaging — can read and sometimes write data to and from your property management system, usually via an API, so staff don't have to manually re-enter the same reservation, guest name and room-status information into multiple systems separately. Done properly, a guest checks in once at the front desk and every connected system already knows who they are, what room they're in, and when they're due to leave, without anyone touching a second piece of software.
No, and this distinction matters because the two get quoted and scoped very differently. A migration replaces the property management system itself — a bigger, riskier project involving data transfer, staff retraining and often a period running two systems in parallel. Integration connects your existing PMS to other systems without touching the PMS itself, which means you can add new integrated systems against a PMS you have no plans to change for years, with far less disruption to day-to-day operations.
Mews and Apaleo were built API-first from the ground up and are generally the most straightforward platforms to integrate against, with modern documentation and predictable behaviour. Opera remains the most common system in larger hotels and hotel groups, with OHIP as the modern integration layer replacing older, more fragile interface methods. Protel's integration difficulty varies more by specific version and deployment than the others, so it's worth checking which version you're actually running before assuming a previous integration experience will transfer directly.
Sometimes partially, but someone still has to configure the actual connection, test the data flow in both directions, and take responsibility when something breaks after a PMS or firmware update. That's usually where we come in.
PMS software updates and firmware updates on the connected system are the most common cause of integrations silently failing — a field mapping changes, an API version deprecates, and nobody notices until a guest complains. Ongoing monitoring matters as much as the initial setup.
Yes, though it's often bundled with the IPTV, Wi-Fi or infrastructure project that's driving the need for it in the first place. We're happy to scope it either way.
Scoping a PMS integration project?
Tell us your PMS platform and what you're trying to connect to it — we'll give you an honest view of what's straightforward and what needs more thought.
Book a free Gap Analysis →