Blog›Connectivity

Booking.com Auto-Replenishment After a Cancellation on a Closed Room

When a guest cancels on a room type you had closed, Booking.com can reopen that room automatically. Here is why it happens and how to stop it reselling a room you meant to keep off the market.

The Prime Host Partners team11 Nov 2026 · 7 min read

A cancellation on a room type you had deliberately closed can quietly reopen that room for sale again, because allotment and stop-sell are not always the same lever behind the scenes. This article explains the mechanism and walks through how to check and correct it before the room gets rebooked.

Full guide on this topic
The pattern that catches properties out

You close a room type deliberately, for maintenance, a long-stay guest, or simply to hold it off the market, and the closure holds for a while. Then a different reservation on that room type gets cancelled, and shortly afterward the room becomes bookable again, even though you never reopened it yourself.

From the outside this looks like the system undid your decision for no reason. In practice, it is usually a specific behavior around how allotment is restored after a cancellation, interacting with a closure that was applied on top of the allotment rather than replacing it.

Why cancellations can reopen a closed room

Allotment is the number of rooms available to sell for a given room type and date, and stop-sell is a separate instruction that blocks sale regardless of allotment. Some setups restore allotment automatically when a booking against that allotment is cancelled, on the logic that the room is now free again, without checking whether a stop-sell or manual closure was also meant to apply to it.

If your closure was applied as a reduction in allotment rather than as an explicit stop-sell, a cancellation can effectively hand that allotment back, and depending on your settings that can be enough to make the room bookable again even though your underlying intention, to keep it closed, never changed.

How to check what happened

Look at the specific cancellation and the room's current state together, rather than only the room's current state in isolation.

What to look at
1How the original closure was appliedCheck whether it was a stop-sell, an allotment reduction, or both, since each behaves differently after a cancellation.
2The timing of the cancellation versus the room reopeningConfirm the reopening happened at or just after the cancellation, not from an unrelated change.
3Current stop-sell status on the roomCheck whether stop-sell is currently active, separate from whatever the allotment number shows.
Fixing and preventing it
Re-apply the closure as an explicit stop-sell on the room and dates in question, not only as a reduced allotment number.
Check whether your channel manager or extranet has a setting controlling whether cancellations automatically restore allotment, and review whether that default fits how you manage inventory.
After the fix, cancel a test booking if you can safely do so, or wait for the next real cancellation, and confirm the room stays closed.
Document which rooms are closed for reasons other than being sold out, so the distinction is clear to anyone else managing the property.
Review closed rooms periodically rather than only when a guest or team member notices one is open again.
How Prime Host stops this from happening again

Read-back verification applies to stop-sell the same way it applies to rates and availability: the actual state on the channel is read back and compared against what you intended, so a room that reopens unexpectedly after a cancellation is reported as a change to investigate rather than discovered through a new booking.

Activity history records who or what changed availability on a room, across a long list of action types, which makes it straightforward to confirm whether a cancellation, a person, or an automated rule reopened it. You can explore both on the public demo at try.primehostpartners.com.

Frequently asked
Is it normal for a cancellation to restore allotment automatically?
Yes, this is common behavior, which is why a closure meant to be permanent should be applied as an explicit stop-sell rather than relying only on a reduced allotment number.
How do I tell whether a room is closed by stop-sell or just has zero allotment?
Check both settings separately in your extranet or channel manager, since a room can show zero allotment while stop-sell is off, or vice versa, and each behaves differently after a cancellation.
Can this same pattern happen on other OTAs, not just Booking.com?
The underlying mechanism, allotment separate from stop-sell, is common across OTA extranets, so the same check is worth applying wherever a closed room has reopened unexpectedly.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service