An OTA Reservation That Never Arrives: a Triage Order

When a booking shows on the platform and not in your calendar, the order you check things in is most of the fix. Start where the break is most likely.

Last updated: October 9, 2026

When a booking shows on the platform and not in your calendar, the order you check things in is most of the fix. Start where the break is most likely, not where it's easiest. This guide lays out a short triage order: where a reservation can stop, the first three things to check, what the timestamps tell you, and how to tell when the channel is the problem rather than you.

Key Takeaways

• Order matters more than speed. Checking in the right sequence finds the break faster than checking everything at once.
• Confirm the booking exists before you touch anything local. A reservation that never reached the platform isn't a sync problem at all.
• Check the listing next, then the calendar. Most breaks sit at the listing that received the booking, or at the calendar that should have taken it.
• Timestamps tell you which side is late. The gap between the booking time and the last update points at where the break is.
• One calendar shows each channel's own rate and status. That's where you see whether a channel is behind before you raise it.

Where a reservation can stop

A booking travels a short path before it reaches your calendar, and it can stop at any point along it. Knowing the stops turns a vague worry into a short list.

First, the booking has to exist on the channel. A guest who thinks they've booked, but whose payment didn't complete, leaves a record that never becomes a reservation. Until it exists on the platform, there's nothing for your side to receive.

Second, it has to reach the right listing. A booking that lands on a listing you don't recognise, or on a unit you've closed, has arrived but gone to the wrong place. It exists on the channel, and it isn't where you expect it to be.

Third, it has to land on the calendar. This is the step people assume has failed, when often the break is earlier. A calendar that's behind, or that was showing a different picture, can make a booking look missing when it's simply not on screen yet.

Fourth, it has to survive on your side. A booking that arrived, was accepted, then quietly moved or cancelled isn't missing. It's there, and it changed state. That's a different problem from one that never arrived, and it needs a different answer.

Naming the four stops does most of the work. When a booking looks absent, you're asking one of four questions, and each has its own check. The order below walks them in the sequence that finds the answer fastest.

The first three things to check

When a booking looks missing, check three things in this order. Each is quick, and each either finds the break or rules out a tier of the problem.

First, open the channel and confirm the reservation exists there. If it doesn't, the issue is on the platform side or in the booking itself, and your calendar was never the problem. That single check saves you from rebuilding a calendar that's working fine.

Second, confirm the listing that received it is the one you expect. A booking that exists and isn't on your calendar is often sitting on a different listing, or on one you renamed last month. Match the booking to the unit before you go further.

Third, compare the calendar's last update against the booking time. If the calendar moved after the booking was made and still shows the night as free, the break is likely on your side. If the calendar hasn't moved since well before the booking, the break is more likely upstream.

Only after those three should you widen the search. Most breaks are found in the first two, and the third tells you which direction the rest of the hunt should take. Working in this order keeps you from the common trap of rebuilding a calendar that was never broken.

A word on the order itself: existence before location, and location before timing. If the booking isn't on the channel at all, the listing and the calendar are irrelevant. If it's on the channel but on the wrong listing, the timing won't tell you much. Each earlier check narrows what the later ones can mean.

What the timestamps tell you

A booking time and a calendar time are two clocks, and the gap between them is a clue. Read the gap before you read anything else.

If the booking was made and the calendar updated shortly after, the two are talking, and the problem is probably about which listing or which night. A communication break would tend to leave a larger gap.

If the calendar hasn't updated since well before the booking, the question shifts to whether your side is receiving at all. That's a different kind of check, and it starts with the connection rather than with the booking.

Keep both times to hand when you raise the issue. A support team can act faster on a booking time and a last-update time than on a description. The timestamps turn "my booking never came through" into a specific question with a specific answer.

Don't read the gap as a rule, though. How quickly updates flow is set by the platform and the connection, not by you, and the current behaviour is what matters rather than a remembered average. The gap narrows your search. It doesn't prove a cause on its own, and it shouldn't be quoted to a guest as though it did.

One habit makes the timestamps usable: write them down the moment you notice the problem. A booking time and a last-update time captured at the start stay accurate. The same two times reconstructed an hour later are guesses.

When it is the channel, not you

Sometimes the check comes back clean on your side and the booking still isn't moving. That's when the issue sits with the channel, and the work shifts from fixing to reporting.

The signs are consistent. The booking exists on the platform, the listing matches, your calendar is up to date, and the night is still free. When your side passes every check, stop testing and start documenting.

Documentation is what makes an escalation move. Record the booking reference, the booking time, the listing it names, and the last time your calendar updated. With those four facts in hand, the question becomes precise enough to trace.

Write it in a form you can copy from. The point of the record isn't a diary; it's a block of facts you can paste into a message. Reference first, then the times, then the listing. Four lines, no adjectives, and a support team can act on it.

Then keep the sync separate from the stay. A missing booking is a problem to solve, and a guest is a person to look after. Fix the person in front of you first, and chase the sync second. A calm arrival outranks a tidy diagnosis.

This is where one view helps you report accurately. LOCALSBNB connects directly to four OTAs, and its calendar shows each connected channel's own source price and status, so you can describe exactly what your side shows while you compare it against the channel. The read-only assistant answers plain questions about a booking's detail, today's availability and a listing's calendar, so you can gather the facts before you make the call rather than after.

With the facts in order, you can raise the issue with the timestamps ready. The channel-by-channel view on localsbnb.com is where that comparison sits while you work.

FAQ

What's the first thing to check when a booking seems missing?

Whether it exists on the channel. If it doesn't, the problem isn't your calendar, and you've saved yourself a search in the wrong place.

If my calendar is up to date and the night is still free, is it the channel?

Probably, yes. When your side passes every check, document the booking time and the last update, and raise it with that evidence in hand.

Should I tell the guest before the sync is fixed?

Look after the guest first. Confirm the booking on the platform, secure their arrival, and sort the sync alongside rather than in front of them.

A missing reservation rewards a fixed order. Confirm it exists, match it to the listing, read the timestamps, and only then decide whether the break is yours or the channel's. That sequence turns a stressful morning into a short checklist. When you want each channel's own price and status in front of you while you trace a booking, start at localsbnb.com.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules and platform terms change, so check the current requirements of your local authority and the terms each platform applies today.