Amazon seller-fulfilled handling time requirement: SKU checks before June 29

Amazon's latest US Seller Forums announcement says that, starting June 29, 2026, seller-fulfilled SKUs need handling times that match actual recent handling behavior. Sellers can use Automated Handling Time or maintain accurate SKU-specific handling times, but Amazon says it will monitor the seller-set route over a 30-day period.

For US sellers, and for UK sellers operating Amazon.com or comparing Amazon.co.uk fulfillment controls, the recovery risk is not only whether the setting changes. The risk is whether a rushed change creates late shipment, OTDR, A-to-Z, cancellation, or Prime promise evidence that the seller cannot explain later.

Short answer: map the affected SKUs first

The safest first step is to identify which SKUs actually depend on seller-set handling time. A broad account-level change can hide the difference between same-day stock, made-to-order products, weekend constraints, and items that should be paused until capacity is clear.

• Export active seller-fulfilled SKUs, current handling time, default handling time, SKU-specific overrides, shipping template, fulfillment channel, and inventory quantity.
• Mark made-to-order, custom, handmade, heavy, bulky, seasonal, and supplier-dependent SKUs separately before applying one rule to all offers.
• Compare the last 30 to 60 days of ship-by dates, actual label purchase times, first carrier possession scans, and late shipment defects.
• Separate Amazon.com orders from Amazon.co.uk or other marketplaces so US-only guidance is not copied into the wrong marketplace file.
• Pause or reduce exposure for SKUs that cannot be shipped consistently inside the promise shown to buyers.

Choose AHT only after testing the exception cases

Automated Handling Time can reduce manual monitoring and Amazon's announcement presents it as the recommended route. That does not mean every SKU is operationally ready for automation. Sellers should test the SKUs where historical speed does not represent future capacity, such as custom work, limited labor days, weather-sensitive products, or supplier-timed orders.

• Check whether AHT is enabled in Handling Time settings and whether the SKU has enough history for Amazon to manage the promise.
• If AHT is off, document why a seller-set handling time is accurate for that SKU rather than only more comfortable for the seller.
• Review order handling capacity, weekend cutoffs, carrier pickup days, and local holidays before trusting recent fast shipments as the new baseline.
• Keep a dated screenshot of the setting decision for each high-risk SKU or product group.
• Avoid deliberately delaying shipments only to train a metric; solve the promise and capacity mismatch instead.

Keep LSR and OTDR evidence separate

Handling time sits close to two different performance risks. Late Shipment Rate looks at whether shipment was confirmed after the expected ship date. OTDR looks at delivery against Amazon's promise record. The evidence for each risk overlaps, but it is not the same.

• For LSR, preserve the order date, ship-by date, shipment confirmation timestamp, first carrier scan, and any reason confirmation was late.
• For OTDR, preserve the promised deliver-by date, actual delivery event, shipping template, SSA status, AHT status, and Buy Shipping label record.
• If Amazon flags an offer, save the Account Health entry and Performance Notification before editing the SKU or template.
• If a label was bought through Amazon Buy Shipping, Veeqo, or another eligible path, record whether the service carried the protection label Amazon recognizes.
• If the carrier scan is missing or delayed, do not convert the case into a generic appeal before checking whether Amazon is measuring shipment confirmation or delivery.

Use the June window to build a control file

The June 29 date gives sellers time to fix the operating file before enforcement pressure turns into Account Health pressure. The useful file is not a long policy memo. It is a SKU table that shows promise, capacity, evidence, and owner for each risky offer.

• Create one row per risky SKU with current handling time, planned handling time, AHT decision, capacity reason, and date changed.
• Attach screenshots of Handling Time settings, Shipping Settings, shipping templates, and the affected SKU offer tab.
• Add order samples that prove the SKU can meet the promised handling time without relying on one unusually fast week.
• Name the person responsible for pausing the SKU when labor, inventory, carrier pickup, or supplier timing changes.
• Review the file weekly through July so early defects are caught before a performance notice arrives.

When this belongs on the late-shipment route

A handling-time cleanup is usually operational. It becomes a recovery issue when Amazon has already sent an Account Health notice, seller-fulfilled offers are at risk, LSR or OTDR is moving toward enforcement, or the seller cannot prove why the promise shown to buyers matched real capacity.

The practical closing test is whether the next reviewer can follow one line: this SKU had this handling-time promise, these orders show the real handoff pattern, this setting now matches capacity, and this control prevents late confirmation or missed delivery promises. If that line is still unclear, return to the late-shipment owner context before another template edit turns an operations fix into a performance case.