A Duplicate Reservation From a Retried Import: The Safe Unwind Order

A retried import can leave the same booking sitting in your account twice. Which copy you cancel first decides whether the guest ever sees a problem.

Last updated: October 2, 2026

A retried import doesn't announce itself. You run the import again because the first attempt looked like it stalled, and when it finishes, the same booking is sitting in your account twice. Both copies look real, because both are real. They point at the same confirmed reservation. What decides whether this becomes a guest-visible problem is the order in which you unwind it.

Key Takeaways

• A retry creates a real booking, doubled. The second copy isn't noise. It points at the same confirmed reservation as the first.
• The channel is the source of truth. Find which copy the channel still recognizes before you touch either one.
• Keep the copy the channel holds. Unwind the extra copy only after you've confirmed which side is authoritative.
• Tell the guest once. If the guest has one confirmation, they should hear one clear message, not two.
• Stop the retry repeating. Fix the reason the first import stalled so the same run doesn't fire again.

How a retry produces a booking that is real and doubled

An import pulls bookings from a channel into your account so you can see them alongside everything else. It's a routine job, and most of the time nothing goes wrong. The trouble starts when one run looks like it failed.

A run can look stalled for ordinary reasons. A slow connection, a refresh in the middle, a screen that didn't update. The natural response is to run it again. That's the moment the doubling happens. The first run had actually completed, and the second run pulled the same confirmed reservations a second time.

Here's what makes it awkward: the duplicate isn't junk. It carries the same channel confirmation as the original, because it's the same reservation. If you delete the first copy you find, you may have deleted the one the channel still recognizes, and now your account and the channel disagree about a booking that's genuinely there. That's how a tidy-up turns into an overbooking.

It's worth separating two things that look similar. A double booking is two different guests who both hold a real reservation for the same night. A duplicated import is one guest and two records of the same stay. They look alike on a calendar, but they call for different fixes, and treating one as the other is how a simple cleanup goes wrong.

Both copies also want the same nights. Your calendar sees two bookings competing for one reservation's dates, which is exactly the shape of a double booking, even though only one guest exists. The fix isn't to delete the extra copy fast. It's to find out which copy the channel is still holding, and unwind from there.

Confirming which copy the channel is still holding

Before you remove anything, look at the channel. The channel is where the guest booked and where the confirmation lives, so it's the source of truth for which copy is real.

Read the reservation the channel still recognizes. Compare it to the two copies in your account, guest and dates first, since those are the facts a guest would repeat. One of your two copies will match what the channel holds. That's the one to keep.

This is where a second view earns its place. On LOCALSBNB, the calendar shows the source rate and source status that came from each connected channel, so you can see what each connected channel reports and spot the copy that doesn't line up. When your account shows one version and the channel shows another, the side-by-side view tells you which value to trust instead of leaving you to guess.

You don't need to memorize an identifier. Guest name and dates are enough to tell the two copies apart in most cases, and they're the facts the guest would give you if you had to ask. If guest and dates match on both copies, you're looking at a duplicate, not two bookings.

Don't skip this confirmation, even when the answer looks obvious. The obvious copy isn't always the authoritative one, and the cost of getting it wrong lands on a guest who did nothing except book a stay.

The order that keeps the guest's reservation intact

Once you know which copy the channel holds, the rest is a short order. Follow it and the guest never sees a problem.

First, leave the channel's copy exactly as it is. It's the reservation. Nothing you do to unwind the duplicate should touch it.

Second, identify the extra copy in your account as the one that doesn't match the channel. Name it clearly to yourself before you act, so you're not deciding while you're clicking.

Third, confirm the guest has one valid confirmation, not two. In almost every case they've received a single confirmation, because the reservation only ever existed once upstream. Confirm it, don't assume it. If the guest somehow has two messages, that changes the unwinding you owe them.

Fourth, release the extra copy on the side that created it. The duplicate came from a retried pull into your account, so that's the copy to clear, not the one the channel is holding. The order matters more than the speed, because speed is what created the second copy.

Fifth, re-check the nights. After the extra copy is gone, the calendar should show one booking on those dates, matching the channel. If it still shows two, stop and re-confirm before doing anything else. The point of the order is that the guest never had to be part of the story.

Stopping the same retry from firing again

Clearing the duplicate fixes today. It doesn't stop tomorrow, unless you deal with why the import retried in the first place.

Start by not running the import again while you're unsure. A second run on top of an unsettled first run is how you get a third copy, and three copies is a harder conversation with a guest than two. When a run looks slow, wait and look before you repeat it.

A retry often looks identical to a fresh import from the outside, which is why it's easy to repeat without meaning to. Note the time you last ran it, and give the pull time to finish before you judge it stuck. A finished import and a stalled one can look the same for a minute or two.

Then find the reason the first run looked stalled. Often it's something ordinary: an interrupted page, a connection that dropped, a pull that finished after the screen stopped updating. Knowing the reason turns a mystery into a habit. Check once, wait for the result, and only run again if you can see it genuinely didn't finish.

Be careful about leaning on a busy/available date feed as a safety net here. On LOCALSBNB, iCal links pass busy and available dates only. They don't carry booking-level detail, so an iCal feed won't tell you which of two copies is the real reservation or which guest holds it. It's a fallback for keeping dates aligned, not a tool for unwinding a duplicate.

The habit that prevents a repeat is small. Treat an import as a job you run once and then read, not one you fire again the moment it looks slow. Most duplicates come from impatience, and most impatience comes from not being able to see whether the first run finished. You can see each connected channel's source rate and source status next to the calendar at localsbnb.com.

FAQ

Which copy of a duplicate reservation should I remove?

Remove the extra copy in your account, the one that doesn't match what the channel still holds. Keep the copy the channel recognizes, because that's the reservation the guest actually booked.

Can the guest end up with two confirmations?

Rarely, because the reservation only existed once upstream. Confirm the guest has a single valid confirmation before you unwind anything, and if they somehow have two, deal with the messages before the calendar.

Will this happen again if I just fix it once?

Only if you remove the cause too. Clear the duplicate, then find why the import looked stalled and stop re-running a job that may have already finished.

A duplicate from a retried import is a sequence problem, not a mystery. Confirm which copy the channel holds, keep it, release the extra copy where it came from, and fix the reason the import ran twice. When you want every connected channel's state in one view, 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.