Scaling

How to spot inventory issues from your tracking data alone

Most dropshippers learn about a supplier stockout the worst possible way: a buyer message asking where their order is, days after the AliExpress seller quietly stopped shipping. By then you have a late order, a nervous customer, and a listing still happily taking sales it cannot fulfil.

Here is the thing nobody tells you when you start: you already own an early-warning system for this. It is your tracking data. Inventory problems leave fingerprints in the order statuses and timing long before they show up as complaints — if you know which signals to read.

Why tracking data sees stockouts first

When a supplier runs low or out, they rarely tell you. What they do instead is stall. The order sits in a pre-shipment state, the tracking ID does not appear or does not scan, and the clock runs. That stall is information. It shows up in your data days before the buyer notices anything is wrong, which means tracking is the earliest reliable place to catch the problem.

A stockout almost never announces itself. It shows up as a cluster of orders that should have moved by now and have not. Read the stalls and you see the shortage before your buyers do.

The signals to watch

No single order tells you much — orders are slow for all kinds of innocent reasons. The signal is in the pattern across orders for the same product. Watch for:

• Awaiting Dispatch that overstays its welcome. One order stuck pre-dispatch is normal. Several orders of the same SKU all stuck past your usual dispatch window is a supply problem. The nuance of this status is worth understanding — see our notes on reading AliExpress carrier and status data.
• Tracking IDs that never gain a scan. A number assigned but never moving for days often means the parcel was never actually handed over — a classic sign the supplier is buying time they do not have.
• Estimated delivery dates that keep slipping. When the EDD on a SKU drifts later across consecutive orders, the supplier's lead time is stretching, usually because they are restocking.
• A spike in cancellations or refunds on one product. If a supplier cannot fulfil, the cleanest exit for them is to cancel and refund. A cluster of refunds on a single SKU is a stockout in disguise — see why matching the right order ID matters so you attribute those refunds to the correct listing.

Turning signals into a routine

Reading these signals is only useful if you do it consistently. Build a light routine around your existing tracking sheet:

1. Group by SKU, not just by date. Stockouts are a per-product event. Sorting by order date hides them; grouping by SKU surfaces the cluster.
2. Flag the stalls. Any order past your normal dispatch window without a scanning tracking number is a candidate. A handful for one SKU is your alarm.
3. Cross-check the refund column. Pair stalls with refunds on the same product. The combination is a much stronger signal than either alone.
4. Act before the buyer does. Pause or de-prioritise the listing, switch to a backup supplier, or message the buyer proactively — all while you still have the initiative.

Why fresh, complete data is the whole game

This early-warning system only works if your tracking data is current and complete. Stale data — checked once a day, or missing the orders your parser silently dropped — means you spot the stockout at the same time your buyers do, which defeats the point. The signal is in the recency; a three-day-old snapshot is just a slower version of the buyer complaint.

That is exactly why Fetch Order Tracking is so useful as a scaling tool, not just a tracking tool. It refreshes every order's status, carrier, EDD, and refund state into the Google Sheet you already own, in batches that auto-chain through hundreds of orders per click — so the whole picture is current, not a sample. Its refund detection catches the delivered-then-refunded and silently cancelled orders that a single-field check misses, which means a supplier quietly bailing on a SKU shows up in your data instead of slipping past it.

Because every order is captured by SKU with its real carrier resolved from the tracking-ID prefix, the per-product patterns that reveal a stockout actually become visible. You stop reacting to buyer messages and start spotting the problem while you can still do something about it.

Your tracking sheet is more than a list of where parcels are — it is a live read on the health of your supply. Keep it fresh and complete, and it will warn you before a stockout turns into a wave of late orders. Try Fetch Order Tracking and turn your tracking data into the early-warning system it was always capable of being.

Frequently asked questions

Which tracking signals point to an AliExpress supplier stockout?

Watch for a cluster of same-SKU orders stuck in Awaiting Dispatch past your usual window, tracking IDs that are assigned but never gain a scan, estimated delivery dates that keep slipping across consecutive orders, and a spike in cancellations or refunds on one product. No single order means much, because orders are slow for innocent reasons. The signal is the pattern across orders for the same product.

How is one slow order different from an actual stockout?

One order stuck pre-dispatch is normal and usually nothing. A stockout shows up as several orders of the same SKU all stalled past your normal dispatch window, often paired with refunds on that same product. Grouping by SKU rather than by date is what surfaces the cluster — sorting by order date scatters the stalls and hides the pattern.

Why does my tracking data need to be fresh to catch stockouts early?

The whole advantage is recency: a stall is only an early warning if you see it days before the buyer does. A once-a-day check, or a sheet missing the orders a parser silently dropped, means you spot the shortage at the same time your buyers do. Fetch Order Tracking refreshes every order's status, carrier, EDD, and refund state by SKU in batches that auto-chain through hundreds of orders per click, so the per-product patterns stay current instead of stale.

Related guides

• Why you should never trust AliExpress's carrier_name field on its own
• Why Awaiting Dispatch needs to mean different things in your sheet
• Scaling past 500 orders a month without hiring a VA

---