Repricing One Channel Without Disturbing the Other Three

A rate change is meant to touch one channel. A mapping slip is how it reaches four, and the symptom shows up as a booking at the wrong price.

Last updated: October 8, 2026

The idea is simple. You change a rate on one channel and the other three stay exactly as they were. Then a booking lands at the old price somewhere else, and you find out the change travelled. A rate change doesn't spread on its own. A mapping slip spreads it. This guide walks the sequence that keeps a repricing local, the symptoms of one that escaped, and how to confirm the other channels are untouched.

Key Takeaways

• One change can reach four channels. A rate change doesn't travel by itself; a unit or channel mapping slip carries it.
• The unit is where the slip starts. A rate that's right for the wrong unit lands on the wrong channel.
• Order beats speed. Change the source rate, check the unit, then read the other three channels before you stop.
• The calendar is your proof. Each connected channel shows its own source rate and status, so you can see who moved.
• A wrong-price booking is the late symptom. By the time it arrives, the change has already spread.

Why one change reaches four channels

LOCALSBNB connects directly to four channels: Airbnb, Booking.com, Agoda and Trip.com. That's the point of a channel manager, and it's also why a single misstep can widen. When one rate sits behind several channels, the mapping between a rate and a unit is what keeps them apart.

A mapping is the join between a rate and the unit it belongs to. Get the join right, and changing one channel touches one channel. Get it wrong, and the change rides a rate that several channels share, so it reaches all of them at once.

The usual cause isn't a broken tool. It's a human shortcut. A host in a hurry edits a rate that two units share, or picks the wrong unit from a list that looks alike. The change saves a minute and costs a week.

There's a second path too. A rate can be copied to a new unit without the copy being separated from the original. From then on, editing either one moves both. Nothing warns you, because from the tool's side the two are behaving as linked.

So the first thing to accept is that four channels are closer than they look. A rate change you mean for one is only one mistake away from the other three. The rest of this guide is about keeping that mistake from happening.

It helps to know how many channels sit behind a single unit. A unit listed on all four channels can look like four separate rate decisions, and it often isn't. If one rate feeds more than one channel, that unit is where a small edit becomes a wide one. Count the channels behind each unit before you touch a rate.

The sequence that keeps a change local

The reliable way to reprice one channel is to follow a fixed order and not skip a step. Order beats speed here, because each step checks the one before it.

Start at the source. Change the rate on the channel you mean to move, and only that channel. Do it from the place where the rate is owned, not from a shared copy. If you're unsure which rate owns the unit, stop and settle that first.

Then check the unit. Before you go any further, confirm the rate you changed sits on the unit you meant. A rate that's correct in value but wrong in unit is the classic slip. Read the unit name, not just the rate.

Then look outward. Read each of the other channels and see what rate they show. If they still show their own source rate, the change stayed local. If one has moved, you've found the slip, and you can fix it before a guest acts on it.

Only then close the job. A repricing isn't finished when the number looks right. It's finished when the other channels are confirmed untouched. That last read is the step hosts skip, and it's the one that catches the problem.

Speed is the enemy of a clean repricing. A host who rushes tends to edit first and check later, which is the reverse of the safe order. Slowing down at the unit step costs seconds and saves the rest. Treat that step as the centre of the job, not an afterthought.

Symptoms of a change that escaped

A change that escaped usually announces itself in one of a few ways, and most of them are quieter than a wrong booking. Learn the early ones and you'll catch the spread before a guest does.

The first symptom is a rate that looks familiar on a channel you didn't touch. If a channel shows a number that matches the one you just set elsewhere, that's the change riding a shared rate. It looks harmless. It's the whole problem.

The second is a gap between the rate you set and the rate a channel displays. A channel can lag or hold its own source rate, and that difference is a signal worth reading. If the numbers disagree, find out which one owns the unit.

The third is the booking at the wrong price. It's the most expensive symptom, because it means the spread already met a guest. By then the fix is a conversation, not an edit, so it's the one you want to prevent rather than catch.

There's a fourth, quieter one. A rate you remember editing looks unchanged later. That can mean your edit landed on a copy, not the original. When an edit seems to vanish, don't repeat it. Check the unit and the mapping first, or you'll spread the same change twice.

None of these symptoms needs panic. Each one points to a specific place to look: the unit, the mapping or a copy. Match the symptom to the cause and the fix is quick. Treat them all as the same problem and you'll keep spreading it.

Confirming the other three are untouched

The final step is a short read, and it's the one that makes the whole job safe. Before you call a repricing done, look at every channel you didn't mean to move and confirm it still shows its own rate.

localsbnb.com makes that read direct. Its calendar shows each connected channel's source rate and status, so you can see at a glance which channel moved and which held. You can also ask a read-only question over your channel rates and unit calendars, so the check fits into the same minute as the change.

Do the read against units, not just totals. A single unit can carry several channels, and it's the unit that tells you whether the change stayed on one. If you manage several units, check the one you edited first, then the ones that share a rate with it.

Give it a rhythm. A quick read after every repricing trains the habit, and a longer pass once a month catches anything that slipped in between. The monthly pass also catches copies that got separated, or units that quietly joined a shared rate.

A monthly pass is worth the ten minutes it takes. Read each unit's channels once, note anything that moved without your say-so, and separate copies that shouldn't be linked. Small drifts caught monthly never become a guest-facing problem.

Keep a short note of what you changed. A line that says which unit, which channel and which date turns a future puzzle into a lookup. When a rate looks off weeks later, that note tells you whether you have a spread to undo or a deliberate change you'd forgotten.

A repricing that stays local isn't luck. It's four steps in a fixed order: change the source, check the unit, read the other channels, then close. Do them in that order and the other three stay exactly where you left them.

FAQ

How do I change one channel's rate without touching the others?

Change the rate where it's owned, not from a shared copy, then confirm it sits on the right unit. Finally, read each other channel's source rate and status. If they still show their own rate, the change stayed local.

What does a mapping slip look like?

A channel you didn't touch shows a rate that matches the one you set elsewhere. That's the change riding a rate several channels share. It looks harmless, but it's the whole problem, so check the unit and the mapping.

What's the last thing to check after a repricing?

Read every channel you didn't mean to move and confirm it still shows its own rate. That final read is the step most hosts skip, and it's the one that catches a change that escaped.

A repricing is only safe once the other channels are confirmed still. Change at the source, check the unit, read the rest, and keep a short note of what moved. When you want each channel's source rate and status in one view, start from localsbnb.com and make the final read a habit.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules, thresholds and platform terms differ by place and change over time; check the current position with your local authority and the current terms of each platform you use.