Revenue Management Terms Every STR Manager Needs in 2026

A property manager pulls up last month’s dashboard and sees 91% occupancy across the portfolio, which reads as a clear win. Then an owner asks why their payout came in lower than the “gross revenue” the manager quoted last week, and the conversation gets awkward fast. That gap between a calendar that looks full and a number an owner can actually bank is where most STR property managers get caught in 2026, especially now that Airbnb’s host-only fee has changed what “gross” and “net” actually mean. This guide works through the ten terms below with the formula and a worked example attached to each one, not just a definition, so the next owner report reads as a clear story instead of a number that needs defending.

Bottom line up front, before the terms: a property manager who reads these ten terms together, not as a checklist, reads a calendar the way a revenue manager does instead of the way a calendar app does.

Occupancy and ADR: Your Building Blocks

Occupancy rate is the share of available nights actually booked, and ADR (Average Daily Rate) is the average revenue earned per booked night. Neither one means much read alone, and in short-term rentals that trap is easy to fall into because most host dashboards lead with occupancy as if it were the whole scoreboard.

Occupancy = Nights Booked divided by Nights Available, times 100. ADR = Total Booking Revenue divided by Nights Booked. A property that books 27 of 30 available nights in a month for $5,670 in room revenue is running 90% occupancy at a $210.00 ADR. A neighboring property at 65% occupancy and a $290 ADR looks less busy but may be earning more per available night, which is exactly what the next term settles.

Bottom line: occupancy tells a manager how much of the calendar sold, ADR tells them at what price, and reporting one without the other to an owner is reporting half a story.

RevPAR: The Number That Catches Mistakes

RevPAR (Revenue Per Available Night, sometimes written RevPAN for rentals) multiplies occupancy by ADR into the one figure that penalizes both underpricing and overpricing equally. It is the number that ends the “we’re always booked” versus “we’re always profitable” argument, because those are not the same claim.

RevPAR = ADR multiplied by Occupancy, or equivalently Total Revenue divided by Total Available Nights. Take two properties at a $400 ADR: one running 35% occupancy earns $51,100 across 365 available nights, while one running 65% occupancy earns $94,900, a $43,800 gap that ADR alone never shows. The full ADR-versus-occupancy break-even math works out exactly how much occupancy loss a rate increase can absorb before RevPAR turns negative.

Bottom line: two properties can share an identical ADR and be nowhere near each other on actual earnings, and RevPAR is the only number in this list that shows the gap.

Net Payout vs. Gross Booking Value

Gross Booking Value is the full amount a guest pays, including the nightly rate, cleaning fee, and any extra-guest charges, before the platform takes its cut. Net Payout is what actually lands in the owner’s account after that cut. Since Airbnb’s host-only fee rollout completed in 2026, confusing the two isn’t a rounding error, it’s a reporting error an owner will eventually notice.

Net Payout = Gross Booking Value minus the host service fee (roughly 15.5% under the current host-only model) minus any PMS or channel-manager pass-through fee. A $1,000 gross booking nets roughly $845 after the platform fee alone; add a 3% PMS fee and it drops closer to $815, before cleaning costs or a manager’s own commission are even subtracted. A property manager reporting “gross revenue” to an owner without stating which figure it is will eventually have to explain a payout that looks $150 to $200 short per $1,000 booked.

Bottom line: every performance report to an owner should say explicitly whether the number quoted is gross or net, because the two can differ by 15% or more and owners notice the difference in their bank account, not in the report.

Who Is Actually in Your Comp Set?

A comp set is the 10 to 15 listings in the same submarket, bedroom count, listing type, and amenity tier that a guest would genuinely compare a property against before booking. Picking the wrong comp set is the single most common reason a property manager misreads whether a listing is priced correctly.

A comp set is built by filtering on location radius, bedroom and bathroom count, listing type, and amenity tier, then disqualifying anything a guest would not seriously cross-shop against the subject property. Comparing a 2-bedroom condo against a 4-bedroom house with a pool inflates or deflates the read on pricing in either direction. The full five-criteria filtering framework works through a disqualifier checklist and a worked RevPAR example showing how comp set choice alone can swing the read on a listing’s performance.

