Blog›Connectivity

Expedia Reservation Modification Not Syncing to Your PMS

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.

The Prime Host Partners team14 Nov 2026 · 7 min read

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.

Full guide on this topic
What a failed modification sync looks like on Expedia

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.

Why modifications are more fragile than new bookings

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.

Where modification sync typically breaks on Expedia
1Reference mismatchThe modification message doesn't match cleanly against the original reservation already stored in your PMS.
2Timing gapThe modification arrives before your system has finished processing the original booking, leaving nothing confirmed to attach it to.
3Partial processingThe modification is received but only part of the change — the rate, for instance, but not the dates — is actually applied.
How to check what actually changed

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.

A stale reservation causes more trouble than a missing one, because everything about it looks normal until someone checks the actual dates against the source.
Correcting the record and preventing a repeat
Read the reservation's current status, dates and rate directly from Expedia Partner Central before changing anything.
Update the reservation manually in your PMS to match if the sync clearly failed to apply the change.
Check your channel manager's modification or sync log to see whether the update was received but not applied, or never received.
Reconfirm the dates directly with the guest if there's any doubt about which version is current.
Flag the specific reservation ID if you need to raise it with Expedia support, so the case can be checked against their own record.
How Prime Host stops this from happening again

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.

Frequently asked
Why does my PMS still show the old dates after a guest changed their Expedia booking?
Most likely the modification message failed to match to the existing reservation or wasn't fully applied, leaving the original booking details in place while Expedia's own record has already moved on.
Is a modification processed the same way as a new reservation?
No — it's a follow-up message that has to correctly reference an existing reservation, which makes it more prone to sync failures than a brand-new booking coming through cleanly.
Which record should I trust if Expedia and my PMS disagree?
Expedia Partner Central, since it reflects what was actually agreed with the guest. Update your PMS to match, then investigate why the sync failed in the first place.
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