Booking.com Closed Room Still Bookable: Why It Happens and How to Fix It
If a room type you closed on Booking.com is still taking reservations, here is why that happens at the system level and the exact checks that confirm whether it is actually closed.
The Prime Host Partners team11 Nov 2026 · 7 min read
Closing a room type in your extranet or channel manager and then watching a new booking come in for it anyway is one of the more alarming things that can happen to a property. This article explains the mechanics behind it and gives you a short, repeatable way to confirm a room is truly closed everywhere it needs to be.
You close a room type, either directly on Booking.com's extranet or through your channel manager, expecting no further reservations for it. Hours or days later, a new reservation comes in for that same room type, as if the closure was never applied at all.
This is unsettling because it looks like the system simply ignored an instruction, but in almost every case the closure did apply somewhere, just not everywhere it needed to, or it applied and was then reopened by something else without anyone noticing.
Why a closed room can still take bookings
Stop-sell, allotment, and the room mapping between your channel manager and Booking.com are three separate settings that all have to agree for a closure to hold. Closing a room in your channel manager sends an update to Booking.com, but that update has to be written, confirmed, and reflected correctly against the right mapped room and rate plan on Booking.com's side.
A second cause is a different system reopening the room after you closed it, for example an auto-replenishment rule, a different user on your team, or a connected system that still has allotment for that room type without the same closure applied. The room looks open to Booking.com because, from its perspective, it genuinely is.
How to check it step by step
Confirm the state of the closure at each layer rather than only checking the one place you expect it to show correctly.
Check each layer in order
1The channel manager or extranet settingConfirm the closure or stop-sell is currently showing as applied, not just that you set it at some point.
2The Booking.com extranet calendar for that roomView the room directly in the Booking.com extranet to see what Booking.com itself believes the current state is.
3Recent activity on that room typeCheck whether anything, a rule or a person, touched allotment or stop-sell for that room after your closure was set.
A closure that was sent is not the same as a closure that was received, confirmed, and still holding.
Fixing and preventing it
Re-apply the closure directly and check the Booking.com extranet calendar for that room afterward to confirm it is reflected there, not just in your channel manager.
Check whether any automated rule, such as an auto-replenishment setting, could have reopened the room after your closure.
If more than one person manages the property's inventory, confirm no one else adjusted that room type after the closure was set.
Verify the room and rate plan mapping between your channel manager and Booking.com is pointing at the room you think it is.
After confirming the fix, watch that room type for a short period to make sure the closure holds rather than reopening again on its own.
How Prime Host stops this from happening again
Read-back verification means every stop-sell and availability update sent to a channel is read back from that channel and compared, field by field, rather than treated as successful just because the request was accepted. If a closure doesn't hold, that shows up as a failure naming the channel and the room, not as a mystery booking days later.
This behavior is visible on the public demo at try.primehostpartners.com, including on a sample resort and a larger sample hotel, without needing to sign up.
Frequently asked
Does closing a room in my channel manager always close it on Booking.com immediately?
It sends the update immediately, but the closure is only confirmed once Booking.com's own system reflects it, which is why checking the Booking.com extranet directly matters.
Can an automated rule reopen a room I closed manually?
Yes, settings such as auto-replenishment after a cancellation can reopen allotment on a room type independently of a manual closure, which is a common cause of this exact symptom.
How do I confirm a closure is actually holding, not just that I set it?
Check the room directly in the Booking.com extranet calendar after setting the closure, and check again after a short period to confirm nothing reopened it.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.