How to set hotel room rates: cost floor, demand and the guest’s alternatives

A hotel room rate is the price of one room for one night. Set it by passing three tests in order: it must cover the cost of the stay, fit what is already booked for that date, and make sense next to the alternatives the guest can see. Write the rules down before you need them.

A room is still unsold at ten in the evening on a night that looked full three months ago. Someone opens the rate screen and lowers the price by feel. Nothing about that decision is written down, so nothing about it can be reviewed, repeated or corrected. This guide turns hotel pricing strategy into three tests, a base rate grid, a written rule for who may move a rate and by how much, and a one-line log for every change.

What three tests should every room rate pass?#

Three, in this order: the cost floor, the demand already on the books for that date, and the alternatives the guest can see. Each test answers a different question, and skipping one produces a different kind of mistake.

Test one is the floor: the lowest rate at which a room night still contributes to the hotel instead of costing it money. The hotel sets it before the date, not during it. Test two is demand: what is already sold for that date, compared with the same point before comparable dates. It moves the rate inside the band the other two tests allow. Test three is the guest's alternatives: the prices the guest can actually see for the same dates, room type and terms, plus the option of not coming at all.

The order matters because the failures differ. A rate below the floor loses money on every sale and cannot be recovered; a rate that ignores demand leaves money on the table; a rate that ignores alternatives sells nothing. Only the first is permanent.

Each test produces something different: a number (the floor), a position (ahead, on pace or behind), and a band (the range the guest will compare). A rate decision is choosing a point inside the band that sits above the floor. The common mistake is starting from a competitor's price and working backwards, which makes the guest's alternatives the only test and quietly drops the other two. The tests describe what is known today; they are not a forecast, and a rate is not a prediction of what the date will do.

How do you work out the cost floor for a room night?#

Add the cost that appears only when a room is sold to a share of the costs the hotel pays whether the room sells or not. The result is a floor per room night, the number below which a sale costs the hotel money.

Variable costs per occupied night include housekeeping time and supplies, laundry, the breakfast and board items a guest actually consumes, in-room consumables, the utilities a guest uses, and any commission or channel fee charged per booking. Fixed costs do not disappear on a quiet night: rent or the building, permanent salaries, insurance, systems and licences. Divide them by the room nights the hotel expects to sell in the period, not by the rooms it owns.

The floor moves with expected occupancy. At a low expected occupancy the fixed share per night rises, so the floor rises. A floor set once a year and never revisited is usually wrong by the second half of the year. Review it whenever a large cost changes: a wage settlement, a utility contract, a new commission agreement, or a change in what the board base includes.

Taxes and duties the hotel collects and passes on are not part of the floor; they sit on top of it. Ask an accountant which lines on your own bill are which, because the treatment differs by tax and by the hotel's status.

The floor is a decision, not an accounting output. A hotel may choose to sit above its calculated floor, or accept a sale below it for a named reason. What it should not do is discover afterwards that it did. Set the floor per room type, not per hotel: a suite costs more to clean, stock and heat than a standard room, so its floor is higher.

For example, if a room costs 400 lira in variable cost to sell for a night and the hotel's fixed costs work out at 600 lira per expected room night, the floor is 1,000 lira before taxes. The numbers are illustrative; the structure is the point.

How do you read demand from the rooms already on the books?#

Compare the rooms already sold for a date with the rooms that were sold for comparable dates at the same distance from arrival. That comparison, not the season, is the demand test.

Pickup is the change in rooms sold for a future date over a period. Pace is pickup measured against the same point before a comparable date. Both are read from the reservation system, not from memory. The comparable date matters more than the number: a bayram week, a trade fair, a concert, a school holiday and an ordinary Tuesday each have their own curve. Compare like with like or the comparison says nothing.

Read rooms, not revenue. Revenue mixes rate and volume, so a revenue figure can look healthy while the room count for the date is behind. Segments also book on different curves: groups and tour operators commit early, while direct and last-minute business arrives late. A date that looks behind may simply be waiting for a segment that always books late.

The output is a position, not a price: ahead, on pace or behind. Each position narrows the band the other two tests allow and points to a different action: hold, raise, or open the date to a segment nobody has asked yet. Restrictions are a separate lever from price; a minimum stay or a closed-to-arrival rule changes what the date sells without changing the number on the screen. Keep the two decisions apart and review them separately.

No outside benchmark is used here on purpose. Pace bands are built from the hotel's own history; an industry average would describe a different hotel in a different place. For a fuller treatment of reading pace day by day, see the guide to the hotel pickup report.

What are the guest's alternatives, and how do they set the ceiling?#

The guest compares your total price for the same dates and terms with the other places they can see, and with not booking at all. That comparison sets the ceiling, and it is wider than most hotels assume.

