What actually happens when a guest or property requests a cancellation fee waiver on Booking.com, who is involved in the decision, and how to track the request properly.
When a guest asks to be let out of a non-refundable booking without the usual fee, the waiver request on Booking.com follows a specific workflow with more than one possible outcome. This article explains how that process works and how to keep track of it so a pending request doesn't quietly fall through.
A guest with a non-refundable or otherwise restrictive booking contacts either the property or Booking.com directly, asking to cancel without being charged the fee the rate plan would normally apply. This can happen for reasons ranging from a genuine emergency to simply a change of plans.
The property's role in this request varies by situation. In some cases the decision sits with the property, since it is the property's cancellation policy being waived. In others, particularly where Booking.com's own terms or a specific circumstance applies, Booking.com can be involved in the decision as well.
A waiver request generally needs to be raised and tracked as a distinct action, separate from simply cancelling the reservation, because cancelling without processing the waiver correctly can leave the fee charged anyway, or leave the booking in an inconsistent state relative to your records.
Because the property's cancellation policy is what's being set aside, the property typically needs to actively agree to the waiver, or respond to a request raised through Booking.com's support channel, rather than the waiver happening automatically just because a guest asked.
Treat each waiver request as a short process with a few concrete steps, rather than a single yes-or-no reply sent from memory of the guest's situation.
Bank-level reconciliation matches payout batches against your bookings and computes expected payment timing, so when a waiver changes what should be charged or paid out for a reservation, that change is reflected in reconciliation rather than left to be noticed, or missed, in a payout report weeks later.
Activity history also keeps a record of decisions made on a reservation, which helps when a waiver request needs to be referenced again later. You can see both features on the public demo at try.primehostpartners.com, open without signing up.