Amazon FBM Offer Deactivation (Aug 31, 2026): Good News With a Math Problem

TL;DR

Since August 31, 2026, Amazon has been temporarily deactivating individual Fulfilled by Merchant offers that put your Account Health at risk, instead of putting your whole account at risk. Four metrics are in scope: Cancellation Rate, Late Shipment Rate, Order Defect Rate, and On-Time Delivery Rate. You get a warning email first, and deactivated offers appear under Other Policy Violations in the Account Health dashboard.

For a seller who moves real volume on every SKU, this is close to pure good news. For a catalog with a long tail, it moves enforcement from a forgiving denominator to a brutal one. A single A-to-z claim on a SKU that sold nine units in 60 days is not a 0.05% defect rate anymore. It is 11%.

The Question You're Actually Asking

Not "what did Amazon announce." You've read that part. The question is whether this makes your business safer, or just moves the risk somewhere your dashboard doesn't show it.

The answer depends almost entirely on one number most sellers haven't looked at: how many orders each individual FBM SKU generates inside each metric's measurement window.

Amazon's performance thresholds are percentages. Percentages behave completely differently when the denominator drops from "every order in the account" to "every order for this one offer." That shift is the whole story, and the announcement doesn't address it.

What Amazon Actually Said

The announcement, titled "Review Account Health updates for FBM offers," went up in Seller Central's News and Announcements forum with an effective date of August 31, 2026. It has been in force ever since.

The mechanics: if an FBM offer puts your Account Health at risk, Amazon temporarily deactivates that offer. Previously, listings that missed required metrics put the entire account at risk. Now only the affected offer goes down, and your other listings and overall Account Health are not impacted.

You receive a warning email before deactivation, with the issue and the steps to fix it. Deactivated offers appear in the Account Health dashboard under Other Policy Violations, along with reactivation instructions.

This isn't a new idea for Amazon. On February 28, 2026, it stopped deactivating every seller-fulfilled listing when On-Time Delivery Rate fell below 90%, and began removing only the listings dragging the metric down. August extends that approach from one metric to four. One caveat carried over from February: Amazon kept the right to deactivate all seller-fulfilled listings when performance is severely or repeatedly below target. Containment is the default, not a guarantee.

What Amazon still hasn't said: how long "temporarily" lasts, how far ahead the warning email arrives, whether a minimum order volume applies before an offer is evaluated, and what thresholds apply at the offer level. The announcement links to the four metric help pages but no help page for the new enforcement behavior itself. Sellers in the thread also pointed out that the post appeared on or around the effective date, which they argue falls short of the notice period in the Business Solutions Agreement.

The Denominator Problem

Here's the arithmetic that changes how you should read this policy.

Amazon hasn't published separate offer-level thresholds. The most literal reading of the announcement, and the safest one to plan around, is that the published account-level thresholds now apply to each offer. Under that reading, here is the minimum order count a single SKU needs inside the measurement window to absorb exactly one defect and stay compliant.

Read the ODR row again. To keep a single offer under 1% after one A-to-z claim, chargeback, or piece of negative feedback, that offer needs more than a hundred orders in 60 days. That's a real product for most sellers. It isn't most SKUs in most catalogs.

The short windows are their own problem. Cancellation Rate runs on 7 days. A SKU needs 41 orders in a single week before one cancellation stops breaking the threshold, which almost no long-tail SKU will ever do.

The uncomfortable version: at the account level, one negative feedback across 2,000 orders is noise. At the offer level, on a SKU doing 15 units a month, the same event is a 3.3% defect rate against a 1% threshold.

Peak season cuts both ways here. Holiday volume fattens the denominator on your top sellers, but carrier delays rise at the same time, which pushes Late Shipment and On-Time Delivery in the wrong direction on exactly the SKUs that didn't get a volume bump.

None of this makes the policy bad. Containment is genuinely better than account-wide exposure, and for a seller with one problem ASIN out of 500, this change may save the business. It does mean "my Account Health is green" is no longer a sufficient answer. Account-level averages now hide the exact SKUs most likely to trip.

The Audit: Find Your Thin SKUs Before Amazon Does

This takes about an hour. If you're also working through the peak-season calendar, our Q4 2026 deadlines guide covers the dates this audit should fit around.

1. Pull 60 days of FBM order data by SKU. Reports, then Order Reports, filtered to merchant-fulfilled. You want one row per SKU with an order count.

2. Bucket every SKU against the table above.

• Fat: 101+ orders in 60 days. Behaves the way it always did. One defect is survivable on every metric.
• Thin: roughly 10 to 100 orders. May survive one late shipment, but does not survive one ODR event.
• Fragile: under 10 orders. A single defect of any kind breaks at least one threshold, possibly all four.

3. Score the thin and fragile buckets for defect exposure, not for sales. Which ship from a supplier who has stocked out before? Which are heavy, breakable, or shipped through a carrier with a weak delivery record in your data? Which have handling times you set two years ago and never revisited? Those are your candidates, not the ones with the lowest revenue.

4. Pick one intervention per flagged SKU.

