You Changed the Rate — Did It Actually Sync?

Verify a rate change in three views so the guest price matches what you saved.

Last updated: September 16, 2026

You clicked save on a new nightly price. The dashboard shows the right number. So the job is done, right? Not quite. For hosts running villas in Bali or apartments in Bangkok, the gap between "saved in your system" and "what a guest actually pays" is where real money leaks. A rate can look updated in one place and still show the old figure on a channel — or worse, update the wrong room or plan.

This guide walks through one habit that catches most sync mistakes before they cost a booking: verify the change in three views, in order, every time you edit a price.

The "saved" message is not the same as "synced"

On a large global OTA, "synced" can mean several different things. A value might be saved in your calendar, queued for delivery, sent to the channel, technically accepted, or still sitting in a cached public result. Each of those is a different state, and only the last one protects you.

The safe routine is the same whether you push rates from LOCALSBNB or edit directly on a channel: confirm ownership, edit in the right place, then prove the new price reached the guest.

First, know which system owns the rate

Before you touch a single cell, work out who is the source of truth for that plan. If your LOCALSBNB connection controls the plan, the rate lives in your calendar and flows out to Airbnb, Booking.com, Agoda, and Trip.com through the direct connection. Editing the price on the channel itself is a temporary move — the next sync can overwrite it.

A quick test is the calendar itself. In LOCALSBNB, open the rate for the room and plan you intend to change and note the current value, currency, dates, occupancy, and restrictions. If a channel shows the same plan as editable on its own side, decide deliberately: either you manage that plan from LOCALSBNB or you let the channel hold it. Mixed ownership is normal, so write down which is which before you start — one slip and a Kuala Lumpur studio can inherit the rate meant for a Phuket beach villa.

Verify the change in three views

A rate edit is finished only when three numbers agree. Most hosts check one and assume the other two followed. The three-view method makes all three explicit, and it is the difference between "I saved it" and "I know it landed."

View 1 — the rate in your dashboard

Open LOCALSBNB and confirm the stored value for the exact room type and rate plan, with the dates, occupancy, and currency you targeted. Reopening the same dates after saving is the only way to be sure the master copy holds what you intended, not a derived or parent-linked figure.

If the stored amount is wrong here, stop. The problem is upstream — fix the source value, not a displayed cell somewhere else.

View 2 — the channel sync status

Next, open Channel in LOCALSBNB and look at the delivery state for that update. A healthy sync reads as sent, then accepted against the correct mapped product. Watch for the other states too: pending means the channel has not confirmed, rejected means the message bounced, and failed means the connection did not deliver at all.

Match the update to the right mapped product. A rejected message usually tells you why — inactive plan, currency mismatch, missing occupancy prices, or mapping error. Fix the root cause and resend only the affected dates; the delivery log for that exact update is the only proof.

View 3 — the guest-facing price

Finally, become the guest. Search the channel in an incognito window using the same dates, number of guests, room, and currency. Look at the nightly amount, the total, taxes, cancellation terms, and any promotion shown before payment.

The public price can trail the stored one by a few minutes while caches refresh, so give it a short pause and search once more. If the first message is still in flight, resist the urge to resend the same range — duplicate updates can create conflicts.

Those three views collapse into one screen when the rate lives in LOCALSBNB: the stored value, the delivery status to Airbnb, Booking.com, Agoda, and Trip.com, and a calendar you can sanity-check — all included when you start free at localsbnb.com.

When the public price still looks wrong

A guest-facing price that differs from what you stored is not proof the sync failed. Before blaming the base rate, make sure the two searches are genuinely the same offer: dates, guest count, exact room and plan, cancellation window, payment timing, currency, and whether taxes and fees are included.

What sits on top of your base rate matters too. A member-only deal, phone or app discount, package bundle, or longer-stay incentive can all lower the number one traveler sees. A child plan linked to your standard plan may also add or subtract a fixed amount.

If one guest count looks wrong, look at per-occupancy pricing and extra-guest charges. If the whole plan is off, check the mapping or parent rate. If a single night vanishes, review availability, minimum and maximum stay, and arrival or departure blocks. Compare the loaded rate with the final checkout total, not the small preview card a channel shows in search.

If the sync never landed

Start with the smallest broken piece: a single room, a single plan, one guest count, and one night. Confirm the value you intended and find the outbound message that matches it in the delivery log.

When a channel rejects an update, read the full error response instead of guessing. Typical causes are an unmapped or inactive product, a currency or amount it rejects, blank occupancy prices, a value outside the allowed band, a clashing restriction, or an expired connection. Fix the cause and resend only the affected dates.

If the channel accepted the update but the price does not show, line up its product codes with your LOCALSBNB mapping. When a value appears then slips back, list every system allowed to send that rate and review timed rules, linked-rate logic, batch jobs, and manual edits on the channel side.

A 30-second pre-change checklist

Frequently asked questions

Which system should I use to change a channel rate?

Edit in whichever system is the source of truth. If LOCALSBNB controls the plan, change it once in your calendar and let the direct connection deliver it to Airbnb, Booking.com, Agoda, and Trip.com. Use the channel's own editor only for plans or promotions it manages directly.

How do I know the sync actually worked?

Match three views: the stored rate in LOCALSBNB, the accepted delivery state in Channel, and the guest-facing checkout price on the OTA. All three must agree; a "saved" label in one place proves nothing about the other two.

Why does the price a guest sees differ from my stored rate?

Promotions, member or mobile discounts, taxes, fees, currency conversion, or occupancy-based pricing can change the visible total. Compare the same dates, occupancy, currency, and cancellation terms first.

What if the rate reverts to the old number after a while?

Another authorized system is likely overwriting it — a scheduled rule, derived-rate link, bulk job, or manual edit on the channel. Compare timestamps to find the real source and fix that source.

How long should I wait before trusting a rate change?

Give the channel a few minutes to refresh its public cache, then search once more. Do not resend while the first update is still in flight; confirm the stored value and delivery state first.

Ready to see saved, sent, and sold-price in one place? Start free at localsbnb.com.

Keep reading

• [Channel Sync Failed on Airbnb, Booking.com or Trip.com? What the Status Means and How to Fix It](/resources/channel-sync-failed)
• [How to Avoid Double Bookings: A Calendar Setup for Airbnb, Booking.com and Trip.com](/resources/double-booking-prevention)
• [An Agoda Booking Never Reached Your Calendar? Trace It Before You Touch Anything](/resources/agoda-booking-missing)

---

Fees, rates, and platform policies change, so confirm current details with each channel before acting. Results vary by market, season, property type, and pricing. LOCALSBNB provides software, not financial or legal advice.