Channel manager mapping: room types, rate plans and testing

Channel manager mapping is the set of decisions that tie each sellable product in the hotel's own system, a room type plus a rate plan plus an occupancy band, to the product a booking channel sells, including its name, board basis, cancellation terms and price link. It is kept as an auditable sheet and retested after every change.

A guest books a sea-view double with half board and arrives to a reservation for a land-view double with breakfast. The front desk blames the channel manager. The cause is usually a row in a spreadsheet that nobody has opened since the season started. After reading this guide you will be able to build that sheet, name products so guests understand them in any language, trace what a derived rate inherits, and test the whole chain with a real booking after every change. For the division of labour between the systems involved, see PMS vs channel manager vs booking engine: what each one does.

What is channel manager mapping, and why do mapping errors look like software faults?#

Channel manager mapping is the set of decisions that connect each sellable product in the hotel's own system to the product a booking channel sells. When those decisions are wrong, the software carries out exactly what it was told, so the result looks like a bug.

A channel manager is the software that carries availability and rates from the hotel's own system out to booking channels and brings reservations back in. It moves data; it does not decide what a product means. The mapping decides that. Mapping has three parts per channel product: which room type it corresponds to, which rate plan it corresponds to, and which occupancy band it covers. The channel's own product code is the fourth piece, and it is the one that must be written down.

The channel's catalogue is not the hotel's catalogue. Channels keep their own room type names, board codes and cancellation categories, and the mapping is the translation between the two vocabularies. Certain symptoms point to a mapping decision rather than a software fault: a guest arrives on the wrong board basis, a child is charged as an adult, a booking arrives on a rate plan the hotel stopped selling, or the cancellation terms shown to the guest differ from the terms in the hotel's own system.

Give the sheet one named owner. The distribution manager maintains it, revenue signs off the rate links, and the reservations team reports every mismatch it sees. Without an owner, the sheet drifts within a season.

When something goes wrong, look in a fixed order: the reservation in the hotel's own system first, then the mapping row, then the channel listing. The channel is the last place the error appears, which is why it is the worst place to start.

Room types, rate plans and sellable products: what is the difference?#

A room type describes the physical room, a rate plan describes the commercial conditions, and a sellable product is one room type sold under one rate plan at one occupancy. Guests buy the third; systems store the first two.

A room type is a physical fact about the building: bed setup, size, view, capacity. It changes only when the building changes. A rate plan is a commercial promise: board basis, cancellation terms, minimum stay, deposit, and the price link to a parent rate. It changes whenever revenue changes its mind.

A sellable product is the combination a guest actually buys. For example: a standard double room, breakfast included, free cancellation up to three days before arrival, two adults. It is the unit that gets a mapping row.

Most mapping errors come from putting one where another belongs: a room type mapped into a field that expects a rate plan, or a rate plan published on a channel with no room type attached, which is how phantom products appear in a channel's list. A room type can also exist without being sellable, for example when it is out of order or held for a group. That is normal, but the mapping sheet must show it as closed rather than simply absent, or someone will reopen it by accident.

Count the sellable products before you map anything: room types multiplied by rate plans multiplied by occupancy bands is the number of rows you will need. If the number looks unreasonable, the rate plan list is too long, not the sheet.

How should you name room types and rate plans so guests understand them?#

Name for the guest, keep a separate internal code for the team, and never let a name promise something the building or the Ministry certificate does not support.

Keep two names per product: a stable internal code that never changes, and a public name that can be edited. The mapping should hang on the code, so renaming a product does not break a channel connection.

Public names should be literal: bed setup, room class, board. A plain name such as "standard room, two guests, breakfast included" tells a guest more than an invented package name that only the sales team understands. Drop abbreviations that only the front desk reads. A channel will show the name to someone who has never seen the hotel and does not know that a three-letter code means a double with breakfast.

Names travel into several languages. Short literal names translate cleanly; idioms, puns and brand-style names do not, and a machine translation of a clever name is often worse than a plain one. Keep view and location claims out of the room name unless every room in that type has them. A name that is true for four rooms out of twenty becomes a complaint at the desk.

There is also a regulatory side to naming. The Regulation on the Qualifications of Tourism Facilities requires a facility's promotion to match its Ministry certificate and give accurate information, bans symbols that suggest stars outside its certified class, and bans terms in the facility's name for units it does not have (consolidated text, Article 16(2) and 16(3), mevzuat.gov.tr (opens in a new tab)). A room name that implies a facility the certificate does not cover is a naming problem before it is a marketing problem.

Channels and agencies carry their own duty. Turkish regulations require travel agencies to verify that accommodation providers hold valid Ministry certificates and to display this information accurately. Regulators are increasingly requiring platforms to remove listings that lack valid certificates. Accurate channel data is in everyone's interest, and the hotel's own certificate details should be checked before a season, with an adviser for the specific case.

What should a channel mapping sheet contain?#

