Amazon Account Health: Monitor and Protect Your Seller Score

Amazon account health is the single system that determines whether you get to keep selling, and most sellers only look at it after something breaks. The Account Health page in Seller Central rolls up two separate enforcement tracks: the Account Health Rating, which scores your policy compliance, and the performance metrics — ODR, Late Shipment Rate, Valid Tracking Rate — each of which can deactivate your account on its own regardless of your score. Sellers doing $500K or more per year have too much at stake to check this page reactively. This guide covers how the AHR score actually moves, the exact metric thresholds Amazon enforces, how violations are weighted, what Account Health Assurance buys you, and the monitoring cadence that catches problems while they are still fixable.

How the Account Health Rating Score Actually Works

The Account Health Rating is a number from 0 to 1,000, displayed with a color band: Healthy (green) at 200 and above, At Risk (yellow) from 100 to 199, and Unhealthy (red) at 99 or below. Every account starts at 200. Unhealthy means deactivation is imminent or already in progress.

The score moves on two inputs. Policy violations subtract points based on severity — a minor listing policy issue might cost a few points, while a product authenticity complaint or a suspected intellectual property violation takes a much larger bite. Selling activity adds points back: accounts with more orders earn score recovery faster, which is Amazon’s way of scaling tolerance to account size.

Two mechanics matter more than the number itself. First, violation impact decays over 180 days, so your score six months from now reflects what you resolve today. Second, resolving a violation — either by submitting a plan of action or by successfully appealing it — restores points faster than waiting for decay. An account with three unaddressed minor violations can sit lower than an account that took one serious hit and cleared it.

There is also a hard override: certain severe violations deactivate the account instantly at any score. Selling a recalled product, dropshipping violations, or a fraud flag will not wait for your AHR to drift down to 99. The score is a buffer against accumulation, not immunity from critical violations.

The Performance Metrics With Hard Deactivation Thresholds

Separate from the AHR, four operational metrics carry enforcement thresholds. Cross any of them and you get a deactivation warning — or a deactivation — regardless of a spotless compliance record.

ODR is the one that ends accounts. It counts three defect types: negative feedback (1- and 2-star), A-to-z Guarantee claims, and credit card chargebacks. The math is unforgiving at low volume — a seller doing 300 orders in 60 days gets deactivation-track scrutiny at just 3 defects. Two levers control it: remove feedback that violates Amazon’s policies (fulfillment-related feedback on FBA orders is strikeable through the Feedback Manager), and respond to every A-to-z claim within 48 hours, because an unanswered claim is granted automatically and counts as a defect even when you would have won it.

LSR, cancel rate, and VTR only apply to seller-fulfilled orders, which is why an FBM or hybrid catalog needs tighter operational monitoring than a pure FBA account. VTR failures are usually process failures — a carrier integration that stopped passing tracking numbers, or a 3PL uploading tracking 48 hours late. Check VTR by category, because Amazon evaluates it that way and a small FBM category can breach 95% on a handful of orders.

One structural note for hybrid sellers: because these metrics only count seller-fulfilled orders, a mostly-FBA account with a small FBM backup program has a tiny denominator. Ten FBM orders a month means one late shipment puts you at a 10% LSR — more than double the threshold. If you run FBM offers as stockout insurance, hold that channel to a stricter internal standard than Amazon’s published one, because you have no volume cushion to absorb a bad week.

Policy Compliance Violations and How They Are Weighted

The Policy Compliance section of the Account Health page lists every open violation, and they are not created equal. Amazon buckets them roughly like this:

• Critical: product safety complaints, recalled or restricted product listings, fraud or illegal activity flags. These can deactivate immediately at any AHR.
• High severity: suspected or received intellectual property complaints, product authenticity (inauthentic) complaints, counterfeit flags. A single one drops your score noticeably; a pattern gets your account reviewed.
• Moderate to low: listing policy violations, product condition complaints (“used sold as new”), regulatory document requests, variation misuse.

Handle each violation through its own workflow on the Account Health page. You generally get three paths: submit a plan of action, provide documents (invoices, authorization letters, compliance certificates), or acknowledge the violation. Acknowledgment is the tempting one-click option, and it is usually the wrong move — you are confirming the violation on your permanent record for a point recovery that decay would give you anyway. Appeal anything defensible. A won appeal removes the score impact entirely, and win rates on invoice-backed authenticity disputes are meaningfully high when your supply chain documentation is clean.

Keep supplier invoices for at least 365 days, in PDF, showing supplier contact details, quantities, and item descriptions that match your listings. Nearly every serious violation defense comes down to producing these within 72 hours. If you cannot, the violation stands no matter how legitimate your sourcing is. Our compliance documentation checklist covers exactly what to keep on file.

The Early Warning Signals Most Sellers Ignore

