At a glance
The single most important number in the Amazon connector: your account standing as Amazon itself reports it, expressed as a status (Healthy, At Risk, or Unhealthy / At Risk of Deactivation) and underpinned by the Account Health Rating (AHR) score. If this gauge moves into the danger zone, every other metric is secondary, an unhealthy account can be suspended, freezing all sales and disbursements. This is the gauge a founder checks before anything else.
| What it counts | The account-level health state Amazon surfaces in Seller Central, combining the Account Health Rating (a 0 to 1000-style score) with policy-compliance and customer-service performance signals into a single status band. |
| Status bands | Healthy (green), At Risk (amber), and Unhealthy / At Risk of Deactivation (red). The gauge renders the current band; the alert fires on At Risk or worse. |
| What drives it | Three pillars: customer-service performance (chiefly Order Defect Rate), policy compliance (intellectual-property complaints, authenticity, listing-policy and restricted-product violations), and shipping / fulfilment performance (late shipment rate, pre-fulfilment cancel rate, valid tracking rate). |
| Fulfilment scope | Account-wide. FBA and FBM both feed the underlying metrics, though FBA insulates you from many shipping-performance defects because Amazon controls fulfilment. |
| Why it matters | A sustained unhealthy state can lead to account deactivation. Deactivation halts sales across the account and can hold disbursements, the existential risk for an Amazon-dependent business. |
| Recovery | Account Health Assurance and the appeal / Plan of Action process can stabilise an at-risk account. Recovery is driven by fixing the underlying metric breaches, not by the status itself. |
| Time window | RT (real time). Amazon recalculates the underlying metrics on a rolling basis; the status reflects the latest evaluation. |
| Alert trigger | AtRisk or Suspended. Any move out of Healthy flips the gauge and notifies the owner and operations roles immediately. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Amazon Seller Central data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A mid-size US seller running mostly FBM with a small FBA range on amazon.com. Snapshot taken 22 Mar 26.| Pillar | Signal | Reading | Status contribution |
|---|---|---|---|
| Customer service | Order Defect Rate | 1.3% (target under 1%) | Breached, pulling status down |
| Policy compliance | IP / authenticity complaints | 0 active | Healthy |
| Shipping performance | Late Shipment Rate | 7% (target under 4%) | Breached, pulling status down |
| Account Health Status (this card) | At Risk (amber) | Alert fired |
- Two metric breaches were enough to flip the gauge. ODR and LSR both sit above Amazon’s targets. Neither alone may have moved the status, but together they pushed the account out of Healthy. The gauge is a composite, so it captures combined pressure that single-metric cards can miss.
- The policy pillar is clean, which is good news. Policy violations (IP complaints, authenticity, restricted products) are the hardest to recover from and the fastest route to suspension. This seller’s risk is operational, not policy-driven, which is more fixable.
- The two drivers are both FBM problems. ODR and LSR are shipping-and-service metrics the seller controls directly on FBM orders. Moving the worst SKUs to FBA, or tightening handling time, attacks both at once.
- This is a Hero card for a reason. When this gauge is amber or red, it outranks revenue. A seller chasing a sales dip while ignoring an At Risk status is optimising the wrong thing, the account itself is the asset at risk.
- The alert is the trigger for a same-day response. At Risk is the warning shot before deactivation. Best practice is to open a Plan of Action immediately: identify the breached metrics, fix the root cause, and document the corrective steps Amazon will want to see.
Sibling cards merchants should reference together
The status gauge is the summary. These cards show the pillars that move it:| Card | Why pair it with Account Health Status |
|---|---|
| Order Defect Rate | The single biggest driver of customer-service health. ODR over 1% is the most common reason a status drops to At Risk. |
| Late Shipment Rate | The shipping-performance pillar. A climbing LSR is an early warning that the status is about to move. |
| Account Health Creep | The slow-drift alert. It catches gradual ODR / LSR rises before they flip this gauge amber. |
| A-to-z Guarantee Claims (open) | Granted claims are ODR defects. A burst of claims is a fast route to an At Risk status. |
| Pre-Fulfilment Cancel Rate | Another shipping-performance defect that feeds the status. Cancellations after payment are scored. |
| Negative Feedback (30d) | A leading indicator of customer-service problems that often precede a health dip. |
Reconciling against Amazon Seller Central
Where to look in Seller Central:Account Health (top navigation, or Performance → Account Health) The dashboard shows the overall status band, the Account Health Rating score, and the three pillars (Customer Service Performance, Policy Compliance, Shipping Performance) with each underlying metric.The status band on that page is exactly what this gauge mirrors. The individual metric values behind it map to the dedicated sibling cards above. Timing and reporting-lag table:
| Topic | Detail |
|---|---|
| Timezone | The Account Health page uses your marketplace’s local timezone for metric windows; Vortex IQ reads the status as Amazon reports it, so the band matches regardless of timezone. |
| Refresh cadence | Amazon recalculates the underlying metrics on a rolling basis. The status can change between checks; the card polls frequently so the gauge stays close to the live state. |
| Rolling windows | The pillar metrics use their own evaluation windows (for example, ODR over a trailing window). A single bad day does not flip the status instantly; it influences the rolling rate. |
| Policy events | Policy violations (IP complaints, authenticity, restricted products) can move the status sharply and quickly, independent of the gradual customer-service and shipping rates. |
| Reason | Direction | Why |
|---|---|---|
| Refresh latency | Ours within minutes | Amazon may update the status on its dashboard slightly before our next poll reflects it. The gap is short. |
| Band vs score | Same band, different detail | This gauge shows the status band. If you are reading the precise AHR number on Amazon, expect the band to agree even when you are watching the score tick within a band. |
| Marketplace scope | Either direction | Account health is evaluated per marketplace region. A seller active in several regions should confirm which marketplace the connected account reflects. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
ebay.ebay-health-score | Marketplace peer. eBay’s seller standards and health score measure the same idea, operational standing, with a different methodology and cadence (eBay evaluates monthly; Amazon rolls continuously). | Independent systems. A seller can be Healthy on Amazon and below-standard on eBay if the weaknesses are channel-specific. |
shopify.total-revenue | Channel context. No direct relationship, but when Amazon health drops, the risk of an account freeze makes own-site revenue resilience more important. | Strategic context, not a reconciliation. |