A dynamic pricing tool optimizes one number, the nightly rate. Two levers sitting right next to that number decide what you actually keep: how you split the all-in price between rate and fees, and how you architect length of stay. No pricing tool I have ever used optimizes either one, and on most portfolios both are still set by hand and then forgotten.
I want to go deep on just these two, because they are where I see the most money left behind on books that already have a pricing tool running clean. The rate is dialed. The fees and the stay-length logic are an afterthought. That afterthought is costing real RevPAR.
"The pricing tool sets the rate. It does not touch the fee split or the stay-length logic. Those two decide what you net."
Lever one: fee-to-rent design
Here is the thing operators miss about fees. The same all-in price a guest pays nets you differently, ranks differently in OTA search, and converts differently depending on how you split it between the nightly rate and the cleaning fee. The total is identical. The outcome is not.
Walk through what a heavy cleaning fee actually does. Take a $250 night with a $200 cleaning fee. On a seven-night stay that fee spreads across seven nights and barely registers, $1,950 all-in, the cleaning is eight percent of the trip. On a one-night stay it is the headline. The guest sees $250 for the room and $200 to clean it, a $450 total where almost half is fee. That guest bounces. Conversion on short stays collapses under a fixed cleaning fee, and the search platforms know it.
OTA ranking is the second-order effect most people never see. Airbnb and Vrbo both surface and reward total-price competitiveness, and a listing carrying a large separate cleaning fee ranks worse against a comparable unit that loaded the same money into the nightly rate. Same money to you. Worse placement, worse click-through, fewer bookings. You paid for the fee twice, once in conversion and once in rank.
So the move is not to abolish the cleaning fee. The move is to design the split deliberately by stay length and by listing. Load more into the nightly rate where short stays matter and search placement is tight. Hold a higher cleaning fee where your inventory skews to week-long bookings and the fee disappears into the trip. This is a per-listing, per-season decision. A pricing tool prices the rate field and leaves the fee fields exactly where you typed them on day one.
"The same all-in price ranks worse, converts worse, and nets the same when it is sitting in a fee instead of the rate."
The negative-RevPAR trap
There is a specific failure mode here that is worth naming, because I see it on portfolios that think they are pricing aggressively. It is the low rate plus a fixed cleaning fee on a one-night booking, and it can net you negative.
Picture a soft midweek night. The tool drops the rate to $90 to chase fill. A guest books one night. You collect $90 in rate plus, say, a $120 cleaning fee. Feels fine on the booking screen. Now run the real cost. The cleaner gets paid the full turnover, often more than the $120 you charged because a one-night turn costs the same as a seven-night turn. Add OTA commission on the whole $210, add linens, consumables, and the unit being blocked. On a true-cost basis that night can clear less than zero. You did not fill a soft night. You paid a guest to occupy it.
The fix is not a lower rate. It is a minimum-stay rule that keeps you out of the one-night-at-a-discount trap in the first place, plus a fee structure that does not pretend a one-night turn is free money. Which is the second lever.
Lever two: length-of-stay architecture
Minimum stays decide which nights are even bookable. Before you price a night, the stay-length rule decides whether a guest can buy it at all. That makes length-of-stay architecture upstream of pricing, not a setting you flip once and ignore.
Three pieces make up the architecture, and they are distinct decisions.
Minimum stays by season and by date.
A 2-night minimum that is right for a sleepy Tuesday is wrong for a high-demand holiday weekend, and a blanket 3-night minimum quietly blocks legitimate short bookings in shoulder season. Minimums have to move with demand, by specific date, not sit as one global number.
Gap-fill rules for orphan nights.
When a 2-night minimum sits between two bookings with a single open night between them, that night is unsellable. It is an orphan. Gap-fill logic detects those gaps and drops the minimum to one for that night only, recovering revenue that the standard rule would have thrown away.
Stay-length pricing.
A 3-night booking and a 7-night booking should not earn the same per-night rate. Longer stays cost you less per night in turnover and commission, so they can carry a lower nightly rate and still net more. Pricing the length, not just the night, is how you steer the book toward the stays you want.
Get the minimum wrong and you orphan your highest-value nights. A 2-night minimum dropped on a peak Friday and Saturday looks disciplined until a guest wants Saturday through Monday and cannot book it, because Saturday is locked to its neighbor. The nights you most wanted to sell at the highest rate are the ones the rule quietly took off the market.
How to set minimum stays by season
There is no single right minimum. There is a process. Here is the sequence I run our team through when we set stay-length logic on a new book.
- 01Start from demand, not habit. Pull the booking pace for each date range. Peak windows that fill themselves can carry a longer minimum. Soft windows need a shorter one, or you block the only bookings on offer.
- 02Set the floor by true turnover cost. Find the stay length where a booking clears your real cost after cleaning and commission. That length, not a round number, is your baseline minimum for normal demand.
- 03Lengthen minimums only where demand outruns supply. Holiday weekends, festival dates, and proven sellout windows can hold a 3 or 4-night minimum, because you will fill them regardless and you want the longer, higher-value stays.
- 04Shorten in the shoulder and on weeknights. Drop to a 1 or 2-night minimum where pace is soft, so you capture the short getaway demand the longer rule was silently rejecting.
- 05Layer gap-fill on top of all of it. Let an automated rule release orphan nights to a 1-night minimum the moment they appear, so the architecture never strands a sellable night.
- 06Reprice the stay length, not just the night. Give multi-night stays a per-night break that still beats a one-nighter on net, and push the book toward the longer bookings that cost you less to service.
Does pushing longer stays actually beat chasing one-nighters?
Yes, and I can show it on a real book. Geneva Lakes Vacations is a 116-unit Wisconsin lake operator we manage. We rebuilt their length-of-stay architecture, lengthened minimums into proven peak windows, and repriced for longer stays. The stay-length distribution shifted toward longer bookings, two-night turnover dropped on premium weekends, and the rate on multi-night bookings rose without surrendering ADR on the rest of the calendar.
The headline result is the one that matters. Same-store Adj. RevPAR went from $88 to $128 year over year, a 46 percent lift on the KeyData same-store methodology. That came from stay-length design, fee architecture, and gap-fill, the structural layers that compound across a season. Pushing the book toward longer stays beat chasing one-nighters by a wide margin, and it beat it on the exact dates a pricing tool would have been discounting into.
"Same-store Adj. RevPAR $88 to $128, a 46% lift on the KeyData same-store methodology. The lift came from stay-length design and pricing discipline."
Why no pricing tool does this
It is not a knock on the tools. PriceLabs, Wheelhouse, and Beyond are very good at the one job they own, which is moving the nightly rate against demand. We run them on our books. But fee-to-rent design depends on your true turnover cost, your owner economics, and your OTA placement strategy, and the tool has none of that. Length-of-stay architecture depends on a per-date read of demand against your cost floor and your channel mix, and the tool prices a night without deciding whether the night should be bookable at all.
These are judgment layers, not rate outputs. They sit above the pricing engine and they decide the structure the rate lives inside. Set them once and forget them and the tool will faithfully price a calendar that is leaking from two directions at once. Set it and forget it is not a strategy here any more than it is on the rate itself.
Where this nets out
Two levers, both upstream of the number your pricing tool optimizes, both still set by hand on most portfolios. Fee-to-rent design decides what the same all-in price nets you and where it ranks. Length-of-stay architecture decides which nights are bookable and steers the book toward the stays that cost you less to service. Neither one is exotic. Both compound, and both are sitting untouched on books that believe a pricing tool has revenue handled.
Pacer runs these layers for property managers on portfolios of 20-plus units. The pricing tool stays. What we build on top is the fee split, the stay-length logic, and the gap-fill discipline that turn a rate engine into a revenue function. If you want to see the gap on your own book, we run a free revenue audit that benchmarks your ADR and RevPAR against your real comp set and shows you exactly where the fee structure and the minimum-stay rules are leaking, with no commitment. We also back the engagement with the Pacer Promise: cancel in the first six months and we return 50 percent of fees paid.
Adapted from Pacer's editorial archive, May 2026.