Hotel dynamic pricing: a practical guide to rules that work
Hotel dynamic pricing moves room rates with demand using occupancy and lead-time rules, seasons and events, kept inside a floor and ceiling you set.
Hotel dynamic pricing means changing room prices as demand changes, instead of keeping one price per season. In practice, hotels set a base rate, then use clear rules based on occupancy, lead time, seasons and events to move it up or down within a floor and a ceiling. Good rules are simple, tested and reviewed often.
What is dynamic pricing for hotels?
A hotel room is perishable. If it is not sold tonight, tonight’s revenue is gone. Demand also changes all the time: a conference is announced, a flight route opens, a heatwave arrives. Dynamic pricing lets your rate follow these changes.
It is not about charging as much as possible. It is about charging the right price for each night, so you fill quiet dates and earn more on busy ones. Done well, guests see prices that make sense for the date. Done badly, prices jump around and guests lose trust.
Dynamic pricing usually works on your best available rate (BAR). Other rate plans, such as member rates and packages, are linked to BAR and move with it.
What drives a hotel’s price?
Most rule-based pricing uses four inputs:
- Occupancy: how full you already are for a date. The fuller you are, the less you need to discount.
- Lead time: how many days remain until arrival. Different guests book at different points, and your options change as the date gets close.
- Seasons: predictable periods of higher or lower demand, such as winter sun, summer holidays or a monsoon low season.
- Events and special dates: one-off or annual demand peaks, such as exhibitions, concerts, sports events, national holidays and religious festivals.
Many revenue managers also watch market prices from similar hotels and pick-up, the number of new bookings since the last check. These help you decide when to adjust your rules.
How do occupancy-based pricing rules work?
An occupancy rule changes the price when on-the-books occupancy for a date crosses a threshold. You set bands and an adjustment for each.
Example: a 60-room hotel with a base BAR of $200 sets these rules.
| Occupancy for the date | Adjustment | BAR shown |
|---|---|---|
| Below 50% | No change | $200 |
| 50% to 69% | +5% | $210 |
| 70% to 84% | +10% | $220 |
| 85% and above | +20% | $240 |
Examples use US dollars; the same maths works in any currency.
For this hotel, 50% means 30 rooms sold, 70% means 42 and 85% means 51. As bookings come in, the price steps up. The thresholds and percentages are an illustration. Pick values that fit your own demand and your market.
Keep bands wide enough that prices do not change after every single booking. Small, frequent jumps confuse guests who check twice in one day.
How do lead-time rules work?
A lead-time rule changes the price based on how far ahead the guest books. There are two common patterns:
- Early bird: a discount for guests who book well in advance and commit early, often on a prepaid plan.
- Last minute: a discount close to arrival to fill rooms that would otherwise stay empty.
Some hotels do the opposite close to arrival: if a date is already busy, they raise the price for late bookers. Combine lead time with occupancy so you discount only when the date needs it.
Example rules for the same hotel:
| Rule | Condition | Adjustment | Price from $200 base |
|---|---|---|---|
| Early bird | Booked 60 or more days ahead | -10% | $180 |
| Last minute | 3 days or fewer to arrival and occupancy below 50% | -15% | $170 |
| Late demand | 3 days or fewer to arrival and occupancy 85% or above | +10% | $220 |
In goDirects, dynamic pricing rules use occupancy and lead time, and promotions cover early bird, last minute and promo codes.
How should you price seasons and events?
Seasons and events are known in advance, so set them first. Rules then work on top of a sensible seasonal base.
- Build a 12-month calendar. Mark high, shoulder and low seasons from your own past data.
- Add special dates. Public holidays, school breaks, religious festivals and major local events. Check official event and holiday calendars, as dates can move from year to year.
- Set a base BAR for each season and a higher base for each special date.
- Add stay restrictions where needed. A minimum stay on an event weekend often matters as much as price. See stay restrictions explained.
- Load prices early. Some guests book events months ahead. If your calendar shows a low-season price for an event date, you sell it cheap and cannot undo it.
In goDirects, seasons and special dates are set in ARI Studio, with bulk changes across dates and room types.
How do pricing rules combine?
When two rules apply to the same night, the result depends on how the system combines them. Know this before you go live.
Example: a date has occupancy of 72% (+10%) and is within a lead-time window with +5%.
- If adjustments add up: +10% and +5% = +15%, so $200 becomes $230.
- If adjustments multiply: $200 x 1.10 x 1.05 = $231.
The gap is small here but grows with larger adjustments. Also check how discounts stack with promo codes and member rates. A member rate on top of a last-minute rate on top of a promo code can push the price below your floor.
Floors, ceilings and guardrails
Every pricing setup needs limits:
- Floor: the lowest price you will accept for a room type. It should cover your cost per occupied room and your distribution cost.
- Ceiling: the highest price you are comfortable showing. It protects your reputation and avoids prices that look like errors.
- Channel check: your website price should not be higher than the OTA price for the same room and night. OTA Price Match checks OTA prices for upcoming nights and keeps your direct price lowest within the floor you set.
- Clear totals: show taxes and fees clearly. In goDirects, totals with taxes and fees are calculated on the server.
A weekly dynamic pricing routine
- Check on-the-books occupancy and pick-up for the next 90 days.
- Compare with the same dates last year, if you have the data.
- Look at similar hotels’ prices for your busiest and quietest upcoming dates.
- Check that events and holidays are loaded for the next 12 months.
- Review rule results: did prices move as expected? Did any date hit the floor or ceiling?
- Adjust thresholds or percentages slowly, one change at a time, so you can see what worked.
- Track results with ADR, occupancy and RevPAR, not ADR alone.
To see occupancy and lead-time rules working with your rates, book a demo of goDirects.
Frequently asked questions
Is dynamic pricing fair to guests?
It can be, if prices are clear and consistent. Guests already expect hotel prices to change by date. Problems come from sudden large jumps, hidden fees or a direct price higher than an OTA. Use sensible bands, a ceiling, and clear totals, and offer direct-booking value such as member rates.
Do small hotels need dynamic pricing?
Yes, often more than large ones. With few rooms, each unsold night is a larger share of revenue. A small hotel does not need complex tools to start. A few occupancy bands, early bird and last minute rules, and a calendar of events can make a clear difference to how prices follow demand.
How often should prices change?
Prices can update whenever a rule’s condition changes, but you should review the rules themselves on a routine, such as weekly, and more often in busy periods. Avoid very narrow occupancy bands that move the price after every booking, as this confuses returning visitors.
Should dynamic pricing go below my floor on quiet nights?
No. A floor exists so that no booking loses money once you count the cost of servicing the room and the cost of the channel. On quiet nights, try targeted offers, added value or a shorter minimum stay before you cut deeper.
Does dynamic pricing replace a revenue manager?
No. Rules automate routine changes, but someone still needs to set the rules, load events, read the market and decide strategy. In a small hotel this may be the owner or general manager. Rules free up their time for that work instead of manual price edits on every date.