Amazon Account Health Rating: Reading the Score and Acting On It

What the number actually measures

AHR isn't a single metric like order defect rate or late shipment rate — it's a composite score Amazon computes from your account's overall policy compliance and performance history, weighted toward more recent activity. It's meant to be a fast, at-a-glance read of standing, the way a credit score summarizes a lot of underlying financial behavior into one number. That summary quality is also its limitation: two accounts sitting at the same AHR can have completely different underlying problems, one with a single serious violation and another with several smaller performance issues accumulating.

Because of that, the number is a starting point, not a diagnosis. It tells you roughly how urgent your situation is; the Account Health dashboard underneath it — broken out by policy compliance, product policy compliance, and customer service performance — is where the actual, specific issue lives.

It's also worth knowing the score is account-wide, not per-listing. A single problematic ASIN in an otherwise clean catalog can drag the whole account's rating down, which is part of why an isolated issue is worth fixing promptly even when the rest of the business looks fine — the number doesn't distinguish between one bad listing and a systemic problem on its own.

The three bands, and what each genuinely calls for

At 200 and above — the healthy, green band — the useful discipline is monitoring, not panic. Check the dashboard regularly enough to catch a new flag early, since the score reflects a trailing window and a single new issue can start pulling it down before it's obviously visible day to day.

At 100 to 199 — the at-risk, yellow band — the account isn't deactivated, but it's genuinely exposed, and the right response is triage: identify every open flag on the dashboard, prioritize the ones tied to the most serious violation categories, and resolve them methodically rather than picking whichever feels easiest first. At 99 and below — the red band — the account is eligible for deactivation if it isn't already deactivated, and every open issue needs a documented, evidenced response, submitted through the correct channel for its type, as close to immediately as the evidence allows.

The mistake sellers make with a healthy score

A score sitting comfortably in the green band produces a natural complacency — the dashboard isn't checked for weeks, because there's no obvious reason to. The problem is that AHR reflects a trailing window, which means a real, current problem can exist for days before it's meaningfully visible in the aggregate number. A seller who only checks the score, rather than the underlying flags, discovers a serious issue later than they would have by watching the dashboard directly.

The healthier habit is treating AHR as a lagging confirmation, and the individual policy and performance sections as the leading indicator worth actually watching on a schedule — weekly is a reasonable cadence for most accounts, more often for one carrying several ASINs in higher-complaint categories.

The other version of this mistake is watching only the topline number and never opening the sub-categories at all. Policy compliance, product policy compliance, and customer service performance can each be trending in different directions under a stable-looking aggregate score, and the one quietly worsening is the one worth catching early, before it drags the overall number down with it.

When a single flag is worth acting on immediately, versus monitoring

Not every flag on the dashboard needs an emergency response. A single, minor performance metric drifting slightly is often worth watching for a cycle before escalating internally, since some fluctuation is normal and chasing every small movement wastes attention better spent elsewhere. A flag tied to authenticity, safety, or a serious policy violation is different — those are the categories most likely to move an account toward the at-risk or deactivation-eligible bands quickly, and they warrant the same case-management discipline as any other serious Amazon case: one case ID, evidence gathered specifically for that violation type, and a documented response rather than a delayed one.

The practical filter is severity, not recency: a flag that could plausibly lead to deactivation on its own gets immediate, evidenced attention regardless of how the rest of the dashboard looks. A flag that's clearly minor and isolated can reasonably wait for the next scheduled review, as long as that review actually happens on schedule rather than being deferred indefinitely.

What to do when the score drops and the cause isn't obvious

Sometimes the dashboard shows a drop without an obviously new, individual flag explaining it — several smaller issues compounding rather than one clear cause. In that situation, work backward through every open item on the dashboard, oldest first, rather than assuming the most recent one is the culprit; a score decline is often the cumulative effect of several unresolved smaller issues, not one dramatic new one. Resolving the oldest open items first tends to move the trailing score more than chasing whichever flag is newest.

It's worth resisting the urge to fix the most visible or most recent item first purely because it's the one currently drawing attention. A methodical pass through every open item, prioritized by how long it's been sitting and how serious its category is, is slower to start but more likely to actually move the score than a series of one-off fixes chosen by whichever flag feels most urgent that day.

Where casework earns its cost on account health

Across the 53 accounts we've run casework on this year, the accounts that stay reliably in the healthy band are the ones treating the dashboard as a weekly check, not a fire alarm — catching and resolving smaller issues before they compound into an at-risk score.

Dr. Shield monitors account health as part of its standard casework and handles the evidenced response when a flag needs one, priced on the call as a contingency against what's actually resolved; it's most valuable once an account has drifted into the at-risk band with multiple open items competing for attention, and less necessary for a healthy account that just needs a consistent weekly check and the discipline to actually keep it.