A guest changed their dates or Booking.com modified a reservation, but your PMS still shows the original booking — here is why modifications can fail to sync and how to fix it.
A guest extends their stay or shortens it through Booking.com, or the extranet itself applies a change, and your PMS never picks it up — it keeps showing the original dates and rate. Modifications are a different message type from new bookings, and they can fail to sync even when the original reservation came through perfectly.
The reservation itself is sitting in your PMS, correctly created from the original booking. Then the guest changes dates, adds a night, or Booking.com's system applies a cancellation-and-rebook for a modification, and none of that update reaches your PMS. You find out when the guest arrives on different dates than your system expects, or when you notice the extranet and your calendar disagree on the length of stay.
This is easy to miss because, unlike a missing new booking, there's already a reservation in your system — it just has stale information, which looks correct at a glance.
A new reservation is a single message: create this booking. A modification is a follow-up message referencing an existing reservation, and your channel manager has to correctly match it to the booking already in your PMS before applying the change. If that matching fails — because of a reference number mismatch, a delay in how the original booking was stored, or a modification message that arrives before the connection has caught up — the update has nowhere confirmed to attach to and can be dropped. Some modifications on Booking.com's side are also processed as a cancellation plus a new booking rather than an edit, which means your system needs to handle two messages correctly, not one.
Open the reservation directly in the Booking.com extranet and read its current dates, rate and status — that is the authoritative version. Compare it against what your PMS shows for the same reservation ID. If your channel manager keeps a modification or change log, check whether the update was received at all or whether it was received and failed to apply; those point to different fixes. If the extranet shows the booking as cancelled-and-rebooked rather than simply modified, check whether both parts of that process landed in your PMS.
For supported channels, including Booking.com, the system can recover a booking or modification the channel failed to deliver, rather than leaving a stale reservation sitting unnoticed. Read-back verification applies here too — after a modification is processed, the resulting reservation is checked against what Booking.com's extranet actually shows, so a mismatch is caught rather than assumed correct. 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.