An OTA Booking That Never Appeared in Today's Arrivals

The guest has a confirmation and your calendar is empty. Between those two facts sits a short list of things that break, and a fixed order for ruling them out.

Last updated: October 2, 2026

A guest arrives with a confirmation in hand and your calendar shows the night as open. That gap doesn't come from a mystery. A booking can stop at five points on its way in, and the fastest fix is to rule those points out in a fixed order, starting from the guest's confirmation rather than from your own list.

Key Takeaways

• Start from the guest's confirmation. It proves the booking exists upstream; your arrivals list is only a local record.
• A booking stops at one of five points. The channel, the import, the mapping, the calendar, or the list. It fails at one, not at all of them.
• House the guest first. Get them into a room before you trace why the booking didn't show.
• Rule the points out in order. Work from the last point that could have dropped it back toward the guest.
• Close the gap on purpose. One missed arrival is a symptom. Find the pattern before next week repeats it.

Start from the guest's confirmation, not from your list

The instinct when an arrival is missing is to doubt the booking. Maybe the guest got it wrong, maybe they're at the wrong property, maybe there's no reservation at all. That instinct is worth resisting, because the guest usually holds the strongest evidence in the room: a confirmation from the channel.

A confirmation means the booking exists on the channel. Your arrivals list is a local view, and a local view can be wrong while the booking is perfectly real. So the useful question isn't "did they book?" It's "where did the booking stop on its way to me?" Those two questions lead to different actions.

The difference matters because the wrong action creates a second problem. If you assume the booking doesn't exist and create it by hand, you've added a copy of a reservation that's already real, and now the calendar has two bookings for one stay. You've turned a display problem into a double booking. Starting from the confirmation stops that mistake before it happens.

There's a reason this happens more often on some setups than others. A booking that stops at the channel or the import never reaches your side at all. One that stops at mapping or the list did reach your side and got lost on arrival. Knowing which kind you're dealing with tells you how far back to look.

So hold the confirmation as the fact and treat everything else as a record that might be out of date. From there, the work is a short list of places to check, in a set order.

Five points where a booking can stop on the way in

A booking travels a path from the guest's click to your arrivals list, and it can drop out at any of five points along the way.

The first is the channel. The booking exists upstream, and the channel itself hasn't pushed it out, so nothing downstream has seen it yet. The reservation is there; the signal is what's missing.

The second is the import. The pull that brings bookings into your account ran, and it ran at a moment before the booking was confirmed. The job completed, so it looks healthy, but it completed too early to catch this stay.

The third is mapping. The booking arrived, but it landed against a unit that isn't open for sale, so it had nowhere to attach. The booking is real and your account is confused about where it belongs.

The fourth is the calendar. The dates changed after the push, and the change didn't follow to your side. The booking exists at the original dates, and your calendar is showing the earlier version of the stay.

The fifth is your own list. The arrival report is filtered to a different property, or to a date range that doesn't include this stay. Nothing broke at all. The booking is sitting in plain sight, one filter away.

Notice how different those five are. Only one of them is "the booking is missing." The rest are records, mappings and filters that say the booking isn't there when it actually is, and you need the source view to tell which is which. On LOCALSBNB, the calendar shows each connected channel's source rate and source status.

What to fix first when the guest is already at the door

When the guest is standing there, the order of your actions changes. Fix the human problem first, then the record.

Get them housed. If the unit is ready and the dates are open, put them in and deal with the paperwork afterward. An empty calendar shouldn't send a confirmed guest away while you investigate a display issue. Their confirmation is valid; your setup is what's lagging.

Then, with the guest inside, trace the cause. Because you didn't re-create the booking, the calendar still shows the truth about what arrived and what didn't, which is exactly the evidence you need. Ruling out the five points in order is easier when you haven't muddied the record first. A clean record is what makes the trace possible.

One caution about speed. Once you know the booking exists, the temptation is to force it in fast. But if the booking already arrived and merely lost its mapping, forcing a second copy is the double booking you were trying to avoid. Confirm which of the five points you're looking at before you act on it.

The door is the deadline, not the diagnosis. House the guest, then work the list.

Closing the gap so it does not recur next week

A single missed arrival is a symptom. The useful question afterward is whether the same gap can open again, and which of the five points is behind it.

Look for the pattern, not just the instance. If the missing arrivals all sit on one channel, the point is probably the channel or the import. If they cluster on one unit, mapping is the likelier suspect. If they show up only in a filtered report, the booking was never missing and the list needs a second configuration. The point you find tells you what to change, and it isn't always the same point.

Build a small habit around the weakest point. A short daily check of arrivals against the calendar, on the same day in the same order, catches a stop at the channel or missing from your arrivals list before a guest finds it for you. It won't guarantee that nothing slips. No setup can promise that. What it does is shrink the window between a booking stopping and you finding out, which is the part you actually control.

A pattern also tells you where not to spend effort. If every miss traces back to the same filter in your report, you don't need a new tool, you need a saved view. Fixing the smallest thing that closes the gap beats rebuilding a setup that was mostly working.

And keep the two questions separate. One is what to do for this guest. The other is what to change so the next guest isn't a test case. Answering the first without the second means you'll be back at the same spot next week. You can keep each connected channel's source rate and source status beside the calendar at localsbnb.com.

FAQ

The guest has a confirmation but the booking isn't in my arrivals. Is the booking real?

Yes. A confirmation means the reservation exists on the channel. Your arrivals list is a local record that can lag or misplace it. The booking is real; the question is where it stopped.

Should I create the booking by hand to get the guest in?

Not before you've checked the five points. If the booking already arrived and lost its mapping, adding a second copy creates a double booking. House the guest first, then confirm which point failed.

How do I stop this happening again?

Find the pattern behind the misses and fix the point that causes it. A short daily check of arrivals against the calendar on the same day and in the same order catches the gap earlier. No setup can promise zero missed arrivals, so the goal is a small window, not a guarantee.

A missing arrival is a sequence problem, not a mystery. Start from the guest's confirmation, rule out the five points in order, house the guest first, and close the specific gap that opened. When you want to line up the calendar with what every connected channel reports, open localsbnb.com.

---

This article is general guidance for hosts and isn't legal or tax advice. Channel terms, market conditions and local rules differ by place and change over time; check current product details and the terms that apply where your property sits.