Workflow
Uploading tracking to eBay on time, every time
Key takeaways
- Every eBay sale has a quiet handshake window to mark the order shipped with valid tracking, and missing it bleeds your seller standing with no alert.
- On-time tracking is really two problems: late but correct uploads feed your Late Shipment Rate, while on-time but wrong uploads set up item-not-received cases.
- Manual uploads fail when the number is not ready yet, when you batch it for later and forget, or when you trust the wrong carrier.
- A reliable system has four parts: pull as soon as tracking exists, resolve the real carrier from the prefix, push the right fields, and run on a clock with a skip-list.
- On-time tracking is a vigilance problem, which is exactly what software is built for, and it gets harder and more important across multiple stores and regions.
There's a deadline hiding in every eBay sale, and it doesn't announce itself. You have a handshake window to mark the order shipped with valid tracking, and if you miss it — or upload a number that doesn't move — eBay records it against you. No alert, no penalty notice. Just a slow bleed on your seller standing.
The cruel part is that on-time tracking is entirely solvable. It's not a judgement call or a customer-service skill. It's a system. Here's how to build one that gets the right number to eBay on time, without you babysitting it.
Why "on time" is two problems, not one
Sellers conflate them, but late uploads and wrong uploads fail differently:
- Late but correct — the tracking is real, you just filed it after the window. This feeds your
LateShipmentRateand dents your shipping metrics. - On time but wrong — you hit the deadline with a number that never shows movement, or the wrong carrier. eBay sees an undelivered shipment, and you're set up for an item-not-received case.
You have to beat both. A system that's fast but sloppy, or accurate but slow, still loses. We dig into the metric side of this in how accurate tracking protects your eBay defect rate.
Where manual uploads break down
The hand workflow has three failure points, and at volume you'll hit all of them:
- The number isn't ready yet. AliExpress hasn't populated tracking, so you skip the order — and forget to come back.
- You batch it for "later". Later becomes tomorrow, tomorrow becomes past the window.
- You upload the wrong carrier. Trusting
carrier_nameinstead of resolving the real courier means eBay can't match the tracking events.
The order you forget is never the one you're worried about. It's the quiet one that shipped fine — and quietly aged past its window while you weren't looking.
The system: pull, resolve, push, on a clock
A reliable on-time system has four moving parts. Whether you build it or buy it, these are the pieces.
1. Pull as soon as it exists
You need to be checking AliExpress for tracking continuously, not in a once-a-week panic. The moment logistics_status indicates a shipment and a tracking ID appears, it should land in your sheet — alongside carrier, status, EDD, and the AE order date.
2. Resolve the real carrier
Before anything goes to eBay, map the tracking-ID prefix to the actual courier — Evri, Yodel, Royal Mail. This is the single most common reason "valid" tracking still triggers a case, because eBay silently fails to match events to a mislabelled carrier.
3. Push the right fields
The upload to eBay needs the tracking number and the correctly-resolved carrier together. Get either wrong and the order looks unshipped no matter how careful you were.
4. Run it on a clock, with a skip-list
The whole loop has to run often enough to beat the window — and it has to know what it already finished. A skip-list means terminal orders drop out of the queue so you're never re-processing delivered or refunded rows. If yours loops on the same orders forever, that's the missing piece — and it's the same waste we measured in our time audit.
Why automation wins this one outright
On-time tracking is the textbook case for automation, because the failure is never a hard problem — it's a vigilance problem. Humans are bad at vigilance; software is built for it. A fetcher never gets distracted, never decides to batch it for later, never forgets the quiet order.
Fetch Order Tracking runs the exact four-part loop above:
- Continuous pull from the AliExpress Dropshipping API into the Google Sheet you already own.
- Carrier mapping from the tracking-ID prefix, because
carrier_namecan't be trusted. - Batch processing — roughly 25 orders per click, auto-chained with a small delay, so a run clears the whole queue in one go.
- A JS skip-list so finished orders never get re-checked and the loop actually terminates.
Multi-store makes it harder — and more important
Run eBay UK, US, and AU and the on-time problem multiplies: different windows, different carriers, different currencies. Tracking three sets of deadlines by hand is how good sellers take avoidable defects. Fetch Order Tracking runs all your stores and regions from one workspace, so "on time" stays true across every marketplace at once.
The payoff
Get this right and two things happen. Your shipping metrics stay clean, which protects your fees and visibility. And buyers see accurate, moving tracking, which heads off the worried "where's my order?" messages before they're sent. Both outcomes come from the same flat monthly plan — no per-order fees, so it costs the same at 100 orders or 1,000.
Stop treating on-time tracking as a thing you remember to do. Make it a system that runs without you. Let Fetch Order Tracking get the right number to eBay on time, every order, every store — and reclaim the deadline you've been quietly losing.
Frequently asked questions
What is the difference between a late upload and a wrong upload?
They fail in different ways. A late but correct upload means the tracking is real and you simply filed it after the window, which feeds your Late Shipment Rate. An on-time but wrong upload means you hit the deadline with a number that never moves or the wrong carrier, so eBay sees an undelivered shipment and you are set up for an item-not-received case. You have to beat both.
Why does my valid tracking still trigger item-not-received cases?
Usually because the carrier is wrong. If you upload a generic service name instead of the real courier, eBay silently fails to match the tracking events and the order looks unshipped even when it arrived. Mapping the tracking-ID prefix to the actual courier before the upload is the single most common fix for this.
How do I make sure I never miss the shipping window?
Treat it as a system rather than a thing you remember to do. Pull tracking from AliExpress the moment it exists, resolve the real carrier, push the right fields, and run the loop on a clock with a skip-list so finished orders drop out. Fetch Order Tracking runs that exact loop with batch processing of about 25 orders per click, so nothing sits past its window.
Related guides
- How accurate tracking protects your eBay defect rate
- What dropshippers should know about eBay Late Shipment Rate
- Why your auto-update keeps looping on the same 25 rows