• Make the handling time honest, or automate it. Padding handling time used to be the easy buffer. It isn't anymore: since June 29, 2026, Amazon flags SKUs that consistently ship at least a day faster than their stated handling time, gives you 30 days to fix it, and then sets it for you. Set a handling time you actually hit, or turn on Automated Handling Time, which Amazon pairs with Late Shipment Rate protection.
• Use Buy Shipping with an integrated carrier. Tracking, on-time status, and shipment confirmation become data Amazon generates rather than data you have to defend. In the February OTDR change, Buy Shipping labels were part of the protection rules. Amazon hasn't said whether the same protections apply under the August policy.
• Move it to FBA. Shipping-side metrics stop being yours. For a genuinely fragile SKU with unreliable supply, this is often the honest answer. Run the numbers first with our FBA calculator.
• Retire it. A SKU doing four units a month with a flaky supplier isn't worth a policy violation record. Ending the offer on your terms costs nothing.

5. Set per-SKU alerts, not account alerts. Whatever tool you use, the trigger needs to be at the offer level now. If your only monitoring is the Account Health dashboard, you're watching the number this policy specifically stopped moving.

6. Make sure the warning email lands somewhere a human reads. The whole protective value of this policy is the warning that comes before deactivation. Check the notification address in Seller Central and confirm it isn't a shared inbox nobody opens.

Two Neighboring FBM Rules to Check While You're in There

Handling time accuracy (live since June 29, 2026). Covered above. Any SKU you pad for safety is now a SKU Amazon may re-time for you.

Business Hour Delivery Rate (enforcement October 30, 2026). For FBM shipments to Amazon Business customers, Amazon expects 90% or more delivered within the buyer's business hours. Sellers still below that on October 30 can have their seller-fulfilled offers deactivated for Amazon Business buyers. Regular retail offers and FBA offers aren't affected. Check it in Account Health alongside the four metrics above.

What This Does Not Change

Offer-level enforcement applies to those four performance policies. It doesn't extend to intellectual property complaints, authenticity claims, review manipulation, related account allegations, restricted products, verification failures, or Section 3 enforcement. Those remain account-level actions with account-level consequences.

It also does nothing about the critique several sellers raised in the thread: an order defect is usually an order problem, a carrier problem, or a one-off customer problem, and attributing it to the SKU is a modeling choice rather than a diagnosis. That critique stands. It just isn't a reason to skip the audit.

FAQ

When did Amazon's FBM offer deactivation policy take effect?

August 31, 2026, per Amazon's Seller Central announcement. It is in force now.

Which metrics can get a single FBM offer deactivated?

Cancellation Rate, Late Shipment Rate, Order Defect Rate, and On-Time Delivery Rate.

Will Amazon warn me before deactivating an offer?

Amazon says yes. You should receive an email identifying the issue and the steps to resolve it. Amazon hasn't said how far in advance it arrives.

Where do I find a deactivated offer?

Account Health dashboard, then Other Policy Violations. Reactivation instructions appear there.

How long does a deactivation last?

Amazon says "temporarily" and has not published a duration or a reinstatement timeline.

Does each offer get judged against the normal thresholds?

Amazon hasn't published offer-level thresholds. Planning as if the account-level thresholds (ODR under 1%, Cancellation under 2.5%, Late Shipment under 4%, OTDR 90% or higher) apply per offer is the safe assumption.

Does a minimum number of orders apply before an offer is evaluated?

Amazon hasn't stated one. Until it does, assume low-volume SKUs are in scope.

Can I just pad my handling time to avoid late shipments?

Not safely anymore. Since June 29, 2026, Amazon flags SKUs that consistently ship at least a day faster than their stated handling time and will set it for you if you don't correct it within 30 days. Automated Handling Time is the safer route.

Does this mean Amazon has stopped suspending accounts?

No. It applies to four FBM performance policies only. Account-level action still applies to IP, authenticity, verification, related accounts, restricted products, and Section 3 matters, and Amazon can still act on all seller-fulfilled listings when performance is severely below target.

Does this affect FBA offers?

The announcement covers Fulfilled by Merchant offers. FBA sellers aren't responsible for the shipping-side metrics in scope, though every other Account Health risk still applies.

Should I move my low-volume SKUs to FBA because of this?

For SKUs with unreliable supply or shipping, it's a reasonable response, since it takes cancellation and shipping metrics off your plate. For everything else, honest handling times and Buy Shipping usually give you enough buffer at lower cost.

Bottom Line

Amazon replaced a catastrophic risk with a smaller, more frequent one. That's a good trade for almost every seller, and it's worth saying so.

But smaller and more frequent means it now lands on SKUs that used to be statistically invisible, and it lands fast, because percentage thresholds are savage when the denominator is nine. The sellers who get hurt by this policy will be the ones whose Account Health stayed green the entire time.

Run the order count by SKU. Find out which offers are one bad Tuesday away from going dark. Then decide, deliberately, which ones you're willing to lose. If you'd rather have a team watch your Account Health at the offer level, that's part of our Amazon account management.