A valid tracking upload is not simply a number in a field. Each marketplace defines validity by a combination of timing, carrier recognition and the presence of specific carrier scan events, and each derives its delivery promise from a different set of inputs. Getting this wrong costs seller metrics and protection even when the parcel itself arrives on time.
Why do marketplaces care so much about tracking validity?
Tracking is the only independent evidence a marketplace has that a seller did what they promised. The marketplace did not pack the box or drive the van, so a carrier scan is the closest thing to a neutral witness.
That evidence supports three functions, and each needs a different scan. Despatch compliance needs an early acceptance or collection event, delivery performance needs a final delivery event, and dispute resolution needs both plus a coherent chain between them.
The underlying principle: marketplaces do not reward you for uploading tracking. They reward you for uploading tracking that resolves, on a carrier they recognise, within the window they specify, producing the events they need.
What does each marketplace actually require?
The four major marketplaces converge on the idea and diverge on the detail.
Amazon
Amazon's seller-fulfilled requirements centre on On-Time Delivery Rate (OTDR), which measures the share of seller-fulfilled orders delivered by the promised date. From February 28, 2026, an OTDR below 90% triggers deactivation at the listing level, deactivating the worst-contributing ASINs rather than the whole catalogue. This is confirmed via an Amazon Seller Central forum thread and corroborated by multiple seller-services sources.
Amazon also offers a protection route rather than relying purely on uploaded data. Amazon Buy Shipping and Veeqo produce OTDR-protected labels, and using them together with shipping settings automation confers protection on those orders.
Unconfirmed, do not plan around it: Amazon Valid Tracking Rate thresholds of 95% and 99% circulate widely in seller communities. As of August 2026, neither figure is confirmed, and this article does not assert either. Similarly, a reported move to a 93.5% OTDR threshold from June 29, 2026 with weekly rather than monthly review could not be verified on any Amazon-owned page and should not be treated as policy.
eBay
eBay ties protection to a specific scan within a specific window. eBay protects seller metrics only where valid tracking with an acceptance scan is uploaded within the stated handling time, according to eBay's published guidance on expected delivery dates.
Two elements of that sentence do the work. The acceptance scan is the requirement, not the tracking number, and the handling time is the deadline. If you print and upload a label on Monday and the carrier does not scan it until Thursday, eBay sees acceptance on Thursday.
Two implications follow. Label creation events, pre-advice and manifest records are not acceptance scans. And collection timing matters more than despatch timing, because a parcel sitting in your outbound area over a weekend is not accepted, whatever your warehouse system says.
Etsy
Etsy requires tracking for US and UK sellers and strongly encourages it in other markets, per Etsy's published seller help documentation. Its delivery estimate is built from two components: processing time plus transit time. Processing time is what you set; transit time is associated with the shipping method you choose.
If your processing time is optimistic, Etsy shows the buyer a date your operation cannot meet, and the tracking data will document the gap rather than excuse it.
Important note: where tracking is encouraged rather than required, uploading it is still the better choice. Tracking is how you evidence despatch in a dispute.
Walmart Marketplace
Walmart Marketplace sets a clear numerical bar. Sellers must achieve 90% or better on-time delivery under Walmart's Seller Performance Standards, as published in Walmart's shipping and fulfilment policy documentation.
Walmart's Expected Delivery Date is derived from four separately configurable inputs, a more granular model than most marketplaces publish.
- Cutoff time determines whether an order counts as received today or tomorrow.
- Lag time is your internal handling allowance before despatch.
- Operational days define which days you actually ship, so weekends and holidays are handled explicitly.
- Transit time is the carrier's committed duration for the chosen service.
Misconfiguring any one produces a promise date your operation was never going to meet. Sellers frequently discover their on-time problem was a settings problem: operational days left at a default including days the warehouse is closed, for instance.
How do the four marketplaces compare?
| Marketplace | Stated requirement | What the delivery promise is derived from |
|---|---|---|
| Amazon (seller-fulfilled) | OTDR below 90% triggers listing-level deactivation of worst-contributing ASINs, from February 28, 2026. Buy Shipping and Veeqo labels plus shipping settings automation confer protection. | Carrier delivery evidence. Valid Tracking Rate thresholds of 95% and 99% unconfirmed as of August 2026. |
| eBay | Valid tracking with an acceptance scan, uploaded within the stated handling time. | Expected delivery dates per eBay's guidance, with handling time set by the seller. |
| Etsy | Tracking required for US and UK sellers, strongly encouraged elsewhere. | Processing time plus transit time. |
| Walmart Marketplace | 90% or better on-time delivery under Seller Performance Standards. | Cutoff time, lag time, operational days and transit time. |
Reading the table honestly: the requirements are not equivalent even where the numbers look similar. Amazon's 90% and Walmart's 90% are computed by different platforms against differently constructed promise dates, so hitting one does not guarantee hitting the other. These requirements are settled and steady-state rather than new for 2026, except the Amazon listing-level change dated February 28, 2026.
Why is this harder than it looks?
Because there is no cross-carrier standard for tracking event codes. That is why two identical-looking parcels can produce entirely different compliance outcomes.
Universal Postal Union (UPU) standards govern the postal network only. S10 identifiers provide the standard item barcode format and M40 EMSEVT V3 defines standard event messages, but their scope is postal operators exchanging items with each other. UPS, FedEx, DHL and Amazon use proprietary code sets of their own design.
The consequence is that an acceptance scan is not one thing. Each network defines its own first event, at its own point in the process, with its own name.
Where this bites in practice
- The first scan means different things. One network's earliest event may fire when a label is created and data transmitted, another's when a driver collects, another's when the item is inducted at a sort facility. The gap can span days.
- Handover between networks creates blind spots. A parcel that starts with a consolidator and finishes with a national postal operator produces two event streams that do not share a vocabulary.
- Final delivery evidence varies in strength. Some networks produce a delivery event with time and signature detail, others a status change with far less behind it.
- Codes change without notice. Proprietary code sets are the carrier's property. They can be extended, renamed or retired, and integrations that pattern-match on raw codes break quietly.
This is the practical case for normalising events into one consistent model before using them for compliance. A tracking layer that maps proprietary codes to a common set of statuses, which is what Ship24 does across its courier and third-party logistics integrations, lets you ask one question across a mixed carrier book: has this parcel been accepted, and has it been delivered.
What should a multi-marketplace seller actually do?
Standardise internally, then map outward to each marketplace's definition. The mistake is running four separate compliance processes when the underlying data problem is the same.
- Normalise carrier events into one status model. Decide what "accepted" and "delivered" mean in your own system, then map each carrier's proprietary codes onto that model.
- Measure time-to-first-scan per carrier. This metric predicts eBay handling-time compliance and Amazon OTDR damage better than any other, and collection scheduling controls it.
- Audit the settings that build the promise date. Walmart's cutoff time, lag time and operational days, Etsy's processing time and your Amazon handling time all generate promises independently of your actual operation.
- Track coverage of protected label channels. For Amazon, the share of orders on Buy Shipping or Veeqo labels tells you how much of your OTDR exposure is mitigated.
- Flag orders with no movement, early. An order with no acceptance scan 24 hours after despatch is a problem you can still fix.
- Do not build to unconfirmed thresholds. Build headroom above confirmed requirements instead.
What is the honest conclusion here?
The rules are less about tracking and more about evidence, and sellers who understand that distinction outperform those who do not. Every requirement above reduces to the same demand: prove, through a third party the marketplace trusts, that you despatched when you said and delivered when you promised.
The genuine difficulty is not marketplace policy, which is mostly stable and documented. It is that the evidence arrives in mutually incompatible formats from networks with no obligation to agree with one another, and the UPU standards that could have solved this cover only the postal network. Cross-carrier normalisation is therefore the compliance layer rather than a convenience.
One final caution on figures. As of August 2026, the confirmed thresholds here are Amazon's 90% OTDR trigger for listing-level deactivation from February 28, 2026 and Walmart's 90% on-time delivery standard. The Amazon Valid Tracking Rate figures of 95% and 99%, and the reported 93.5% OTDR change from June 29, 2026, remain unconfirmed. Treat any operational plan built on an unsourced number as a plan built on nothing.
Sources & methodology
- eBay Expected delivery dates Primary platform documentation.
- Etsy Shipping and tracking help Primary platform documentation.
