Changelog
Follow up on the latest improvements and updates.
RSS

TL;DR →
- Wheelhouse has a new RM API, and IntelliHostis among the first partners to build directly on top of these.
- Every morning it reviews your entire portfolio against that traffic, flags underpriced dates, andpushes approved rate changesstraight into Wheelhouse — one tap in Slack
- It also runs automated AI listing optimizationand gives you total portfolio performance in a single view
- No logging in, no copy-paste, no manual re-entry: thefull pricing loop, closed automatically
- Active IntelliHost users see an average 21% revenue increase with roughly 10 minutes of hands-on work per week
- This is the first of a new class of Wheelhouse integrations— tools built directly to our API that extend what Wheelhouse can do inside your workflow
🔌 A New Class of Wheelhouse Partner
Until now, Wheelhouse integrations have meant connecting your PMS or OTA so your prices flow downstream.
This is something different.
IntelliHost is the first partner to build directly on the Wheelhouse API — meaning it can read from and write to your Wheelhouse account programmatically, as part of a fully automated workflow. IntelliHost doesn't just connect to Wheelhouse; it acts on Wheelhouse, on your behalf, based on rules you define.
For property managers running 20 to 200+ units, that's a meaningful distinction. Your pricing strategy is only as good as your ability to execute it consistently — and execution at scale, done manually, is where revenue leaks.
🔍 What IntelliHost Does
IntelliHost is a performance intelligence platform for professional short-term rental operators. What makes it different: it brings in your real OTA click traffic from Airbnb and Vrbo — the impressions, clicks, and conversions your listings are actually getting — and runs your pricing, your listing optimization, and your portfolio reporting off of that signal.
That traffic data drives three things:
Traffic-based pricing. Every morning, IntelliHost reviews your whole portfolio and finds dates where your pricing is leaving money on the table — based on how much real click demand each date is pulling. When it finds one worth acting on, it pings you in Slack. You tap approve, and the updated rate is pushed directly into Wheelhouse. That’s it.
Automated AI listing optimization. IntelliHost diagnoses where each listing is underperforming — title, photos, amenities, conversion — ranks the fixes by revenue impact in dollars, and rewrites what’s holding the listing back. Visibility isn’t the goal; turning impressions into clicks and clicks into bookings is.
Total portfolio performance. One dashboard shows the health of every property, which listings have the most upside, and what to fix first — instead of a half-day spent compiling spreadsheets.
What IntelliHost handles automatically:
- Portfolio-wide pricing reviews (daily), driven by live OTA click data
- Underpriced date detection using your property’s real Airbnb and Vrbo traffic
- AI listing optimization, ranked by dollar impact
- Portfolio-level performance tracking and automated owner reports
- Slack-based approval workflow
- Rate push directly to Wheelhouse via API
🪄 What This Unlocks Together
Wheelhouse handles the intelligence layer: building a dynamic pricing strategy calibrated to your market, your comp set, and your listing's demand curve.
IntelliHost handles the execution layer: monitoring that strategy every day against your real OTA traffic, catching the gaps, and acting on approvals without requiring you to log in.
Together, the loop is closed. You set your strategy in Wheelhouse. IntelliHost watches for drift. You approve in Slack. Wheelhouse updates.
No logging in. No copy-paste. No manual re-entry.
For a portfolio of 50 properties, that's the difference between a pricing strategy you review when you have time and one that runs continuously — on your terms, with your approval at every step.
📈 The Results
Active IntelliHost users see an average 21% revenue increase — achieved with roughly 10 minutes of hands-on work per week.
That figure comes from IntelliHost's live customer base and reflects the compounding impact of daily portfolio reviews that most managers simply can't do manually at scale.
🚀 How to Get Started
If you're already a Wheelhouse customer, connecting IntelliHost takes just a few minutes.
- Visit intellihost.co and book a demo
- Connect your Wheelhouse account via the IntelliHost integration flow
- IntelliHost begins monitoring your portfolio the next morning
🥳 Pro Tip! IntelliHost's daily monitoring works best when your Wheelhouse Min and Max prices are set — it uses those guardrails when evaluating which underpriced dates are worth flagging. If your floors and ceilings are out of date, now's a good time to review them in your portfolio settings.
Learn More
- 📽️ Watch: How to connect IntelliHost to Wheelhouse → https://youtu.be/MGW8m7dmkbI
- 📽️ Watch: IntelliHost + Wheelhouse demo → https://www.youtube.com/watch?v=lS3C8rNRG2k
Let's Build!
IntelliHost is the first in a new class of Wheelhouse API partners. If you've built a tool on top of our API and want to be featured, reach out to hello@usewheelhouse.com

