Quick answer: Late Shipment Rate asks whether the seller confirmed shipment by the expected ship date. Valid Tracking Rate asks whether shipments contain valid, recognized tracking with acceptable carrier events. On-Time Delivery Rate asks whether tracked units arrived by the promised date. A parcel can pass one and fail another, shipped on time but scanned late, or delivered on time but reported with the wrong carrier code.
A used-book seller dispatched 420 orders during a university textbook rush. His warehouse printed labels at 4:00 p.m. and placed USPS sacks on the loading dock for evening pickup. Most books arrived before the promised date. His Valid Tracking Rate fell anyway. The first carrier acceptance scans didn't appear until the following afternoon, several labels used a mail class mapped incorrectly by the shipping software, and a batch of orders was confirmed after the actual handoff because the confirmation job ran overnight. From his perspective, the operation was excellent, customers received books quickly. From the metric system's perspective, the event chain was incomplete and late. The business had optimized physical speed but ignored data speed.
The promise chain
A seller-fulfilled order moves through a sequence: the customer orders, the handling clock begins, the seller packs, the seller confirms shipment, the carrier accepts and scans, the carrier transports, and Amazon receives the event data. Each metric observes a different part of this chain.
Late Shipment Rate
LSR equals late-confirmed orders divided by total seller-fulfilled orders in the measurement window, times 100. It measures shipment confirmation relative to the shipping promise, not the delivery date. Common causes include handling time set too short, orders missed at cutoff, weekend or holiday calendar errors, and batch software failing to confirm orders on time. Shipping early doesn't compensate for other orders confirmed late, the objective is a consistent process.
Valid Tracking Rate
VTR measures whether eligible shipments contain valid tracking information that Amazon can recognize and use, generally expected above 95% for covered shipments, though categories and exemptions vary by marketplace. VTR is not merely "a tracking number was entered," the data must connect to the correct carrier, correct service, valid format, and timely confirmation with carrier scan events. A seller can paste a real tracking number and still fail if the carrier is selected as "Other," the number belongs to a different service, or Amazon can't associate the events correctly.
On-Time Delivery Rate
OTDR equals units delivered on or before promise divided by tracked seller-fulfilled units, times 100. Amazon's threshold remains 90%, and as of February 28, 2026, enforcement shifted to listing-specific deactivation rather than broadly deactivating every seller-fulfilled offer for one low score. Getting that narrower, listing-level protection requires actively configuring Shipping Settings Automation and Automated Handling Time, plus purchasing labels through Amazon Buy Shipping or Veeqo, sellers who haven't set these up before their OTDR dips below 90% don't benefit from the change. Listing-specific enforcement doesn't make OTDR unimportant, losing eligibility on the wrong group of fast-moving listings can still be commercially severe.
The metric comparison
| Metric | Main question | Seller controls | Common hidden failure |
|---|---|---|---|
| LSR | Did you confirm shipment on time? | Handling, cutoff, confirmation | Confirmation batch ran late |
| VTR | Is tracking valid and recognized? | Carrier code, tracking entry, method | Correct parcel, wrong carrier mapping |
| OTDR | Did it arrive by promise? | Promise, dispatch timing, service | Carrier delay or unrealistic promise |
Edge case: delivered on time, failed VTR
Reasons include the wrong carrier selected, tracking added after delivery, a missing first scan, or the order marked shipped through an unsupported workflow. Don't appeal VTR with only a delivery screenshot, show the order ID, promised ship date, confirmation timestamp, carrier selection, tracking number, first scan, and delivery event together.
Edge case: VTR is valid, but OTDR fails
The tracking is recognized and contains scans, but the package simply arrived after the promise. Possible causes include an overly aggressive transit time, a carrier service underperforming by postcode, or a promise built from an inaccurate shipping template. The fix isn't changing the tracking number, it's repairing the promise or the service selection itself.
Edge case: OTDR is good, but LSR fails
A seller may confirm shipment late while using a fast courier that still delivers before the customer promise, customers are happy, OTDR is good, and LSR is poor anyway. The system still sees the seller missing the ship-date process. Confirm shipment when physical handoff actually occurs, using an accurate automated workflow rather than a batch job that runs hours later.
Edge case: printing a label is not carrier acceptance
Some operations print labels in the morning and hand parcels over at night, or print Friday for Monday collection. A printed label creates a shipment-confirmation event without a physical carrier scan, and if the promise assumes same-day handoff, that first-mile gap can damage VTR or OTDR. Measure label-to-first-scan time (first carrier acceptance timestamp minus label creation timestamp) and track the median and 90th percentile by carrier and warehouse.
Edge case: shipping too quickly can distort automated handling time
Automated handling time learns from how long the seller usually takes to hand SKUs to carriers. Sellers have reported that unusually fast dispatch patterns can reduce calculated handling time, leaving less buffer on a slower day. The correct response isn't delaying good orders artificially, it's understanding the automated setting, applying SKU-specific overrides for products that genuinely need more time, and ensuring carrier scans reflect actual handoff.
Edge case: one postcode group destroys an otherwise strong OTDR
National averages hide regional failure. Segment OTDR by destination postcode, carrier, service, and warehouse. A seller with 97% national OTDR may have a 72% rate to remote regions, worth excluding unsuitable services or extending the promise for those routes specifically rather than treating the national number as representative.
A root-cause code for every failure
Use standardized codes: HT (handling time too short), CUT (cutoff or calendar error), CONF (shipment confirmation late), MAP (carrier or service mapping wrong), SCAN (first scan missing or late), TRANSIT (carrier transit delay), STOCK (inventory unavailable). Review the distribution monthly, if 60% of failures are SCAN, changing product handling time hides the symptom without fixing the actual handoff process.
A 48-hour metric incident response
Hours 0-2: export affected orders, separate LSR, VTR, and OTDR, and identify carrier and postcode concentration. Hours 2-8: pull label, confirmation, scan, and delivery timestamps, check integration logs, and contact the carrier for missing batch scans. Hours 8-24: adjust only the affected shipping templates or services and move urgent orders to a reliable service. Hours 24-48: measure whether new orders are receiving scans correctly and document the permanent corrective action.
EcomSanity can show sales, order, and profitability consequences when seller-fulfilled offers lose visibility or eligibility, but it doesn't replace Amazon's performance dashboards or carrier event records. A strong setup combines EcomSanity for commercial impact and ASIN prioritization, Amazon performance reports for official metrics, and a root-cause log for operational improvement.
Frequently asked questions
What is Amazon's on-time delivery rate requirement in 2026?
The threshold remains 90%, but as of February 28, 2026, enforcement shifted to deactivating only the specific listings contributing most to a low OTDR rather than the entire seller-fulfilled catalog, though accounts with consistently low performance can still face broader deactivation.
Can a package delivered on time still fail Valid Tracking Rate?
Yes. VTR isn't just about entering a tracking number, it requires the correct carrier selection, valid format, and recognized scan events. A real tracking number can still fail if the wrong carrier is selected, the number belongs to a different service, or Amazon can't associate the events correctly.
Does Amazon deactivate the whole account for low OTDR?
Not automatically as of the February 2026 update, which introduced listing-level enforcement instead. But getting that listing-level protection requires actively configuring Shipping Settings Automation and Automated Handling Time, plus purchasing labels through Amazon Buy Shipping or Veeqo, sellers who haven't set these up don't benefit from the narrower enforcement.