Back to blog
Shipping & Logistics

Why "Lost" Packages Take So Long to Resolve

 ·  ⏱ 3 min read
Investigation happens before resolution. Set expectations while the search is active.

A customer messages you: their tracking hasn't moved in two weeks, or it says delivered and they never got it. You want to fix it immediately. The carrier's process doesn't work on your timeline, and understanding why helps you manage the customer conversation instead of just apologizing on repeat.

Lost package investigation timeline and resolution protocol.
Lost package investigation timeline and resolution protocol.
Parcel journey through export and local delivery handoff.
Parcel journey through export and local delivery handoff.

Why we can't just declare a package lost

Carriers won't open a loss investigation the moment tracking goes quiet. Most require the shipment to be a set number of days past its expected delivery window, often around 30 days for international parcels, before they'll formally investigate. Before that point, a stalled scan is usually still moving, it's just not visible in the tracking feed yet. Customs holds, regional sorting backlogs, and last-mile handoffs all create gaps where nothing updates for days at a time without the parcel actually being lost.

The three things that look identical to a customer but aren't

Genuinely delayed. Still moving, just slow. Resolves itself, usually within another 1-2 weeks.

Address or customs issue. Held up pending a correction, a duty payment, or a redelivery attempt. Needs action, not just waiting.

Actually lost. Rare, but it happens. Only confirmable once the carrier's investigation window has passed.

You can't tell which one you're looking at from the tracking page alone. That's why we don't reship or refund the instant a customer complains, we'd be guessing, and guessing wrong either costs you money on a parcel that shows up in three days, or makes a genuinely lost customer wait longer than they should.

What we actually do while you wait

Check the last scan location and date against normal transit patterns for that route, not just "has it moved."

Flag anything that's genuinely outside normal range for investigation, rather than waiting the full window on every stalled tracking number.

Chase the carrier directly once a parcel qualifies for investigation, so you're not stuck making the call yourself in a language you don't speak.

Tell you honestly which of the three categories above we think it's in, based on the pattern, not just repeat "please wait" messages.

What to tell your customer in the meantime

Something like: your order is confirmed shipped and the tracking will typically update within a certain window, carriers sometimes have gaps in scanning that don't mean anything's wrong, and you're actively monitoring it. If it passes the threshold where a real investigation kicks in, that's when a reship or refund conversation actually starts, not before, because starting it earlier just means guessing with your own money.

If you've got a customer chasing you about a parcel that's gone quiet, send us the order number on WhatsApp (+86 178 4666 9989). We'll tell you honestly whether it's a normal gap or something that needs action.

What to collect when a parcel appears lost

  • The original and local tracking numbers, plus the latest scan and date.
  • The customer's delivery address, contact details and any report from the delivery location.
  • Photos of the parcel, delivery area or proof of damage where relevant.
  • A clear timeline of the customer's report and every update already sent.

Communication matters while the trace is open: tell the customer what is being checked, when you expect the next update, and what the possible outcomes are. Do not promise a refund or reshipment before the evidence and route policy support it.

Need a route or order checked for a specific order?

If a specific order's tracking has you or your customer worried, send us the order number on WhatsApp (wa.link/dropship) and we'll check what's actually going on.

Check Order on WhatsApp →