- You now have two options as the anchor sourcefor Historical Anchoring.
- Leverage your final booked price(today's default) or thelast Wheelhouse-posted price at the time of booking.
- This new option (last posted price) ensure promo codes, wholesale net rates, and group discounts don't quietly become next year's floor.
- Historical Anchoring now protects your entire 18-month pricing horizon, anchoring off the most recent comparable booking — even if that booking is still in the future.
- Nothing changes today: every account defaults to Booked price, exactly like current behavior. You'll simply see the new option waiting for you.
- Portfolio Settings now support bulk copyand smartergroupingfor Historical Anchoring, so managing this setting across large portfolios is easier.
🗝️
New Unlock: Anchor Source
Historical Anchoring has always protected your floors by looking at what actually booked last year.
That's great — until a promo code or channel-specific discount leads to a booking, and that discounted rate quietly becomes your floor for the same date next year.
Now you can choose what Historical Anchoring anchors to:
- Booked price (default)– the final booked nightly rate we ingest for that stay date. This is current behavior, and it's what your account stays on unless you change it.
- Wheelhouse suggested price at time of booking– the last Wheelhouse-recommended nightly rate for that stay date, as of the booking timestamp, so external discounts and commissions don't factor in.
Imagine a last-minute traveler booked your July 4th weekend at a steep discount, due to PMS or channel specific discounts.
Under Booked price anchoring, that discounted rate could drag down your floor for July 4th next year.
Switch to Wheelhouse's Posted Price, and your floor instead reflects what your engine actually recommended before that discount was applied.
Activating this is a quick switch, that you can setup in your
Settings → Historical Anchoring
, under Source
.
🚩
Two Flags!
There are two (2) important callouts for this setting.
First
, as you know, we only post prices for connected listings.Therefore, if a booking occurred before you connected to Wheelhouse, we won't know the "final posted price" for your bookings. (We can see the booking amount, but can't infer potential discounts from your final price)
This drawback means this new data source is
most
useful/valuable for listings that have been on Wheelhouse for 1+ years.Second
, historically we have stored the final posted price for an unbooked night for 7 months. Starting now, we will store this price posting data for 12+ months, but it will take 5 months for us to accumulate 12 months of historic prices for each stay date.
Therefore, for the next few months, you will want to leverage other protections to ensure we protect your nights as intended.
🗓️
Protecting Your Full 18-Month Horizon
Good news!
Historical Anchoring now protects every date across your
entire 18-month pricing horizon
— using the most recent same-day booking as an anchor, even if that booking is still in the future, relative to today.For example:
- October 30, 2026 booked at $1,000/night (still upcoming as of July 2026)
- When pricing October 30, 2027, we will anchor off the October 2026 booking.
- However, if October 30th, 2026 had no booking, our system would fall back to 2025 to look for a booking anchor.
And, for stay dates
12+ months out
, if no comparable booking exists one year back, Wheelhouse extends the lookback up to two years to find an anchor.🧮
Full Transparency, Built In
Every time your account's Anchor source setting changes, Wheelhouse logs it — timestamp, user, and the old and new values — so you and your team always have a clear record of what changed and when.
🧩
Built for Portfolios
Managing Historical Anchoring across a large portfolio just got easier:
- Bulk copyyour Anchor source setting across listings from Portfolio Settings.
- Smarter grouping— listings on Booked price and listings on Wheelhouse suggested price now group separately in Portfolio > Grouped Settings, so you can see and manage them at a glance.

🚀
Getting Started
Nothing changes for you today — every account, new or existing, defaults to
Booked price
, exactly like current behavior.To try the new option:
- Go to Settings → Historical Anchoring
- Under Source, selectHistorical posted price

