Repricing After a Channel Fee Change: Protecting Net, Not Rate

When a channel shifts more of its fee onto the host side, the visible rate does not change. The number that changes is what reaches your account.

Last updated: October 14, 2026

A fee change arrives quietly. Your listing page looks the same, the guest pays the same, and the rate you set is still the rate you set. What moved is the distance between that rate and your payout. Reprice for it like a rate problem and you'll overcorrect on three channels that didn't change. Reprice it like a net problem and the work fits in an afternoon.

Key Takeaways

• The rate is the wrong signal. A fee change barely touches the guest-facing number and lands directly on your net.
• Recompute the floor, not the rate. Your old floor was built with the old deduction. If the deduction rose, that floor is now fiction.
• Change one channel. The other channels' deductions didn't move, so a portfolio-wide rise overprices the nights that were fine.
• Keep a control. Leaving one channel untouched gives you something to compare against in two weeks.
• Review nights and net together. Occupancy without net says nothing, and net without occupancy hides the bookings you priced away.

Read the fee change as a net change

Start by writing the four lines that sit between a guest's payment and your bank account. The rate the guest sees. The channel's deduction. Whatever tax is taken or remitted along the way. The amount that actually arrives.

Most hosts carry a rough sense of that gap and never write it down. A fee change is exactly the moment the rough sense stops working, because the change lands on one of the four lines and leaves the other three alone.

So ask three questions in order. Which line moved? From when? On which channel? If the answer to any of them is a guess, read the channel's current terms before you touch a rate. Fee structures are published, dated and specific, and guessing at them is how a repricing exercise turns into a second correction two weeks later.

Then test the change against two nights, not against an average. Take a typical midweek night and a typical weekend night, and run all four lines for each. A fee that looks small against a weekend rate can be painful on a midweek night that was already close to your floor, and an average hides exactly that.

There's a second trap in the arithmetic. A fee change expressed as a share of the rate scales with the rate, so the nights that carry the highest rate take the biggest hit. That means the impact isn't spread evenly across your calendar. It's concentrated in your best nights, which are also the ones you can least afford to misprice.

One more distinction worth writing down: a fee isn't a tax, and a tax isn't a fee. They behave differently, they're treated differently in your records, and one of them you may be able to recover. Keep them on separate lines even when the channel combines them on a statement.

Recomputing the floor on one channel only

Your floor was never a rate. It was the net below which a night costs you money, and you built it from costs plus a contribution you're willing to accept.

When the deduction rises, that floor doesn't move. What moves is the rate required to reach it. The relationship is simple: take the net you need, and divide it by what's left after the channel's cut. The result is the new rate floor for that channel.

Do that sum for the affected channel and no other. The other channels still deduct what they deducted last month, so their floors are unchanged, and raising them would only make you uncompetitive on nights that were already working.

Here's where most repricing goes wrong. The instinct is to pass the change through one-for-one, adding the same share to every rate on the channel. That treats a net problem as a pricing problem, and it assumes guests won't react. They will, at the margin, and the nights you lose are usually the ones that were closest to your floor anyway.

The better version is to pass through partially, and to choose where. Raise the floor on the nights where demand is proven, and hold the rate on the nights that were already filling slowly. That keeps the net line moving without turning a fee change into an occupancy change.

Write the new floor down with a date next to it. Six months from now, when the next change arrives, you'll want to know which floor was built on which set of terms.

Keeping the other channels where they are

The strongest argument for leaving the other channels alone isn't fairness. It's evidence.

If you reprice all four channels on the same day, you have no comparison. Every number moves at once, and two weeks later you can't tell whether a change in bookings came from your new rates or from the season, the weather or a competitor's decision. One untouched channel gives you a control group for free.

There's a second reason, and it's about the guest rather than your spreadsheet. Rates that differ across channels get noticed, and some channel terms constrain how you present them. Check the current terms rather than assuming, and keep the differences small enough that they're explainable.

Keeping the others still doesn't mean ignoring them. LOCALSBNB's calendar shows each connected channel's source rate and source status, so you can confirm that the change you made on one channel didn't travel to another through a shared rate plan. That kind of leak is common when one plan feeds two connections.

And keep the untouched channel untouched in the literal sense. Don't quietly trim a weekend rate there, don't add a last-minute discount, don't run a promotion because the calendar looks soft. The moment you touch it, the comparison is gone and you've paid for the experiment without getting the result.

If parity pressure makes you nervous, give the untouched channel a time limit rather than an exception. Two weeks of difference is a test. Two months of difference is a pricing policy you didn't mean to adopt.

Reviewing the result after two weeks

Two weeks is the shortest window that tells you anything and the longest you should wait before correcting. Shorter, and you're reading the weather. Longer, and a bad pass-through has already cost you a fortnight of bookings.

Read three things per channel: nights sold, net per night, and net in total. The first tells you whether demand held. The second tells you whether the repricing did what you intended. The third is the one that decides.

Then apply three plain rules. If nights held and net per night rose, keep it and stop watching. If nights fell by more than the net gain, the pass-through was too aggressive, and the correction is to lower the floor on the nights that stopped selling rather than to undo everything. If nothing has moved at all, wait another week before changing anything, because a second change stacked on an unread first one teaches you nothing.

LOCALSBNB's Home dashboard shows occupancy, ADR and RevPAR, which is the fastest way to see whether a channel's nights held while its rate moved. localsbnb.com keeps those three next to each channel's source rate, so the review is a comparison rather than a reconstruction.

Write the result in one line: date, channel, old net, new net, nights. Six lines like that over a year turn fee changes from events into a pattern you can price against.

And resist the urge to make the second change before the first has been read. Most repricing damage isn't caused by the fee. It's caused by three corrections stacked on top of one unread result.

FAQ

Should I raise rates on every channel when one channel raises its fee?

No. The other channels' deductions didn't change, so their floors didn't either. Raising everywhere overprices nights that were already working and removes the comparison you need.

How much of the fee increase should I pass through?

Partially, and selectively. Raise the floor on nights where demand is proven and hold the rate where nights were filling slowly. A full pass-through assumes guests won't react, and at the margin they will.

Why two weeks and not a month?

Two weeks is long enough for booking pace to show and short enough to correct without losing a fortnight. A month tells you more about the season than about your change.

What if I can't tell whether the fee or the season caused the drop?

Keep one channel untouched and compare the same nights across the two. Without a control, a seasonal dip looks exactly like a pricing mistake.

A fee change is a small event with a long tail. Read it on the net line, move one channel, keep one still, and give the result two weeks before you judge it. If you want the net and the nights side by side while you decide, localsbnb.com shows each channel's rate and performance in one place rather than four statements.

---

This is general advice for hosts, and it isn't legal, tax or financial advice. Fee structures, tax treatment and platform terms vary by place and change over time; check the current terms of each channel you use and take local advice where the amounts matter.