Blog›Pricing

How to Change Rates in Trip.com's eBooking Extranet vs. via Your Channel Manager

Changing rates directly in Trip.com's eBooking extranet and changing them through your channel manager can disagree, and this explains the difference and which one to trust.

The Prime Host Partners team17 Nov 2026 · 7 min read

You update a rate through your channel manager, or directly inside Trip.com's eBooking extranet, and the two don't seem to agree afterward — one shows the new rate, the other still shows the old one. Both paths can change your rate, but they interact differently with your connectivity setup, and knowing which one you actually used is the first step to fixing a mismatch.

Full guide on this topic
Two different places to change the same rate

Your channel manager normally pushes rate changes out to Trip.com automatically whenever you update them centrally, which is the intended path if you manage multiple channels from one place. But Trip.com's own eBooking extranet also lets you edit rates directly on its side, which is useful for a quick, channel-specific adjustment but bypasses your channel manager entirely unless something is set up to read it back.

The mismatch shows up when a rate is changed in one place and the other system doesn't know about it — your channel manager keeps pushing its old stored rate, overwriting the direct edit, or the direct edit sits there unreflected in your centralized rate view.

Why a direct extranet edit can get overwritten

Most channel managers treat themselves as the source of truth for rates and will periodically push what they have stored back out to every connected channel, including Trip.com. If you edited the rate directly in Trip.com's eBooking extranet without also updating it in your channel manager, the next scheduled or triggered push from your channel manager can silently overwrite your direct edit with the old number, and there's often no alert when that happens — the rate simply reverts.

What determines which edit wins
1Which system pushes lastWhichever system sends its stored rate most recently to Trip.com is the one that determines what guests actually see.
2Whether your channel manager reads back direct editsSome setups can detect a rate was changed directly in the Trip.com extranet; many don't and will overwrite it.
3Scheduled pushes you didn't triggerA routine or automated push from your channel manager can revert a same-day direct edit without you doing anything.
How to check which rate is actually live

Check Trip.com's eBooking extranet directly for the rate on the specific dates in question — that reflects what guests are actually being shown right now, regardless of what either system's records say. Then compare it against what your channel manager currently has stored as the rate for those same dates. If they disagree, decide which system should be the source of truth going forward for that rate plan, and make the edit there rather than in both places inconsistently.

Editing a rate in two places isn't double coverage — it's two systems each assuming they're the only one in charge, and whichever pushes last quietly wins.
Keeping rate edits consistent
Decide on one system — your channel manager or Trip.com's eBooking extranet directly — as the source of truth for each rate plan.
If you make a direct edit in the Trip.com extranet, update your channel manager to match immediately, or expect it to be overwritten.
Check Trip.com's extranet directly for the live rate on the dates in question when something looks off, rather than trusting either system's internal record alone.
Avoid editing the same rate plan from both places in the same day unless you've confirmed your setup reconciles the two.
Keep rate changes centralized through your channel manager where possible, since that's the setup most connectivity providers are built around.
How Prime Host stops this from happening again

Trip.com connects directly, and read-back verification checks what Trip.com's extranet actually has stored after every rate push, rather than assuming a push succeeded because it didn't error — so a direct edit that got silently reverted shows up as a mismatch instead of staying invisible. Activity history also keeps a record of who changed what and when, across 39 action types for 400 days, which makes it straightforward to see whether a rate change came from your channel manager or was edited directly on the channel side. If rate edits keep getting overwritten without warning, that visibility is the structural fix — you can check it on the public demo at try.primehostpartners.com without signing up.

Frequently asked
Can I edit a rate directly in Trip.com's extranet instead of my channel manager?
You can, but check whether your channel manager will overwrite it on its next push. If it doesn't read back direct edits, the safer path is to make the change centrally in your channel manager.
Why did my rate change revert back to the old number on its own?
Most likely your channel manager pushed its stored rate — the one from before your direct edit — back out to Trip.com on a scheduled or triggered sync, overwriting the change you made directly.
Which system should I treat as the source of truth for rates?
Whichever one you've decided to edit consistently. Centralizing through your channel manager is usually simpler if you manage more than one channel, since it avoids edits landing in two places.
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