Blog›Pricing

Changing Rates on Booking.com: Extranet vs. Channel Manager, Which Wins

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.

The Prime Host Partners team13 Nov 2026 · 7 min read

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.

Full guide on this topic
Why editing in two places causes a real conflict

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.

What actually determines which rate sticks

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.

What to know before editing a rate directly in the extranet
1Your channel manager is likely the source of truthUnless configured otherwise, it will push its own stored rate on schedule, regardless of a manual extranet edit.
2A direct edit is temporary unless mirroredUpdate the same rate in your channel manager too, or the next scheduled push will revert your extranet change.
3Timing is unpredictableYou generally can't see exactly when the next push will happen, so a manual edit's survival window isn't something to count on.
How to check whether this already happened to you

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.

The extranet and the channel manager are both telling the truth about the rate they each hold — the mistake is assuming either one is automatically aware of what the other just did.
Avoiding rate conflicts going forward
Decide on one primary source for rate changes — generally the channel manager — and treat direct extranet edits as the exception.
If you do edit a rate directly in the extranet, update the matching rate in your channel manager immediately after.
Check your channel manager's stored rate first whenever an extranet change appears to have reverted unexpectedly.
Review your channel manager's sync or activity log for a rate push around the time of any unexplained reversal.
Communicate to anyone on your team who might edit rates directly which room types and dates are actively managed by the channel manager.
How Prime Host stops this from happening again

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.

Frequently asked
Why did my manual rate change in the Booking.com extranet get reverted?
Most likely your channel manager still held the older rate and pushed it on its next scheduled sync, overwriting the direct edit — not because of an error, but because the channel manager wasn't told about the change.
Should I ever edit rates directly in the extranet if I use a channel manager?
You can, but update the matching rate in your channel manager immediately afterward, or the next scheduled push will likely overwrite your direct change.
How do I know if a channel manager push caused a specific rate reversal?
Check your channel manager's sync or activity log, if it keeps one, for a rate push around the time the reversal happened, and compare the pushed rate to what reappeared in the extranet.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service