How to Set Seasonal Rates for a Short-Term Rental
Most rate cards are three numbers and a guess
Ask a host for their rates and you’ll usually get something like: “about 620 normally, 810 in high season, and 1,500 over Christmas and New Year.” Which is a perfectly good rate card. The trouble starts when you try to express it in software.
Many booking systems only let you set one base price and percentage adjustments. So you’re asked to describe 1,500 as “+142% on the base”, and to keep that percentage correct as the base moves. That’s not how you think about your rates, it’s not how they appear on your listing elsewhere, and the first time you adjust the base every season silently changes.
This guide covers the model that actually fits: seasons as first-class things, three ways to price one, and the two mechanisms — discounts and escalation — that sit on top.
Start with absolute rates where you have them
The first decision is per season, and there are three sensible modes:
A fixed nightly rate. The season costs what it costs. 1,500 is 1,500, not a percentage of anything. Use this whenever you have a rack rate that must match a number published elsewhere, because a percentage will drift away from it the moment you touch the base.
A percentage above or below a base. Genuinely useful when a season is defined relative to normal — “shoulder season is 15% off” is a real pricing policy, and expressing it as a percentage means it stays correct when you reprice.
No price change at all. An underrated option. A season that exists purely to set a minimum stay — a four-night minimum over a public holiday, say — without touching the rate. Seasons are as much about the rules as the price.
Mixing modes is normal. Fixed rates for your named seasons, a percentage for shoulder, and a no-price season for the school-holiday minimum stay.
Make seasons recur, or you’ll redo this every year
A season should be stored as month and day, not a date — 15 December to 10 January, every year — and expanded to real dates when a price is calculated for a specific stay.
Two things to check in whatever you’re using:
Does a season that crosses New Year work? A range from 15 December to 10 January is, naively read, a range that ends before it starts. It has to be split at the year boundary and handled as two spans. If your tool silently prices those nights at the base rate, your most valuable fortnight of the year is being sold cheap.
Are seasons set once, or re-entered annually? If you’re typing next year’s dates in every autumn, you will eventually forget, and you’ll find out from a booking.
Length-of-stay discounts, and where they apply
On top of seasonal rates sit discount rules. The common set, which maps to what the large channels already offer so your direct rates stay comparable:
- Weekly — seven nights or more
- Monthly — twenty-eight nights or more
- Last-minute — within a few days of arrival
- Early bird — booked well in advance
- Trip length — your own thresholds
- Custom promotions — with usage limits, so a code can’t be shared into oblivion
Two details decide whether these behave sanely.
Stacking. Some discounts should combine and some absolutely shouldn’t. A weekly discount plus an early-bird discount plus a promo code is three reductions on one booking, and if your tool applies all three by default you’ll discover it in your margin rather than in your settings. Each rule needs to declare whether it stacks.
Order of operations. Discounts should apply after the seasonal accommodation total and before fees and taxes. If a length-of-stay discount is applied after the cleaning fee, you’re discounting your cleaner’s wages. If it’s applied after tax, your tax figure is wrong. This sounds pedantic until an accountant asks you to explain a line.
The yearly increase, and the detail that catches everyone
Most hosts raise rates once a year, in a hurry, from memory. A yearly escalation makes it a setting rather than an annual scramble: a percentage, a base year, and compounding from there.
Two things to get right.
Escalate per season, not per property. Your peak season might be exactly right where it is while a quiet season needs a different treatment entirely. A single flat percentage across the property applies the same medicine to both.
Compound by the year of the night, not the year of the booking. This is the one that catches people. A guest booking in December for the following August should get August’s rate, escalated for August’s year. If escalation keys off the booking date instead, then booking eighteen months ahead quietly buys last year’s prices — and a stay that crosses New Year is priced wrong on one side of it. Nobody notices until a guest works it out and tells their friends.
Check what you achieved, not what you charged
Here’s the step that turns rate-setting from guesswork into a decision.
The number that matters isn’t the rate on your listing. It’s what you actually achieved per night, by season — because the gap between the two is the entire story. A season that’s fully booked at 80% of its nominal rate is telling you the listed rate is fiction. A season achieving 98% and selling out early is telling you it’s cheap.
Two rules worth applying before you act on that:
Only raise a season that’s achieving close to what you already ask. If a season isn’t getting the rate you’ve set, price isn’t the constraint — raising it is the wrong lever. A reasonable threshold is 95% of the set rate over the last full year.
Don’t move more than about 15% on one year’s evidence. One exceptional season is a story. Two years agreeing is a trend. This rule mostly protects you from yourself after a good summer.
And watch what’s inside the “achieved” figure. If your per-night number is derived from the total booking value, it probably includes the cleaning fee — which makes short stays look like they’re beating a room rate that excludes cleaning. On one real property, seventeen of twenty-five bookings carried a cleaning fee of around $116 against a 4.4-night average stay. That’s a meaningful distortion in exactly the seasons where stays are shortest. Strip it before you draw conclusions.
A workable sequence
If you’re setting this up from scratch:
- Write down your rate card the way you’d say it out loud. Named seasons, absolute numbers where you have them.
- Enter seasons as recurring month-day ranges. Check the one that crosses New Year.
- Add minimum stays as season rules, including any no-price seasons that exist only for that.
- Add length-of-stay discounts to match what your channels already offer, and decide explicitly what stacks.
- Check the order: accommodation, then discounts, then cleaning, fees and taxes.
- Leave escalation off until you have a year of data. Then set it per season, from achieved rates.
- Once a year, compare achieved against set, season by season, and move only the ones the evidence supports.
That’s a rate card that survives contact with a real calendar, and an annual review that takes twenty minutes instead of a nervous afternoon.
Related: Price Next Season Before You Have To for how Airflow recommends the increase, One Resource or One Hundred for applying this across a portfolio, and Your Own Booking Engine, For Free for taking the direct bookings these rates apply to.