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.
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.
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.
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.
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.
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.