Price Elasticity

In hotel revenue management, price elasticity is how much the demand for your rooms changes when you change the rate, and the single most useful thing to know about it is that it belongs to the date rather than to the property.

"Our guests are price sensitive" is the most expensive sentence in independent hotel pricing, because it takes something true of some dates and applies it to all of them.

See how ampliphi prices for independent hotels

Get a free revenue audit · Book a demo

What is price elasticity?

The responsiveness of demand to price, borrowed from economics and applied to a room night.

Demand is elastic when a price change produces a larger proportional change in bookings. Raise the rate ten percent and lose twenty percent of your demand, and the date is elastic. Demand is inelastic when the change in bookings is proportionally smaller, or barely there at all.

The economics textbook treats elasticity as a property of a product in a market. Hotels are a poor fit for that, because the same room in the same building is a different product on different nights. The room is highly elastic on a soft Tuesday 40 days out, where the traveller has dozens of alternatives and no urgency. It is close to perfectly inelastic on a compression night three days out, where the alternatives are gone and the guest has a reason to be in town.

So the question worth asking is never whether your guests are price sensitive. It is whether this date is, and the answer changes by day of week, by season, by lead time and by who is travelling.

Three drivers do most of the work. Alternatives: how many comparable rooms are available nearby at that moment. Urgency: whether the traveller has a fixed reason to be there. Lead time: late bookers are consistently less price-sensitive than early ones, which is precisely why discounting in the final week is such a poor trade.

Resources: Compression night · Booking pace · ADR

How price elasticity works in practice

You do not calculate it. You observe it, on comparable dates, one change at a time.

Worked example. A 46-room inn tests two dates. It raises a soft November Tuesday from $148 to $168, a 13.5 percent increase, and seven-day pickup on that date falls from a typical nine rooms to five, a 44 percent drop. That date is clearly elastic and the increase cost more than it earned. Separately it raises a festival Saturday from $205 to $268, a 31 percent increase, and pickup barely moves. That date is close to inelastic and the property had been leaving money on it every year. Same building, same rooms, same guests in the aggregate, opposite behaviour.

That contrast is the whole practical content of the concept.

The everyday use is deciding where to be brave. Dates with few alternatives, high urgency and short lead time can carry rate increases that feel uncomfortable and are not. Dates with abundant alternatives and no particular reason to travel cannot, and a rate increase there is simply a booking given to a competitor.

Testing it properly is harder than it looks and worth doing loosely rather than not at all. Change one thing, on a category of dates rather than a single date, and measure pickup over a fixed window rather than watching bookings-to-date. A single date at 46 rooms carries too much noise to conclude anything, and four comparable Tuesdays carry rather less.

The honest limit is that you cannot run a clean experiment on your own inventory. Demand moves for reasons you did not cause, competitors change their rates, the weather turns. What you can get is a direction, repeated enough times to be believable.

Resources: Demand forecasting · Dynamic pricing

Why price elasticity matters for independent hotels

Because the belief that guests are price sensitive is usually formed on the wrong dates and then applied to the right ones.

An owner who has watched midweek shoulder-season rooms fail to sell at $155 has genuinely learned something about elasticity on those dates. The trouble starts when the lesson becomes a property-level belief, and the same owner prices a festival Saturday at $205 because raising it further feels risky. The Saturday was the date where the belief did not apply, and it is the date where being wrong is most expensive.

The reverse error also exists. A property that raises rates uniformly because a consultant said independents underprice will lose midweek business it needed, on dates where the market genuinely will not pay.

The useful discipline is holding both at once: most of your dates are elastic and a small number are not, and the whole skill is telling them apart. That is what booking pace and a rate shop are for.

Resources: Revenue management for independent hotels

How to test price elasticity at your property

1. Test a category of dates, not one date. Four comparable Tuesdays tell you something. One tells you nothing.
2. Change one variable at a time. A rate change alongside a new offer or a restriction teaches you nothing about either.
3. Measure pickup over a fixed window, typically seven or fourteen days, rather than watching total bookings drift.
4. Expect noise and repeat. At 46 rooms a two-room difference is meaningless on its own.
5. Test upward on strong dates first. That is where the unclaimed money is and where the downside is smallest.
6. Write down what you changed and what happened. Elasticity findings are only useful if they survive to next year.

Resources: RevPAR · Booking pace

What price elasticity will not tell you

It cannot be isolated. Every test you run is confounded by competitor pricing, weather, events, your own visibility and whatever the market was doing that week, and none of those hold still while you experiment.

