Restoring a reservation that was canceled by mistake takes more than reopening the booking — inventory, the original rate and every connected channel all need to agree again.
A reservation gets canceled by mistake — the wrong booking, a miscommunication with the guest, a staff error — and restoring it isn't as simple as reopening the record in your PMS. The room's inventory, the original rate, and every channel that was notified of the cancellation all need to be put back in agreement, or the restored booking can end up wrong in ways that surface later.
Canceling a reservation in your PMS typically does three things at once: it releases the room back into available inventory, it may trigger a cancellation notification out to whichever OTA the booking came from, and depending on your setup, it can affect how commission or payment for that booking is recorded. Restoring the reservation has to undo all three, not just reopen the record and leave the rest as it was.
If the room has already been resold to someone else in the time between the cancellation and the attempt to restore, there's no clean restoration possible — that case has to be handled as a genuine conflict, not a simple undo.
The inventory that was released by the cancellation may already have moved — sold directly, sold through another channel, or adjusted by a stop-sell applied afterward — so restoring the reservation without checking first risks creating a double booking rather than fixing a mistake. The rate the reservation originally had may also no longer be the current rate for those dates, particularly if pricing has moved since the cancellation, so restoring at “whatever the rate shows now” can quietly change what the guest is actually charged. And if a cancellation notification already went out to the OTA the booking came from, simply reopening the PMS record without telling the channel can leave the OTA's own system still believing the booking is canceled.
First confirm the room is still actually available for those dates — check your PMS calendar and, if the booking came from a channel, that channel's own extranet too, since either side could have sold into the gap. Decide and document which rate applies to the restored booking, rather than letting whichever number happens to populate become the final answer by default. If the cancellation was communicated to the originating channel, follow up through that channel's own process for reinstating a reservation rather than only fixing it on your side.
At the database level, reservations are protected by a physical no-double-booking guarantee, so restoring a canceled reservation into a room that's already been resold is caught by construction rather than discovered after the fact. The calendar's drag-to-move and date-shift tools also make it straightforward to move a restored booking to another available room if the original is genuinely gone, instead of forcing a conflict. Activity history keeps a record of the original cancellation and the restoration together, which helps if the sequence of events ever needs to be reviewed. You can try all of this on the public demo at try.primehostpartners.com without signing up.