Blog›Connectivity

Stop-Sell Not Syncing to the OTA: Diagnosis and Fix

You closed a room type for sale, but the OTA is still accepting bookings for it, and this walks through why a stop-sell can fail to sync and the steps to actually fix it.

The Prime Host Partners team16 Nov 2026 · 7 min read

You apply a stop-sell for a room type — maintenance, an internal block, a date you want closed — and your channel manager shows it as applied, but a booking still comes through from the OTA for a date that should be closed. A stop-sell that doesn't actually sync is one of the few extranet problems that can turn into a real overbooking, so it's worth diagnosing properly rather than just reapplying it and hoping.

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

Your channel manager's own interface shows the room type as closed — no error, no warning. The OTA's extranet, checked separately, still shows it open, or a booking simply arrives for a date you believed was blocked. Because the failure is invisible on the sending side, most properties only discover it once a booking has already landed, which is the worst time to find out.

This is distinct from a stop-sell that was never applied in the first place — that's a process error. A stop-sell that was applied correctly in your system but didn't reach the OTA is a sync failure, and the fix is different.

Why a stop-sell can fail to reach the channel

Most connectivity setups send a stop-sell as a message to the channel the same way a rate or availability change is sent, and that message can fail to deliver, be delayed, or arrive and be rejected without a visible error on your side — each of those looks identical from your interface, which just shows the stop-sell as applied internally. A second cause is scope: a stop-sell applied at the wrong level — a specific rate plan rather than the whole room type, or vice versa — can sync successfully but simply not cover the booking that then comes through, which looks like a sync failure but is actually a scope mismatch. A third is sequencing: if a booking request and a stop-sell are processed close together, the order they're applied in can determine whether the stop-sell closes the room before or after that booking already went through.

The three usual causes, in the order to check them
1Message never delivered or was rejectedThe stop-sell applied in your system, but the update to the channel failed silently.
2Wrong scopeApplied to a rate plan instead of the room type, or vice versa — it synced, but doesn't cover the booking that got through.
3Timing collisionA booking and a stop-sell processed close together in time, with the stop-sell landing just after the booking rather than before it.
How to find out which one happened

Open the OTA's own extranet directly and check the actual current status of the room type and rate plan for the specific dates in question — this is the only way to know whether the stop-sell truly didn't sync, versus synced to the wrong scope. Check your channel manager's activity or change log for that stop-sell to see the exact scope it was applied to and the timestamp, and compare that timestamp against the booking's own timestamp if one came through. If the extranet shows the room correctly closed now but a booking still arrived earlier, that points to a timing collision rather than a sync failure.

A stop-sell that silently failed looks exactly like one that worked — right up until a booking proves otherwise.
Fixing it and reducing the risk of a repeat
Check the OTA extranet directly for the room type and dates in question — don't trust your channel manager's internal status alone.
If a booking already came through for a date that should've been closed, treat it as a real reservation to honor or resolve, not just an inventory fix.
Check the scope of the original stop-sell — room type versus a specific rate plan — and confirm it actually covers what you intended.
Reapply the stop-sell and verify directly on the OTA's side that it's now showing closed, rather than trusting the confirmation alone.
If this room type or rate plan has had sync issues before, check whether it's mapped correctly across all the rate plans tied to it.
How Prime Host stops this from happening again

This is exactly the case read-back verification is built for: every stop-sell is read back from the channel after it's sent and compared against what was intended, so a message that failed to deliver or was applied to the wrong scope shows up as a mismatch immediately rather than looking identical to a success. Combined with a physical no-double-booking guarantee at the database level, a stop-sell failure that does slip through still can't result in two overlapping reservations for the same room — it's prevented by construction, not by a check that could itself be skipped. You can see both on the public demo at try.primehostpartners.com without signing up.

Frequently asked
Why would a stop-sell show as applied but not actually work?
Most often the message to the channel failed to deliver or was applied to the wrong scope — a rate plan instead of the whole room type, for instance — which looks identical to success from your own interface.
Is a failed stop-sell sync the same thing as an overbooking?
Not automatically — it only becomes an overbooking if a guest actually books the room during the window it should have been closed. Until then, it's a sync failure worth fixing before it becomes one.
How quickly should I check a stop-sell after applying it?
As soon as practical, by checking the OTA extranet directly rather than only your channel manager's internal confirmation — that's the only way to catch a silent failure before a booking does.
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