
Audit FBM handling time before Amazon manages it for 180 days
Amazon now tests whether each FBM SKU's configured handling time matches its actual ship speed. Here is how to choose AHT or manual control without creating a late-shipment problem.
By WAYAMZ Team
Padding an FBM handling time used to look like cheap insurance. A team that normally shipped in one day could promise two and preserve room for a bad Monday.
That gap is now a control Amazon measures. Since June 29, 2026, Professional sellers have been required to keep the configured handling time for seller-fulfilled SKUs consistent with actual shipping speed. The risk is not a single early parcel. It is a recurring pattern in which the promise is slower than the operation.
The rule is about accuracy, not simply speed
Handling time runs from order placement to carrier handoff. Transit time starts after that handoff. Amazon uses both to calculate the delivery date shown to the shopper, so adding an extra handling day makes the offer look slower before the carrier is evaluated.
Amazon says more than 87% of US seller-fulfilled orders are handled within one day and claims that a one-day improvement in promised delivery time produces an average 5% sales increase. Treat that as an aggregate observation, not an ASIN forecast; price, offer position, location, carrier coverage, and category can change the result.
The requirement applies to Professional sellers. Amazon’s current help page exempts qualifying custom products, registered Amazon Handmade products, perishables, and less-than-truckload products weighing at least 150 pounds. An unusual operation is not automatically exempt; confirm the exact criteria in the account.
Map the control path for every FBM SKU
Amazon offers two paths. Automated Handling Time, or AHT, uses recent shipping history by SKU. With enough history, it overrides both the account default and a manually entered SKU value. New or thin-history SKUs can retain the manual value or automated default until history is sufficient.
The manual path remains available, but it creates a monitoring duty. Amazon reviews a SKU over 30 days. If the SKU is consistently shipped at least one day faster than its configured time, Amazon can mark it non-compliant. The seller then has 30 days after notification to set an accurate time. If that does not happen, Amazon says it will adjust the SKU for the next 180 days, provide Late Shipment Rate protection for the SKU it updated, and prevent the seller from changing that handling time during the period.
The announcement does not publish the minimum order count or the statistical threshold behind “consistently.” Sparse SKUs therefore need more caution, not invented precision. Keep the order-level evidence and read the notice Amazon actually sends.
Do not solve this by shipping later
Holding a ready order until the final ship-by day preserves padding on paper while making the customer wait. The team starts optimizing for the setting instead of matching the setting to the team.
Keep shipping when the parcel is ready. If the normal operation is one day, set one day or let AHT recognize it. If the operation is genuinely variable, identify why: production, personalization, pickup coverage, warehouse closures, inventory transfers, or volume spikes. Then place the control at that constraint rather than hiding every case inside a longer blanket promise.
AHT is useful when recent history represents the operation you expect to keep. Manual control is more defensible when a known process change or a qualified exception makes history misleading. Amazon says an AHT recommendation can take up to three weeks to reflect a faster process; its faster-handling option can honor a shorter seller-set time, but the affected SKUs lose AHT’s LSR and On-Time Delivery Rate protection. That is a trade, not a free override.
Treat capacity and cutoffs as separate controls
Handling time cannot compensate for an unconfigured operating calendar. Verify the cutoff displayed in Shipping settings, the business days for each location, and the real carrier pickup. Same-day handling makes orders before the configured cutoff due for shipment that day; a one-day promise generally makes the next business day the ship-by date.
Set order handling capacity as a surge valve. Amazon says orders above the configured capacity receive one additional handling day. That is more truthful than slowing every order all year. Match the limit to demonstrated pack-out capacity and test what happens when orders cross it.
Finally, close the confirmation gap. Amazon defines a shipment as late when confirmation is missing after the expected ship date, even if the box physically left on time. LSR is measured over 10- and 30-day periods, applies to seller-fulfilled orders, and must stay below 4%. Carrier handoff, confirmation, and valid tracking therefore belong in the same control.
Build the evidence packet before the notice arrives
Download the Handling Time Report and create one row per marketplace and SKU. Record the configured mode, configured days, order volume, actual handoff distribution, fulfillment location, cutoff, pickup schedule, capacity setting, exception status, and any Amazon notification date. Add an owner and the next review date.
Review high-volume SKUs weekly. Segment new and low-volume SKUs so one unusual week is not narrated as a stable capability. Mark planned closures, carrier failures, system outages, and temporary labor changes, but do not use anecdotes to overrule a sustained pattern.
If a notice arrives, preserve the before state, the orders behind the pattern, the chosen correction, and the timestamp of the change. The objective is not merely to avoid Amazon’s 180-day management window. It is to know which promise was live, why it was supportable, and whether the new promise improved conversion without pushing late shipments toward the 4% boundary.
The Operator Read
Amazon has turned handling time from a comfortable account default into a SKU-level accuracy requirement. That does not mean every seller should switch on AHT blindly, and it does not mean every early shipment is a problem.
It means the control now needs an owner. Use AHT where history is representative. Keep manual settings where variability is real and reviewed. Put surge risk into capacity, calendar risk into cutoffs, and carrier risk into the transit plan. Then ship the order when it is ready.
The wrong buffer is an extra day nobody can explain. The right buffer is a measured constraint with evidence, an owner, and a rule for when it changes.
The Operator Brief
One email a week, operator's cut.
The week's sharpest Amazon signals from the journal — policy changes, fee math, and the data reads worth acting on. No spam, unsubscribe anytime.