Dynamic Pricing and the Fee Base: When to Override

An automated rate is only as good as the figure it was given. When the fee base moves, automatic and correct stop being the same thing.

Last updated: October 9, 2026

An automated rate isn't a judgement. It's a calculation, and it's only as good as the number it was handed. When the fee base moves — the figure a percentage is taken from — the tool keeps working from its old assumption while your real net drifts. This guide explains what a pricing tool actually optimises, why a wider base changes the answer, and the signals that say a host should override it by hand.

Key Takeaways

• A pricing tool optimises one figure, not your whole booking. It moves the nightly rate. It doesn't see every deduction that lands after the guest pays.
• The fee base decides what a percentage applies to. Widen the base and the same rate stops producing the same net.
• Three signals call for a manual override. A widened base, a local levy and a one-off event are the ones worth a human check.
• Record the override and the reason. A changed rate with no note is a number nobody can explain a month later.
• Treat every rule as current. Fee structures follow each platform's current terms and your local authority, not last season's pattern.

What a pricing tool actually optimises

An automated pricing tool does one job well: it suggests a nightly rate. It reads signals like demand, season, day of week, booking pace and how far out the stay is. Then it moves your price up or down to chase the outcome it was told to chase.

What it can't see is the rest of the booking. It doesn't know your cleaning cost, your local levy, the channel share on that stay, or the discount you funded. Those land outside the rate. The tool optimises the one number it controls and stays quiet on the rest.

That's fine while the fee base is stable. The rate the tool suggests clears your floor, and the same subtraction works every time. The trouble starts when the base moves and the tool keeps pricing as if it hadn't.

Here's the shift worth making. The tool is a rate-setter, not a net-calculator. It answers "what should the nightly rate be". It doesn't answer "what will this booking actually pay me". Keep those two questions apart and the tool becomes useful rather than trusted by default.

There's a second limit worth knowing. The tool learns from the outcomes on your own calendar, so it's only as current as the bookings it has seen. When the base changes, its recent history is a record of a world that no longer applies. That's not a fault. It's a reason to check the assumption behind the price, not just the price.

Why the fee base changes the answer

The fee base is the figure a percentage is taken from. Change the base, and every percentage taken on it changes, even when your rate stays exactly the same.

Picture it without numbers. A percentage fee is a share of whatever figure it's applied to. If the base grows — because more of the booking now carries a percentage, or because a tax joins the same figure — then the share taken grows with it. Your advertised rate can sit untouched while your net moves down.

That's why "the rate didn't change" isn't the same as "my income didn't change". The rate is one input. The base, the deductions stacked on it, and the order they land in all decide what's left. A tool that only reads the rate can't see any of that.

So when a platform widens what its fee applies to, or adds a line that rides on the same figure, the safe move is to stop and re-read the whole booking rather than the rate alone. The automatic answer was correct for the old base. It isn't automatically correct for the new one.

A quick way to feel the effect is to hold the rate fixed and move only the base. Same nights, same rate, same tool. If a booking now carries more of its total as a percentage line, the amount taken rises without anyone touching the price. Nothing visible on the rate screen changed, which is exactly why the drift is easy to miss.

Three signals to override by hand

Most of the time, leaving the tool to do its job is fine. Three situations are worth stepping in.

The first is a widened base. When more of the booking carries a percentage than it used to, the rate that cleared before may no longer clear. Re-check the nights the tool has priced recently and see whether the net still holds.

The second is a local levy. When a tax lands on the same figure, the net moves even when the rate doesn't. A levy set by your local authority sits outside the tool's view, so the tool keeps pricing as though it weren't there.

The third is a one-off event. Demand that exists for a single weekend isn't a seasonal pattern. The tool reads it as one more data point. A host reads it as a decision about a specific set of nights.

In practice you'll spot these in different places. A widened base shows up when a platform changes its fee or tax treatment and tells you. A local levy shows up on the booking or on a statement before it shows up in your rates. A one-off event shows up in the search results for your dates, long before it shows up in your net. Train yourself to check the nights the tool priced, not the tool itself.

Recording what you overrode and why

An override you can't explain is a number you'll second-guess later. Write it down while the reason is fresh.

Keep it short. The date, the nights you changed, the rate you set instead of the suggested one, and one line on why. A note like "local levy applies to these nights" is enough. The point is to make the decision visible to your future self.

A record does one more thing. It turns a pile of one-off edits into a pattern you can read. After a month, you can see whether you're overriding because the base genuinely moved, or because you keep second-guessing a tool that was right. That distinction is hard to make from memory and easy to make from notes.

Keep the note where you'll see it, not in a file you open once a season. A line on the listing's own notes, or a dated entry beside the rate, is enough. The point isn't the format. It's that the next time you look at the night, the reason you set that rate comes back with it.

The calendar view in LOCALSBNB shows each connected channel's own source price and status, and its read-only assistant answers plain questions about channel rates and business figures. You can compare what you set against what each channel shows without opening a tab per platform. You can start free at localsbnb.com and let the record build before you decide the tool is wrong.

FAQ

Does the tool need to be switched off after a fee change?

No. The tool still prices most nights better than a manual pass would. Keep it on, and override the specific nights where the base or a local levy has moved. Switching it off entirely trades one problem for a slower one.

How often should I re-check the fee base?

Any time a platform tells you its fee or tax treatment has changed, and once a season as a habit. The base doesn't move often, but when it does, every night priced under the old assumption is a guess until you re-check it.

Is overriding the tool a good habit?

Only when you can name the reason. An override with a clear cause — a levy, a widened base, a one-off event — is a fix. An override that's just a feeling about a night re-creates the work the tool was meant to save.

The habit is small: let the tool price, and step in only where you can say why. Note each override, review the pattern monthly, and an automated rate stays a starting point instead of a decision you never checked. See how your channels read side by side at localsbnb.com.

---

This is general guidance for hosts, not legal, tax or insurance advice. Fee structures and local rules change, so check the current terms each platform applies and the current position of your local authority.