How to choose a channel manager: questions to ask before you sign

A hotel channel manager is the system that carries rates, restrictions and bookings between your hotel system and the booking sites, in both directions. Choose one by asking what it carries, which channels and agencies it connects in both directions, how it reports failures, how fast updates land, and how you export your data and leave.

You change a rate at nine in the morning and it is still on the booking site two hours later, or a guest arrives with a confirmation your front desk has never seen. Both are channel manager problems, and both are decided long before the guest appears: at the questions you asked, or did not ask, before signing. This page gives you those questions, section by section, so you can walk into every demo with the same one-page brief and compare vendors on answers rather than on logo walls.

What does a hotel channel manager actually do?#

It moves two kinds of data in two directions: your rates and restrictions out to the channels, and the bookings those channels produce back into your hotel system. Anything that does not do both is a listing tool, not a channel manager.

Outbound, it sends room availability, rates, restrictions such as minimum stay or closed to arrival, and stop-sale, to each connected channel. Inbound, it writes new bookings, modifications, cancellations and no-shows into your hotel system, so the room is taken out of inventory everywhere else. The plain-words idea behind it is a single source of truth: one place holds the real state of a room, and every channel reads from it rather than keeping its own copy.

A one-way tool pushes rates but leaves bookings to arrive by email, which means a person retypes them and the inventory is briefly wrong. A two-way connection is not automatically instant: ask what the update window is, because that window is where double bookings live. The channel manager does not decide your prices and does not replace your hotel system; it carries decisions made elsewhere. If you are unclear on where it sits next to a property management system (PMS) and a booking engine, read our explainer on what each system does.

Which channels and partners must it connect to, in both directions?#

Start from your own channel mix, not from the vendor's logo wall, and ask for the list in writing with the direction and the last test date for each entry.

List the booking sites you actually sell on today, plus the two or three you plan to add, and check each one individually rather than accepting a total count. Ask separately about travel agencies and wholesalers: contracted rates, allotments and on-request bookings are a different connection from a public booking site, so ask whether the tool handles them at all, because an agency connection is a different build from a public booking site.

Ask which connections are direct with the channel and which pass through an intermediary switch, because a switch adds a party to every failure conversation. Ask what happens when a channel changes its interface: who updates the connection, how long it takes, and whether you keep selling in the meantime. Ask for the date each connection was last tested end to end, and be suspicious of a list that has never been tested with a live booking. Confirm that each channel works in both directions: a channel that receives rates but returns bookings by email is only half connected.

Can it carry your rate structure exactly as you sell it?#

Only if every rule you use in your own pricing has a place to live in the tool, so test your most complicated rate, not your simplest one.

Derived rates are the first trap: a rate built from another by a rule, for example half board priced as bed and breakfast plus a fixed supplement. Ask whether the tool derives it or makes you maintain two separate numbers. Board types, occupancy pricing for single, double and triple use, and child ages with their own price rules must each map to the channel's own fields, and each channel defines them slightly differently.

Restrictions matter just as much: minimum stay, closed to arrival, stop-sale and release periods on allotments. Ask which restrictions the tool can send and which it silently drops. Confirm how a rate in one currency reaches a channel that displays another, and who sets the conversion.

Mapping is the real work. Room types and rate codes must be paired by name and code between your system, the channel manager and each channel, and someone has to own that sheet and keep it current. Ask to see the mapping document before signing, ask who does the mapping, you or the vendor's team, and how long it takes. The detail of that work belongs to our guide on channel manager mapping, room types and rate plans.

What happens when an update or a booking fails?#

Every channel manager fails sometimes; the question is whether you find out from the system or from a guest at the front desk.

Name the failure types out loud in the meeting: a rate update rejected by the channel, a queue that falls behind, a booking received but not written into the hotel system, a cancellation that never arrives, a modification lost in between. Ask who is alerted, how, and how fast: a dashboard nobody watches is not an alert. Ask for email or message alerts to named people at the hotel.

Ask for a daily reconciliation view you can read yourself: what was sent, what was accepted, what was rejected and why. Ask about retries: does a rejected update retry automatically, and does it stop after a number of attempts and tell someone. Ask what the tool does when the connection to a channel is down for hours: does it hold the queue, and does it tell you which bookings may be missing. Ask who is responsible when a late update causes a double booking, and get the answer in the contract rather than in a sales conversation. The causes behind that failure mode are covered in our piece on double bookings across channels.

How does it connect to your hotel system, and who is accountable?#

The channel manager is only as good as the link behind it, so ask how it talks to your hotel system and who owns the mapping on that side.

Ask whether the link is a direct system-to-system connection or a file or email handover, because a handover means a person retypes bookings and inventory is briefly wrong. Confirm which fields must match on both sides: room type codes, rate codes, occupancy and the identity of the booking, and who maintains them. Ask what happens when the two systems disagree about availability, and which one wins.

Ask whether the same vendor supplies both systems. One supplier means one number to call and one party to hold accountable, but also one exit to negotiate. Test one booking end to end from channel to reservation to bill, and watch where the guest details and special requests land. If you are choosing the hotel system at the same time, settle the system first and make the channel manager fit it, not the other way round. Our questions for choosing a hotel PMS in Türkiye cover that first decision.

What should the contract cover before you sign?#

The contract is where the exit, the failures and the money are decided, so read it as an operating document rather than a formality.

Pricing models differ: per room, per channel, a flat monthly fee or a share of bookings. Each shifts risk differently, and the cheapest headline is rarely the cheapest total once setup, mapping and added channels are counted. Ask what is included and what is charged extra: setup, mapping, training, additional channels, additional properties. Check the minimum term, the notice period and how prices can change during the term.

Data export decides your future choices: in what format, how often, at what cost, and whether you can take your booking history with you. Exit matters most of all: how long the connection stays live after you terminate, who tells the channels, and who removes your rates so they do not sit on a site you no longer control. Liability closes the list: what the vendor accepts responsibility for when a booking is lost or duplicated, and what it does not.

How do you test support and the connection before you commit?#

Run a short trial with real bookings on the channels you will actually use, and test the support in the language and the hours your team works.

Make a test booking on each channel, then cancel one and modify another, and check that all three land correctly in your hotel system. Change a rate and time how long it takes to appear on each channel, including at night and at the weekend. Send a support request in Turkish during your busiest shift hours and time the first useful reply, not the first automated one.

Ask who answers, whether first-line support is in-house or outsourced, and what the escalation path is when the first answer does not solve it. Ask for the support hours in writing and check they cover the time zones your guests book from. Ask existing clients for references and ask them specifically about failures, not about features.

What to do next#

Write your channel list, your three most complicated rates and your failure questions on one page, and take that page to every demo. The vendor who answers it in writing, with test dates and a contract that lets you leave, is the one to sign with. The technical message flow behind these answers belongs to the integration explainer, so read that next and keep this page as the commercial checklist.