What seasonal pricing is actually for
Two different jobs, at opposite ends of the year.
In the peak, demand exceeds your fleet. You cannot serve everyone, so the question is which rentals you take. A higher rate does three useful things: it raises margin on the rentals you were going to get anyway, it slightly reduces demand to something you can physically handle, and it funds the capital purchase that will serve next season's peak.
In the trough, your fleet exceeds demand. The unit is already paid for and already insured; the marginal cost of renting it out for three days in January is close to the cost of cleaning it. A lower rate that produces one extra rental a week is strictly better than a proud rate that produces none.
Both are the same mechanism — moving price to meet capacity — which is why it is worth setting up once, properly, instead of improvising a discount every February.
Seasons are dates, not adjectives
The single most common implementation mistake is defining seasons as words. "Summer rate" invites the question of when summer starts, and the answer differs between you, your website and the member of staff on the counter.
Define each season as a from–to date range with a year, both ends inclusive, attached to a specific unit or unit class. That means:
- no ambiguity at the boundary,
- the schedule is auditable a year later when a customer disputes what they were charged,
- you can have as many periods as reality needs — a short Easter peak, a long summer, a bank-holiday weekend — rather than the two the word "season" implies.
And define them per unit, because different kit peaks in different months. A single fleet-wide calendar is nearly always wrong for half the fleet.
| Unit type | Typical peak | Typical trough |
|---|---|---|
| Tipping and bulk trailers | spring to early autumn | midwinter |
| Car transporters | steady, summer peak | midwinter |
| Campervans and motorhomes | school holidays and midsummer | late autumn to early spring |
| Boat trailers | late spring to early autumn | winter |
| Moving vans | month ends all year, summer peak | mid-month, winter |
| Garden and landscaping machines | spring and early summer | midwinter |
| Heating, drying and lighting kit | inverted — autumn and winter peak | high summer |
That last row is the one people forget. Not everything peaks in July, and an inverted-season unit is a genuinely useful thing to own precisely because it fills the trough of everything else.
How many seasons, and how far apart
Keep it to two or three rate levels. More than that and nobody — including you — can quote a price from memory.
| Level | When it applies | Typical position |
|---|---|---|
| Peak | the weeks you demonstrably turn work away | base rate plus 15–30 % |
| Base | the majority of the year | your standard published rate |
| Off-peak | the weeks the unit reliably sits idle | base rate minus 15–25 % |
Treat those percentages as a starting shape, not a recommendation — the right spread depends on how sharp your demand curve is, which you can read straight off your own utilisation figures. If you do not have them yet, Fleet Utilisation for Small Rental Businesses sets out how to calculate the numbers this decision needs.
One practical constraint: keep the peak uplift small enough that a customer who books in both seasons does not feel ambushed. A visible, moderate seasonal difference reads as normal commercial practice. A doubling reads as gouging, and gets written down in a review.
Billing across a season boundary
A rental that starts in the base season and ends in the peak has to be priced somehow. There are three approaches, and only one survives contact with customers.
| Approach | How it works | Verdict |
|---|---|---|
| Start date wins | whole rental at the rate of the first day | invites gaming — customers start a day early to dodge the peak |
| Highest rate wins | whole rental at the most expensive overlapping rate | simple but feels punitive, and is hard to justify line by line |
| Day by day | each day charged at the rate applying to that day | fair, explainable, and matches what the customer sees on the calendar |
Charge day by day. It is the only method you can explain on an invoice without an argument, and it removes the incentive to shift dates artificially. It also handles awkward cases automatically: a ten-day hire spanning the start of the peak is simply six days at one rate and four at another.
The interaction with length tapering matters too. Apply the seasonal rate first, then the length discount, and say so in your terms — otherwise a long peak booking can end up cheaper per day than a short base-season one, which is the opposite of what you intended.
The peak lever nobody minds: minimum length
Raising the headline rate is not the only way to manage a peak, and it is not always the best one. In the busiest weeks, the constraint is usually your handling capacity, not the price: three one-day hires consume three handovers and three returns for the same rented days as one three-day hire.
A peak-season minimum rental length — two days, or a three-day minimum over a holiday weekend — converts the same fleet into more revenue with less work, and customers accept it readily because it is a common practice in every rental sector they have used.
Sensible variants:
- Minimum length in the peak only, defined by the same date ranges as the rates.
- No same-day returns on the busiest weekends, so turnaround is not compressed.
- Reduced collection windows in the peak — fewer, longer slots rather than any time you like.
Whatever you pick, it should be visible when the customer books, not revealed at the counter. Staff should be able to override it for a good reason, and that override should leave a trace so you can see how often the rule is really being applied.
Publishing the change
Seasonal rates only work if they are boring and public. A short checklist:
1. Set next year's dates before this year's peak ends, while you can still remember which weeks were impossible.
2. Publish the calendar — the season dates and the rate for each, on the same page as the standard price list.
3. Quote the total, always. A customer should see the full price for their dates, not a day rate they have to multiply.
4. Freeze existing bookings. A confirmed booking keeps the price it was confirmed at, even if you later change the season definition. This is the single rule that prevents complaints.
5. Review once a year, with the utilisation figures open, not in response to one busy weekend.
Cancellation terms deserve the same treatment in the peak: a peak-season no-show costs far more than an off-season one, which is why many operators use a longer notice window in the busy weeks — see Cancellation and No-Show Policy for a Rental Business.
Common mistakes
- Seasons defined fleet-wide. Half the fleet gets the wrong calendar.
- Rates changed retroactively, catching already-confirmed bookings. Never worth the money.
- Discounts instead of off-peak rates. A discount is a favour you have to keep granting; an off-peak rate is a published price.
- Forgetting the deposit. Deposits generally track the value and risk of the unit, not the season, so keep them steady while rates move.
- No end date. A season with no end silently becomes the permanent rate. Always set both ends.
Where Flotello fits
In Flotello, each unit carries its own base price list plus seasonal periods defined as explicit from–to dates, and the price of a booking is calculated day by day — so a rental crossing a boundary is billed exactly, without anyone reaching for a calculator. Minimum-length rules can be set alongside the seasons and overridden by staff with a logged confirmation. You can set up your own season calendar during the seven-day trial.