Your rate shows correctly on one channel and wrong on another, and this covers why rate sync drifts between channels and how to confirm every channel actually matches before a guest finds the gap.
You update a rate once in your PMS expecting it to appear the same everywhere, and then a guest or a quick manual check shows one OTA still displaying the old number while the rest have moved. Rate sync is supposed to make this invisible, but it fails in specific, checkable ways, and verifying it is different from just trusting that the push went out.
You change a rate for a date range, and within minutes most of your connected channels reflect it. One doesn't — it still shows the previous price, sometimes for hours, sometimes until someone notices a booking came in at the wrong number. The inconsistency is rarely obvious in your PMS, which shows the rate you intended, not what each channel is actually displaying to a guest.
This is distinct from a one-off pricing error on a single reservation. A sync gap affects every future booking on that channel until it's caught, which is why a small drift left unchecked becomes a real revenue or reconciliation problem over a week rather than a single day.
Each channel connection processes rate updates independently, through its own API or extranet queue, so a delay or a failed push on one channel doesn't affect the others — which is exactly why the problem looks like it's only happening on one OTA when it's really a general risk across all of them. A temporary outage on the channel's side, a rate plan ID that changed without the mapping being updated, or a push that technically succeeded but wasn't actually applied by the channel can all leave one price stuck while the rest move on schedule.
Checking your PMS isn't verification — it only confirms what you intended to send, not what arrived. Open the guest-facing side of each channel, or its extranet rate calendar, for the dates you just changed, and read the price it's actually showing. Do this for the channel that's drifted before and for one or two others, since a consistent pattern across channels tells you whether the problem is isolated to one connection or something broader in how changes are being sent.
Read-back verification exists specifically for this: every rate and availability write is read back from the channel after it's sent and compared against what was intended, rather than counting a successful-looking response as proof the price actually changed. A mismatch shows up as a mismatch instead of staying invisible until a guest books at the wrong rate. If rate drift across channels keeps costing you a manual check every week, that verification step is the structural fix — you can see it on the public demo at try.primehostpartners.com without signing up.