When a Rate Push Fails: Mapping, Rate Plan and Time Zone

A rate that will not sync is usually not broken. It is aimed at a record nobody is selling.

Last updated: September 19, 2026

A host changes a nightly rate, sees it land on one channel and not another, and concludes the connection is broken. It usually is not. A rate push travels along a chain of records — the connection, the mapping, the rate plan and the date — and a break at any link produces the same symptom: the old price still showing on the listing. Working the chain in order is faster than re-pushing the same number and hoping, and it tells you whether you have a software problem or a records problem. This article walks the chain, then gives a short check to run before you escalate.

Key Takeaways

• Start at the connection, not at the price. A listing that is not live on that channel will never take a rate, however many times you push it.
• Mapping is the most common break. The push succeeds against a record the channel is no longer selling, so nothing changes where guests are looking.
• A rate plan mismatch looks identical to a failure. The number arrives, attaches to a plan nobody is booking, and the public rate does not move.
• Time zone shifts move the date, not the price. An edit aimed at one night lands on the previous or next one when the day boundary differs.
• Diagnose from what the channel reports back. A calendar that shows each connected channel's own rate and status turns a guess into a comparison.

The chain a rate travels along

Four things have to line up before a number you typed appears as the price a guest sees. The channel has to be connected. The listing on your side has to be mapped to the record the channel is actually selling. The rate you are sending has to belong to a rate plan attached to that record. And the date you are editing has to be the same date the channel thinks it is.

Read in that order, the symptom stops being mysterious. A connection problem affects everything on that channel. A mapping problem affects one listing. A rate plan problem affects one plan across its dates, often leaving other plans untouched. A time zone problem affects one night at the edge of the range you edited. Each has a different footprint, and the footprint is what tells you where to look.

Start where the channel reports its own state. In LOCALSBNB, the single-channel detail view is where you check three things before you touch a number: whether the channel is connected, whether the listing is live on it, and whether the mapping still points at the record you think it does.

Mapping failures, and how they look

A mapping failure is the case where your side and the channel's side disagree about which record is being sold. It happens after a listing is relisted, after a room is renamed or merged on the channel, and after a property is migrated between accounts. The push itself may report success, because it did succeed — against the record it was pointed at.

Symptom	What it usually means	Where to look
One listing ignores every rate change	Mapping points at a retired or unsold record	The channel detail view, mapping section
Every listing on one channel is stale	The connection, not the mapping	Connection status for that channel
One rate plan updates, another does not	Plan mismatch, not a push failure	The rate plan attached to the listing
Only the first or last night of a range is wrong	Date boundary, usually time zone	The date range and the property's time zone
The channel shows your rate but not your availability	Two different records being updated	Both mapping and calendar status

The repair is dull and reliable: confirm the record on the channel, re-point the mapping at it, and push one night as a test rather than a whole season.

Rate plan and time zone mismatches

A rate plan carries the conditions attached to a price — the minimum stay, the terms of the stay, the board basis in markets where that applies. If the plan you push is not the plan attached to the listing on that channel, the number can arrive and still not be the price a guest is offered. The give-away is partial: some plans update, others do not, and the difference tracks the plan rather than the property.

Time zone errors are smaller and easier to miss. A date range you set in one zone can be interpreted as a different range by a channel operating in another, so the night at either end of the range takes the new rate and the one you meant does not. If the wrong night is always the first or the last one, stop looking at the price and start looking at the date.

Because both faults show up as "the channel disagrees with me", the useful view is one that shows the disagreement directly. localsbnb.com keeps availability and rates in step across Airbnb, Booking.com, Agoda and Trip.com from a single calendar, and the calendar shows what each connected channel currently holds as its rate and its status, so you are comparing two numbers on one screen rather than switching between a property management view and four extranets.

A five-minute check before you escalate

Run these in order, and stop as soon as one of them explains the symptom.

1. Confirm the channel is connected and the listing is live on it. Nothing else matters if it is not.
2. Confirm the mapping still points at the record the channel is selling, not at one that was retired.
3. Push a single night as a test, rather than a whole range, and watch that one night.
4. Compare what your calendar holds against what the channel reports back, on the same night.
5. If only the edge night is wrong, check the time zone before you check anything else.

If all five come back clean, you are past what a host can determine from the outside, and the useful thing to send is evidence rather than a description: the listing, the night, the rate you pushed, the rate the channel reports, and the timestamp.

When the push is not the problem

Some stale prices are not failures at all. A channel may apply its own rounding, its own currency conversion, or its own promotional logic on top of what you sent, so the number a guest sees is derived from your rate rather than equal to it. A minimum stay or a closed date can also make a rate invisible without making it wrong, which looks like a push failure to a host checking one night in isolation.

Allow, too, for the ordinary delay between a push and the channel acting on it. Sending the same change repeatedly while a channel is still processing the first one creates more records to untangle than one patient check, and it makes the evidence harder to read if you do end up escalating.

FAQ

Why did my rate update on one channel but not another?

Because the two channels hold different records for the same property, and only one of them is mapped correctly. The connection is per channel, and so is the mapping, so a failure that touches one channel and not the others points at that channel's records rather than at your rate.

The push says it succeeded but the price did not change. How?

The push reports what it did, not what the guest sees. If it wrote to a rate plan that is not attached to the listing, or to a record the channel no longer sells, the number landed somewhere other than the public rate.

Could this be a time zone problem?

Yes, when the wrong night is consistently the first or the last one in the range you edited. The rate is right and the date is off, so check the property's time zone against the channel's before you look at anything else.

How do I see what the channel actually holds?

Compare it rather than guess. The calendar shows the rate and status each connected channel reports, for the four channels LOCALSBNB connects to directly, which turns a stale price into a visible difference between two numbers.

When should I contact support?

After the five-step check comes back clean. Send the listing, the specific night, the rate you pushed, the rate the channel reports and the time you pushed it: that is enough to act on, where "my rate did not update" is not.

---

Channel behaviour, mapping and rate plan structures vary by channel and change over time, so confirm the current position for your own listings before acting. Results vary by market, season, property type and pricing. LOCALSBNB provides software, not financial or legal advice — see how the calendar keeps your channels in step at localsbnb.com.