TL;DR →
- You can now kick off a listing syncdirectly through the API
- You can now create and edit Segmentsvia the API
- You can now view and manage Teamsvia the API
- You can now fetch Base Price historythrough the API
- You can now fetch Calendar Day history— observed status and posted prices
- We also completed a big documentation cleanup, fixing mismatches between the docs and the actual implementation
🧮
Base Price History
If you're building pricing logic on top of the Wheelhouse RM API, you now have a direct line into how Base Price recommendations have moved over time.
The new endpoint returns a historical log of Base Price settings and recommendations for any listing — so you can track how pricing has evolved, audit changes, or feed historical context into your own tooling without reconstructing it from scratch.
🗓️
Calendar Day History
Similarly, you can now pull a day-by-day history of calendar state for any listing — including observed status and posted prices.
This means you can now see, for any date, what price was actually posted and what the observed booking state looked like — a foundational building block if you're building reporting, auditing, or anomaly-detection tools on top of your portfolio's pricing history.
🔄
Kick Off a Listing Sync
Previously, triggering a fresh price sync for a listing meant waiting on our internal cadence. Now, you can kick off a sync job directly through the API.
This is especially useful if you're building automation that needs pricing to reflect the very latest settings immediately — no more waiting on the next scheduled sync.
🧩
Create and Edit Segments
Segments — your saved, dynamic portfolio filters — are now fully manageable via the API.
You can create new Segments and edit existing ones programmatically, which means any tooling you're building to manage large or complex portfolios can now define and adjust Segment logic without a manual trip into the Wheelhouse UI.
👥
View and Manage Teams
Teams can now be viewed and managed directly through the API as well. If you're building integrations or internal tools that need to reflect your organization's team structure — who's on which team, and how teams map to portfolios — you can now do that programmatically instead of keeping a manual mirror of it.
📚
Documentation Cleanup
Separately from new endpoints, we did a significant pass across the RM API docs to fix mismatches between what the docs described and what the implementation actually does.
If you've hit friction in the past where the docs didn't quite match real behavior, this should meaningfully clean that up.
🥳
Pro Tip!
Base Price History and Calendar Day History pair well together — combine them to reconstruct a full pricing-and-outcome timeline for any listing, rather than pulling each in isolation.🚀
Ready for the Hackathon!
All five of these endpoints are live now — which means they're fair game for anything you build during our API Hackathon (July 21–24). Whether you're reconstructing pricing history, automating syncs, or building portfolio tooling around Segments and Teams, this week's additions give you more surface area to work with.

TL;DR →
- AI assistants (Claude, Cursor, VS Code, and more) can now connect directly to your Wheelhouse account via MCP
- 58 tools expose 1:1 parity with the Wheelhouse UI — if you can do it in the product, you can now do it in a prompt
- With our APIs & MCP, you can move your workflows from clicks to commands, in an afternoon
- And, getting your MCP setup takes 2 mins (📽️ Video proof)
🔌 What the Wheelhouse MCP Does
The Wheelhouse MCP (Model Context Protocol) server connects AI coding assistants and chat clients —
Claude, Cursor, VS Code, and others
— directly to your Wheelhouse account.Once connected, those tools get access to 58 endpoints built on our RM APIs, which offer full 1:1 parity with the Wheelhouse UI. Every portfolio view, every pricing setting, every reservation and comp — accessible via natural language or code.
Your team doesn't need to learn a new interface. They just describe what they want to do.

🧮 What You Can Build
The range here is wide. A few examples of what this unlocks:
- "Pull my pacing vs my neighborhood comps, and prepare an email to send to owners where their minimum prices are impacting bookings."
- "Analyze my seasons and flag any listings where my Base Price is below the neighborhood median for peak weeks."
- "Pull my last 90 days of reservations and show me which listings are underperforming on ADR vs. comp set."
These aren't hypotheticals — these are the kinds of prompts your team can run today, in an afternoon, after a straightforward setup.
🗝️ Built on the RM APIs
The MCP is built on Wheelhouse's new Revenue Management APIs, which were designed from the ground up with external access in mind.
That 1:1 parity matters: you're not working with a simplified read-only layer. You have access to the same data and levers your team uses inside the Wheelhouse UI — pricing preferences, min/max rules, reservations, comp data, custom rates, and more.
🚀 Getting Started
To connect an AI assistant to your Wheelhouse account:
- Go to your account and navigate to Connections → API Key
- Enable MCP Access
- Follow the setup instructions for your client — we have step-by-step guides for Claude, Cursor, VS Code, and any other client
📽️ Watch a demo: https://www.loom.com/share/07d239b07b2a4cf18b67e95c0d02311e

