The pricing mistakes that cost the average operator $8k a year.

Where the money goes

Most operators don't lose money on the booking they argued about. They lose it on the 340 nights they never thought about.

Take one property at a $180 average nightly rate. Here's where a typical year leaks.

Mistake 1 — The flat rate all year

You set $180 in March and it's still $180 in December. Peak weekends carry the same price as a wet Tuesday in the off-season.

The cost cuts both ways. You leave $40–60 a night on the table across 25 or so high-demand nights you could have charged more for. And you sit empty on shoulder nights you'd have filled at $130. Call it $2,000 a year on one property, and that's conservative.

Mistake 2 — Pricing on a calendar, not on demand

A school holiday isn't the same week every year. A conference moves cities. A long weekend three towns over fills your area whether or not it's on your radar.

Operators who price off last year's spreadsheet miss the events that actually move demand. Miss four demand spikes a year — three extra bookable nights each, at $70 above your flat rate — and that's another $840 gone, plus the nights you priced high into a week when nothing was happening and stayed empty.

Mistake 3 — The orphan-night discount that never fires

You have a Thursday open between two bookings. Nobody wants a one-night gap at full price, so it goes empty — over and over.

A standing rule that drops orphan nights 15–20% turns dead inventory into bookings. Even a dozen recovered gap nights a year at $150 is $1,800 you were throwing out with the bins.

Mistake 4 — Never moving the minimum

A two-night minimum in low season protects you from nobody. It just blocks the solo traveller who'd have taken Tuesday-to-Wednesday.

Loosen minimums when demand is soft, tighten them when you can fill the whole week anyway. Operators who never touch their minimums lose roughly $3,000 a year on a single property in refused short stays and badly shaped weeks.

Add it up: about $7,600 to $8,000 a year. On one property. Run three and you're not arguing about a tool subscription anymore — you're funding it many times over with nights you already own.

The fix isn't "check prices more often"

Nobody scales by re-pricing 365 nights by hand. The operators who get this right set the rules once — how much weekends move, how aggressively to discount orphan nights, where minimums flex — and let a pricing engine apply them every day across every property.

That's why dynamic pricing in Symplehost runs on PriceLabs natively: a serious engine, your rules, no second tool and no second bill. But the engine isn't the lesson here. The lesson is that the expensive mistake is treating price as a setting instead of a system.