The actual sequence for cancelling a reservation made through your own booking engine — inventory, refund and guest notice — rather than just deleting the record.
Cancelling a reservation made through your own direct booking engine involves a few more steps than deleting a row from a calendar — the room needs to go back to inventory correctly, any payment needs to be handled according to the rate's actual policy, and the guest needs a clear notice of what happened. This walks through the sequence in order.
A direct booking engine reservation, unlike one coming from an OTA, is entirely within systems you control, which makes it easy to assume cancelling it is just a matter of removing the record. But the room still needs to be released back to available inventory correctly rather than just disappearing from the list, any payment already collected needs to be handled according to the rate's actual cancellation policy rather than refunded by default, and the guest needs a clear, documented notice of the cancellation rather than silence.
Skipping any of these three steps tends to surface later — either as a room that looks unavailable when it isn't, a payment dispute because the guest never received confirmation, or a refund given on a non-refundable rate without anyone noticing.
First, check the rate plan the reservation was made on and what its actual cancellation policy allows, since a non-refundable or restricted rate may not entitle the guest to a refund even if they're asking for the cancellation. Second, process the cancellation in your booking engine or PMS so the room is released back to inventory, and confirm it shows as available again rather than assuming the release happened automatically. Third, handle the payment according to the policy — a full or partial refund if the policy allows it, or a clear explanation to the guest if it doesn't — and send the guest a written notice confirming the cancellation and whatever was agreed about payment.
If the room doesn't show as available again after cancelling, check whether the cancellation actually completed in your booking engine rather than just being marked pending, and look for a connected block or hold that wasn't cleared along with the reservation itself. If a guest disputes a refund decision, go back to the exact rate plan's policy text as it existed at the time of booking, not the current version if it's since changed, since that's what the guest actually agreed to.
The calendar's cancellation and date-shift tools release inventory as part of processing the change itself, rather than leaving a separate step to remember, and activity history keeps a record of who cancelled what and when, across 39 action types kept for 400 days, so a disputed cancellation has a clear paper trail to point to. You can try the calendar tools on the public demo at try.primehostpartners.com without signing up.