Local Events Are Back on Your Calendar
TL;DR →
- Local events — conferences, holidays, and high-demand dates in your market— are now visible directly on your Individual Listing calendars
- Wheelhouse built a custom AI to detect and surface the eventsthat matter most for your pricing
- Toggle market events on or off via the Displaybutton on your calendar
- Combine with your own Events & Seasonsconfiguration for a complete picture of every demand driver on your calendar
---
🗓️ What's New: Market Events on Your Calendar
Local events are back — and meaningfully improved.
You can now see market events directly on your Individual Listing calendar: conferences, holidays, festivals, and other high-demand dates in your area, all surfaced automatically.
To turn them on, head to your calendar and click the
Display
button in the top right. From there, toggle on Market Events
, and you'll start seeing relevant local demand drivers appear on your calendar.
---
🤖 Powered by a Custom Wheelhouse AI
Wheelhouse built its own AI to detect and curate the events that are actually relevant to your market.
The goal: surface the most important things to get right, pricing-wise — not just a firehose of noise.
We're continuing to refine this, and we'd love your feedback. If you're seeing events that don't seem relevant, or missing ones you'd expect, let us know.
---
🗝️
Show next to your own Events & Seasons Settings
Here's where it gets interesting.
In addition to Market Events, you can also toggle on
Events & Seasons
from the same Display menu. This layer shows the events and seasons you've
created in your settings — the ones you've already built minimum stay policies, minimum price rules, and other configurations around.Seeing both layers at once gives you a powerful side-by-side view:
- What Wheelhouse's AI is detecting in your market
- What you've already built a strategy around in your own configuration
This combination makes it much easier to validate your existing events setup, catch any gaps, and quickly identify demand dates that deserve attention but haven't been configured yet.
---
Watch a demo

Are your listings pacing ahead or lagging behind your local market? Answering this question just got a lot faster and more precise.
We’ve rolled out
Neighborhood Occupancy Views
& Filters
across Wheelhouse to give you a multi-angle read on your locale's performance.Here where you can see it:
- In-Context Views 📈:See your neighborhood occupancy data charted directly alongside your pricing and booking trends.
- Smart Portfolio Filtering ⚡:Filter and sort your listings by how they stack up against the neighborhood (e.g., sort by % Diff to instantly surface listings underperforming their market).
- Custom Segments 🛠️:Use these new metrics to build powerful, automated Segments and Views tailored to your operational strategy.
Quick Tutorial:

TL;DR →
- Wheelhouse users now get 20% off BNBCalc + a 7-day free trial (code: WHEELHOUSE20)
- -> link here
- BNBCalc Marketsis a live map of 10M+ Airbnb and Vrbo listings, with gross yield and revenue data on every property.
- Research any market's occupancy, ADR, top amenities, and real comp sets — before you buy or expand.
- See the most profitable markets, by state or nationwide.
- It's the research layer that plugs in before Wheelhouse: find and validate the market, then price it confidently.
🗺️ What Is BNBCalc: Markets?
BNBCalc Markets is a live, searchable map of 10M+ active Airbnb and Vrbo listings. Every listing shows its gross yield and revenue — not estimates, real data — so you can pressure-test any market before committing to it.
When you're evaluating a new property or market, Markets gives you:
- Occupancy and ADR benchmarks for any geography
- Amenity impact data — which features (pools, hot tubs, pet-friendly, etc.) actually move the needle on earnings in that market
- Comp sets built from real listings, not synthetic averages — so you can see exactly what you'd be competing against
📐 How It Fits Your Workflow
If you're already using Wheelhouse to optimize pricing on your current portfolio, Markets answers the question that comes before that: should I add this property or expand into this market at all?
A realistic scenario: you're evaluating a 3BR cabin in a new mountain market. Before you run any numbers in Wheelhouse, you open Markets, find the market, filter for comparable listings, and see the actual revenue distribution — not a headline average. You spot that 2BR properties dominate and 3BRs underperform the market average. Now you're negotiating with real data, or moving on to a better opportunity.
That's the research foundation. Once you have it, you bring the property into Wheelhouse and price it from day one with confidence.
🎁 Discounted for Wheelhouse Users
As a Wheelhouse user, you get:
- 20% off BNBCalc with code WHEELHOUSE20
- 7-day free trial to explore Markets before committing
👉 Start your free trial → link

