A guest cancelled through an OTA, but your PMS still shows the reservation as active and holding a room, and this explains why that sync can fail and how to clear it safely.
You check an OTA extranet and a reservation is clearly marked cancelled, but your PMS still lists it as active, still holding the room on your calendar. This is a specific kind of sync failure — not a missing booking, but a stale one — and clearing it properly means more than just deleting the reservation from your side.
The reservation is sitting in your PMS exactly as it was created, with the guest's name, dates and rate, and your calendar still treats that room as unavailable. Meanwhile the OTA extranet — Booking.com, Agoda, Expedia, whichever channel the booking came through — clearly shows the same reservation as cancelled, sometimes with a cancellation date and reason attached.
Unlike a booking that never arrived at all, this one looks completely normal in your system. Nothing is flagged as broken, which is exactly why it tends to sit unnoticed until the room is needed and someone finds it's still blocked for a guest who isn't coming.
A cancellation is, like a modification, a follow-up message that has to correctly reference the original reservation already stored in your PMS. If that reference doesn't match cleanly — because of a formatting difference, a delay in how the original booking was stored, or the cancellation arriving in an unusual sequence relative to other updates on the same reservation — your channel manager can fail to apply it even though the message itself was sent and received by the connection. Some cancellations are also processed differently depending on whether the guest cancelled directly, the property cancelled on the guest's behalf, or the OTA cancelled it for a policy reason, and not every one of those paths is necessarily handled the same way by every connectivity setup.
Open the reservation directly in the OTA's extranet and read its exact current status, cancellation date and any stated reason — that is the authoritative version of what happened. Then check your channel manager's activity or modification log, if it keeps one, for that reservation ID, to see whether the cancellation message was received at all or received and failed to apply; those point to different fixes. Only once you've confirmed the extranet genuinely shows it cancelled should you treat the PMS record as stale rather than correct.
Read-back verification applies to cancellations as much as new bookings or modifications — once a cancellation is processed, the resulting reservation status is read back from the channel and compared against what the extranet actually shows, instead of assuming the message applied because it was sent. Activity history also keeps a record of exactly which cancellation path triggered the change and when, across 39 action types kept for 400 days, so a stale reservation is easy to trace rather than a mystery. If a stuck cancellation has blocked a room before, that combination is the structural fix — the public demo at try.primehostpartners.com is open to try without signing up.