Amazon Deactivates One Bad FBM Offer, Not Your Account
A single failing FBM offer can now be turned off on its own. Here are the four policies that trigger it and how to get the offer back before it drags Q4 revenue.

On this page
- Quick Answer
- What Actually Changed
- The Four Trigger Policies
- Offer-Level vs Account-Level Risk
- What Amazon Has Not Explained
- Why Low-Volume Sellers Should Worry
- Set Up Early-Warning Monitoring
- Reinstate a Deactivated Offer
- Protect Q4 When a SKU Goes Dark
- Build Your Evidence File
- Your This-Week Checklist
- Conclusion
- References
Quick Answer
As of August 31, 2026, Amazon changed US Account Health enforcement so it can temporarily deactivate a single failing FBM offer instead of putting your whole account at risk. Four performance policies can trigger this offer-level action: Cancellation Rate, Late Shipment Rate, Order Defect Rate, and On-Time Delivery Rate.
- Only the affected offer is deactivated. Your other listings stay active.
- Amazon sends a warning email first that should name the issue and give steps.
- A deactivated offer shows up under Other Policy Violations in Account Health.
- Fix the cause, follow the reactivation path, and keep the case record.
This is a real shift in how FBM risk works. For years, missing your required fulfillment metrics could threaten the entire account. Now Amazon can isolate the problem to one offer. That lowers the suspension risk of running FBM. But it also means you need to spot a deactivated offer fast, because a dark SKU in Q4 is lost revenue every hour it stays down.
Below is the plain version: what changed, the four policies to watch, what Amazon has not told us, and a step-by-step plan to get an offer back on before it hurts.
Reviewed by the SellerShorts editorial bench, which tracks Amazon Account Health and fulfillment policy changes for FBM and FBA sellers. Metric definitions and thresholds are login-gated in Seller Central, so verify current numbers against Amazon's live help pages before you rely on any figure.
What Actually Changed
Amazon updated US Account Health enforcement for Fulfilled by Merchant offers. The core of it: an underperforming FBM offer can now be temporarily deactivated on its own. The rest of your catalog and your overall Account Health stay active.
- The change applies to US Account Health enforcement for FBM offers.
- Amazon can temporarily deactivate a single failing offer instead of risking the whole account.
- The change is effective August 31, 2026.
- Amazon does not state that every metric breach triggers immediate deactivation.
In simple terms, the penalty got more surgical. One bad offer no longer has to drag the whole account down with it. That is good news. The catch is that you now have more small fires to watch instead of one big one.
The Four Trigger Policies
Amazon names four performance policies that can trigger the offer-level action. These are the fulfillment metrics you already know. The difference is the consequence now lands on a single offer.
| Trigger policy | What it measures (verify current definition in Seller Central) |
|---|---|
| Cancellation Rate | Seller-initiated cancellations before shipment. |
| Late Shipment Rate | Orders confirmed as shipped after the expected ship date. |
| Order Defect Rate | Orders with a defect such as a claim, chargeback, or negative feedback. |
| On-Time Delivery Rate | Orders that reach the buyer by the promised delivery date. |
These four are the named triggers. The policy pages define the underlying metrics, but they do not define the new offer-selection method. Amazon also revised several fulfillment measures during 2026, so older thresholds you have in your head may be outdated. Confirm the live numbers before you trust them. If you want a refresher on how these tie together, read our breakdown of the Account Health metrics that matter.
Offer-Level vs Account-Level Risk
The old framing, in Amazon's own words, was that missing required metrics could put the entire account at risk. The new system only deactivates the affected offer while other listings stay active. Here is the side by side.
| Aspect | Prior system | New system (from Aug 31, 2026) |
|---|---|---|
| Scope of action | Whole account at risk | Only the failing FBM offer |
| Other listings | Exposed to account-level risk | Stay active |
| Overall Account Health | Could be dragged down | Stays intact |
| Where it shows | Account-level warnings | Other Policy Violations, per offer |
The description of the old system is Amazon's own framing, so treat it as context, not a precise legal record. The practical takeaway is clear enough: the blast radius shrank.
What Amazon Has Not Explained
Be honest about the gaps. Amazon left several important pieces undefined, and you should plan around the uncertainty rather than assume the best case.
- Amazon did not define how it selects the affected offer when metrics are tracked across many orders and time windows.
- Amazon did not publish an offer-level trigger threshold.
- Amazon did not state the amount of advance warning it gives.
- Amazon did not state the duration of a temporary deactivation.
- Account-level metric thresholds do not necessarily explain the new offer-selection method.
- Amazon has not said whether it uses minimum-order requirements, confidence thresholds, or other safeguards before deactivating an offer.
One more thing worth naming: an unavailable offer is expected to stop serving ads. Amazon has not confirmed that as policy, so treat it as a reasonable expectation, not a promise. Either way, check your campaigns when an offer goes down.
Why Low-Volume Sellers Should Worry
If you sell low-order-volume SKUs, this change carries a hidden edge. One defect on a handful of orders creates a far higher percentage than one defect on thousands of orders. That concentration can push a niche SKU past a threshold fast.
- A single A-to-z claim on a 5-order SKU is a huge percentage. The same claim on a 5,000-order SKU is noise.
- Amazon has not said whether it applies a minimum-order safeguard before it acts.
- SKU-level handling-time settings can create delivery promises some products cannot meet, which raises your late and on-time risk.
Seller objections that late shipments, carrier delays, or claims are not really properties of a single SKU are anecdotal. They may feel fair, but they are not proof the attribution is wrong. Plan for the system as it is, not as you wish it were. If you are still deciding how to fulfill, our guide on FBA vs FBM lays out the trade-offs.
Set Up Early-Warning Monitoring
The warning email is your first signal, and you do not know how much time it buys you. So build a system that catches trouble before Amazon does and that reacts the second an email lands.
- Build a weekly FBM exception report by SKU. Cover seller cancellations, late confirmations, promised vs actual delivery dates, A-to-z claims, chargebacks, and negative feedback.
- For each order, record the carrier, service level, warehouse or 3PL, and the Amazon delivery promise shown at purchase.
- Set an alert on the warning mailbox and assign one person the authority to open the Account Health case. No debate, no waiting.
- Align your catalog-wide handling-time defaults with SKU-level realities so you stop making promises you cannot keep.
- Verify current metric thresholds against live Seller Central help before you rely on any number.
Delivery timing is where a lot of FBM sellers get burned right now. If you have not read it yet, our note on the 2026 delivery rate rule explains why on-time delivery matters more than ever.
Reinstate a Deactivated Offer
A deactivated offer appears in Account Health under Other Policy Violations. You restore it by following the reactivation instructions listed there. Do it in this order.
- Open the warning email if you received one. It should identify the issue and give resolution steps.
- Go to Account Health and find the offer under Other Policy Violations.
- Read the reactivation instructions listed for that offer.
- Fix the underlying cause first. Correct handling time, swap carriers, or resolve the defect pattern.
- Follow the reactivation path and submit your response.
- Keep the case record. Save the email, the Account Health entry, and the order-level records you used.
- Check your ad campaigns after the offer is removed to control wasted spend.
Do not try the shortcut. Relisting the same inventory under a new SKU to evade the action is not allowed. That path only creates a bigger problem.
Protect Q4 When a SKU Goes Dark
The worst time for a top SKU to go dark is peak season. Build a backup plan for every advertised FBM offer before you need it.
- Map every advertised FBM SKU to a backup fulfillment plan.
- Backup options include corrected handling time, a different carrier, a temporary pause, a 3PL change, or FBA if the economics work.
- Because an unavailable offer is expected to stop serving ads, check campaign status the moment an offer is removed.
- Move the fastest-selling SKUs to the front of your reactivation queue.
A backup plan you build in October beats a scramble on Black Friday. Decide now who acts, what they switch to, and how fast.
Build Your Evidence File
When you respond to a deactivation, records win. Start collecting them before you ever get a warning, because some data changes or disappears over time.
- Save any Amazon warning email, the Account Health entry, and the order-level records you use in a response.
- If a carrier scan or customer event looks wrong, preserve the original tracking pages and timestamps before the data changes.
- Keep the carrier, service level, and warehouse or 3PL for each order tied to a defect.
- Store the Amazon delivery promise shown at purchase alongside the actual delivery date.
A clean file lets you answer fast and specific instead of guessing. That is the difference between a quick reactivation and days of back and forth.
Your This-Week Checklist
Do these seven things in the next few days.
- Build a weekly FBM exception report by SKU.
- Set an alert on the warning mailbox and name one person to open the case.
- Align catalog-wide handling-time defaults with each SKU's real capability.
- Map a backup fulfillment plan to every advertised FBM SKU.
- Verify current metric thresholds on live Seller Central help pages.
- Start an evidence file with carrier, promise, and delivery data per order.
- Write down the exact reactivation steps under Other Policy Violations so nobody hunts for them mid-crisis.
Conclusion
The change is a net positive. One bad FBM offer no longer has to threaten your whole account. But the gaps Amazon left, no published threshold, no stated warning window, no defined selection method, mean you cannot rely on the system to be gentle. Watch your four metrics per SKU, act on the warning email the moment it arrives, and keep an evidence file ready so reactivation is fast.
When an offer comes back on, make sure it earns clicks. Pair tight fulfillment with a strong listing by studying our Amazon listing optimization checklist and, if delivery timing is your weak spot, our take on what the 2026 delivery rate rule changed. Surgical enforcement rewards sellers who run a tight operation.
References
Frequently asked questions
Which four policies can cause my FBM offer to be deactivated?
Will Amazon deactivate my whole account or just one offer now?
Do I get a warning before an offer is taken down?
Where in Account Health do I find and fix a deactivated offer?
How does Amazon decide which offer is the 'affected' one?
How long does a temporary offer deactivation last?
Does one late shipment or A-to-z claim automatically kill a SKU?
Can I relist the same product under a new SKU to get around it?
AI Tools You Can Try
Your listings should never be the reason an offer stalls
While you tighten fulfillment, tighten the copy too. The Amazon Listing SEO Optimizer PRO pulls real keywords and competitors, rebuilds your title, bullets, and backend terms, and pushes to Amazon in one click.
Try the Amazon Listing SEO Optimizer PRO