Amazon Late Shipment Rate: staying below 4% and keeping your listings.
Amazon’s Late Shipment Rate is one of three metrics that can suspend listings. 4% sounds generous, the 30-day rolling, 1-business-day calculation is not.
- Amazon’s LSR threshold is 4% on a 30-day rolling window, a single bad week can push you over the line for nearly a month.
- The clock starts when the carrier physically scans the package, not when you click “confirm shipment”, that gap drives most avoidable breaches.
- Through 2026, On-Time Delivery Rate at 90% is the metric with enforcement teeth, measured at listing level, not account level.
Halia alerts at 3% projected LSR, giving you 10–14 days to act before the real breach at 4%.
How Amazon calculates LSR.
Introduction to Amazon’s Late Shipment Rate (LSR)
Amazon’s Late Shipment Rate (LSR) is a critical performance metric for sellers fulfilling their own orders, directly impacting account health and eligibility for key selling features. This metric precisely measures the percentage of your seller-fulfilled orders for which shipment confirmation occurs after the expected ship date. It is calculated over both a 10-day and a 30-day rolling period, providing a continuous assessment of your fulfillment efficiency.
Impact and Penalties of a High LSR
To maintain good standing on the Amazon platform, sellers are required to keep their LSR below 4%. Exceeding this threshold can lead to significant penalties and negative impacts:
- Deactivation of your seller-fulfilled offers
- Suspension of your Fulfilled by Merchant selling privileges
- Increased A-to-z Guarantee claims
- Negative feedback
- Heightened customer contact rates
- Suppressed Buy Box eligibility (even above 2%)
- Reduced organic visibility, forcing greater reliance on paid advertising
Understanding the Expected Ship Date
The “expected ship date” is determined by Amazon based on several factors:
- The handling time you specify for your products (account level or individual SKUs)
- Your specified operating days, including any weekends you enable
- Your daily order cut-off times
For instance, an order placed after your designated cut-off time will be expected to ship on the next business day. Amazon also adjusts expected ship dates to account for national holidays. As of June 29, 2026, Amazon is implementing a requirement for sellers to maintain accurate handling times that consistently match their actual shipping speed, with Amazon potentially adjusting these on your behalf if discrepancies are found.
The True Definition of “Shipped” by Amazon
A critical detail that often catches sellers off guard is Amazon’s definition of “shipped.” An order is not considered shipped when you print the shipping label or click “confirm shipment” in Seller Central. Instead, it is deemed shipped only when the carrier physically scans the package. This means if you print a label late in the afternoon but the carrier doesn’t perform the initial scan until the following business day, that order will count as a late shipment, even if your internal records show it was processed on time. To avoid this common pitfall, it’s essential to:
- Coordinate closely with your carriers to ensure timely pickups and scans
- Consider using carrier scan forms for bulk drop-offs
- Factor in carrier cut-off times when setting your own order processing deadlines
- Regularly monitor your LSR in the Account Health dashboard for proactive adjustments and to maintain reliable late order fulfillment performance
Why the 4% threshold is harder than it sounds.
The math seems forgiving, 4% of orders can ship late before any consequence. The catch is the rolling window.
Typical causes of LSR breach:
- Weekend orders shipping Monday vs. Tuesday based on warehouse coverage
- Holiday volume spikes against fixed 3PL capacity
- Supplier replenishment delays causing manual back-order workflows
- Sleep-mode automation where a missed cron pushes 30+ orders an hour late
Late Shipment Rate vs On-Time Delivery Rate: the 2026 shift.
LSR is no longer the metric with the most weight. Through 2026, Amazon has moved enforcement toward On-Time Delivery Rate (OTDR), which measures whether tracked seller-fulfilled units actually reached the customer by the promised date, not just whether they left your warehouse on time.
ship on time
deliver on time
window
level (2026)
What you measure to stay below it.
The visible metric in Seller Central is the trailing LSR. The metric you want to manage is the leading indicator: ship-confirm timing variance against expected ship date, broken down per warehouse and per channel.
The 95th percentile matters more than the median. The median tells you the typical order. The 95th percentile tells you whether your tail is getting late enough to threaten the rate.
What to do when you breach.
Once your LSR crosses 4%, lengthen handling time temporarily. Bumping from 1-day to 2-day handling reduces the late-confirm rate immediately, even though it costs conversion. The wrong move: silently ship-confirming early to beat the clock. Amazon’s carrier-handoff tracking can detect when ship-confirm timestamps don’t match real carrier scan events, the consequence is an Account Health violation that compounds with the LSR breach.
How to reduce your Late Shipment Rate.
- Turn on Shipping Settings Automation and Automated Handling Time. Amazon uses these signals to build delivery promises it trusts, and they protect you when the carrier, not you, causes the delay.
- Set an honest handling-time buffer. A realistic 2-day promise you keep 99% of the time beats a 1-day promise you miss twice a week.
- Buy OTDR-protected labels through Amazon Buy Shipping. Labels bought through Buy Shipping carry delivery-performance protection.
- Treat carrier choice as a performance decision. The cheapest carrier that scans a day late is the most expensive one you have.
- Confirm shipment only when it is real. Tie ship-confirm to the actual handoff or first carrier scan, not to a print job.
How
Halia catches it early.
Halia ingests your Amazon Selling Partner API events and watches Order created → ship-confirm timing in real time. When your projected 30-day LSR crosses 3%, you get a finding with the specific orders driving the regression, usually traceable to a specific weekday, warehouse, or SKU range.
Amazon LSR questions, answered.
What is Amazon's Late Shipment Rate threshold?
Amazon’s policy threshold is 4%. Above 4% your Account Health shows a warning. Above 10% sustained, account suspension is a real risk. The metric is calculated as a 30-day rolling rate, so a single bad week can put you over the threshold for nearly a month.
Does LSR apply to FBA orders?
No. LSR only applies to seller-fulfilled orders (FBM and Seller-Fulfilled Prime). FBA orders are Amazon’s responsibility once they’re in the FBA network, those carry different metrics (Out-of-stock rate, In-stock rate) that you don’t control directly.
How do I view my current LSR?
Seller Central → Performance → Account Health → Customer Service Performance. The dashboard shows your 30-day rolling LSR with a trailing trend chart. Refreshes daily.
Can I appeal an LSR-driven suspension?
Yes, but the appeal must include a Plan of Action describing root cause, immediate corrective action, and prevention. Amazon expects specifics, “we hired more warehouse staff” doesn’t pass; “we added 2 staff on Tuesday/Thursday based on our analysis of day-of-week variance” does.
Why is my On-Time Delivery Rate failing when my Late Shipment Rate looks fine?
LSR checks whether the order shipped on time; OTDR checks whether it was delivered on time. A clean LSR with a failing OTDR almost always means the carrier is delivering late after a timely handoff, a carrier problem rather than a warehouse one. Amazon's 90% OTDR threshold is now the stricter of the two, and since February 2026 it deactivates listings at the item level.
How quickly can I bring LSR back below 4% after a breach?
The 30-day rolling window means about 30 days of clean performance. Bumping handling time from 1-day to 2-day on the listing is the fastest tactical lever, it reduces late-confirms immediately. Once back below 4%, you can return to 1-day handling.
Related guides.
Build a carrier scorecard
Four metrics, data sources, and the QBR script for flagging late patterns before they hit Account Health.
Guide · 7 minDrift detection vs dashboards
Why standard KPI dashboards miss trending metrics, and how drift detection catches a breach before it happens.
IndexAll operator playbooks
The full Instirio resource library, metrics, carrier SLAs, 3PL costs, and fulfillment analytics.
See these patterns on your store.
Connect in 5 minutes. First findings the same day. Free under 500 orders/mo.
Start free →