Hotel PMS, Booking Engine and Channel Manager Explained

Hotel PMS, Booking Engine and Channel Manager Explained

This guide is for hotel owners and operators who are choosing or connecting hospitality software and want to understand which system does what. In short: the property management system (PMS) holds your reservations and rooms, the channel manager sends availability and rates to OTAs and brings their bookings back, and the booking engine takes direct bookings on your website. The risk sits in the connections between them, because that is where overbooking and wrong prices come from.

Most published explanations come from software vendors, so their emphasis reflects their products. We have cited who said what and marked our own judgement.

What each system does

The first three are the core. Vendor SmartOrder describes their roles in these terms: the PMS runs day-to-day operations, the channel manager pushes live rates and availability to OTAs and pulls bookings in, and the booking engine takes direct bookings on your own website. The others sit around the core and often connect through the PMS.

How they connect

There is no single standard architecture, and this is the most important thing to find out from a vendor.

One common pattern, described by Lean Hotel System, is that availability goes from the PMS to the channel manager, rates and restrictions come back from the channel manager to the PMS, and the booking engine reads availability, rates and rules from the channel manager rather than from the PMS directly. Web bookings return to the PMS through the same route. The same vendor notes that some PMSs connect to the booking engine directly instead, so verify the supplier's actual design.

Vendors also publish APIs for this. Mews, a PMS vendor, documents separate interfaces: a Channel Manager API that is two-way (distributing availability, rates and inventory to channels, and accepting reservations from them), and a Booking Engine API that lets booking engines create reservations directly. Mews says the booking engine interface is meant for front-end clients and is unsuitable for continuous polling from a server, and that custom booking engines for connected properties need a particular subscription. Other vendors differ. The point for you is that "has an API" is not an answer. Ask what it can read, what it can write, and what it costs.

What data typically syncs

Lean Hotel System lists availability, rates, restrictions such as minimum stay and closures, room types, policies, taxes and confirmed bookings, and, depending on the supplier, guest data, extras, notes and payment status. It also advises deciding which system is the master for each type of data, so two systems never both think they own the price.

What goes wrong: common integration failures

The same source lists failure modes that match what we would expect from any two-way integration:

• Stale availability when a connection drops, so a room sold on one channel still shows as free on another.
• Overselling from inconsistent inventory.
• Price differences between your website and OTAs that you did not intend.
• Mapping errors, where a room type or rate plan in one system is attached to the wrong one in another.
• Duplicated rules when a booking engine sits outside the main channel route.
• Taxes and policies that differ between systems and reach the guest or invoice wrongly.

Our judgement: mapping errors are the likeliest cause of bad surprises, because they are created once during setup and then ignored. Audit them when you add a room type, change a rate plan or switch a vendor.

SmartOrder also makes a useful point about order: a channel manager or booking engine that feeds a spreadsheet instead of a PMS has not removed the double-booking problem; it has moved it.

Which to buy first

Vendor guidance is fairly consistent here, though it is still vendor guidance:

• A new hotel on one or two OTAs usually needs a PMS first, possibly with channel management included. A channel manager alone has nowhere to send bookings.
• A hotel trying to reduce commission can add a booking engine once the PMS and channel manager are working reliably.
• If you want all three, consider whether a single integrated platform removes connectors you would otherwise have to maintain.

An all-in-one product is easier to run, but you accept its booking engine, its limits and its pricing. Separate specialist tools give you choice but make you responsible for the connections. Neither is right for everyone.

Buy, integrate or build

Our judgement: very few hotels should build a PMS. A custom front end on top of a vendor's booking engine or API is the more sensible custom piece, because it gives control over the guest experience while the vendor keeps inventory. We built the direct booking experience for Platinum Peak (see our portfolio) as a UI and conversion design project, and our web development service covers front ends like this. If your aim is more direct bookings, read our guide to building a hotel direct booking website to reduce OTA commission.

Questions to ask any vendor

• Which systems do you integrate with natively, and which need a third-party connector? Who supports the connector?
• Is the integration two-way, and how quickly do availability changes reach other channels?
• What happens if the connection drops? Are there alerts, automatic retries and a manual fallback?
• Which system is the master for rates, restrictions and inventory?
• Can we use a custom booking engine or front end, and on which plan?
• How are room types and rate plans mapped, and who checks them?
• What are the fees per booking, per channel or per connection?
• Can we export our data if we leave?

Lean Hotel System also suggests testing real scenarios before go-live: different devices, dates, promotions, cancellations and modifications, and confirming that confirmation emails go out and bookings appear correctly in the PMS. We agree, and would add testing a booking made at the same moment on two channels for the last room.

Sources

• PMS vs Channel Manager vs Booking Engine, SmartOrder
• Booking engine and PMS integration, Lean Hotel System
• Channel Manager API, Mews documentation
• The Mews APIs, Mews documentation