Workflow

Why Awaiting Dispatch needs to mean different things in your sheet

Open your tracking sheet on any busy morning and the most common status you will see is Awaiting Dispatch. It feels like a single, harmless state: the order is placed, the parcel has not moved yet, nothing to do. So you scroll past it. That instinct is exactly how a defect sneaks up on you.

Awaiting Dispatch is not one thing. It is at least three completely different situations wearing the same label, and each one demands a different action from you. Treat them as identical and you will either panic over orders that are perfectly fine, or ignore orders that are quietly dying.

The three orders hiding behind one status

When AliExpress reports an order as placed but not yet shipped, the raw logistics_status sits in something like WAIT_SELLER_SEND_GOODS. Your sheet flattens that into Awaiting Dispatch. But the same string covers three very different stories:

• Brand-new — you placed the AE order two hours ago. The supplier has not packed it yet, and that is normal. No action needed.
• Stuck — the order has been sitting unshipped for four, five, six days. Something is wrong: a stockout, a payment hold, a supplier who is slower than promised. This one needs a nudge today.
• Dead — it has been a week or more with no tracking ID ever assigned. The eBay handling time clock has run out, and you are now exposed to a Late Shipment Rate hit and an angry buyer.

Same label. One is fine, one is a warning, one is a fire. The whole skill is telling them apart before the buyer does it for you.

Age is the variable that splits them

The signal that separates the three cases is not the status itself — it is the age of the order against the date it was placed. That is why the AE order date matters so much. If your sheet does not store the original order date next to the status, you literally cannot tell a healthy order from a stalled one.

A status without a timestamp is a rumour. Awaiting Dispatch on a two-hour-old order is good news; the identical words on a six-day-old order are a refund waiting to happen.

Fetch Order Tracking captures the AE order date automatically on every fetch, so each Awaiting Dispatch row carries its own clock. A simple conditional-format rule then does the triage for you: green under 48 hours, amber at three to five days, red past your handling window. You stop reading statuses and start reading colours.

Build the three buckets into your workflow

You do not need a complicated system. You need three buckets and a habit. Here is the workflow we run:

1. Ignore the green. Anything under two days old in Awaiting Dispatch is doing exactly what it should. Touch nothing.
2. Chase the amber. Three to five days unshipped means message the supplier or check stock. Catch a stockout here and you can re-source before eBay ever notices.
3. Rescue or refund the red. Past your handling time with no tracking, you make a decision: expedite, re-order from a faster supplier, or proactively refund the buyer before they open an Item Not Received case.

The amber bucket is where the money is. Most sellers only ever look at the red — by which point the damage is done. Catching the stalled order while it is still amber is how you keep your defect rate clean and your buyers calm.

Why automation makes the split actually work

You can do all of this by hand for fifty orders. At three hundred a month it falls apart, because the one thing the split depends on — a fresh status and an accurate age on every single row — is the one thing manual checking never keeps current. You check a batch on Monday, by Wednesday half of them have moved and you have no idea which.

This is the job Fetch Order Tracking was built for. It re-fetches the live logistics_status for every open order, stamps each with its AE order date, and skips the ones that are already terminal so a run finishes in one pass instead of looping the same rows. Your Awaiting Dispatch rows stay honest without you babysitting them.

If stalled orders are slipping into refunds, it is worth reading our guide on the hidden cost of a missed AliExpress tracking update — and once an order finally moves, our breakdown of the seven statuses that should map to Shipped shows what comes next. Or just connect your store to Fetch Order Tracking and let the colours do your triage.

Frequently asked questions

What does Awaiting Dispatch actually mean on an AliExpress order?

It means the AliExpress order has been placed but the supplier has not shipped it yet, so no tracking ID exists. The raw logistics status behind it is usually WAIT_SELLER_SEND_GOODS. The trouble is that the same label covers a two-hour-old order that is perfectly fine and a six-day-old order that is in trouble, so the status alone never tells you whether to act.

How long should an order sit in Awaiting Dispatch before I worry?

As a rule of thumb, anything under two days is normal and needs no action. Three to five days unshipped is the point to message the supplier or check for a stockout, and anything past your eBay handling time with no tracking is a fire that needs a decision today. The exact thresholds depend on your handling window, which is why the order age matters more than the label.

How do I tell a healthy Awaiting Dispatch order from a stalled one automatically?

You need the original AliExpress order date stored next to the status so you can measure the order's age. Fetch Order Tracking captures the AE order date on every fetch and re-pulls the live logistics status, so a simple conditional-format rule can colour each row green, amber, or red by age. You stop reading status strings and start reading colours.

Related guides

• Seven tracking statuses that should map to Shipped in your sheet
• The hidden cost of a missed AliExpress tracking update
• Reading the raw AliExpress order_status and logistics_status fields

---