When Two Channels Disagree on Availability

Two channels show two different calendars for the same nights. One of them is wrong, and guessing which one is how double bookings happen.

Last updated: October 14, 2026

A guest asks about a weekend, you open two tabs, and the two channels don't agree. One shows the nights open; the other shows them sold. Your first instinct is to compare the two pages and trust whichever looks newer. That instinct is what turns a small gap into two guests holding one door code.

Key Takeaways

• Trust the booking, not the calendar. A confirmed booking is a fact. An open night is only a claim, and claims are the part that drifts.
• Block first, diagnose second. Close the disputed nights everywhere they're still open, then work out what caused the gap.
• Read the last sync, not the last edit. A change you made two minutes ago tells you nothing about what the other side has received.
• Most gaps come from three places. A change made off-origin, a mapping that points twice, or a link that went quiet without telling you.
• Reopen one night at a time. Releasing a whole month at once is how you find out you fixed nothing.

Which side to trust first

Start by separating two things that look like the same thing. A booking is a commitment a guest is holding. An open night is a claim by a calendar. When those two conflict, the booking wins, and it wins no matter which channel it came from.

That gives you a first move that doesn't require you to know which side is broken. If a guest holds a confirmation for a night that somewhere else still shows as open, that night is sold. Close it in the other place before you do anything else.

Between two calendars, the one worth trusting is the one you edit. Pick the place you make changes in — your own calendar rather than a channel page — and treat that as the source. It isn't more accurate because it's cleverer. It's more accurate because you know what you did to it and when.

The screen that looks freshest deserves the least trust here. A page can show a change that was made and never sent, which makes it look current while being wrong. Appearance and reality come apart precisely when the link is the thing that's broken.

So the order is short. Find every booking first. Then name the source you edit. Then treat everything that disagrees with those two as a copy with a problem.

Reading the last sync instead of the last edit

Two timestamps exist for every night in this story, and only one of them answers the question you care about. One says when the calendar was last edited. The other says when the connection last completed a successful exchange.

The first one is about you. It tells you when you sat down and changed something. The second one is about the link, and it tells you what the other side actually knows.

Those two can sit hours or days apart, and the gap between them is where double bookings live. You edited at nine and the screen still looks fine, because the edit is real. It just hasn't travelled yet, and nothing on screen tells you that.

There's a third number that fools people, and it isn't a sync time either. The time printed on a channel page tells you when that page last changed. That's a different question from whether the channel is still hearing from you.

Read both sides of the link before you judge either. Your own calendar shows each connected channel's source rate and source status, so you can see which channels are still reporting and what they're reporting from. That's the reading that separates a stale copy from a channel that vanished.

A small habit makes this quick. Whenever you change a night, note the time. Then check when each side reflects it. The pair of times narrows a disagreement from "somewhere last week" to a window of minutes, and it's the difference between guessing and knowing.

The three causes behind most gaps

Most disagreements you'll meet come from one of three places, and they look nothing alike once you know what to look for.

The change that never travelled. You blocked a night on a channel's own page instead of at the source. The change is real, it's saved, and it exists on exactly one side of the connection. It will survive there until something else overwrites it, which is the worst possible moment.

The mapping that points twice. Two units of yours are matched to one record, or one unit is matched to two. Now the calendars disagree because they aren't describing the same door. This one is nastier than the first, because both sides look consistent with themselves and the problem only appears when you compare across.

The link that went quiet. A connection can stop exchanging information without announcing it. Nothing arrives, nothing errors loudly, and the channel keeps showing whatever it last received. You find out when a guest books a night that was sold days ago.

Each cause has a different first check, and refreshing a page helps with none of them. For the first, ask where the change was made. For the second, read the mapping on both sides and count the doors. For the third, look at when each channel last reported at all.

You don't need to name the cause before you act, though. You need it before you reopen anything, because reopening while the cause is still live puts you straight back where you started.

Closing the gap without overselling

The order is block, fix, reopen, and it's worth keeping even when it feels slow. Blocking is cheap and reversible. Two guests at one door is neither.

Block every disputed night wherever it's still showing open. Do it on the channel side as well as at your source, because you don't yet know which side the gap came from. Yes, you may give up a bookable night. That's the price of not handing out a key to a unit someone else is sleeping in.

Then fix the cause. Correct the mapping if two doors are sharing one record. Make the change at your source if the edit went somewhere else. Get the channel reporting again if the link went quiet. Four channels can be connected at once — Airbnb, Booking.com, Agoda and Trip.com — so check the one you suspect before you decide it's the culprit.

Then reopen, one night at a time. Pick a date far enough out that nobody will book it while you're looking, open it, and confirm it moved. Then check the other side. Doing a whole month at once hides which change worked and which didn't.

Read-only questions are useful here, in the narrow sense that they don't change anything. Asking what's arriving today, who's in house and which nights are open gives you the state of your own records, not a repair. It tells you where you stand. It won't tell you the mapping is wrong; only the two mapping screens will.

Finish by writing down what happened, in two lines. The date, the channel, which of the three causes it turned out to be, and the change you made. That note is what stops the same gap from reappearing in a month with a different guest on the other end of it.

If the four calendars are the part you'd rather not hold in your head at once, localsbnb.com keeps the connections and their source status on one screen, so you can compare before you act.

FAQ

Which calendar should I fix first when the pages disagree?

Neither. Close the disputed nights on both sides first, then look for the cause. Fixing before blocking means a guest can book the night while you're still diagnosing it.

How do I tell a stale copy from a channel that dropped off?

Read when each side last reported. A stale copy is a channel that's still exchanging information and holding an old version. A dropped link is a channel that's stopped replying altogether, and its page will keep showing the last thing it received.

Is there a way to stop this happening again?

Nearly. Keep every availability change at your source rather than on channel pages, read the mapping after any reconnect, and note when each channel last reported. The three causes are consistent, so the checks that catch them are too.

Two channels disagreeing is rarely a mystery. It's usually one change in the wrong place, one mapping pointing twice, or one link that went quiet. Fix the cause before you reopen the nights, and the same gap stops coming back. If you want the four connections and their status in front of you while you check, localsbnb.com is built for exactly that reading.

---

This is general advice for hosts, and it isn't legal, tax or insurance advice. Rules and platform terms vary by place and change over time; check the current requirements of your local authority and the current terms of each platform you use.