Your entire business runs on a permission you can lose in a single email. Account health is the discipline of making sure you never get that email.
There is a particular kind of silence that arrives the morning after an Amazon suspension. Orders stop. Ads stop. Deposits stop. Inventory you already paid for sits in a warehouse you no longer have access to. And somewhere in your inbox is a notice that tells you almost nothing about why — just enough to know that your business is offline until you can write something convincing enough to bring it back. Every Amazon seller is one bad week away from that morning, and most of them never see it coming because they treat account health as a dashboard they glance at instead of the system that decides whether the business gets to keep operating tomorrow. This guide is the complete prevention and recovery playbook: how the Account Health Rating actually works, which metrics matter most, what triggers suspensions, the anatomy of a Plan of Action that gets accepted, and the 60-day plan to lock in the routine that keeps your account safe.
For related risk-management context, see the Brand Registry & trademark playbook and the returns and reimbursements guide.
The Account Health Rating is Amazon's composite score reflecting a seller's adherence to its policies and performance standards. It combines policy compliance and performance metrics into a single rating displayed in Seller Central, used to flag accounts at risk of enforcement action including suspension.
What Amazon Account Health Actually Is
Amazon Account Health is the system Amazon uses to monitor whether a seller is meeting its policies and performance standards. It is visible in Seller Central as the Account Health page, which surfaces every performance metric, every policy compliance issue, and every active warning. The page is not optional reading — it is the dashboard that decides whether the account stays open.
What the system is really doing
Account Health is Amazon's risk-management layer for its marketplace. Amazon needs every seller to deliver acceptable customer experiences, comply with policies, and stay inside performance thresholds, and the Account Health system is how it tracks that at scale. From a seller's perspective, it is the early warning system that tells you when something is going wrong before it becomes a suspension — if you bother to look.
What the Account Health page shows
- The Account Health Rating — the composite score with a colored status
- Customer service performance — order defect rate and related signals
- Shipping performance — late shipment, cancellation, valid tracking, on-time delivery
- Policy compliance — product policy violations, listing policy issues
- Intellectual property complaints — copyright, trademark, patent
- Product authenticity — inauthentic-item or counterfeit complaints
- Product safety — safety-related complaints and notices
The Account Health Rating Explained
The Account Health Rating, or AHR, is Amazon's composite score that combines policy violations and performance metrics into a single rating. Higher ratings indicate healthier accounts; lower ratings signal accounts at risk of enforcement. The AHR is what Amazon's automated systems and account-health specialists look at first when evaluating risk.
How the AHR works
The AHR moves up when an account stays clean and resolves issues, and down when violations or performance problems accumulate. The exact scoring is Amazon's internal system, but the practical behavior is consistent: every unresolved policy violation drags the rating, every accumulating performance metric breach drags it harder, and a low enough rating triggers enforcement action. Treating the AHR as a real-time risk gauge — not a vanity score — is the right mental model.
Why the AHR matters operationally
- It is the early-warning gauge. A drifting AHR signals trouble building before any single metric breaches a threshold.
- It affects buyer trust at exit. A clean AHR history is one of the things acquisition buyers check — a history of poor ratings lowers the multiple they will pay.
- It is what Amazon shows you first. When an account-health specialist reviews your case, the AHR colors their first impression of whether you are a reliable seller.
- It compounds. A lower AHR makes Amazon's systems more sensitive to additional issues, so falling further is easier than recovering — which is why early intervention matters.
The Performance Metrics That Actually Matter
The core Amazon performance metrics are Order Defect Rate (ODR), Cancellation Rate, Late Shipment Rate, Valid Tracking Rate, Pre-fulfillment Cancel Rate, and On-Time Delivery Rate, plus return-rate signals. Each has an Amazon-set threshold, and breaching any of them puts the account at risk. For FBA-only sellers, Amazon handles shipping metrics, so ODR and policy compliance dominate.
The metrics and what they measure
| Metric | What It Measures | Who Controls It |
|---|---|---|
| Order Defect Rate (ODR) | % of orders with negative feedback, A-to-z claims, or chargebacks | Seller (product quality, listing accuracy, service) |
| Cancellation Rate | % of seller-initiated cancellations before shipment | FBM sellers; FBA-handled |
| Late Shipment Rate | % of orders shipped after the expected ship date | FBM sellers; FBA-handled |
| Valid Tracking Rate | % of orders with valid tracking provided | FBM sellers; FBA-handled |
| On-Time Delivery | % of orders delivered by the expected date | FBM sellers; FBA-handled |
| Return Reason / Rate Signals | Patterns in returns suggesting product or listing issues | Seller (product, listing, packaging) |
Why Order Defect Rate dominates
ODR is the most consequential single metric Amazon tracks for one reason: it directly measures whether customers had a bad experience. Negative feedback, A-to-z guarantee claims, and service chargebacks each indicate something went wrong from the buyer's perspective — and Amazon's marketplace runs on buyer trust. An ODR breaching Amazon's threshold can trigger account suspension on its own, regardless of how every other metric looks. If a seller only watches one number, ODR is the one to watch.
A handful of bad orders can swing ODR fast when your order volume is low. One A-to-z claim against ten orders puts you at a 10% defect rate. The same claim against a thousand orders is 0.1%. New sellers and lower-volume sellers should be especially cautious — the percentage punishment for any single defect is much larger than the same incident on a high-volume account.
What Actually Triggers an Amazon Suspension
Amazon account suspensions are typically triggered by performance metrics breaching thresholds, intellectual property complaints from rights holders, policy violations such as restricted product listings or review manipulation, authenticity complaints, safety complaints, or accumulated violations dragging the AHR low. Suspensions can be limited to listings, ASINs, or hit the entire selling account.
The main suspension triggers
- Performance threshold breachesODR, cancellation rate, late shipment rate, or on-time delivery moving outside Amazon's accepted range. ODR breaches are the most aggressive trigger.
- Intellectual property complaintsA trademark, copyright, or patent owner filing a complaint against one of your listings. Even a single valid complaint can suspend the listing immediately.
- Policy violationsSelling restricted products, manipulating reviews, using prohibited claims in listings, or violating any documented Amazon policy. Some violations trigger instant action.
- Authenticity / inauthentic complaintsCustomer or rights holder complaints alleging counterfeit or inauthentic products. Among the hardest categories to recover from.
- Safety complaintsReports of product safety issues. Amazon treats these as high priority, with rapid enforcement.
- Accumulated AHR damageMultiple smaller issues pulling the Account Health Rating low enough that Amazon takes systemic action.
- Verification or compliance failuresFailing required document verification, tax compliance checks, or other administrative requirements.
Levels of suspension
- Listing-level. A single listing is removed. Other listings continue selling. Often the result of an IP or policy issue on one ASIN.
- ASIN-level. An ASIN is blocked across the account. Reinstatement requires addressing the specific ASIN issue.
- Account-level. The entire selling account is suspended. All listings stop. Reinstatement requires a comprehensive Plan of Action.
How to Monitor Your Account Weekly
Monitor your account weekly by opening the Account Health page in Seller Central and reviewing every metric, every active warning, and the AHR. The discipline is not optional — suspensions can build over a week of unwatched signals, and a weekly review catches problems while they are still small enough to fix without disruption.
The weekly review routine
- Open the Account Health pageNavigate to Performance, then Account Health. Do this on a fixed day each week so it never gets skipped.
- Check the AHR trendNote whether the rating is stable, climbing, or falling compared to last week. Any downward movement deserves investigation, even if the absolute level is still "healthy."
- Review every performance metric against thresholdFor each metric, confirm you are well inside the threshold — not just barely under it. "Barely under" is one bad week from being over.
- Read every active warning or violationEach warning is Amazon telling you something. Read it, understand it, and decide whether action is needed today.
- Look at customer feedback and A-to-z claimsNew negative feedback or any A-to-z claim activity is an early signal of an emerging ODR problem.
- Document what you sawKeep a brief weekly log so you can see trends over time and demonstrate diligent monitoring if you ever need to.
Weekly is the right cadence for one reason: it is fast enough to catch issues before they escalate and slow enough to actually do every week. Monthly is too slow — a metric trending wrong can breach in three weeks. Daily is more than most sellers will sustain. The accounts that survive long-term are the ones with the weekly habit firmly built in, not the heroic ones that check daily for a month and then forget.
The Ecom Profit Box
Free PDF guides covering Amazon profitability, operations, conversion, and brand protection.
Grab it free →Account Health & Risk Strategy
We help $1M-$10M Amazon brands stabilize accounts, reduce risk, and prevent suspensions.
Book a strategy call →Anatomy of a Strong Plan of Action
A strong Plan of Action addresses three things clearly: the root cause of the issue, the immediate corrective actions you have taken, and the preventive steps you will take going forward. It is specific, takes responsibility without excessive excuses, addresses Amazon's exact concern, and reads as factual and professional. Vague or defensive plans are routinely rejected.
The three-part structure
- Root causeState clearly what actually caused the issue. Not what you wish caused it — what the evidence shows. "We did not have a process to verify supplier-provided product images" is a real root cause. "It was an isolated incident" is not.
- Corrective actionsList the specific things you have already done to fix this instance — not what you plan to do, but what is done. Removed listings, refunded customers, contacted suppliers, audited inventory.
- Preventive measuresDescribe the systematic changes you have implemented to prevent the issue from recurring. New review processes, additional QC steps, supplier vetting protocols, monitoring routines.
Root cause: Our team identified that the issue stemmed from [specific, honest cause]. We acknowledge this should have been prevented by [the missing control].
Corrective actions taken: We have already [specific completed actions, dated where possible].
Preventive measures implemented: Going forward we have [specific systematic changes, including who is responsible and how it will be monitored].
Closing: We take full responsibility, value our customers and Amazon's marketplace standards, and have implemented the above to ensure this does not recur.
What gets a Plan of Action rejected
- Vagueness. Generic statements that could apply to any seller. Specifics signal real understanding.
- Defensiveness or blame. Plans that argue Amazon got it wrong, or blame customers, suppliers, or carriers without taking responsibility.
- Not addressing the exact concern. Responding to a different issue than the one Amazon raised, often because the seller did not read the notice carefully.
- Excessive apology without substance. Pages of apology with no real root cause, corrective action, or preventive system.
- Promises instead of completed action. "We will implement" reads weaker than "We have implemented." Use the past tense for corrective actions.
Recovering From a Suspension
Recover from a suspension by reading Amazon's notice precisely, identifying the exact concern, gathering supporting evidence, writing a focused Plan of Action that addresses root cause, corrective action, and prevention, and submitting it through the correct appeal channel. Quality and precision of the Plan of Action is the single biggest factor in reinstatement.
The recovery sequence
- Read the suspension notice preciselyAmazon's notice tells you the specific concern. Read it more than once. Misunderstanding the concern is the most common reason for rejected appeals.
- Gather evidencePull supplier invoices, authenticity documentation, listing screenshots, customer service records — whatever supports your case. A POA without evidence is just a story.
- Identify the real root cause honestlyBe willing to find the actual cause, even if it is uncomfortable. A POA built on the wrong root cause cannot succeed.
- Take corrective actions before submittingDo not promise — do. Remove the affected listings, refund affected customers, audit inventory, fix the broken process. Submit the POA with the corrections already complete.
- Write the Plan of ActionUse the three-part structure, address Amazon's exact concern, keep it specific and professional, and include the evidence references.
- Submit through the correct channelUse the appeal channel specified in the suspension notice. Wrong channel submissions delay everything.
- If rejected, escalate carefullyIf the first POA is rejected, do not submit the same plan again. Identify what Amazon's rejection signals and revise materially before resubmitting.
Suspensions create intense urgency — sales are stopped, inventory is locked, every day costs money. The temptation is to submit something fast. Resist it. A POA submitted in panic three hours after suspension that gets rejected sets you back further than a thoughtful POA submitted the next day that gets accepted. Slow down enough to do it right the first time. The fastest path to reinstatement is the one that does not require resubmission.
Intellectual Property Complaints: A Special Case
Intellectual property complaints — trademark, copyright, or patent — are among the most disruptive enforcement actions because a single valid complaint can suspend a listing immediately, and resolution typically requires either authorization from the rights holder, retraction of the complaint, or formal counter-notice. Strong brand protection is the best long-term defense.
The three IP complaint types
- Trademark complaints. A trademark owner alleges your listing infringes their trademark — usually by using their brand name, logo, or protected marks without authorization.
- Copyright complaints. A copyright holder alleges your listing copies their protected creative work — images, text, packaging artwork.
- Patent complaints. A patent holder alleges your product infringes their patent. Among the most legally complex and hardest to resolve quickly.
How to respond
- Verify the complaint's basisIs the complainant actually the rights holder? Is the right they cite valid in the relevant jurisdiction? Sometimes complaints are filed in bad faith.
- Contact the complainant directlyIf the complaint is valid, the cleanest path is often to contact the rights holder, address the issue, and ask them to retract the complaint with Amazon.
- Provide authorization if you have itIf you are an authorized reseller or have licensing, provide that documentation to Amazon as evidence.
- File a counter-notice when warrantedIf the complaint is invalid, you can file a formal counter-notice with Amazon. This is a legal action with consequences; do it carefully.
- Remove the listing where appropriateIf the complaint is valid and cannot be resolved with the rights holder, removing the listing may be the right move.
The long-term defense against IP issues is the inverse of being a target: protect your own brand with trademark and Brand Registry so you have standing, and rigorously vet your own listings so they cannot reasonably draw a valid IP complaint.
Your account is not yours. It is a permission Amazon grants — and every day you operate is a day you earn it back by following the rules of the system you do not own.
Long-Term Suspension Prevention
Long-term prevention means building the habits and systems that keep your account well inside every threshold by default. Weekly account health monitoring, strong brand protection, careful listing compliance, proactive customer service, supplier vetting, and a documented response process for warnings are the core practices that prevent suspensions across years, not just months.
The six prevention practices
- Weekly account health monitoring. The single habit that catches the most problems early.
- Trademark and Brand Registry. Strong brand protection both deters IP complaints against you and gives you tools to defend the brand.
- Rigorous listing compliance. Vet every listing for restricted claims, prohibited language, accurate categorization, and authentic imagery before publishing.
- Proactive customer service. Resolve issues before they become A-to-z claims or negative feedback. A refund handled well is cheaper than an ODR hit.
- Supplier vetting and documentation. Keep authentic supplier records for every product. Authenticity complaints fail when you can document a real supply chain.
- A documented response process. When a warning arrives, you should not be figuring out what to do — you should be executing a known process.
The compounding effect
These six practices compound. A brand with trademark protection, clean listings, and proactive customer service almost never has the issues that trigger enforcement, which keeps the AHR high, which makes Amazon's systems less sensitive to any individual incident, which makes the brand more resilient to the inevitable random complaint that does arrive. Each practice makes every other one more effective. Sellers who invest in all six have dramatically lower lifetime suspension risk than sellers who treat account health as something to fix when it breaks.
The 60-Day Account Protection Plan
The 60-day plan to lock in long-term account health breaks into three phases: build the monitoring routine and resolve any active issues (days 1-20), strengthen the structural defenses (days 21-40), then institutionalize the practices and prepare for any future incident (days 41-60).
Days 1-20: Monitor and resolve
- Set a fixed weekly time to review the Account Health page and start the habit
- Audit every active warning, violation, or open issue and respond to each
- Pull the last 90 days of performance metrics and confirm where you sit on each
- Read every customer-feedback and A-to-z claim from the last 90 days for patterns
- Document your current baseline so you can measure improvement
Days 21-40: Strengthen defenses
- Confirm trademark and Brand Registry are in place; file if not (see the Brand Registry playbook)
- Audit every active listing for restricted claims, prohibited language, and authenticity risk
- Strengthen customer service so issues resolve before they become claims or feedback
- Verify supplier documentation for every product is current and retrievable
- Identify the metric closest to its threshold and build a specific plan to widen the buffer
Days 41-60: Institutionalize
- Document a written response process for the most common warning types
- Prepare a Plan of Action template you can adapt quickly if needed
- Keep a brief weekly log of Account Health reviews to demonstrate diligent monitoring
- Run a fire drill: pretend a suspension just hit and walk through how you would respond
- Set the monitoring as a recurring calendar block — the routine is the protection
By day 60 the account is protected not because nothing will ever go wrong, but because when something does, you will see it early, know exactly what to do, and have the documentation and brand protection that make a successful response far more likely.
The 6 Things to Remember About Account Health
- Account Health is the system that decides whether your business gets to operate tomorrow — treat the page in Seller Central as a real-time risk gauge, not a vanity dashboard
- The AHR is a composite score; Order Defect Rate is the single most consequential metric, and a breach can suspend an account on its own
- Suspensions are most often triggered by performance breaches, IP complaints, policy violations, authenticity complaints, safety complaints, or accumulated AHR damage
- Monitor weekly — fast enough to catch issues early, slow enough to actually sustain. Weekly checks save more accounts than any other single habit
- A strong Plan of Action has three parts: honest root cause, completed corrective action, and systematic prevention — vague or defensive POAs are routinely rejected
- Long-term prevention compounds: weekly monitoring, Brand Registry, listing compliance, proactive customer service, supplier documentation, and a written response process