Blog›Connectivity

Expedia Closed Room Still Selling: A Sync Failure Explained

A room type you closed is still taking bookings on Expedia, and this explains the sync mechanism that can cause a stop-sell to fail silently and how to confirm and fix it.

The Prime Host Partners team13 Nov 2026 · 7 min read

You close a room type for specific dates — for maintenance, an allotment adjustment, or simply because it's genuinely sold out elsewhere — and a new reservation for those same dates still arrives from Expedia. When a stop-sell doesn't actually stop sales, the room is still open somewhere in the chain even though your PMS believes it's closed, and the fix starts with finding exactly where that disagreement sits.

Full guide on this topic
What a failed stop-sell on Expedia looks like

Your PMS or channel manager shows the room type as closed for the relevant dates, and from your side, that should mean no further sales. Then a reservation for those exact dates comes through from Expedia, confirmed and often already paid or guaranteed, as if the closure was never applied on Expedia's end at all. The room itself may genuinely not be available, which turns this into an overbooking rather than just an inventory discrepancy to tidy up.

This is specifically a sync failure, not a timing issue — unlike availability catching up after a short delay, a stop-sell that failed to push tends to stay wrong until someone notices and corrects it manually.

Why a stop-sell can fail to reach Expedia

A stop-sell is an update message like any other rate or availability change, and it can fail the same ways others do — a delivery failure that isn't retried, a mapping issue on the specific room type or rate plan being closed, or a connection that's degraded without producing an obvious error on your side. It's also possible for a stop-sell to apply correctly to one rate plan under a room type while another rate plan for the same physical room stays open, if the closure was sent to only one of them rather than all rate plans sharing that inventory.

Where a stop-sell typically fails silently
1Delivery failure with no retryThe update message to close the room didn't reach Expedia, and nothing on your side flagged it as unsent.
2One rate plan closed, another left openIf a room type has multiple rate plans sharing the same inventory, a stop-sell sent to only one of them leaves the room sellable through the others.
3Mapping drift on that specific room typeA room type's mapping has degraded since it was first connected, so updates for it specifically are less reliable than for the rest of the property.
How to confirm the stop-sell actually failed

Open Expedia Partner Central directly and check the room type's current availability status for the exact dates you closed — this is the only way to know what Expedia actually has stored, rather than trusting your own PMS's assumption that the push succeeded. If your channel manager keeps an update or error log, check whether the stop-sell message shows as sent and confirmed, or sent without confirmation, or not sent at all — each points to a different next step. If the room type has multiple rate plans, check every one of them individually rather than assuming a stop-sell on one plan closed the whole room type.

A stop-sell that silently fails is worse than one that visibly errors, because nothing about your own dashboard tells you the room is still for sale somewhere else.
Fixing it now and reducing the risk going forward
Check Expedia Partner Central directly for the room type's actual availability status on the affected dates.
If a reservation came through for a closed room, treat it immediately as a real overbooking to resolve with the guest.
Check every rate plan under the room type individually — a stop-sell on one doesn't guarantee the others are closed too.
Resend the stop-sell and confirm in Partner Central that it actually applied this time, rather than trusting the first attempt.
If this room type fails more often than others, check its mapping for drift since it was first connected.
How Prime Host stops this from happening again

Read-back verification exists specifically for this failure mode — every stop-sell and availability change is read back from the channel after it's sent and compared against what was intended, so a failed push is flagged as failed instead of looking successful because the request didn't error. The database itself also enforces a physical no-double-booking guarantee, meaning the system cannot record two overlapping bookings for the same room by construction, which matters as a last line of defense if a stop-sell issue slips through before it's caught. You can see both in the public demo at try.primehostpartners.com without signing up.

Frequently asked
Can a room really still sell on Expedia after I close it in my PMS?
Yes, if the stop-sell message failed to reach Expedia or wasn't applied to every rate plan sharing that room's inventory. Your PMS showing it closed doesn't guarantee Expedia's side matches.
How do I know if the problem is one rate plan or the whole room type?
Check every rate plan under that room type individually in Partner Central. A stop-sell sent to only one rate plan can leave the room sellable through others attached to the same inventory.
What should I do first if a closed room still gets booked?
Treat it as a real overbooking immediately — contact the guest and Expedia support with the reservation details — before investigating why the stop-sell failed to sync.
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