Delivery delayed — decide what to do next
🧭 PRIMARY ENTRY Intent: shipment late, no clear reason
Rule: if you don’t know why the delay is happening — you should be here.
What to do now (decision route)
Worst mistake
Waiting “a bit more” with no escalation and no deadline. That’s how people miss compensation windows (carrier claims, seller policies, or card disputes).
Stop. Answer one question
- Has there been a new scan / tracking event in the last 72 hours?
- “ETA changed” is not a scan. You need an actual tracking event in the history.
- If status says Exception, jump to Delivery exception.
Route A — yes, there’s a recent scan (package is moving, but still late)
- Check the updated ETA and whether it has changed multiple times.
- Capture proof: screenshot the scan history with timestamps.
- Set a hard timer: if there’s no new scan within 48 hours, switch to Route B.
Route B — no scan for 72+ hours (treat as potential loss / system stall)
- Open an official carrier case (investigation / claim entry point).
- Notify the seller with order #, tracking #, and the carrier case number.
- Protect deadlines: check the seller’s refund policy and your payment method dispute window; set your final date now.
Always available next steps: if the delay is actually an exception, use /delivery-exception/. If it’s “in transit forever,” use /package-stuck-in-transit/. If it’s simply not delivered, use /item-not-received/.
Outgoing (always)
Incoming: all delivery-related pages → /delivery-delayed/ (primary entry). Homepage → “Delivery & Orders” block → /delivery-delayed/.
Red flags (treat as escalation triggers)
- “In transit” with no scans for 7+ days
- “Arrived at hub / facility” then silence for 72+ hours
- “Exception” with no clear reason → go to delivery exception
- ETA changes more than twice
- Seller tracking vs carrier tracking do not match
- No proof of delivery / signature where it should exist
- Cross-border shipment stuck “between customs steps” with no movement
Interpretation rule
- Red flag = action, not panic. Your job is to protect deadlines and get a case number.
- A tracking page that “looks active” but has no scans is still Route B.
Verify safely (before you escalate)
These steps reduce false alarms and help support teams act faster.
- Check tracking in two sources (carrier + a neutral tracker)
- Look at full scan history (not just the latest status)
- Confirm timestamps/timezone (some sites shift times)
- Verify delivery address in your order confirmation
- Capture screenshots of the scan history and ETA changes
- Collect basics: order #, tracking #, item value, ship date, destination country
- Write down your deadline date for refund/dispute (don’t “remember it later”)
If your only signal is “email says it’s delayed”
Ignore the email wording. Go straight to carrier tracking you open manually. If there’s no scan history change, this page still applies.
Risk rubric (low / medium / high)
Recent scans exist; delay is short
- Default action: Route A + timer (48 hours).
No scans for 3–7 days
- Default action: open a carrier case + notify seller.
No scans for 7+ days or “Exception”
- Default action: carrier case + seller escalation + prepare dispute if deadlines approach.
Why this matters
- Carriers and sellers often require a case to start the clock.
- Bank/card disputes are deadline-driven. “Waiting to see” is not a strategy.
FAQ (top questions)
When is a package considered “lost”? ▾
When the carrier completes an investigation and can’t locate it, or the shipment exceeds their “no-scan” threshold. Practically: if scans stop for 7+ days, treat it as escalation territory.
How long should I wait before opening a carrier case? ▾
If there’s no scan for 72+ hours, it’s reasonable to start Route B. Don’t wait a week “just in case.”
My ETA changed, but there are no scans — is it still moving? ▾
No reliable evidence. ETA is an estimate. Scans are events. If scans stopped, treat it as Route B.
Who is responsible: seller or carrier? ▾
Depends on the shipment agreement. As a buyer, your safest approach is parallel escalation: carrier case + seller notification, then protect payment deadlines.
What if tracking says “Delivered” but I didn’t receive it? ▾
That’s a different scenario. Go to /item-not-received/ (proof of delivery, misdelivery, neighbor/locker checks, dispute steps).
What does “Exception” mean? ▾
A catch-all for issues (address, customs, weather, failed delivery attempt, damage, etc.). Use /delivery-exception/ to map it to actions.
Will opening a case slow delivery down? ▾
Usually no. It creates a trace/investigation and a reference number — which you want anyway if it becomes a claim/refund problem.
What evidence should I collect? ▾
Scan history screenshots, order confirmation, payment receipt, tracking number, ship date, item value, and any seller communication.
Is a delay always customs? ▾
No. Customs is common, but “no scans” can also mean sorting backlog, label damage, missort, or misrouted parcel. Don’t assume — verify by scan history.
Can I request a refund before the carrier finishes? ▾
Depends on the seller policy. Many require an investigation first. Either way, you should still protect deadlines and not wait silently.
When should I consider a card dispute/chargeback? ▾
When the seller refuses to help or deadlines are approaching. Don’t miss the window while waiting for “one more update.”
Why do different trackers show different statuses? ▾
They can cache data or interpret events differently. The carrier’s scan history is the anchor, but a second source helps catch sync issues.
External resources (official)
Use official carrier claim/help pages. If you’re the buyer, you may still need the seller (shipper) to file a claim — but you can always open an investigation/contact ticket and get a reference number.
ClearExplained — simple pages that remove panic and reduce mistakes.