TL;DR →
- Our popular Historical Weightsetting is now "Historical Protections", and we've added two big upgrades.
- New Protection Type:You can now protect future nights with your prior data serving as either a"Weight"or a"Floor".
- New Protection Source:You have a new option for our data source -Posted price (with booking fallback)- that leverages last year's posted price when one exists, while automatically leveraging booked prices when no posted prices exist.
- Mix and match: 2 protection types × 3 protection sourcesgives you precise control over how future nights are protected.
- Everything is opt-in. Nothing changes until you choose it.
🛡️ New: Two Protection Types — Weight or Floor
Historical Protections now let you decide
how
your prior data protects your future nights:- Weight:As a weight, your historical data caninfluence future price recommendations.
- Floor:As a floor, your historical dataestablishes as price floor.
Let's explore these two options more deeply.
Weights
Weight increases your recommended price by a percentage of the difference between your current recommendation and historical price.
Example: If your current recommendation is $600 and your historical price is $1,000, the difference is $400.
- 0% Weight: No adjustment → $600
- 50% Weight: Add $200 (50% of the difference) → $800
- 100% Weight: Add $400 (the full difference) → $1,000
Note:
Weight only increases prices. When set to 100%, if your current recommendation is already higher than your historical price, no adjustment is made. If set above 100%, your recommendation won't fall below that percentage of your historical price. For example, at 150%, a $1,000 historical price would imply a future price of $1,500 or more.Floors
Floor establishes a minimum recommended price based on a percentage of your historical price.
Example:
If your historical price is $1,000 and you set a 50% Floor, future recommendations won't fall below $500. A recommendation of $400 would increase to $500, while a recommendation of $600 would remain unchanged. - 0% Floor: No floor.
- 50% Floor: Floor set at 50% of last year's price.
- 100% Floor: Floor at 100% of last year's price.
Note:
If you have set a minimum price is higher than your floor, the higher minimum price will determine the final price.You can choose your type under
Protection Type
in Settings → Historical Protections
.🚩 Resolving a Miscommunication
In what has been one of our most interesting product learnings to date, it came to our attention in Q3 that we were not consistently communicating how Historical Anchoring (now, Historical Protections) worked.
In short, this setting has always been a "weight", meaning it could pull prices up.
However, we learned that certain clients had been taught this setting as a "floor", meaning they thought this setting created a price floor. (It did not)
As we explored the best way to solve this miscommunication with a number of customers, you all taught us that BOTH of these options were valuable, which is why we are now making both options available.
Thank you for the guidance and insights!
🎯 New: Protection Source — Posted Price (with Booking Fallback)
Additinonally, you now have access to
three options
for the Historical Protections Source
:- Booked price(default): the final booked nightly rate for the comparable stay date.
- Posted price: the last price Wheelhouse posted for that stay date before it was booked. Promo codes, wholesale net rates, and other discounts applied after the price left Wheelhouse don't affect it.
- Posted price (with booking fallback)(new): uses the posted price when one exists, and the booked price when it doesn't.
Booked price was our initial setting value.
Earlier this year, we introduced "posted price" as a second protection source. This option become the popular choice for teams whose booked rates are distorted by promos, commissions, or contracted rates.
However, "posted price" had one major limitation - properly handling new listings.
For example, Wheelhouse never posted a price for a date, there was nothing to protect that night with.
This happens most often when:
- A listing joined Wheelhouse recently, so earlier stay dates pre-date its posted-price history.
- A reservation was imported into Wheelhouse, rather than booked while the listing was on Wheelhouse dynamic pricing.
In both cases there's a real booked rate, but no posted rate, because Wheelhouse wasn't setting the price at the time.
Hence, why we have introduced your 3rd option - "posted price w/ booking fallback".
How Posted Price (with Booking Fallback) Works:
- If a posted price existsforlast year's stay date, Wheelhouse uses it.
- If no posted price exists, Wheelhouse uses thebooked price for that identical stay date.
Most of a listing's calendar stays protected by posted prices, and a handful of gap dates fall back to booked price automatically.
🗓️ Let's See This in Action:
You onboarded a listing to Wheelhouse in early 2026 and imported its existing reservations. New Year's Eve 2026 was booked at $650 before the listing came onto Wheelhouse pricing.
To protect New Year's Eve 2027, your Historical Protection is a weight set to 80%, and the current recommendation is
$420
.- Posted price:No posted price exists for NYE 2026, so the date isn't protected. Your recommendation stays at$420.
- Posted price (with booking fallback):No posted price exists, so Wheelhouse uses the $650 booked price. With an 80% weight, your recommendation moves up to$604.
For every other date on that listing's calendar where a posted price exists, posted price remains the foundation.
🧮 What Doesn't Change
These updates change
which type
of protection is applied and which source
it references. They don't change how the comparable date is chosen:- Day-of-week alignment works the same way.
- Your 18-month pricing horizon works the same way.
- The existing lookback still applies. For stay dates 12+ months out, if the comparable date one year back has no price, Wheelhouse can look back up to two years.
- If no posted or booked price exists for that date, nothing is protected, just as today.
🔍 See Exactly What's Driving Each Date
With more options comes more need to see what's happening. Before you switch, you can:
- Preview the series:On the Historical Protections settings page, preview the Posted price (with booking fallback) series alongside Posted price and Booked price to see how your recommendations change before you commit.
- Check any stay date:See whether a given date is protected by itspostedprice or hasfallen back to booked price.
👥 Built for Portfolios
Posted price (with booking fallback) works with the portfolio tools you already use:
- Bulk copy:Apply it across many listings at once from Portfolio Settings.
- Grouped Settings:Listings on Posted price (with booking fallback) group separately from listings on Booked price or Posted price, so you can see which listings use which source at a glance.
- Changelog:Every Protection Source change is logged with the timestamp, the user, and the old → new value.
🚀 How to Get Started
- Go to Settings → Historical Protections.
- Choose your Protection Type:WeightorFloor.
- Choose your Protection Source:Booked price,Posted price, orPosted price (with booking fallback).
- Preview the series, then save.
Already on Posted price? Nothing changes unless you choose the new option.
🥳
Pro Tip:
Use Grouped Settings to find every listing currently on Posted price, then preview the fallback series on a few with imported or older reservation history. Those are the listings most likely to have gap dates that will start being protected.🤓 Learn More