Hotel market segmentation: how to set up segment codes

Market segmentation splits a hotel's bookings into groups that behave alike, so each can be priced and measured on its own. Set it up by giving segment, source, channel, market and board type their own fields, using a short fixed code list, one code per booking, assigned at reservation and checked monthly.

A forty-room group is entered under the same code as a walk-in, and for a month three reports quietly disagree with each other. Segment codes are not paperwork: they decide what your pace, your ADR by segment and your next contract review actually measure. This article gives you the five fields, a starter code list, rules for who assigns the code at booking, and a monthly check that catches miscoding before it distorts anything you act on.

What is hotel market segmentation, and why do segment codes go wrong?#

Hotel market segmentation is the practice of grouping a hotel's bookings by how they are bought and who buys them, so each group can be priced, forecast and reviewed on its own. Codes go wrong because one field is asked to answer several different questions at once.

A segment is a group of bookings with a similar buying behavior and a similar decision maker: a tour operator holding rooms on allotment, a company buying negotiated rates, a family booking on the hotel's own website. Hotels segment because the answers change decisions: what rate to load, what cancellation terms to attach, who in the team owns the relationship, and whether a contract is worth renewing. It is a working tool, not a reporting ornament, and it feeds directly into hotel revenue management practice.

The first failure is a single list that mixes who the guest is, how the booking arrived and which country the contract covers. The codes then overlap, and staff choose by habit or by whatever the list happens to show first. The second failure is the silent default. The system fills a code when nobody touches the field, that default becomes the largest segment, and everything else disappears inside it. The third failure is undocumented codes invented by one person: when that person leaves, nobody can say what the code meant, and the history stops being comparable.

What clean coding buys is modest but real. You get an ADR by segment you can compare across months, a pace you can read segment by segment, and a defensible answer in a contract review. None of that requires new software; it requires the fields to be separated and the rules to be written down.

Which fields do you need: segment, source, channel, market and board?#

Each of the five answers a different question, and each needs its own field. When two of them share a field, one of the two questions stops being answerable.

Segment answers who buys and how the booking is bought, and it is the field that pricing and reporting rules hang on. Source names the company, contract or partner that produced the booking: a named agency, a corporate account, the hotel's own website. It is a party, not a category. Channel answers through which system the booking arrived; the same agency can send a booking through its own system or through a booking site, and the two behave differently when something goes wrong.

Source market answers which market the contract or rate covers, and board type answers what the price includes. Board type belongs to the rate, not to the segment name, or you end up with a code list that doubles every time a board changes. The test for a new field is simple: name the report or decision that cannot be made without it. If there is no such report, do not add the field.

Why source market is not guest nationality#

Source market is a commercial attribute of a contract: it says which market the negotiated rate was built for. It is not the guest's nationality, and it should never be filled from a passport or an identity document. A German agency can sell an all-inclusive contract for the German market to a family whose members hold three different passports; the contract is still one line, in one market. Keeping source market on the contract and the rate, and off the guest record, also keeps you away from personal data you do not need for the report, which is the safer position under any privacy regime.

What should a starter segment code list look like?#

Start with six to eight codes that match how the hotel actually sells today, and add a code only when a report or a contract needs the split.

For example: individual direct, booking-site business, corporate negotiated, group, agency allotment, agency free sale. A hotel with airline crew or long-stay contracts adds one code for each, not a family of codes. Allotment and free sale must stay apart: allotment means the agency holds rooms the hotel has committed, free sale means the agency sells and the hotel confirms each booking. They behave differently in pace and carry different cancellation risk, so merging them hides exactly the difference a contract review needs.

Write one line per code: what it means, who may use it, and one example booking. A code without a written rule is a code that will drift. Keep names fixed and free of dates, hotel names or staff initials, because a code whose meaning changes between seasons makes last year's comparison useless.

Give a group one master code, and let the individual rooms inside it inherit that code, so the group's revenue and its displacement can be measured together. And retire codes instead of deleting them: old bookings keep the code they were made with, while new bookings cannot select it.

What changes for a resort that sells through agencies?#

Two fields carry most of the weight: the source market the contract covers and the board type the price includes. Without them, two contracts that look identical in the system are not comparable.

One agency can hold several contracts, each for a different market and a different board. If the agency is the only thing recorded, the contracts collapse into one line and the review cannot tell which one worked. Board type changes what the guest is buying and what the hotel must deliver: a room-only rate and an all-inclusive rate from the same market are not the same product and should not be averaged into one figure.

Record board type on the rate, and let the booking inherit it. Typing it per booking invites a mismatch between what was sold and what the kitchen and the front desk expect. When you review an agency, read production by source market and board together; a market that looks weak overall can be strong on one board and weak on another, and that distinction is worth money at the next negotiation.

Who assigns the code, and what should the booking screen require?#

The person who takes the booking assigns the code, at the moment of booking, and the screen should refuse to save without one.

Reservations owns the field at entry. Sales owns the contract-level default, meaning which segment and source market a contracted rate carries. Finance owns the reconciliation, not the original entry. Make the field required, with no silent default; if a default exists, show it on screen and require the agent to accept it deliberately.

Pre-fill what the contract already decides. A corporate rate is corporate; an allotment booking from a contracted agency is agency allotment. The agent should be confirming, not choosing from a long list every time. For bookings that arrive through a partner system, map the incoming partner or rate to a segment once, in the integration settings, instead of retyping it per booking. One mapping reviewed monthly beats a hundred manual choices.

Put the code list on the reservations desk and train once at setup, then once whenever a code is added or retired. Give the agent a free-text note field next to the code: the note is where the odd booking explains itself, and it is what makes the monthly check fast.

How do you clean up miscoded bookings every month?#

Run one short pass over the previous month, look for combinations that should not exist, correct them with a note, and then fix the rule that allowed them.

Pick a fixed day and a fixed scope: last month's bookings, with segment, source, channel, market, board type, rate code, nights and room revenue in one export. Correct with an audit trail: void and re-enter, or change the field with a reason, but never delete a booking to fix a code. Keep a one-page log of what was corrected and why, so next month's check starts where this one ended.

Compare each segment with its own previous months, not with an industry figure. A sudden jump in one segment usually means a default, a mapping change or a new rate, not a new market. This is the same discipline described in hotel data quality work before AI: clean the input, and every downstream report improves at once.

Which reports depend on clean segment codes?#

Pace, ADR by segment, displacement and contract reviews all read the same field, so one miscoded booking can show up in four places.

Pace compares bookings on the books for a future arrival date with the same point in a previous period. A segment carrying the wrong code makes pace look like demand that is not there. ADR by segment is room revenue divided by rooms sold, calculated per segment, and it is only comparable across segments if the posting rules are the same: a group rate that carries meals inside the room rate cannot be set beside a room-only rate. The formulas themselves are simple, and the common mistakes are in what goes into them, as covered in RevPAR, ADR and occupancy rate formulas.

Displacement asks whether a group's rooms would earn more sold to another segment, and that question needs the group to have its own code and its own rate, or the comparison has no second side; the full method is in group displacement analysis. Contract reviews ask whether an agency's production and rate still make sense, and they need allotment and free sale kept apart, with the source market recorded on the contract.

What to do next#

Write the one-page code list this week, make the segment field required at booking, and put the first monthly check in the calendar before the next contract review. The five fields, the short list and the monthly pass are one system: the fields make the list usable, the list makes the check fast, and the check is what keeps pace, ADR by segment and your agency reviews measuring the same thing.