Tracking

When AliExpress shows Delivered but your buyer disagrees

There is one tracking status that can cost you a refund, a defect, and a customer all at once — and it is the one that looks like good news. The order says Delivered. You move on. Three days later the buyer opens an "item not received" case and you have nothing to fight it with.

A false or premature Delivered is the most dangerous status in dropshipping precisely because it disarms you. You stop watching the order at the exact moment you most needed to. Here is why it happens, and how to catch it before it turns into an INR case you lose.

Why "Delivered" is so often wrong

AliExpress and its carriers do not see your buyer's doorstep. They see scans. A package marked delivered usually means a courier pressed a button at a depot, a hub, or a neighbour's porch — not that your buyer is holding the box. The mismatch comes from a handful of predictable causes:

• Scanned-then-stuck: the parcel hits a "delivered to local facility" scan that the API surfaces as delivered, but the last mile never completes.
• Wrong address or safe place: Evri or Yodel leaves it somewhere the buyer never finds.
• Premature scans: the courier pre-scans a round before driving it, then the van breaks down.
• Genuine porch theft: delivered, real, gone.

If your sheet says Delivered and your inbox says "where is my item?", trust the inbox. The buyer is standing where the carrier never looked.

The window you are actually fighting for

On eBay, an item-not-received case is a clock. Once a buyer opens it, you have a short window to respond with proof or the platform refunds them and your money is gone — sometimes with a transaction defect attached. The whole game is to have the evidence ready before you need it, not to go scrambling through AliExpress order pages while the timer runs.

That means two things have to be true for every order on your sheet:

1. You can see, at a glance, which orders are marked delivered but might be disputed.
2. You already have a carrier delivery-proof link attached, so a reply takes ten seconds instead of ten minutes.

Catching the false Delivered early

The fix is not heroics — it is making the data work for you. A delivered status should never be the end of an order's life in your tracking; it should be a flag to verify. Three habits make this reliable:

• Resolve the real carrier. AliExpress's carrier_name is famously unreliable, so a "delivered" claim from the wrong courier is worthless. Map the courier from the tracking-ID prefix instead — that is the only way to pull a genuine proof page. (We cover this in depth in why you should never trust AliExpress's carrier_name field.)
• Keep a proof link on every row. Not the AliExpress page — the carrier's tracking page, with the delivery scan and any GPS or signature data the courier exposes.
• Watch for delivered-then-refunded. A buyer who got their item and still got a refund is a separate, expensive problem. See why your refund column shows Cancelled for a delivered order.

Where Fetch Order Tracking comes in

Fetch Order Tracking exists to make that "before you need it" state the default. For every order it syncs into your Google Sheet, it auto-fetches the tracking ID, the resolved carrier, the live tracking status, the estimated delivery date, and a carrier delivery-proof link — so when a buyer disputes a delivery, you reply with a real courier page in seconds, not excuses.

Because it resolves the courier from the tracking-ID prefix rather than trusting carrier_name, the proof link actually points at the right carrier. And because every order keeps a live status instead of freezing at "Delivered", a parcel that scans delivered but never truly arrives stays visible until you confirm it. That is the difference between catching a false delivery on day one and discovering it inside an open INR case.

A false Delivered will always happen at volume — couriers are couriers. What you control is whether you see it coming. Try Fetch Order Tracking and let every order carry its own proof, automatically.

Frequently asked questions

Why does AliExpress show Delivered when my buyer says nothing arrived?

A Delivered status is generated from a carrier scan, not a confirmation that your buyer received the box. The scan can fire at a local depot, a wrong address, a safe place the buyer never checks, or as a premature pre-scan before the round is even driven. When your sheet says Delivered and the buyer says otherwise, trust the buyer and verify the last-mile scan on the carrier page before you respond.

How do I protect myself against a false Delivered before it becomes an INR case?

Keep a live status and a carrier delivery-proof link on every order so a Delivered scan is a prompt to verify rather than a signal to stop watching. Resolve the real courier from the tracking-ID prefix, not from carrier_name, so the proof link points at the carrier that actually carried the parcel. With that ready in advance you can reply to an item-not-received case in seconds instead of scrambling through AliExpress order pages while the clock runs.

Can Fetch Order Tracking flag a delivered-then-refunded order?

Yes. Fetch Order Tracking keeps a live tracking status and refund state on each row instead of freezing the order at Delivered, so a parcel that scans delivered and is later refunded stays visible. It detects delivered-then-refunded orders specifically, which is a separate and more expensive problem than a simple non-delivery.

Related guides

• Why you should never trust AliExpress's carrier_name field on its own
• Why your refund column shows Cancelled for a delivered order
• Winning eBay disputes with delivery proof links

---