Late Shipment Rate (LSR) is one of the more punishing Account Health metrics for FBM sellers. Cross the threshold for too long and your selling privileges get reviewed, your Buy Box eligibility drops and your account ends up on Amazon’s watch list. The math is simple. The data feeding it is where most issues hide.

This guide explains how Amazon calculates LSR, what counts, and how to monitor it daily.

TL;DR: Late Shipment Rate measures the percentage of FBM orders confirmed shipped after their promised ship-by date. Amazon’s threshold is 4% over rolling 10-day and 30-day windows. The metric only applies to seller-fulfilled orders, not FBA. The data feeding it is your ship confirmations, the order ship-by dates Amazon assigns, and your tracking submissions. Monitoring leading indicators — carrier delays, warehouse staffing, weekend volume — catches problems before LSR moves.

How Amazon calculates LSR

LSR = Orders shipped after promise date ÷ Total FBM orders shipped

Calculated over rolling 10-day and 30-day windows. Both have to stay under threshold (typically 4%).

Counts:

• FBM orders only — FBA shielded.
• Ship confirmation timestamp later than the promise date.
• Both standard and expedited orders.

Does not count:

• FBA orders (Amazon handles those).
• Cancelled orders.
• Orders pending shipment (not yet confirmed).

Where the data feeding it lives

• Order detail report — contains promise date per order.
• Ship confirmation timestamps — when you sent the shipment confirmation through SP-API.
• Carrier tracking data — sometimes used by Amazon to validate the actual ship date.

Amazon defaults to your confirmation timestamp. If you confirm late but the carrier scan shows the package was actually shipped on time, you can dispute the late status.

Common causes of LSR drift

Late ship confirmations

Most common cause. The package shipped on time but the confirmation submission lagged — often a workflow bottleneck in your warehouse.

Carrier delays misattributed

Carrier picked up late, you confirmed late as a result, even though it was their fault.

Weekend ship cutoffs

Orders coming in late Friday with same-day promise can ship Monday and miss the window.

Holiday volume spikes

Q4 and major holidays. More orders, same staff, more late confirmations.

How to monitor leading indicators

Daily LSR is too lagging to catch issues before Amazon flags them. Better signals to track:

• Confirmation lag — average time between order receipt and ship confirmation. Trending up = warning.
• Same-day-of-week confirmation rate — percent of orders received on day X confirmed by promise date.
• Carrier-specific delay rate — if one carrier is consistently late, switch volume.
• Order volume vs warehouse capacity — if orders per day are climbing faster than fulfillment capacity, LSR will follow.

How to dispute LSR violations

If LSR is flagged but you have evidence the package shipped on time:

• Carrier tracking with ship-date scan can override Amazon’s ship confirmation timestamp.
• Open a case with documentation — tracking number, carrier scan timestamp, original promise date.
• Resolved cases adjust the metric retroactively.

The bottom line

LSR is technically a percentage, practically a workflow problem. Sellers with reliable confirmation processes, smart carrier choices and demand-aware staffing rarely have LSR issues. Sellers with broken workflows find out when they get the warning email.

DataDoe’s Amazon data layer joins order data, ship confirmation timestamps and carrier tracking so leading indicators of LSR drift surface in dashboards and alerts.