TL;DR →
- You can now bulk-adjust check-in/check-out rules for an entire month in one click — no more day-by-day editing
- Customize check-in/check-out availability by day of week and update your full configuration in seconds
- A UI update makes it easy to see your current check-in/check-out rules for any day
- Seasons and events now support time-based check-in/check-out rules — finally, full alignment between your seasonal strategy and your gate rules
- Time-based Event & Season rules are already available via the API
- 📽️ Demo Here
-
🗓️ Quick Adjustment: Update 1-100+ nights at Once
Check-in/check-out configuration just got a lot faster to manage.
You can now make bulk adjustments to your check-in/check-out rules across any date range, right from your calendar.
This is a significant time-saver for anyone managing seasonal transitions or rolling out rule changes across a large date range.
📅 Customize by Day of Week
To expand on this capability, you can set check-in/check-out availability by
specific day of the week.
- Want guests to be able to check in or out on any day? Easy — select all days and save.
- Want to restrict to weekends only? Same workflow.

Updated UI: Show on Calendar
You can now see your Check-In/Check-Out rules on your calendar views.
Simply open your "display" setup, and toggle on check-in/check-out.

🗝️ Time-Based Check-In/Check-Out for Seasons & Events
This is the most significant of the three updates.
You've long been able to configure check-in/check-out rules at the season level.
But until now, there was no way to set
time-based
rules within a season — your seasonal gate rules and your time-based rules lived in separate worlds.For example, open up more nights for check-in as a stay date approaches for your Summer high season.
This unlocks a much more precise strategy:
- Set permissive gate rules close-in to maximize late bookings
- Tighten check-in/check-out to preferred days in your far-future seasons
🔗
Everything's Available via API
These updates — date-specific overrides, day-of-week customization, and time-based seasonal check-in/check-out — are supported in the Wheelhouse API. If you're managing configurations programmatically, these settings are accessible the same way you'd expect.
🥳
Pro Tip!
Pair your new time-based seasonal check-in/check-out rules with your minimum stay rules in Events & Seasons Config.---
📽️ Watch a demo

