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