Removing a Channel Without Leaving Stale Rates Behind
Channel Management

Removing a Channel Without Leaving Stale Rates Behind

Localsbnb Editorial TeamOctober 1, 20268 min read

Disconnecting a channel stops the feed, but it doesn't tidy your own calendar. Stale rates, unreleased blocks and a live listing stay behind. This checklist walks through the four leftovers to clear before you switch a channel off, and the two-week check that catches what you missed.

Screenshot of the LOCALSBNB channel detail screen with a 'Before you disconnect' headline overlay
A channel detail screen is where you check the rates and blocks you set before removing the connection.

Disconnecting takes one action. The leftovers are the problem: rates, blocks, and a listing that stays live for a while after you think it is gone.

Last updated: October 2, 2026

Disconnecting a channel takes one action and closes a door. It doesn't clear the room behind it. Rates you set for that channel stay on your calendar, blocks stay in place, and the listing can keep taking bookings on the platform side after you think it's gone. The cleanup is the real job.

Key Takeaways

  • Disconnecting stops the feed; it doesn't tidy your own calendar. Scheduled rates and blocks stay exactly where you put them.
  • Four leftovers cause almost all the mess. Stale rates, unreleased blocks, a listing still live, and a date feed nobody switched off.
  • The platform side is a separate switch. Removing the connection doesn't remove the listing, and closing the listing doesn't remove your rates.
  • Delisting takes time, and nothing honest claims otherwise. Give the channel room to process, then go and verify.
  • Check twice: once within days, once at the two-week mark. The second look catches what the first one missed.

What disconnecting does not do

It's worth being clear about the boundary, because most of the frustration in this task comes from expecting a disconnect to be a cleanup. It isn't. A disconnect ends the exchange between two systems. It doesn't reach back into either one and undo what you set.

So the rates you scheduled for that channel before you decided to leave stay on your calendar. If Friday was set to a weekend rate through the end of the year, Friday still carries that weekend rate after the channel is gone. Nothing recalculates it, because nothing knows it should.

The same goes for blocked dates. Any block you added to protect a night for that channel remains a block. Your calendar stays honest about the fact that the night is unavailable; it just no longer has a channel interested in the answer.

And the listing itself keeps living on the platform side until you deal with it there. That's the part that surprises people most. A guest can still find the listing, see the photos, and try to book a night, even though your side has stopped talking to the channel.

None of this is a design flaw. It's what you get when two independent systems stop listening to each other: each one keeps whatever it last knew. The work is to bring both sides to a clean resting state, in an order that doesn't open a night you meant to sell.

It helps to think about who holds which record. Your calendar holds rates and blocks. The platform holds the listing page and any dates you left open there. A direct connection or a date feed is only the wire between them. Cut the wire and both records remain, sitting on either side of the gap.

The four leftovers to clear before you switch it off

There are four things sitting on your side when a channel is about to go. Clear them in this order, because a couple of them depend on the others being settled first.

Scheduled rates. Look at every future rate you set specifically for this channel. Take them off, or reset them to your standard rate, before the disconnect. Leave them and they'll sit there for months, quietly shaping how you read your own pricing.

Blocked dates. Any block placed to hold a night for this channel needs to be released if you intend to sell it elsewhere. This is where a disconnect can cost you money, because a block nobody lifts looks like a sold night on your calendar.

The mapping between the listing and the channel. Your listing is tied to a specific unit on a specific channel. Once the channel goes, that tie is a loose end. Note the pairing down before you remove the connection, so you can match records later if a booking arrives late.

Any date feed still pointing at the channel. A one-way date feed left running will keep pushing busy and free dates for a listing you no longer maintain. Feed it nothing and it will keep the last picture it received, which is rarely what you want.

Work through the four in that order and you'll notice they share a shape. Each one is a record you created for the channel, and none of them disappears when the channel does. The order matters because the rate and the block both live in your calendar, while the mapping and the feed are the links that would keep feeding the channel after you'd rather it stopped.

Card: the four leftovers to clear before disconnecting a channel
Scheduled rates, blocked dates, the listing mapping and a live date feed all survive the disconnect until you clear them.
Card: the order in which to clear channel leftovers and close the platform side
Clear your own calendar first, disconnect, close the platform side, then verify at two points in time.

Closing the listing on the platform side

Your side of the disconnect and the platform's side are two different switches. Flipping yours doesn't flip theirs. Closing the listing is a job you do on the platform, and it deserves the same care as the rest of the checklist.

Start with any dates still open on the platform. If the listing shows availability for next month, a guest can book next month, and that booking will arrive after your side has gone quiet. Close the availability first, then close the listing.

Then handle the listing's status on the platform. Taking it offline and deleting it are usually different actions, and the gentler one is often the better fit if the channel might return later. Keep the photos and the description intact if there's any chance you'll want them again.

Expect a delay. Delisting isn't instant, and treating it as instant is how a listing ends up taking one more booking after you've told yourself you're finished with the channel. Give it room, then go back and check.

Record what you did and when. A short note with the date you closed the listing and the date you disconnected is enough. If a booking turns up days later, that note tells you whether it came through a path you've already closed.

One more thing belongs on the platform side: any automatic setting that could reopen the listing. A seasonal rule, a saved draft, or a scheduled change can quietly put availability back. Clear those too, or the listing may return on its own after you've moved on.

A two-week check after it goes quiet

The last step isn't the disconnect. It's the check, and it needs to happen twice. The first pass catches what you got wrong; the second catches what the channel got wrong on its way out.

Within a few days, look at your calendar for the channel's former dates. Any rate still carrying the channel's shape should be reset, and any block you meant to lift should be gone. Fix what's left while it's fresh and the cause is still obvious.

Then come back at the two-week mark. By now the channel has had time to process the change, and anything still live is a real loose end rather than a slow one. Check the listing on the platform side, the dates, and the rate you'd quote if somebody asked today.

Both passes are quick on a single channel, but the second one is the one that saves the surprise. A rate that was still cached somewhere, or a listing page still resolving, will surface at two weeks rather than on day one.

Keep the record from the first pass and update it on the second. That note becomes the template the next time you wind a channel down. The same calendar also shows each connected channel's source rate and source status, so you can confirm nothing stale is left on localsbnb.com.

LOCALSBNB — start free

FAQ

Does removing a channel delete the rates I set on it?

No. Removing the connection ends the exchange; the rates stay on your calendar until you change them. Go through the future rates you set for that channel and reset them before you disconnect.

How long before a listing comes down on the platform side?

It varies by platform, and it isn't instant. The practical answer is to close the dates first, request the status change, then verify rather than assume.

What should I check if a booking arrives after disconnecting?

Check whether that booking came through a path you've already closed. If the listing was still live, a guest could book it, and the right move is to treat it as a genuine booking and settle it with the guest directly.

Finished with the channel, but keep the file. The dated note you wrote becomes a template for next time, and the second pass is what keeps a stale rate from surprising you later. When you want every connected channel's source rate in one view while you wind things down, start at localsbnb.com.


This is general guidance for hosts, not legal, tax or insurance advice. How a channel handles a delisting request, and how long it takes, is set by that platform's current terms; check the current terms of each platform you use.

Reviewed by

Localsbnb Editorial Team