TL;DR →
- 13 new and updated metricsare now available across Wheelhouse — as portfolio columns, filters, chart overlays, in reports, and via the API.
- 6 new Neighborhood Occupancymetrics let you benchmark each listing against its local market, with adjusted, % diff, and ratio views.
- Blocked & available revenuenow give more insights into potential actions you can take to drive revenue.
- Two new RevPARvariants account for fees and bookable nights — for apples-to-apples performance comparisons.
- Leverage metrics to create new Segments, Views or Reports.
-
🏘️ Neighborhood Occupancy: Six Ways to See How You Stack Up
This is the biggest new metric cluster in this release. Six new metrics let you measure how your listing's occupancy compares to the surrounding neighborhood — across a range of views depending on how you want to look at it.
Occupancy (Neighborhood)
— the percentage of booked nights in your listing's neighborhood within your selected time frame. Your baseline market occupancy number.Occupancy (Neighborhood Adjusted)
— same as above, but the denominator uses bookable nights only (blocked nights excluded). A cleaner benchmark when you want to strip holds out of both sides of the comparison.Two
Neighborhood Diff
metrics show the gap between your listing and the neighborhood in percentage points:- Occupancy (Neighborhood % Diff)** — your listing's occupancy minus the neighborhood's
- Occupancy (Neighborhood Adjusted % Diff)** — same comparison, using adjusted occupancy on both sides
Two
Neighborhood Ratio
metrics express the same comparison as a multiplier:- Occupancy (Neighborhood Ratio)** — your occupancy divided by neighborhood occupancy
- Occupancy (Neighborhood Adjusted Ratio)** — your adjusted occupancy divided by neighborhood adjusted occupancy
Together, these give you a fast, multi-angle read on whether your listings are outpacing, matching, or lagging the local market — and by how much.
🥳 Pro Tip! Add Occupancy (Neighborhood % Diff) as a column on your portfolio page and sort by it. Any listing running significantly below the neighborhood is a candidate for a pricing or availability review.
-
💰 Revenue & Potential Revenue: A Number for Every Context
Revenue is the metric you use constantly — for performance reviews, owner reporting, accounting, and market benchmarking. The problem is that "revenue" means different things depending on what question you're asking. We've expanded the revenue metric family so you always know exactly what's included.
- Revenue (+ Fees)— the sum of rent + fees for all booked nights. This is the updated name (and updated calculation) for what was previously "Total Revenue." It's the right number for most day-to-day performance tracking: the all-in rate guests are paying, minus taxes.
- Revenue (+ Fees, Taxes)— rent + fees + taxes for booked nights. Use this for gross booking value analysis, or any reporting that needs to match what guests actually paid end-to-end.
- Revenue (Blocked)— the sum of current Asking Rates for your blocked nights. This is your opportunity cost metric: how much potential revenue is sitting behind holds, owner blocks, and maintenance windows at any given time.
- Revenue (Available)— the sum of current Asking Rates for all open, unbooked nights. Your unrealized revenue potential, live and up to date.
Between these four, you can slice your revenue picture in every direction — what you've earned, what guests paid in full, what's tied up in blocks, and what's still on the table.
🥳 Pro Tip! For portfolio hygiene — sort your portfolio by Revenue (Blocked) to quickly surface which listings have the most revenue tied up in holds. A listing with an unusually high blocked revenue figure might have stale holds that were never cleared.
-
📈 RevPAR: Fee-Inclusive and Occupancy-Adjusted Variants
We've added two new RevPAR variants to match the expanded revenue and occupancy definitions.
RevPAR (+ Fees)
— Revenue (+ Fees) divided by all calendar nights. Use this when you want a RevPAR figure that reflects the full all-in rate guests see on OTAs, not just rent.RevPAR (Adjusted Occupancy)
— Revenue divided by bookable nights (blocked nights excluded from the denominator). This gives you a cleaner RevPAR signal when your calendar has a meaningful number of holds or maintenance blocks that you'd rather not have penalizing the metric.-
🏷️ Asking Rate (+ Fees): Updated for Market Reports & Sets
Asking Rate (+ Fees)
— the current observed price from OTAs, inclusive of fees — has been updated and is now available in Market Reports and Sets. This gives you a direct view of what guests are seeing in your market, including the fee loads that increasingly drive booking decisions on platforms like Airbnb and Vrbo.-
🚀 Where to Find These Metrics
All 13 metrics are live now. You can access them anywhere data lives in Wheelhouse:
- Portfolio columns— find many of the new metrics in the column picker
- Filters— open the Filters panel; new metrics appear in the filter list
- Chart overlays— on the performance page, open the "overlays" to add context to your pickup charts
- Reports— all metrics are available when building or customizing reports
- API— every metric is available via the Wheelhouse RM API
Performance Page:

Reports:


We're excited to be bringing transparent, data-driven revenue management to one of the world's most sophisticated vacation rental markets.
1. 🌍 Built for scaling European operators
Avantio powers professional portfolios across Europe and beyond. Now those operators can pair its vest-in-class Channel Manager and PMS with Wheelhouse's fully customizable pricing & revenue tools.
2. 🛠️ Avantio users can now build on top of Wheelhouse's RM APIs
This partnership lets Avantio operators build their own tools on top of Wheelhouse. You get full API access to our entire pricing stack.
3. 🚀 Connect Avantio <> WH in 3 simple steps
Connecting Wheelhouse & Avantio is fast: 1) Connect your Avantio account, 2) Fine-tune your pricing strategy, 3) Automate and sync.
4. 🤝 Backed by real Support
This isn't just software. Every operator gets dedicated Wheelhouse Revenue Management onboarding to start strong. And Wheelhouse support connects you to a real person in under 60 seconds.
Load More
→