It does not survive being averaged. A property-level elasticity figure blends dates that behave in opposite directions and describes none of them, which is exactly the mistake the concept is supposed to prevent.

And it says nothing about the right price. Knowing a date is inelastic tells you the rate can go higher and never how much higher, and the only way to find the ceiling is to move in steps and watch what happens.

How ampliphi approaches price sensitivity

Ampliphi does not model elasticity explicitly. There is no elasticity curve being fitted and no coefficient being estimated per date, and it is worth saying so plainly because the category invites the assumption.

What the everyday rate suggestion does is respond to behaviour. It is demand-based, built on booking pace and occupancy, so a date filling faster than its own history gets a higher suggestion, and a date that slows after a rate moves shows up in the pace signal that feeds the next one. That is responsiveness to observed demand rather than a model of how demand responds to price, and the two are related without being the same thing.

The practical effect is that the strong dates, where inelasticity is real and money is usually left behind, get pushed upward as they fill rather than sitting at a rate set months ago. The suggestion covers your base rate and the differential between room types, you approve every rate before it publishes, and ampliphi runs on top of the PMS you already use.

Key takeaways: price elasticity

• How much demand changes when you change the rate.
• It belongs to the date, not to the property. The same room behaves differently on different nights.
• Three drivers: available alternatives, the traveller's urgency, and lead time.
• Late bookers are consistently less price-sensitive, which is why late discounting is such a poor trade.
• "Our guests are price sensitive" is a lesson learned on soft dates and misapplied to strong ones.
• You cannot run a clean test on your own inventory. Aim for a direction repeated often enough to believe.

Frequently asked questions about price elasticity

Are hotel guests price sensitive?

On most dates yes, on some dates hardly at all, and the difference is what actually matters.

A traveller choosing between a dozen available properties for an ordinary Tuesday is extremely price sensitive. The same traveller trying to find a room on the Saturday of a festival, with three options left in the town, is not. Neither fact is about your guests. Both are about the market conditions on a particular night.

Treating sensitivity as a fixed characteristic of your clientele leads directly to underpricing your best dates, which for most independents is a larger loss than any midweek discounting.

How do I measure price elasticity at my hotel?

Loosely, across categories of dates, by watching pickup after a change.

Pick four or five comparable dates, change the rate on them, and measure seven-day or fourteen-day pickup against what those dates normally do. Repeat it. A single test at 46 rooms is dominated by noise, and the pattern across several is where the information is.

Do not expect a number. What you are after is a direction: this kind of date tolerated a fifteen percent increase, that kind did not. That is enough to price better and it is about as much as your data supports.

Does raising rates always reduce bookings?

No, and on some dates it barely affects them at all.

On an inelastic date the constraint on the traveller is availability rather than price. If the market is short of rooms and they have a reason to be in town, a thirty percent increase can leave pickup essentially unchanged, which is exactly what a compression night looks like from inside the property.

There is also a smaller effect worth knowing: at the very bottom of a market, an unusually low rate can signal poor quality and reduce bookings. That is rare and real, and it is a reason not to assume the cheapest rate always wins.

Why are last-minute bookers less price sensitive?

Because their alternatives have mostly disappeared and their reason for travelling has not.

Someone booking three days out has usually committed to the trip, and the cheaper options in the market are frequently already sold. The comparison is no longer between your room and ten others, it is between your room and a long drive or no trip.

This is the single most commonly ignored fact in independent pricing, because it inverts the usual instinct. The final week is when properties discount hardest and when their remaining demand cares least about price.

Should I discount to fill a soft date?

Usually as the last lever rather than the first, even on genuinely elastic dates.

A discount applies to every guest including those who would have booked anyway, so on a date that will sell 25 rooms regardless, a $30 cut costs $750 before it produces a single extra booking. The cheaper moves come first: relax a restriction, open a rate plan you closed, extend an offer to the adjacent nights, reach a segment that books late.

When rate is the answer, move it modestly and early. A small change at 25 days has time to work. A large one at five days is mostly a gift to the guests who were coming anyway.

Related terms

Compression night

A date where market demand exceeds supply. The clearest real-world case of inelastic demand, and the one most often underpriced.

Booking pace

How a date is filling against its own history. The signal that tells you which kind of date you are looking at before you change anything.

ADR

The average rate achieved per room sold. What moves when a rate change works, and what falls when a discount was unnecessary.

RevPAR

Room revenue per available room. The number that settles whether a rate change was right, since it cannot be gamed by rate or occupancy alone.

Demand forecasting

Predicting how a date will finish. Elasticity is about how that prediction changes when you change the price.