Hotel PMS and Channel Manager: How They Work Together

Hotels shopping for software meet the same two terms in every brochure: PMS and channel manager. Some vendors sell them as one product, some sell one and connect to the other, and the line between them gets blurred. This guide explains what each one does, how they talk to each other, where your inventory should live, and what to check so the connection doesn't become the source of your overbookings.

• The PMS runs the hotel and should hold the one true count of rooms for sale.
• The channel manager distributes that inventory to OTAs and returns their bookings.
• The link between them needs to be two-way: rates and availability out, bookings, changes and cancellations in.
• Most overbookings come from changes made outside the PMS or updates that fail silently.
• Built-in and separate channel managers both work; visibility into the sync matters more than the packaging.

What a PMS does

A property management system is the hotel's operating system. It holds reservations and the room grid, runs check-in and check-out, posts charges to the folio, tracks housekeeping status, closes the day at night audit and produces the reports. Because walk-ins, phone bookings, room moves, extensions and rooms taken out of order all happen in the PMS, it is the only system that knows exactly how many rooms are really free tonight.

What a channel manager does

A channel manager connects the hotel to its online travel agencies. Instead of logging into each OTA's extranet to change a rate or close a date, the hotel makes the change once and the channel manager sends it to every connected OTA. In the other direction, it collects bookings, modifications and cancellations from each OTA and passes them on. It doesn't run the front desk, bill guests or know which room is being cleaned; it is a distribution layer.

PMS vs channel manager at a glance

• Job: the PMS runs operations; the channel manager runs distribution
• Users: the PMS is used by the front desk, housekeeping and accounts; the channel manager mostly by whoever manages revenue
• Inventory: the PMS holds it; the channel manager publishes it
• Bookings: the PMS stores and services every booking; the channel manager carries OTA bookings into it
• Without the other: a PMS alone means updating OTAs by hand; a channel manager alone means running the hotel on spreadsheets

How the two-way connection works

Outbound, the PMS sends availability per room type and date, rates per rate plan, and restrictions such as stop-sells, minimum length of stay and closed-to-arrival. The channel manager forwards them to each OTA in that OTA's format.

Inbound, the channel manager delivers each OTA booking to the PMS with the guest's details, dates, room type, rate plan, amount and the OTA it came from. Modifications and cancellations follow the same path. The PMS then recalculates availability and sends the new count back out, which closes the loop.

A simple example: a hotel has two deluxe rooms left for Saturday. A walk-in takes one at the front desk. The PMS drops deluxe availability to one and pushes the update, and within moments every OTA shows one room. When that last room sells on an OTA, the booking arrives in the PMS, availability goes to zero, and the stop goes out everywhere.

Keep the inventory in one place

The PMS has to be the single source of truth. If someone closes a date in an OTA extranet, or changes availability directly in the channel manager, the PMS doesn't know, and the next update from the PMS can reopen what was closed or leave the systems disagreeing. The rule for staff is simple: rates, availability and restrictions are changed in the PMS and nowhere else. The same applies to rates; deriving every OTA rate from one best available rate is the easiest way to keep rate parity.

Built-in or separate channel manager

A PMS with a built-in channel manager means one vendor, one bill and no mapping between two systems. The trade-off is that its OTA coverage and the depth of each connection depend on that one vendor, and if you change PMS you rebuild your OTA connections too.

A separate channel manager is usually a distribution specialist with wide OTA coverage. Your OTA connections live there, so changing PMS doesn't disturb them, which makes a PMS migration much less risky. The trade-offs are a second subscription and one more link that has to be mapped and monitored. Either approach works if the sync is genuinely two-way and someone can see when an update fails.

Setting up the connection

1. Clean up room types and rate plans in the PMS first; a messy setup gets copied to every OTA
2. Map each PMS room type and rate plan to its match in the channel manager
3. Decide which rate plans are derived from a base rate, so one change updates all of them
4. Push availability and rates, then check them on each OTA's extranet
5. Make a test booking, a modification and a cancellation on one OTA and confirm each arrives in the PMS
6. Tell staff that rates and availability are now changed only in the PMS

Why overbookings still happen

• Availability changed in an OTA extranet or in the channel manager, outside the PMS
• A new rate plan or room type was added on an OTA but never mapped, so its bookings don't arrive
• An update failed and nothing alerted anyone
• Room blocks and out-of-order rooms weren't subtracted from the availability being sent
• Two bookings for the last room arrived within seconds of each other, before the stop reached every OTA

The last one can't be eliminated entirely, which is why hotels still need a policy for walking a guest. Our post on overbooking covers that side.

Questions to ask a vendor

• Is the sync two-way, including modifications and cancellations?
• How quickly does an availability change reach the OTAs?
• Can I see a log of what was sent, when, and what failed, and can failed updates be retried?
• Do room blocks and out-of-order rooms reduce the availability that is sent?
• Does every booking keep its OTA source, so OTA commission and, in India, TCS can be tracked per channel?
• If I change PMS later, what happens to my OTA connections?

Channel managers for hotels in India

Most Indian hotels sell on MakeMyTrip and Goibibo, which belong to the same group, alongside Booking.com, Agoda, Expedia and Cleartrip. Before choosing a channel manager, check that it connects to every OTA you sell on today, MakeMyTrip and Goibibo included, and to the PMS you plan to use.

OTAs collect TCS on the payments they pass on to hotels, under Section 52 of the CGST Act. When the PMS keeps each booking's OTA source, your accountant can match the TCS each OTA reports against your own bookings. See TCS on OTA bookings.

If you sell rooms by the hour, ask whether your channel manager and OTAs handle hourly inventory at all. Many sell only overnight stays, so hourly and day-use rooms are often sold at the desk.

How StaySynq handles it

StaySynq is the PMS, and it connects two-way with the channel manager you choose rather than connecting to OTAs directly. Rates, availability, restrictions and stop-sells go out from StaySynq; new, modified and cancelled bookings from every OTA you've enabled in your channel manager come in, each tagged with its source. Availability comes from the same inventory the front desk sells, including room blocks and rooms out of order, and a sync queue shows what was sent and what failed so it can be retried. Direct bookings come through the StaySynq booking engine from the same inventory. See how it works on the channel manager page.