A guest cancels on Expedia, and understanding what that cancellation actually changes — for your inventory, your payout and your records — matters more than the refund amount alone.
A cancellation notice on Expedia looks like a single event, but it's really three things happening at once: a refund calculation, an inventory change, and possibly a commission adjustment. Understanding each one separately is what lets you confirm a cancellation went through cleanly instead of just trusting the status label.
At the front desk, a cancellation usually shows up as a reservation whose status changed, either because the guest cancelled through Expedia or contacted you directly. What matters beyond the status label is what happens behind it — whether the room reopens for sale, what the guest is actually refunded, and whether commission is still owed on a booking that no longer exists.
The distinction between a free-cancellation booking and a non-refundable rate matters for the guest's refund amount, but it shouldn't change whether the room itself reopens in your available inventory — that should happen either way once the cancellation is processed.
The cancellation policy that applies to a given reservation is set at the rate-plan level, not as a single blanket rule for your whole property, and Expedia applies that specific policy automatically once the guest cancels. That means the refund amount is a function of which rate plan the booking was made under, not something you calculate or decide at the moment of cancellation.
Open the reservation directly in Partner Central and read its current status and the cancellation policy it was actually booked under, rather than assuming based on your general rates. Compare that against what your PMS shows for the same reservation, and if the room hasn't visibly returned to available inventory, treat that as the thing to fix first.
Read-back verification applies to a cancellation the same way it applies to a stop-sell or a rate change — when a cancellation should reopen a room, the system reads back what the channel actually shows afterward instead of assuming the reopening worked just because the cancellation message didn't error. Activity history then keeps a record of exactly when the cancellation landed and what changed, so a dispute weeks later doesn't depend on memory.
If a cancelled room has ever sat closed when it should have reopened, that gap is the structural problem this closes — you can see it on the public demo at try.primehostpartners.com without signing up.