Formal violations are lagging indicators. By the time something appears in Policy Compliance, buyers have usually been telling Amazon about the problem for weeks through channels you can read directly.

Voice of the Customer is the most underused page in Seller Central. It scores every ASIN’s CX Health from Excellent to Very Poor based on returns, refunds, negative feedback, and buyer contacts, and it surfaces the actual complaint text. An ASIN sliding to Poor is a leading indicator of three separate enforcement events: a product condition complaint, a listing suppression, and a negative review cluster that drags your ODR. When VOC flags “item arrived broken” on a product at any meaningful rate, fix the packaging this week — Amazon is reading the same signal, and its response is a violation, not a suggestion.

Return reason codes in the FBA returns report tell you which complaints are product problems (“defective,” “not as described”) versus buyer behavior (“no longer needed”). A rising defective rate on one ASIN is next month’s authenticity or condition complaint, especially if the product is commingled with other sellers’ stock.

Buyer-seller messages are evidence Amazon can read. A pattern of buyers asking whether your product is genuine, or reporting a safety issue, will surface in an investigation. Answer every message within 24 hours and treat recurring themes as defect reports, because that is exactly how Amazon’s systems treat them.

None of this requires new tooling — it requires assigning someone to read these three reports weekly and route what they find to whoever can fix the root cause.

Account Health Assurance: What It Buys You

Account Health Assurance (AHA) is the closest thing Amazon offers to suspension insurance, and it costs nothing. Enrolled accounts do not get deactivated for AHR-related issues without Amazon first reaching out — you get a call and 72 hours to work with an account health specialist on resolution before any enforcement lands.

Eligibility is automatic, not applied for: hold an AHR of 250 or higher for at least six months and keep a valid emergency contact number on file. That is the practical reason to treat 250, not 200, as your operating floor. An account cruising at 210 is technically Healthy but permanently locked out of AHA protection.

Know the limits. AHA covers Account Health Rating enforcement. It does not protect you from ODR deactivations, fraud flags, related-account enforcement, or Amazon’s business-decision closures. It converts a sudden-death suspension into a conversation for one class of problems — a class that happens to include most of the violation-accumulation suspensions that hit growing brands.

An Amazon Account Health Monitoring Cadence That Actually Catches Problems

Amazon gives you 72-hour and sometimes 48-hour response windows. A weekly check-in is not enough. Here is the cadence we run on managed accounts:

Daily (5 minutes):

• Open the Account Health page. Confirm AHR number and check Policy Compliance for new violations.
• Check the Performance Notifications inbox — enforcement notices land here, sometimes without an email.
• Scan new negative feedback and A-to-z claims. Respond to claims same-day.

Weekly (30 minutes):

• Review ODR, LSR, cancel rate, and VTR trends, not just current values. A VTR sliding from 99% to 96% is a process problem you fix before it becomes an enforcement problem.
• Check Voice of the Customer for CX Health flags — “Poor” and “Very Poor” ASINs are your next product condition complaints and listing suppressions in waiting.
• Review any open violation appeals and case log follow-ups.

Monthly:

• Audit listings against restricted product and pesticide-claim triggers (bots flag keywords like “antibacterial” or “FDA approved” retroactively).
• Verify emergency contact info and confirm AHA eligibility status.
• Refresh your invoice archive for top-selling ASINs so a documentation request never starts a scramble.

This is the unglamorous work that ongoing account management is built around — most account-level disasters announce themselves two to six weeks in advance through exactly these signals.

When a Violation Escalates Past Monitoring

Sometimes you inherit the problem too late. If your AHR has gone red, if you have received a “your account is at risk of deactivation” notice with a deadline, or if a critical violation has landed, you are past monitoring and into appeal territory. The mechanics of writing a plan of action that Amazon’s investigators actually accept — root cause, corrective action, preventive measures, with evidence — are covered in our guide to Amazon account suspension appeals.

And if the account is already deactivated, treat it as the revenue emergency it is: every day suspended is a day of rank decay on every ASIN you own, on top of the lost sales. Start with our suspended account emergency page — the first 72 hours of a suspension determine how long reinstatement takes, and the most common mistake is firing off a rushed, generic appeal that burns your best chance. We have reversed a suspension in 14 days for a seller whose first self-written appeal had already been rejected, and the recovery would have been faster without that first rejection on file.

Account Health Is an Operations Function, Not a Dashboard

The sellers who never face a suspension are not lucky — they treat account health as a daily operational discipline with owned checklists, response-time standards, and a documentation archive that is ready before Amazon asks. That takes consistent hours every week, which is precisely what falls off the plate first when you are also running inventory, PPC, and product development. A professional Amazon account management service puts a team on that cadence for you: daily health monitoring, same-day violation response, appeal drafting, and the metric hygiene that keeps your account permanently inside AHA protection. If your Account Health page has open violations right now, or nobody checked it yesterday, that is the conversation to have.