A guest changed their Expedia reservation but your PMS still shows the original booking, and this covers why modification messages fail to sync and how to fix the record safely.
A guest extends their stay or Expedia itself applies a change to an existing reservation, and your PMS keeps showing the original dates and rate as if nothing happened. Modification messages are a different mechanism from new bookings, and when the sync fails, the result is a reservation in your system that looks correct but is quietly out of date.
The original reservation is sitting correctly in your PMS from when it was first created. Then a guest changes dates through Expedia, or a modification is applied on Expedia's side, and your PMS never reflects it — you discover the gap when the guest's stated dates don't match your calendar, or when someone cross-checks the Expedia Partner Central reservation against your system and finds a difference.
This is harder to catch than a missing new booking, because there's already a confirmed reservation in your PMS — it simply has information that's no longer current, which doesn't look wrong unless you specifically compare it against Expedia's own record.
A new reservation is a single, self-contained message. A modification instead references an existing reservation and depends on your channel manager correctly matching it to the booking already stored in your PMS before the change can be applied. If that match fails — because of a reference mismatch, a delay in how the original reservation was processed, or the modification arriving before the connection has caught up on an earlier message — the update has nothing confirmed to attach to and can be silently dropped rather than applied or clearly rejected.
Open the specific reservation directly in Expedia Partner Central and read its current dates, rate and status — that is the authoritative version of what the guest and Expedia agreed to. Compare it line by line against what your PMS shows for the same reservation ID, rather than assuming a visual glance is enough. If your channel manager keeps a modification or sync log, check whether the update was received and failed to apply, or never received at all — the two point to different fixes, one on your mapping and one on your connection.
For supported channels, including Expedia, a booking or modification the channel failed to deliver can be recovered rather than left as a stale reservation sitting unnoticed in your PMS. Read-back verification applies after a modification is processed too — the resulting reservation is checked against what Expedia Partner Central actually shows, so a mismatch is caught at the time rather than discovered later by chance. If a modification has ever caused a guest arrival surprise, that's the exact gap this closes — you can see it on the public demo at try.primehostpartners.com without signing up.