Amazon OTDR listing deactivation: seller-fulfilled checks before you appeal

Amazon's 2026 OTDR update changed the practical risk for seller-fulfilled offers. In the US announcement, Amazon said that from February 28, 2026, it would usually deactivate only the seller-fulfilled listings that most affect a seller's on-time delivery rate instead of deactivating every seller-fulfilled listing at once.

That sounds narrower, but it still needs careful triage. US and UK sellers should not answer an OTDR notice with a generic late-shipment appeal. The better first step is to separate the affected ASINs and SKUs, the promised delivery dates, the carrier events, the shipping-template settings, and the exact Account Health route Amazon is using.

Short answer: find the listing-level risk first

The useful question is not only whether the carrier was late. It is whether Amazon is reviewing one seller-fulfilled listing, a group of high-impact listings, or the seller's broader ability to list seller-fulfilled products.

• Save the email, Account Health entry, Performance Notification, marketplace, ASINs, SKUs, order IDs, and response or review date.
• Check whether Amazon labels the reason as Order Performance - On time Delivery Rate or uses a broader performance warning.
• Export the OTDR or delivery defect report before editing templates, handling times, or shipping methods.
• Separate standard shipping, Seller Fulfilled Prime, premium shipping, and cross-border seller-fulfilled orders.
• Identify whether the risk is one listing, repeated OTDR failure, or a significantly low account-level OTDR.

Rebuild the deliver-by evidence

Amazon's OTDR FAQ says the report looks at tracked seller-fulfilled units delivered on or before the seller-promised deliver-by date, using a 14-day window with a delay for orders still in delivery. That means the evidence packet should start with the dates Amazon measured, not only with the date the seller handed the package to the carrier.

• Record the order date, ship-by date, promised deliver-by date, actual carrier delivery date, and time zone shown in Seller Central.
• Preserve the first possession scan, in-transit scans, delivery scan, proof of delivery, and any carrier disruption notation.
• Compare the promised date in Seller Central with the delivery date the customer saw only after you know which date Amazon used for OTDR.
• For low-volume sellers, check whether the measured period has enough orders for the requirement to apply.
• For international seller-fulfilled delivery, document the transit-time setting and any customs or cross-border handoff separately from domestic carrier proof.

Check whether the order had OTDR protection

For standard shipping, Amazon's US guidance points sellers to three controls: Shipping Settings Automation, Automated Handling Time, and an OTDR Protected label bought through Amazon Buy Shipping, Veeqo, or another eligible Buy Shipping path. Seller Fulfilled Prime and premium shipping have a different protection setup, so do not mix the evidence.

• Confirm whether the shipping template used Shipping Settings Automation and showed transit time as managed by Amazon.
• Check whether Automated Handling Time was enabled for the relevant standard-shipping orders.
• Save the Buy Shipping, Veeqo, or integrator label record showing whether the service was marked OTDR Protected or Late Delivery Risk.
• If the label was bought outside Amazon's protected path, do not claim protection unless Amazon's current workflow supports that carrier and service.
• For UK seller-fulfilled orders, keep Amazon.co.uk OTDR policy evidence, carrier service, and delivery-promise records separate from US-only assumptions.

Do not merge OTDR with every performance metric

OTDR sits near Late Shipment Rate, Valid Tracking Rate, Order Defect Rate, A-to-Z claims, and cancellation risk, but each metric answers a different question. A strong response names the metric Amazon is actually enforcing before attaching evidence for adjacent problems.

• Use OTDR language when the core issue is delivery by the promised date.
• Use Late Shipment Rate language when the core issue is confirming shipment after the expected ship date.
• Use Valid Tracking Rate language when Amazon is testing whether tracking was valid, scanned, and carrier-recognized.
• Use A-to-Z or Order Defect Rate language when buyer claims, negative feedback, or claim funding are the real account-health issue.
• Use ASIN listing language only when Amazon has deactivated specific offers or listings rather than only warning about fulfillment capability.

When this belongs on the late-shipment owner route

An isolated OTDR listing warning may be solved by the Account Health path Amazon gives for the affected listing. It becomes a broader performance recovery issue when several seller-fulfilled listings are at risk, the same carrier or template keeps producing late delivery, Buy Shipping protection is inconsistent, or the account is already carrying LSR, VTR, ODR, or A-to-Z pressure.

The practical closing test is whether a reviewer can follow four facts quickly: which listing Amazon is measuring, which promise date was missed, whether the order used the protected shipping path, and what setting or carrier-control change prevents the same OTDR pattern. If one of those facts is still unclear, return to the late-shipment or performance owner context before another appeal turns a listing-level warning into an account-wide performance case.