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.
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.
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.
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.
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.
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.