Rate Plan Mapping When One Channel Adds a New Rate Type

The channel changes its catalogue; your mapping doesn't change itself. Nothing warns you — the numbers simply start disagreeing.

Last updated: September 30, 2026

A channel doesn't ask before it adds a rate type. One day there's a new shelf in its catalogue, and your mapping still points at the old layout. Nothing breaks loudly. The rates just start disagreeing — one plan sits empty, another carries a price you didn't set, and a guest books at a number you never chose. It's the quiet failure mode of direct connections, and it's fixable in three steps.

Key Takeaways

• A new channel rate type creates an unmapped shelf. Your existing plans don't move, so something has to own the new one.
• Nothing warns you. The signal is a mismatch in the numbers, not an error message.
• Step one is an inventory, not a guess. Find every plan that talks to that channel before you change anything.
• One plan should own the new type. Two owners on one shelf is how competing rates appear.
• Verify with a live booking. A connection that reads as connected isn't the same as a rate that arrives correctly.

What a new channel rate type actually breaks

Your direct connections sit on four channels: Airbnb, Booking.com, Agoda and Trip.com. Each carries your plans in its own structure, and your mapping is the agreement about which of your plans lands on which of its shelves.

When a channel adds a rate type, it's adding a shelf with nothing on it. Your plans keep pointing where they always did, so the new shelf either stays empty or gets filled by whichever plan the channel decides looks closest. That second outcome is the dangerous one. A rate you built for one purpose shows up where you didn't put it, and the guest sees a price that belongs to a different booking rule.

The failure is quiet because both sides think they're fine. Your setup shows the plan as connected. The channel shows the rate type as available. Neither screen flags a problem, because the problem isn't an error — it's a gap between two structures that used to line up.

There's a timing trap here as well. Channel catalogue changes rarely arrive at a convenient moment, and they don't wait for your quiet week. If a change lands during peak, you'll feel it as a strange booking rather than a broken setting, which is the worst way to find out.

Channels evolve their catalogues as their own markets shift, and they don't coordinate that with you. A structure that fit your plans when you connected still fits your plans; it just doesn't fit the channel's new layout. Your mapping, meanwhile, is a snapshot. It recorded a decision you made on a particular afternoon, and nothing in it updates when the other side moves.

Step one: find every plan that talks to that channel

Before you decide anything, take inventory. The question is simple: which of your plans currently send rates to the channel that changed?

Don't answer it from memory. Most hosts run more plans than they can hold in their head, especially once cancellation terms and meal arrangements multiply the combinations. A plan you set up last season and forgot is exactly the one that will claim the new shelf by accident.

The rate plans list on LOCALSBNB is built for this. It shows each plan alongside the channels it connects to, so you can read down the list and see which ones talk to the channel that changed. Narrow your attention to those and ignore the rest — a plan that doesn't touch that channel can't be part of this problem.

Write the list down, even if it's short. A mapping fix that lives only in your head is one you'll have to rediscover the next time a channel changes something.

Step two: decide which plan owns the new type

Now assign the new shelf to exactly one plan. That decision sounds trivial, and it's the one that causes the most damage when it's skipped.

The rule is one owner per shelf. If two plans both claim the new rate type, you get two rates competing on a single booking option, and the channel will resolve the conflict in a way you didn't choose. If no plan claims it, the shelf sits empty and you lose whatever demand that rate type was meant to catch.

So the real question isn't which plan can send a rate here — several probably could. It's which single plan should. Pick the one whose terms actually match the new type, then make sure it's the only one pointing there.

Then check the neighbors. A new rate type usually arrives beside existing ones, and the edge between them is where guests compare. If your new plan's rate sits close to an adjacent plan's, make sure the difference is deliberate rather than two plans drifting apart.

Write the decision somewhere you'll find it. A one-line note — this plan owns the new type, and these plans don't — turns a mapping choice into something a co-host can respect without asking you. It also saves you from re-deciding the same question from scratch the next time a channel reshuffles its catalogue.

Your calendar shows each connected channel's source rate and source status at localsbnb.com, which is how you confirm what each channel is actually carrying after you've assigned the shelf. Seeing the source rate is the difference between assuming the mapping worked and knowing it did.

Step three: verify with a live booking, not with a setting

The last step is the one people skip, because the setting looks fine. A plan that reads as connected is not the same as a rate that arrives correctly.

Check it the way a guest would. Search the channel as if you were booking, find the nights you changed, and confirm the price and terms are the ones you intended. A test booking on a real date tells you more than any status screen, because it exercises the whole path rather than one link in it.

If the number is wrong, you've learned something before a guest did, and that's the entire point of the check. If it's right, cancel the test cleanly and note what you verified, so next time you're not repeating the same inspection from scratch.

Then turn it into a habit rather than relying on luck. Whenever a channel announces a change to its rate structure, repeat the three steps: inventory the plans, assign the shelf to one owner, and confirm with a live booking. It takes an afternoon once, and it costs far less than the booking that reveals the mismatch for you.

One more thing about the check: do it before the rate type goes live in a busy period, not after. A mismatch caught in a quiet week is a settings problem. The same mismatch caught in peak is a guest standing at your door with a rate you never agreed to, and that conversation is harder to have.

FAQ

How do I know when a channel adds a rate type?

The reliable signal is a rate that doesn't match what you set — one plan sitting empty, another carrying a number you didn't choose. Channel announcements aren't consistent, so treat a mismatch in the numbers as your alert.

Can two plans send rates to the same channel rate type?

They can, and that's exactly what you want to avoid. Two plans on one shelf produce competing rates, and the channel, not you, resolves which one wins. Keep one owner per rate type.

Is checking the settings enough to confirm the mapping?

No. A connection that reads as connected can still carry the wrong rate. Search the channel like a guest, find the dates you changed, and confirm the number is the one you set.

How long does a remapping take to check?

The setup isn't what takes the time; the verification is. Budget a short block for the inventory and the single-owner decision, then leave room to search the channel like a guest and confirm the rate you set actually arrived.

A new rate type isn't a crisis. It's a shelf with no owner, and the fix is the same every time. Find the plans that talk to that channel, give the new shelf exactly one owner, and confirm the result with a booking rather than a status screen. Done properly once, the next channel change becomes an afternoon's work instead of a surprise. When you want each channel's source rate and status in front of you while you check, the calendar at localsbnb.com shows all four connections together.

---

This article is general guidance for hosts. Channel structures, rate types and platform terms change and differ by region; check the current terms of each channel you use before you change a mapping.