VACATIO COLUMN

Dynamic pricing 101: data over instinct

2026.08.29

A graph showing room revenue changing with automated rate adjustment

Dynamic pricing means adjusting room rates daily according to demand. It sounds exotic but has long been standard in airlines and lodging; the hard part is not the concept but deciding, on what basis, how much to raise or lower. Building that basis starts with three metrics everyone in the property defines the same way.

Three metrics: occupancy, ADR, RevPAR

  • Occupancy = rooms sold ÷ rooms available. How full you were.
  • ADR (Average Daily Rate) = room revenue ÷ rooms sold. What each sold room went for.
  • RevPAR (Revenue Per Available Room) = room revenue ÷ rooms available. The industry-standard identity is RevPAR = occupancy × ADR.

You need all three because occupancy and ADR trade against each other. Cut the price and occupancy rises while ADR falls; raise it and the reverse happens. Targeting either one alone guarantees losing the other, which is why their product, RevPAR, is the number you steer by.

The opportunity cost of a flat rate, in arithmetic

Take a 20-room property selling at one price. The rate is fixed at 100,000 KRW and on a peak Saturday all 20 rooms sell before 3pm. A sellout looks like a win, but selling out early means demand exceeded supply at that price. If 20 rooms would also have sold at 120,000, that day left 400,000 KRW on the table. Ten such Saturdays in a season is 4,000,000.

The other direction costs just as much. On an off-peak Tuesday, that same 100,000 sells only 6 rooms: revenue 600,000, RevPAR 30,000. Drop to 70,000 and sell 14: revenue 980,000, RevPAR 49,000. ADR fell by 30,000 while RevPAR rose. Which direction is right depends on that date’s demand, and a flat rate is wrong in both cases.

An operations dashboard showing occupancy, ADR and daily revenue together
The number to steer by is neither occupancy nor ADR but their product. Neither a sellout nor a high rate is a result on its own.

Three axes of demand: weekday, season, lead time

Weekday is the most regular axis. Leisure properties cluster on Friday and Saturday, business-driven ones on Tuesday and Wednesday, and the weekly pattern repeats. Because it repeats it is predictable, and because it is predictable it can be priced in advance. If you do not yet have a weekday rate table, that is the first thing to build.

Season has the widest amplitude. Fixed-date drivers such as school holidays, public holidays and local events go straight on the calendar; unsettled ones such as weather or a change in nearby supply have to be read from booking pace. The point is not to reduce the year to two buckets: within one peak season, the first week and the last week behave differently.

Lead time, the interval between booking and stay, is the most often ignored axis. For the same date, a booking made two months out and one made today come from different buyers. Reading remaining inventory against remaining time gives you the call: half the rooms open three days before arrival argues for filling them at a lower price, while 80% sold three weeks out is no reason to rush the rest.

A standalone stay whose demand swings by weekday and season

Why doing this by hand breaks down

The combinations. Three room types across five channels is 15 decisions a day, or 450 over a month of forward dates. Layer weekday, season and lead time on top and all of it has to be recomputed daily. What a person can supply is the direction of judgement, not a recalculation at that scale.

When adopting automated pricing, check explainability before accuracy. If you cannot see why a price moved, you will eventually switch it off. It only stays on if manual overrides such as floors, ceilings and pinned dates coexist with it.

The order: track the three metrics daily under one definition, write down demand patterns along weekday, season and lead time, then translate those patterns into rate rules. The moment the number of rules exceeds what you can redo in a day is the moment for an RMS.

FAQ

Q. Will guests object if prices change often?

Rates varying by date are already familiar from airlines and lodging. What causes friction is not variation itself but a sharp drop right after someone books the same conditions. So operate with a floor, a cap on how far a rate can move, and a rule that confirmed bookings are never repriced retroactively. With a clear cancellation and refund policy, most objections resolve there.

Q. Should I not aim for 100% occupancy?

Chasing occupancy alone pushes you in only one direction: down. Since RevPAR = occupancy × ADR, a rise in occupancy that costs more in ADR reduces revenue. In particular, a date that sells out early is a signal that demand exceeded supply at that price, so treat it as evidence for raising the rate next time the same conditions occur.

Q. Do small properties need dynamic pricing too?

The trigger is the number of pricing combinations and the spread of demand, not room count. A small property with several room types and a sharp seasonal swing pays the full opportunity cost of a flat rate. With one room type and flat year-round demand, it is low priority. Recording the three metrics for a single month makes clear which case you are.