When a rate is changed in both the Booking.com extranet directly and through a connected channel manager, the two can disagree about what the current price actually is.
If you or your team sometimes change a rate directly in the Booking.com extranet, and a channel manager is also pushing rate updates to the same room type, the two paths can genuinely conflict — not because either one is broken, but because they're two different sources trying to set the same number. Knowing which one actually wins, and when, is what prevents a rate from quietly reverting to one you thought you'd already changed.
A channel manager works by pushing the rate it holds to Booking.com whenever that rate changes or on its regular sync schedule — it doesn't typically check the extranet first to see if someone already changed the price there. If you edit a rate directly in the extranet and the channel manager's own stored rate for that room type and date hasn't also been updated to match, the next scheduled push from the channel manager can overwrite your extranet change with the older number it still has on file.
This isn't a sync failure in the usual sense — both systems are working correctly according to their own logic. The problem is that there's no single source of truth once a rate can be changed from two places that don't check with each other first.
In most setups, the channel manager is intended to be the single source of truth for rates, with direct extranet edits treated as a manual override that's only safe if you also update the channel manager's own rate to match, or if you've disabled syncing for that specific room type and date. Without that extra step, a direct extranet change is temporary by default — it lasts only until the channel manager's next scheduled push, which can happen without warning soon after you made the manual edit. The specific timing of when the channel manager's push next runs is what decides how long your extranet-only change actually survives.
If a rate change you made directly in the extranet appears to have reverted, check your channel manager's own stored rate for that same room type and date first — if it still shows the old number, that's almost certainly what got pushed back out and overwrote your edit. Check your channel manager's sync or activity log, if it keeps one, for a rate push around the time your extranet change disappeared, which confirms the sequence rather than leaving it as a guess. Going forward, decide deliberately whether a given rate change should be made in the channel manager, so it propagates correctly, or in the extranet with the matching update made in the channel manager too.
Read-back verification checks that a rate pushed by the channel manager is actually what Booking.com's extranet shows afterward, which at least confirms the channel manager's own pushes are landing correctly — the remaining discipline of not making conflicting manual edits in the extranet is still on your side, since no system can know you changed something outside of it unless you tell it. Activity history helps here too, keeping a record of what the channel manager changed and when, so a reverted rate is easier to trace back to a specific push rather than staying a mystery. You can look at the activity log yourself on the public demo at try.primehostpartners.com without signing up.