Bottom line: a property manager who has never rebuilt a comp set since onboarding a listing is very likely benchmarking against properties that no longer represent who the guest is actually choosing between.

Minimum Stay and Orphan Nights

Minimum length of stay (MinLOS) is the shortest booking a listing will accept for a given date, and an orphan night is a single unsellable night stranded between two bookings by a minimum-stay rule set too high for the gap. Getting this wrong quietly caps occupancy in a way that never shows up as an obvious mistake.

Every MinLOS setting should clear a break-even conversion rate: the extra nights it captures per booking have to be worth more than the bookings it filters out entirely. A single-night gap between two 2-night-minimum bookings becomes unsellable orphan inventory unless the minimum stay flexes down as the gap shrinks. The full minimum-stay break-even framework works through the conversion-rate math and a lead-time ladder, and the companion orphan-night playbook closes these gaps without gutting ADR on the nights that do sell.

Bottom line: a minimum-stay setting that was right for last quarter’s calendar shape can be quietly creating orphan nights this quarter, and nobody notices until occupancy is already down.

Is Your Booking Pace Telling You Anything?

Booking pace is how far ahead of a given date a property is booked compared to its own historical booking curve for that same lead time. A property manager who only checks pace the week of the stay is finding out about a demand problem after it is too late to fix cheaply.

Pace is read against a property’s own history, not a generic rule, because the widely repeated “75-55 rule” is quoted with contradictory definitions across the industry and rarely matches any specific portfolio’s actual booking curve. The full booking pace framework gives the discount-versus-uplift break-even formula that decides whether a rate cut in response to soft pace will actually pay for itself, rather than just filling the calendar at a loss.

Bottom line: pace only means something measured against a property’s own history at the same lead time last year, not against a rule of thumb borrowed from a blog post.

Cancellation Policy as Expected Value

A cancellation policy is a set of rules for how much a guest gets refunded if they cancel, and it functions as a revenue decision, not a hospitality one. The policy that maximizes bookings is not automatically the one that maximizes revenue once rebooking probability is factored in.

The right policy is chosen by expected value: (probability a cancelled night rebooks) times (the rebooked rate) compared against the refund cost and the conversion lift a flexible policy gives at the point of booking. A firm policy protects revenue on dates likely to rebook anyway; a flexible policy can convert more bookings on soft dates that would otherwise sit empty. The full expected-value framework works through a seasonal policy calendar rather than a single fixed setting applied year-round.

Bottom line: the “guest-friendly” cancellation policy and the revenue-optimal one are sometimes the same policy and sometimes opposites, and only the expected-value math tells a manager which case applies on a given date.

Base Price: Where Dynamic Pricing Starts

Base price is the rate a dynamic pricing tool starts from before it applies demand, seasonality, and lead-time adjustments, and it is the single input that determines whether automated pricing helps or quietly caps revenue. A dynamic pricing tool set on top of a wrong base price optimizes around the wrong number all year.

Base price should reflect a property’s true floor and typical value against its comp set, not a round number picked at onboarding and never revisited. A base price set too low means even a well-tuned pricing engine spends most of the year discounting from a starting point that was already underpriced. A checklist worth running quarterly:

• Base price is checked against the current comp set, not the comp set from onboarding
• Base price reflects the property’s actual floor, not a guess carried over from a previous season
• Seasonality and lead-time multipliers are reviewed separately from the base price itself
• A minimum price floor is set explicitly, not left to the algorithm’s default

Bottom line: a dynamic pricing tool is only as good as the base price it starts from, and a wrong base price is invisible on a performance dashboard until someone checks it directly.

Frequently Asked Questions

Conclusion

These ten terms are the working vocabulary of short-term rental revenue management in 2026, and treating any one of them as the whole story is how a portfolio ends up looking busy on the calendar while quietly underearning. If keeping all ten current across a growing portfolio is more than your team has time for, get in touch with Revenuenaire and we will show you exactly where your properties sit on each one.