Blog›Connectivity

How to Disconnect an OTA Channel from Your PMS Safely

Disconnecting a channel from your PMS or channel manager sounds simple, but doing it in the wrong order can leave open bookings or stuck inventory behind.

The Prime Host Partners team15 Nov 2026 · 7 min read

Whether you're dropping a channel you no longer use, swapping connectivity providers, or temporarily pausing a listing, disconnecting it from your PMS is not just flipping one switch. There's an order that avoids leaving reservations orphaned or inventory stuck half-closed, and it's worth following even when the disconnection feels routine.

Full guide on this topic
Why disconnecting isn't a single action

A channel connection touches several things at once: a live mapping between your room types and the channel's listings, a flow of reservations still arriving, and often inventory and rates that are actively being pushed out on a schedule. Switching off the connection stops the flow, but it doesn't automatically resolve what was in progress at that moment — a reservation partway through processing, or a rate update that was queued but not yet confirmed.

The risk isn't usually the disconnection itself. It's what's left unresolved on either side once the two systems stop talking, which can sit unnoticed for weeks if nobody checked before pulling the plug.

What to close out before disconnecting

Existing reservations on that channel need somewhere to live after disconnection — your PMS should keep them as valid bookings for guests already arriving, even once new reservations stop coming in. If the channel still shows open availability on its own extranet, closing it there first (rather than relying on the disconnection to do it) avoids a guest booking a room through a channel that's no longer actually connected to anything. Any pending rate or inventory push that hasn't been confirmed as delivered should be allowed to finish or be verified before you cut the link.

Before you disconnect
1Confirm no reservations are mid-processCheck your channel manager's queue or activity log for anything still being written to or read from that channel.
2Close the listing on the channel's own extranetSet it to sold out or inactive there directly, rather than relying on the disconnection to stop new bookings.
3Keep existing reservations visible in your PMSGuests with confirmed bookings on that channel still need to show up on your calendar after the connection is gone.
How to disconnect without losing anything

Start from the channel's own extranet and close the property or listing there, so it stops accepting new bookings independently of what your channel manager does next. Then, in your channel manager's settings, remove or pause the mapping for that channel, and check whether it offers a clean way to archive the connection rather than simply deleting it, in case you need the mapping history later. Finally, confirm in your PMS that reservations already on the books for that channel are still intact and correctly attributed, not silently dropped along with the connection.

A disconnected channel should leave a clean edge behind — not a loose thread someone finds three weeks later.
After disconnecting
Close the listing directly on the channel's own extranet before removing the connection in your channel manager.
Check for any reservation, rate push or inventory update still in progress and let it resolve first.
Confirm existing reservations from that channel remain visible and correct in your PMS after disconnection.
Archive rather than delete the mapping if your channel manager supports it, in case you reconnect later.
Recheck availability on every other connected channel afterward, in case inventory logic was shared across channels.
How Prime Host stops this from happening again

Activity history keeps a record of what changed and when, including connection and mapping changes, so if a reservation or inventory setting looks wrong after a disconnection, you can see exactly what happened rather than reconstructing it from memory. Read-back verification also applies here — if availability is closed on a channel as part of a planned disconnection, the system confirms that the closure actually landed rather than assuming it did. You can see the activity log yourself on the public demo at try.primehostpartners.com, no sign-up required.

Frequently asked
Will disconnecting a channel cancel existing reservations?
No, it shouldn't — reservations already confirmed on that channel should remain valid bookings in your PMS. Disconnection stops new activity, not existing guest bookings.
Should I close the listing on the channel first or disconnect in my PMS first?
Close it on the channel's own extranet first. That stops new bookings independently, so nothing new arrives while you're still unwinding the connection on your side.
What if I need to reconnect the channel later?
If your channel manager can archive rather than delete the mapping, reconnecting later is usually faster and avoids rebuilding room and rate mappings from scratch.
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