Get started with PriceLabs now!
Want to learn what PriceLabs can do for you? See for yourself with a free trial. Get started now!
Almost every guide on this subject tells you dynamic pricing raises revenue and stops there. This one gives you the arithmetic instead, worked on a single property from the first section to the last.
That property is Cabin 4, a two-bedroom in Broken Bow, Oklahoma. Every number below belongs to it, so the figures reconcile with each other. Replace them with yours and the method still holds. If you are running rates across a book of owned properties rather than your own, the property management guide covers the commercial side of that.
Dynamic pricing for vacation rentals means setting a different nightly rate for each date based on live demand, rather than holding one rate for a season. Software reads booking pace, competitor availability, lead time, and local events, then recalculates every date on your calendar, usually once a day.
The comparison people reach for is a high season and low season rate. That comparison undersells the difference, because seasonal tiers change your price four times a year while demand changes daily.
| Static or seasonal pricing | Dynamic pricing | |
|---|---|---|
| What sets the price | A rate you chose in advance | An algorithm reading live market data |
| How often it changes | A few times a year | Daily, sometimes more |
| Responds to | The calendar | Booking pace, competitor availability, lead time, events, gap nights |
| Misses | Anything that was not predictable in January | Anything outside its data, including your own property's quirks |
| Effort after setup | None until the next season | About thirty minutes a week |
| Suits | One property in a stable market | Almost everything else |
Dynamic pricing sits inside the broader discipline covered in our revenue management guide, which deals with distribution, length of stay, and channel mix alongside rate.
Four families of input drive the number.
Reading the surrounding market well is a skill in itself, and our short-term rental analytics guide covers how to interpret occupancy and rate data before you act on it. To see that data for a specific market, PriceLabs Market Dashboards shows comp set occupancy and average daily rate by month.
Three numbers control everything the algorithm does. Most operators guess all three. Only one of them can be calculated exactly, and it is the one that protects you.
Your floor is the lowest rate at which the night still makes money. Below it, a booking costs you more than an empty night would. Here is Cabin 4, worked through.
Cabin 4 pays its cleaner $120 per turnover and spends $25 on consumables and linen per stay. Average length of stay is 2.5 nights.
($120 + $25) ÷ 2.5 nights = $58 per night
This is the step almost everyone skips. A cleaning fee is a per-stay cost, so dividing by your actual average stay length is the only way to compare it against a nightly rate.
| Monthly fixed cost | Monthly fixed cost Amount |
|---|---|
| Mortgage or rent | $1,400 |
| Utilities | $180 |
| Insurance | $95 |
| Software | $32 |
| Total | $1,707 |
At 60% occupancy, Cabin 4 sells about 18 nights a month.
$1,707 ÷ 18 nights = $95 per night
$58 + $95 = $153 per night of true cost.
Assume the channel you sell through keeps 3% of the booking. Dividing rather than multiplying is what makes the fee come out correctly:
$153 ÷ 0.97 = $158
Then add the minimum margin you are willing to accept, here 15%:
$158 × 1.15 = $181
Cabin 4's floor is $181. Any night sold below that loses money, however good the occupancy looks.
Two things follow from having a real number. The algorithm can be aggressive without being dangerous, because it has a hard boundary underneath it. And a floor also filters your guest mix, since the guests hunting the cheapest listing in a market are reliably the ones who generate the most damage and the worst reviews. The floor protects margin and guest quality at the same time.
Recalculate it whenever your cleaning rate or your average stay length moves. Both move more often than people expect.
Your base price is the rate for an ordinary night with nothing special happening, and it anchors every adjustment the algorithm makes. Our guide to setting a base price covers the methods in detail. Cabin 4 runs a base of $214.
Your ceiling exists to stop a data error selling a holiday weekend at an absurd number, in either direction. Set it high enough that it almost never binds. A ceiling that triggers every month is set too low and is quietly capping your best dates.
Five levers, in rough order of how much they change annual revenue for a property like Cabin 4.
If you want the wider framing around these levers, our Airbnb pricing strategy guide sets them in sequence.
A listing with no reviews is not competing on the same terms as one with eighty, and pricing it as though it were is the most common mistake new operators make.
Search ranking on every major channel leans on booking velocity and review count. A new listing has neither, so it has to buy them. Experienced operators open below their comp set, often around 10% to 15% under, hold that until roughly the first ten reviews land, then step the rate up toward the comp set over the following weeks.
Two cautions. The discount runs against your comp set, never below your floor, because a loss-making booking with a five-star review is still a loss-making booking. And the ramp needs a date in your calendar, since the failure mode is not the discount itself but forgetting to end it. Cabin 4 opened at $185, near its floor of $181, and reached its $214 base after fourteen reviews.
If you are earlier than this and still setting the listing up, our guide on becoming an Airbnb host covers the steps before pricing becomes the problem.
RevPAR tells you revenue per available night. It does not tell you what reached your bank account, and the difference is larger than most operators think.
| Line | Calculation | Amount |
|---|---|---|
| Nights sold 18 at $214 $3,852 | 18 at $214 | $3,852 |
| Channel fee −$116 | 3% of $3,852 | −$116 |
| Consumables | 7 stays at $25 | −$175 |
| Net revenue | $3,561 | |
| RevPAR | $3,852 ÷ 30 | $128.40 |
| Net RevPAN | $3,561 ÷ 30 | $118.70 |
The gap is $9.70 per available night. Across a year on one cabin that is roughly $3,500, and across a portfolio it is the difference between a good year and an average one. Two properties can post identical RevPAR and hand you materially different amounts of money, depending on channel mix and stay length.
Track both. RevPAR tells you whether your pricing is working; net RevPAN tells you whether your business is. The metrics worth tracking covers the full set, and our guide to calculating rental income carries the same logic through to annual net.
Dynamic pricing is not unattended pricing. A pricing tool running on settings nobody has revisited since January is a static strategy wearing a different label.
Once a week, in this order:
Anything beyond this is usually fiddling. Guidance on where the useful settings live is in customizing your pricing rules, and the wider question of which tasks to automate is covered in our vacation rental automation guide.
Want the tool rather than the theory? If you already know how you want to price and just want it running daily, go to PriceLabs Dynamic Pricing and start there. The rest of this page is about the decisions around it.
Every vendor in this category writes as though the answer is always yes. It is not, and knowing the exceptions makes the rest of your pricing better.
If there are six short-term rentals in your town, there is no meaningful comp set. The algorithm is reading noise. Price from your own booking history instead and use the software mainly for gap nights.
No listing data and no market data together leave the algorithm with nothing. Price manually for the first few months.
Corporate lets, insurance placements, and long stays booked at agreed rates do not respond to nightly demand. Exclude those dates rather than letting the algorithm price around them.
Where regulation limits you to a fixed number of nights a year, the goal changes from filling the calendar to maximizing the rate on the nights you are allowed to sell. Dynamic pricing still helps, though the settings are close to the opposite of the usual ones.
No pricing algorithm fixes bad photography, a weak title, or a 4.2 review average. If your conversion is poor at every price point, the problem is the listing, and our listing optimization guide is the right page for it.
This one is worth arithmetic. Cabin 4 at its $214 base, with a 15% weekly discount, a 20% last-minute discount, and a 10% channel promotion all applying to the same booking:
$214 × 0.85 = $181.90 $181.90 × 0.80 = $145.52 $145.52 × 0.90 = $131
Against a floor of $181, that booking loses $50 a night. Discounts multiply, they do not add, and most operators set them in different screens on different days without ever seeing them combine. Audit every active discount together, in one sitting, at least twice a year.
Covered above. A guessed floor is the difference between aggressive pricing and unprofitable pricing, and you cannot tell which one you have until you calculate it.
If your cleaner can handle four turnovers on a Sunday and your pricing generates seven, you have sold nights you cannot service. Pricing and operations are one system.
A full calendar at the wrong rate is the easiest failure to mistake for success. Revenue per available night is the number that matters.
See the weekly review above.
Both adjust rates automatically, though they are not equivalent. Smart Pricing moves your rate inside a minimum and maximum you set, using Airbnb's own demand signals. It works on Airbnb only, so rates do not reach Vrbo or your direct site, and it does not act on newly announced local events. Its behavior depends almost entirely on the minimum you give it.
Divide your per-stay costs by your average length of stay, add your monthly fixed costs divided by the nights you expect to sell, divide that total by one minus your channel fee, then add your minimum margin. The worked example above takes a two-bedroom cabin through every step.
It costs you some, which is the point. The question is whether the rate increase earns more than the lost nights cost. On high-demand dates it usually does, because the guests who drop out at a higher rate are replaced by guests who were always willing to pay it.
Repeat guests at a single property sometimes do. Most guests book one stay in a market and never see your pricing pattern, so the risk is smaller than it feels. Where it matters, tier your discounts so the deepest ones apply only inside seven days.
Daily is standard, and more often on dates inside a fortnight. Manual weekly updates were reasonable a decade ago and now leave money on dates that moved on a Tuesday.
The arithmetic works the same at one property as at fifty, though the time saved is smaller. Below roughly three properties you can plausibly review calendars yourself. Above that you are approximating, and the approximation costs more than the software. Comparing pricing tools covers what to look for.
Partly. It handles seasonality and gap nights from day one, though it cannot price your specific property well until it has booking history. Run it with a floor you have calculated and a base set below your comp set, then raise the base as reviews arrive.
Want to learn what PriceLabs can do for you? See for yourself with a free trial. Get started now!