The comparison set is what the guest sees, not the set the hotel chooses. It includes other properties in the same area and price band, other destinations, a shorter stay, a different week, and staying home. Compare total price, not room rate: breakfast, taxes and fees, parking, cancellation terms and payment timing all change what the guest pays and what they risk. Two rates are only comparable when the date, room type, occupancy, board base and cancellation terms match; anything else is a different product with a different price.

Being above the band is not automatically wrong. A guest will pay more for something they can see: a location, a room, a service, a term. If the difference cannot be said in one sentence at the desk, the rate is the problem. Being below the band is not automatically safe: check the floor and the demand read first, because a low rate that fills rooms the hotel could have sold anyway costs money and teaches the market to wait.

Matching a competitor's rate is not a strategy. You do not know their cost floor, their occupancy or their contract terms, so a match copies a decision made with information you do not have. Watch, too, the alternatives that are not hotels: apartments, guesthouses and rooms let by their owners compete for the same guest on price and on length of stay.

If one line fails, the comparison is a different product, not a cheaper one.

How do you build a base rate grid by season, day of week and room type?#

Choose one reference night, set its rate, and derive every other rate from it by written steps for season, day of week and room type. The grid is a starting point, not a price.

Define the reference first: usually a standard room, double occupancy, room only or bed and breakfast, on an ordinary mid-week night in a named month. Everything else is expressed as a step from it. Season bands come from the hotel's own history and the local calendar, not from a national season; a coastal hotel and a city hotel have different bands in the same month.

Day-of-week steps follow who books. Business hotels run mid-week, leisure hotels run at the weekend, and some markets have a dead day that no step will fix. Room type steps should follow something the guest can see: size, view, floor, bed, balcony, quiet. A step that cannot be explained at the desk will be argued about at the desk.

Board base steps, from room only through bed and breakfast, half board and all inclusive, should price the board as its own cost plus its own margin, so a guest upgrading does not silently buy the room cheaper. Keep the grid small enough to hold in your head: for example, three seasons, three day types and four room types give 36 cells; add three board bases and it is 108. Past that, derive rather than list. Date and version the grid, so that when a step changes, the change is visible, with the reason and the name of the person who made it.

This grid sits inside a broader working guide to hotel revenue management for independent hotels.

When should a person move a rate, and by how much?#

Only when a named trigger fires, and only by a step the written rule allows. The rule is written before the date, when nobody is under pressure.

Triggers worth writing down include: pickup outside the pace band for a comparable date, a group or series request large enough to change the date, a verified move by properties the guest actually compares, a cost change, and a date that has entered its final cancellation window with rooms still open. Size the step in money, not in a target. "Move this room type by one step, up to the next grid cell" is a rule; "raise by a set percentage because the month is behind" is a guess with a number attached.

Name who may approve what. A receptionist may apply a rule; a move outside the rule should need a revenue manager or the owner, and the approval should be recorded with the change. Separate the rate decision from the restriction decision: raising a rate and adding a two-night minimum are different answers to the same date, and they are reviewed differently. The details of those levers are covered in the guide to hotel rate restrictions: minimum stay, CTA and CTD.

Never move a rate to hit a revenue target. The target is a plan; the rate is a response to what the date is doing. Chasing a monthly number with the rate is how a hotel sells its best dates cheaply and its worst dates expensively. Never move below the floor without a named reason written next to the change: a group with food and beverage attached, a contract obligation, a segment test with an end date.

Software can hold the grid, calculate the steps and keep the log. It does not decide the price. A recommendation is an input to the rule, not a replacement for it; what to check before accepting one is covered in the guide to AI rate recommendations.

How do you keep contract, public and website rates in one structure, and log each change?#

Derive every channel from the same base grid by a written rule, and record each change in one log. One structure, many doors.

Contract rates for travel agencies and corporate clients are a rule applied to the base, not a separate price list. The rule names the base it uses, the step it applies and the floor it may not cross. Public and website rates come from the same base: when the base moves they move, and when they do not move, the reason should be written down.

Parity between channels is a contract question before it is a pricing question. Read what your agreements actually require and take advice on how they apply to your own channels. Board bases and room types multiply the cells, so keep the derivation visible: a change to one step should be traceable through every channel it touches.

The log holds one line per change: the date it applies to, the room type and board base, the old and new rate, the trigger, the rule applied, and the person who approved it. Review the log on a fixed cadence, monthly is enough. Look for rules that fire every day (the rule is wrong), rules that never fire (the trigger is wrong), and changes with no trigger (the discipline is wrong). The log is also the hotel's memory: when someone asks in six months why a date was priced the way it was, the answer is a line, not a recollection.

What to do next#

Start with the floor. Before the next rate change, write down the cost floor per room type, the comparable dates you will measure pickup against, and the rule that says who may move a rate and by how much. Then log the next change you make, even the small one. The three tests only work in order, and the order only holds if it is written down before the pressure arrives.