Channel manager vs PMS: how do they differ for hotel chains?

Part 1: PMS, channel manager and booking engine — three systems, three jobs

An easy way to remember it: the PMS keeps the books, the channel manager takes rooms out to the channels, and the booking engine sells rooms on the hotel's own website.

The three systems complement each other rather than replace each other. In the DiHotel ecosystem, website booking is handled by DiBooking; the connection to OTA channels goes through the channel manager each property has a contract with.

Part 2: What the PMS does that a channel manager does not

A hotel with few channels may still manage by hand, but it still needs a correct booking book — the companion DiCloud article covers this in more detail. In chains and resorts, work outside the channels is most of the operational workload, and it is where real money is recorded:

• Folios and charging services to the room. Restaurant, spa, minibar, laundry and transfers charged to the room, with folios split by who pays. How resorts do it is in the article charging services to the room.
• Group blocks and corporate or tour operator contracts. Holding rooms for groups, rooming-list deadlines, contract rates, receivables by partner.
• Check-in, check-out, assigning specific rooms, housekeeping status. The channel manager knows "one Deluxe room has been sold"; the PMS knows which room the guest is in and which rooms are being cleaned.
• Bookings outside the channels: phone, email, walk-ins, each property's regulars. A channel manager only knows bookings that pass through it.
• Reports by property and combined reports for the whole chain: revenue, occupancy, ADR and RevPAR across all guests, not just guests from the channels.
• Accounting. Revenue from the PMS goes to DiACC, with combined reporting across several entities; how this works under Circular 99 is in the article chain accounting under Circular 99.

Conversely, a PMS does not replace a channel manager: it does not maintain many separate connections to each OTA channel. A chain selling on many channels needs both, connected two ways.

Part 3: A channel manager for hotel chains — one connection per property

A common misunderstanding is that a chain has "one channel manager for the whole chain". In practice, each property is a separate hotel on each OTA channel: its own account, its own room types, its own reviews. At the channel manager, each property is also its own account or hotel, with its own mapping table. So the connection between the PMS and the channel manager is also one connection per property.

• Properties can use different providers. Properties acquired or opened at different times often bring their current provider with them. Draw up a table: which property, which provider, which channels.
• A connection problem at one property does not drag the others down. When it is handled, the contact is that property's own sales person.
• The contract with a provider can be signed at chain level, but set-up, mapping and monitoring are still per property.

Part 4: Multi-property inventory synchronisation — inventory and rates property by property

"Synchronising inventory across properties" does not mean pooling the properties' rooms into one shared stock. Each property has its own rooms, room types and rates, and a property's availability goes out to that property's channels. What is shared across the chain is the way of working:

• Common conventions for room type names, rate plans and booking sources in the PMS, so channel reports can be compared across properties.
• Anything that changes sellable rooms is recorded in the PMS first: group bookings, phone bookings, rooms temporarily withdrawn from sale. The PMS holds the source book, so availability sent to the channels is only right when the source book is right.
• Timely synchronisation between the PMS, the provider and the channels reduces the risk of double bookings, especially in conference season when group blocks and individual bookings compete for the last rooms. Handling deposits and inventory in that season is in the article conference season: deposits and inventory across properties.

Part 5: Who may change rates — permissions in the PMS

In a chain, "who may change rates" matters as much as "what the rate is". When rates go from the PMS to the provider and out to the channels, whoever changes a rate in the PMS is changing it on every channel of that property at once.

• User permissions in the PMS: be clear about who may change rates; people not responsible for pricing, such as the front desk, should only be able to view them.
• One pricing contact per property, with an approver at chain level for major rate changes such as peak season and Lunar New Year.
• Avoid editing directly on the channel's extranet or at the provider once rates come from the PMS, because the two places drift apart easily and it becomes hard to trace who changed what.
• Ask the vendor about a record of rate changes: this belongs in due diligence, because when there is a complaint about a rate, the chain needs to know who changed it, when, and at which property.

Part 6: The two-way flow between the PMS, the channel manager and the OTA channels

Outbound: inventory and rates

• Step 1. The property's availability and rates by room type and rate plan live in DiHotel.
• Step 2. DiHotel sends them to that property's channel manager, according to the agreed mapping table.
• Step 3. The provider pushes them out to each OTA channel connected to the property.
• Step 4. When a new booking arrives from any source, availability in DiHotel changes and the loop runs again.

Inbound: bookings

• Step 1. A guest books on an OTA channel.
• Step 2. The booking goes to the property's channel manager.
• Step 3. The provider passes the booking into DiHotel with the mapped information (room type, rate plan), so the front desk does not re-enter it.
• Step 4. In DiHotel, the booking continues through the PMS's work: room assignment, recording how it is paid (prepaid to the channel or paid at the hotel), opening a folio when the guest arrives, recording revenue by source.

