Get started with PriceLabs now!
Want to learn what PriceLabs can do for you? See for yourself with a free trial. Get started now!

Seasonal vacation rentals pricing means setting different nightly rates, minimum prices and minimum stays for each stretch of the year when demand in your market behaves differently. A beach rental that fills every night in July and sits empty in February needs two different pricing setups, not one average rate carried across both. This guide covers what seasonality is, how to map the seasons in your own market, what dynamic pricing handles for you by default, how to build custom seasonal profiles for the periods the default misses, and how to review the whole thing on a fixed schedule.
Seasonality is the part of your demand that repeats at roughly the same point every year. Ski towns peak between December and March, beach markets peak in summer, and city markets often peak twice, once around a convention season and once around a holiday period. The dates shift by a week or two each year, and the shape of the curve stays recognisable from one year to the next.
Three forces set the shape of that curve:
Pricing by season is a question of price floors as much as price ceilings. In peak weeks the risk is booking out early at last year's rates and leaving money on the table. In low weeks the risk is holding a minimum price that no guest in your market will pay, which turns a slow month into an empty one. Vacation rental seasonality is the pattern you price against, and the rest of this guide turns that pattern into settings you can act on today.
Start with your own past performance, because it is the only data that reflects your specific property. Pull the last 24 months of occupancy and ADR by month from Portfolio Analytics and sort each month into a band. Two years is enough to tell a repeating pattern from a one-off, and a month that lands in a different band across the two years is a month to watch rather than a season to define.
| Band | Occupancy over the last 24 months | What it usually means | Example months, summer beach market |
|---|---|---|---|
| Peak | Above 80% | Demand exceeds supply, and your floor is too low | Mid-June to end of August |
| Shoulder | 50% to 80% | Demand is real but price-sensitive | May, early June, September |
| Low | Below 50% | Price alone will not fill the calendar | October to April |
| Event | Varies, spikes for a few nights | Priced separately from the season around it | Festival week, Christmas fortnight |
Then widen the view to the market, because your own calendar only shows what you captured at the prices you charged. Market Dashboards shows month-on-month occupancy and rates for a comp set you build yourself, so you can see whether a weak March was your pricing or the whole market. Build one comp set of 10 to 20 listings that match your bedroom count, guest capacity and neighbourhood, name it, and use it as the filter for every chart you read afterwards.
Four inputs are worth collecting before you commit to any season dates:
Finish the mapping by writing down four to six seasons with explicit start and end dates. A workable set for a summer beach market is peak from mid-June to the end of August, shoulder in May, early June and September, low from October to April, with a separate profile for the Christmas and New Year fortnight. The dates matter more than the labels, because the dates are what you will enter into your settings. Neighborhood Data is a useful cross-check at this stage, since it shows the same seasonal curve from a different angle than your comp set does.
We apply seasonality to your prices by default, so the baseline work is done before you build a single custom profile. Our Hyper Local Pulse algorithm reads a hyper-local comp set rather than a broad market average, which is what lets a beach neighbourhood and an old town in the same city carry different seasonal curves. You can see the effect on any date by opening the pricing tooltip in Review Prices, where Seasonality, Demand Factor and Pacing Factor are listed separately under Market Factors.
The data behind those factors refreshes on a set cycle, built from what comparable listings on Airbnb and Vrbo are charging in your area:
| What happens | How often |
|---|---|
| Pricing and availability collected from existing Airbnb and Vrbo listings | Every 2 days |
| Pricing and availability collected from newly created listings | Every 15 days |
| Your prices recalculated | Every 24 hours |
| Updated prices pushed to your property management system | Every 24 hours |
Manual seasonal pricing cannot match that cadence across a portfolio, and it tends to fail in the same two places every year. The first is the shoulder weeks nobody remembers to reprice, and the second is the events announced three months out, which is why shoulder season pricing and event pricing are usually the two quickest wins in a seasonal market.
What the default cannot know is the part of your seasonality that lives in your head. A month your market reads as low but that your property has always sold well, a snowbird season that starts earlier than the market average, or a property you refuse to rent below a certain figure in August are all cases for a custom profile on top of the default. Dynamic pricing sets the baseline, and your customizations handle the exceptions.
A custom seasonal profile applies its own price and minimum stay rules to a date range you define, overriding the defaults for that window only. Create one profile per season you mapped, name each one by the season and its dates rather than by a code, and set them at the account, group or listing level depending on how much of your portfolio shares that season. A single property takes a listing-level profile, while a group of coastal listings that all peak in July takes one group-level profile applied once.
Set the minimum price rather than the base price in each profile. We recommend leaving base price alone unless something has genuinely changed about the property, because it feeds the algorithm's whole understanding of your listing, while the minimum price is the floor you want protected in that specific window. Here is a starting set to adapt to your own numbers:
| Season | Minimum price | Maximum price | Minimum stay |
|---|---|---|---|
| Peak | 20% to 30% above your annual minimum | Raised, so the algorithm has room to climb | 2 to 3 nights, to sell the gaps between longer stays |
| Shoulder | Your standard minimum | Standard | 2 to 3 nights |
| Low | 15% to 25% below standard | Standard | 5 to 7 nights, to chase extended bookings |
| Event | Well above peak for those dates only | Raised | Set to the length of the event, commonly 3 nights |
Use percentages rather than fixed amounts whenever a profile covers more than one listing. Listings inside a group usually carry different base, minimum and maximum prices, so a fixed figure that protects a four-bedroom house will overprice a studio in the same group. Percentage adjustments keep the relative gap between your listings intact however many properties the profile touches.
Attach the minimum stay rules to the same profiles instead of managing them separately, because dynamic minimum stays do as much seasonal work as price does. A longer minimum in a quiet February chases the kind of extended booking that fills a slow stretch in one reservation, and a shorter minimum in August lets you sell two-night gaps at the highest rates of the year.
For portfolios of more than about 20 listings, the bulk route is faster than clicking through each property:
Single dates that sit outside any season, such as one festival weekend or a known maintenance closure, belong in date-specific overrides instead of a profile. Overrides appear in black on the Review Prices calendar, so you can see at a glance which dates you have pinned by hand and which are still moving with the market. If you are setting all of this up for the first time, the first-time setup order is worth following before you add seasonal layers on top.
Pick one date each month and review the calendar on that date every month. The first working day of the month is a sensible choice, and the review takes about 30 minutes for a small portfolio. Open Review Prices, step through the next four months one at a time, and compare each month's current occupancy against where that month sat at the same point last year.
| What you see | What it means | What to change |
|---|---|---|
| Pacing more than 10 points behind last year | The floor is too high for current demand | Lower the minimum price in that profile, or shorten the minimum stay |
| Within 10 points of last year | Working as intended | Nothing |
| Above 85% occupied, more than 60 days out | Selling too cheaply, too early | Raise the minimum and maximum in that profile now |
| Your comp set is down by the same amount | A market shift, not a listing problem | Hold price and work on off-season demand instead |
Check the market alongside your own calendar every month, because an entire market softening is a different problem from a single listing underperforming. Your comp set in Market Dashboards shows whether the gap sits with you or with everyone, and demand trends tell you whether the shift is temporary or the start of a new pattern. Portfolio Analytics reporting is where the listing-level version of that comparison lives.
Twice a year, once after the peak ends and once before the next one begins, revisit the season dates themselves. Move the boundaries if your peak has been starting or ending a week or two off where you drew it, and split a season in two if one half consistently behaves differently from the other. Low-demand season strategy is worth revisiting at the same time, since the quiet months are where most of the year's avoidable empty nights sit, and a softer market is the point at which filling off-season nights matters more than holding a rate.
| Week | What to do | What you end up with |
|---|---|---|
| Week 1 | Pull 24 months of monthly occupancy and ADR for every listing and sort each month into peak, shoulder or low | Four to six seasons with start and end dates |
| Week 2 | Build a comp set of 10 to 20 comparable listings and check your season map against the market curve | A confirmed season map and a 12-month event list |
| Week 3 | Create one custom seasonal profile per season at the account, group or listing level, with minimum and maximum prices as percentages | Every season live in your settings |
| Week 4 | Add date-specific overrides for single events and blocked dates, and set a recurring reminder for the monthly review | A calendar with nothing left on default |
At the 30-day mark, compare occupancy and ADR for the next 90 days against the same forward window you recorded in week one. Peak months should show a higher ADR and low months should show more nights booked. If neither has moved, the likely cause is a minimum price set too close to your old flat rate, so widen the gap between your peak and low minimums and check again after another 30 days.
We calculate seasonality for your market automatically and apply it to every night in your calendar, then recalculate and sync your prices every 24 hours. On top of that:
The full setup walkthrough sits in our help centre under Seasonal Minimum, Base, and Max Price Settings.
Four to six seasons covers most markets, usually a peak, a shoulder on either side of it, a low season, and one or two short profiles for a holiday fortnight or an annual event. Going beyond about eight becomes difficult to review each month without losing track of which profile is doing what. Highly seasonal markets such as ski towns are the exception, where a dozen or more narrow profiles can be worth the extra admin.
We recommend leaving the base price alone and adjusting the minimum and maximum prices inside each seasonal profile instead. The base price feeds the algorithm's understanding of your listing as a whole, so moving it seasonally distorts the recommendations for every other month. Change it only when something structural has changed, such as a renovation, a new bedroom or a long-term drop in your listing's performance.
Prices are recalculated every 24 hours and pushed to your property management system every 24 hours, so a market change shows in your calendar the next day. The underlying market data refreshes on its own cycle, with existing Airbnb and Vrbo listings collected every two days and new listings every 15 days. Your seasonal profiles stay applied through all of it, so there is nothing to reapply as the dates approach.
Lower minimum prices help, and in most markets the minimum stay setting does more. Dropping to a two-night minimum in a quiet February captures short winter breaks that a five-night minimum turns away, while a longer minimum in the same month can suit markets with a genuine extended-stay audience such as snowbird destinations. Test one approach for a full month before switching to the other, because mid-month changes make the result impossible to read.
A seasonal profile applies rules across a date range and keeps the algorithm working inside the floor and ceiling you set, which suits anything from a fortnight to five months. A date-specific override pins a particular date or short run of dates to settings you choose and stops the algorithm adjusting them. Use profiles for seasons and overrides for single events, blocked dates and the handful of nights you want to control yourself.
Want to learn what PriceLabs can do for you? See for yourself with a free trial. Get started now!