One row per sellable product per channel, carrying both codes, the full commercial meaning of the product, and the date it was last tested.

Columns that earn their place: hotel product code, public name, room type, board basis, occupancy with adult and child counts and age bands, rate plan, cancellation terms, channel, channel product code, last tested date, owner. One row per product per channel, not one row per room type. A room type sold on three channels under two rate plans is six rows, and each of the six can fail on its own.

Keep the sheet where the team can audit it row by row and print it. A spreadsheet with a version date beats a screen nobody outside the distribution team can read. The sheet answers the question "why did this booking arrive like this" in one lookup. A channel manager's own interface shows the current state, not the decision behind it.

Show derived rates with their parent in the same sheet, so a change to a parent can be traced to every child without opening each channel. Review the sheet before each season, after every new room type or rate plan, and whenever a channel changes its own product list. A row with no test date is a row with an unknown state.

For example, a small sheet might look like this, with invented names:

The third row is the one that will cause the next desk incident. This sheet sits inside a wider question of how inventory is shared across channels, covered in Hotel distribution strategy: one inventory across every channel.

Board basis, occupancy and child age bands: where does mapping drift?#

Board types and child age bands are industry usage rather than a single regulated definition, so each channel interprets them in its own way and the mapping has to translate rather than assume.

Board basis covers room only, bed and breakfast, half board, full board and all inclusive. These are commercial definitions, not fixed ones, so a channel's half board may or may not include drinks with dinner. Write the hotel's own definition into the rate plan terms and read the channel's definition before mapping.

Map adults and children separately. A product sold as two adults and a product sold as two adults plus one child are different rows even when the room is the same, because the price and the rules differ. Child age bands are the hotel's decision, for example free up to 6, reduced from 7 to 12, adult from 13. The channel has its own bands. The mapping must carry the hotel's bands, and the channel's band must be checked against them, not the other way round.

Extra beds belong in the rate plan, not in a note the guest never sees: whether an extra bed exists, and whether it is included in the price or charged on arrival. Double for single use is a separate sellable product. If the hotel sells a double room to one guest at a different price, it needs its own row and its own channel code.

When a booking arrives wrong, check in this order: the occupancy on the reservation, the board on the rate plan, then the child's age at arrival. The first two are mapping questions; the third is often a date-of-birth entry error at the channel.

What does a derived rate inherit from its parent?#

A derived rate follows its parent's price with a fixed offset or a multiplier, and it also inherits the parent's restrictions unless the hotel deliberately overrides them.

The mechanism is simple: the hotel sets a base rate, then creates a child that is, for example, the base plus a fixed amount or a percentage of it. When the parent changes, the child recalculates. What is inherited is price movement plus, typically, restrictions such as minimum stay, closed to arrival and stop sell. What exactly is inherited depends on the system and on the channel, so it must be tested rather than assumed.

The classic failure runs in both directions: the hotel closes the parent for a date and believes only the parent is closed while the child keeps selling, or a child that should stay open is closed together with its parent.

Cancellation terms and board basis are commercial promises, not price links. Check whether the child carries its own terms or copies the parent's, and write the answer into the sheet. Draw the parent-child tree into the mapping sheet and mark which restrictions are deliberately overridden on each child. A tree nobody can see is a tree nobody checks.

After editing a parent, list every child and test the ones that carry a different restriction set. A stop-sell that fails to reach a child is one of the ordinary routes to selling the same room twice, a failure mode covered in Hotel double bookings across channels: causes and prevention.

How do you test a mapping, and how do you retire an old rate plan?#

Test with a real booking on a far-future date after every change, and retire a rate plan by closing it to new sales while leaving existing bookings untouched.

Trigger a test after a new room type, a new rate plan, a board change, a child band change, a parent rate edit, or a new channel. A change without a test is an untested state, not a finished task. Choose a date months ahead with open inventory and no group block. Never test on a near date or a sell-out date, because the result will be distorted by restrictions that have nothing to do with the mapping.

The test-booking routine#

Record the date and the result in the mapping sheet. A row with no test date is a row the team cannot vouch for.

Retiring a rate plan#

Retire in order: close it to new sales, keep it readable, mark its mapping rows retired with a date, check its children, and remove the product on the channel side too, because a channel can keep a stale product live after the hotel has stopped selling it.

Never delete a rate plan that has future bookings. The guest's confirmation must still match what they bought, and a deleted plan turns a routine arrival into a manual rebuild at the desk. Hotels preparing for AI-assisted booking will find the same discipline applies there; see AI booking readiness checklist: what hotels can prepare now.

What to do next#

Build the mapping sheet this week, starting with the products you sell most: one row per sellable product per channel, both codes, the board and occupancy written out in full, the parent rate named, and a test date. Everything in this guide hangs on that one artefact. Names, inheritance, testing and retirement are all decisions you can only audit if they are written in the same place.