Both flows run per property. Room types and rate plans are mapped by each property's sales person together with the channel manager's staff, because they know which rate plan is on sale on which channel; the DiHotel implementation team helps set things up on the DiHotel side to match. If the chain is on another PMS and considering a move to DiHotel, properties keep the channel manager they use and only switch the connection, without running in parallel; the property-by-property sequence is in the article switching software for a hotel chain: reconnect OTA channels?

Part 7: White-label channel managers bundled with a PMS: cheaper, but what to ask

Some cloud PMS products on the market are sold in packages with a channel manager built in. In some cases that is a white-label channel manager: the PMS buys another provider's channel connection platform and puts its own name on it. There is nothing wrong with this, and bundled packages are often priced attractively. For a chain, where each property sells on many channels and contracts run for years, the executive team should know exactly what it is buying.

How to recognise one

• The channel manager has no name of its own, or has the same name as the PMS.
• The hotel has no contract or account of its own with the provider that actually runs the channel connection.
• You cannot find that provider in the connectivity partner programmes of the major OTA channels.
• Channel problems have to be reported through the PMS, with no contact at the channel connection provider.

What may happen, depending on the contract

• Changing PMS may mean reconnecting each channel, if the channel connection is held in the PMS's name. In that case each property has to reconnect each OTA channel; this hidden tie multiplies with the number of properties.
• Rate and availability problems may take the long way round through the PMS. A property's sales person usually does not work directly with whoever holds the connection.
• The quality of the connection with each channel belongs to the original provider, and it is hard for the hotel to check it.
• The channel manager fee may already be included in the package price — ask for the price split to compare properly.
• If the PMS changes its platform supplier or goes out of business, the whole chain's channel connections may change with it, without the hotel being asked first.

What to ask when offered a package with a built-in channel manager

• Which provider runs the channel connection? Does each property have its own contract and account with that provider?
• If the chain changes PMS later, can each property keep its connection with its OTA channels?
• Split out: how much is the PMS, how much is the channel connection, per property or per room?
• When availability on a channel is wrong, whom does the property's sales person call, who is responsible for fixing it, and how soon does someone handle it?

DiHotel's position, and what that position costs

DiHotel has no channel manager of its own and does not attach a white-label channel manager. Each property signs directly with the channel manager it chooses, has its own account and contact, and keeps that relationship. So when it changes PMS, the property keeps the same provider and channels and only switches the connection.

To be complete: this approach has a price. The hotel pays the channel manager fee separately under its contract with the provider, so the total cost can be higher than a bundled package. In return the chain gets independence and transparency: it knows whom it pays, for what, and its sales channels are not tied to one PMS vendor.

Part 8: Channel manager connection due-diligence checklist for chains

Before signing a PMS or a channel manager, the executive team should have written answers to each line below, property by property:

Pilot the connection at one property first, reconcile the channels, the provider and the PMS for a number of real bookings, and only then extend it to the other properties.

Part 9: Where DiHotel fits in a chain's sales channels

DiHotel, the AI hotel management software, is the original platform for 4–5 star hotels, resorts and chains. The AI part is DiChatbot, an AI chatbot that helps answer guests; the channel manager connection is not AI, it is data synchronisation according to the mapping table. On a chain's selling side:

• A source booking book per property: bookings from the channels, from the website through DiBooking, from group contracts and by phone, all in one book.
• Two-way connection per property with the channel manager that property chooses, from the list of connected providers.
• User permissions in the PMS, so the chain sets who may change rates.
• Owners and GMs follow revenue, ADR, RevPAR, occupancy and receivables through DiOwner, a read-only app with figures that match the operating system, by property or for the whole chain.
• Accounting in DiACC, with combined reporting across several entities.

How do a channel manager and a PMS differ?

A PMS is the hotel management system: it keeps the source booking book and handles check-in, check-out, folios, payments, housekeeping and reports. A channel manager sends availability and rates to OTA channels and brings bookings back from them. A chain selling on many channels usually needs both, connected two ways.

How is a booking engine different from a channel manager?

A booking engine lets guests book and pay directly on the hotel's website. A channel manager serves external OTA channels. Neither replaces the other; both should take availability and rates from the PMS.

Do the properties in a chain share one channel manager connection?

No. Each property is a separate hotel on each channel and at the channel manager, so the connection between the PMS and the provider is one connection per property, with its own inventory, rates and mapping table. What is shared across the chain is the naming convention for room types, rate plans and booking sources.

Who should be allowed to change rates on the channels?

One pricing contact per property, given permission in the PMS, with an approver at chain level for major rate changes. Avoid editing directly on the channel or at the provider once rates come from the PMS.

What is a white-label channel manager, and should we use one?

It is a channel manager built into a PMS package, running on another provider's platform but carrying the PMS's name. Bundled packages are often priced attractively. Before using one, ask which provider runs the channel connection, whether each property has its own contract with that provider, whether you keep the channel connection if you change PMS, and what the split price is.

Does DiHotel have its own channel manager?

No. DiHotel connects two ways with the channel manager each property uses: inventory and rates go from DiHotel to the provider and out to the channels, and bookings come from the channels to the provider and into DiHotel. The channel manager fee is a separate contract between the hotel and the provider.