A guest's dates changed on Trip.com but your PMS still shows the original booking, and this explains why modification messages fail to sync separately from the original reservation.
A guest extends or shortens a stay through Trip.com, or a change is applied on the Trip.com side, and your PMS never picks it up — it keeps showing the original dates and rate as if nothing happened. A modification is a different kind of message from a new booking, and it can fail to sync even when the original reservation arrived correctly in the first place.
The reservation is already sitting in your PMS, correctly created from the original order. Then the guest changes dates, or Trip.com's system applies a change on its side, and that update never reaches your PMS — you find out when the guest arrives on different dates than your system expects, or when someone notices the Trip.com extranet and your calendar disagree on the length of stay.
This is harder to catch than a missing new booking, because there's already a reservation on file — it simply has stale details, and a stale reservation looks correct at a glance in a way a missing one never does.
A new order arrives as a single, self-contained message: create this reservation. A modification is a follow-up message that has to correctly reference an order already recorded in your PMS, and your channel manager needs to match the two before the change can apply. If that matching fails — a reference mismatch, a delay in how the original order was stored, or a modification arriving before the connection has fully caught up on the original — the update has nowhere confirmed to attach to and can be dropped rather than applied. Some modifications are also processed internally as a cancellation paired with a new booking rather than a simple edit, which means two messages need to land correctly instead of one.
Open the specific reservation directly in the Trip.com extranet and read its current dates, rate and status — that's the authoritative version of what the guest and Trip.com agreed to. Compare it against what your PMS shows for the same order ID, and if your channel manager keeps a modification or change log, check whether the update was received at all or received and failed to apply, since those point to different fixes. If the extranet shows the booking as cancelled-and-rebooked rather than a straightforward modification, confirm both parts of that process landed in your PMS, not just one.
For supported channels, including Trip.com, a booking or modification the channel failed to deliver can be recovered rather than left as a stale reservation nobody noticed. Read-back verification applies to modifications as well — after a change is processed, the resulting reservation is checked against what Trip.com's extranet actually shows, so a mismatch is caught rather than assumed correct just because nothing errored. If modification syncing has caused a guest arrival surprise before, that's the exact gap this closes — you can see it on the public demo at try.primehostpartners.com without signing up.