At a glance
A single composite score, on a 0 to 100 scale, that rolls up the handful of signals that actually decide whether your Amazon channel is healthy: authorisation / Buy Box win rate, inverse suppression load, and inverse account-health drift. It is the one number to glance at when you do not have time to read every card. A high score means listings are buyable, you are winning the Buy Box, and your account standing is steady. A falling score is the prompt to open the detail cards and find what moved.
| What it is | A weighted composite of the most decision-relevant Amazon signals, expressed as a single 0 to 100 number. Higher is healthier. It is designed to move before any single underlying card hits its own alert, so it is an early aggregate warning. |
| What feeds it | A blend of: authorisation / Buy Box win rate (are your offers actually winning the sale), inverse suppressed-listing load (more suppressions push the score down), and inverse account-health creep (a drifting account-health signal drags it down). The exact weighting is tuned to reflect real revenue impact. |
| Why a composite | No single card tells the whole story. Buy Box can be strong while suppressions quietly climb, or account health can drift while sales look fine. The composite catches a deterioration that no one card would flag on its own. |
| How to act on it | Treat the score as a thermostat, not a diagnosis. When it falls, open the contributing cards (Buy Box win rate, suppressed listings, account health) to see which input moved and act there. |
| Marketplace scope | Computed per connected marketplace, since Buy Box, suppression, and account-health signals are region-specific. |
| Time window | RT/7D (live composite, with a 7-day view to read the trend rather than a single snapshot) |
| Alert trigger | <70, driven by the Executive Command Centre detection layer. A sub-70 score means at least one major input has deteriorated enough to warrant a look. |
| Roles | owner, finance, operations |
Calculation
Calculated automatically from your Amazon Seller Central data. The score blends authorisation / Buy Box win rate, inverse suppressed-listing load, and inverse account-health creep into a single 0 to 100 figure, weighted to reflect revenue impact. See the At a glance summary above for the inputs and the worked example below for how a falling score reads.Worked example
A UK consumer-electronics-accessory brand on amazon.co.uk. The owner glances at the Executive Command Centre on 14 Mar 26 and sees the score has slipped.| Input signal | Last week | This week | Direction |
|---|---|---|---|
| Buy Box win rate (top ASINs) | 96% | 88% | Down (third-party offers appeared) |
| Suppressed listings | 0 | 2 | Up (worse) |
| Account-health creep | Steady | Slight drift (a late-shipment uptick) | Up (worse) |
| Marketplace Health Score (this card) | 91 | 68 | Down, now below 70 |
- One number caught three small slips. None of the three inputs alone was catastrophic this week, but together they pulled the composite from 91 to 68 and tripped the alert. That is the whole point of the score: it aggregates deterioration that no single card would yet flag loudly.
- The score points, it does not diagnose. A 68 tells the owner to look, not what to fix. The next move is to open Buy-Box Win Rate (top-50 ASINs), Suppressed Listings, and Account Health Status to see which input moved most.
- Buy Box did most of the damage here. The 8-point Buy Box drop, caused by new third-party offers, is the biggest single contributor. That routes to a pricing or offer-competitiveness decision.
- Read the 7-day view, not the snapshot. A single real-time dip can be noise. The 7-day trend confirms whether the score is genuinely deteriorating or just had a wobble.
- Above 70 is not a free pass. A score of 75 with a slowly falling trend still deserves attention. Use the trend direction, not just the absolute number against the threshold.
Sibling cards merchants should reference together
The score is an aggregate. These are the cards it rolls up, and the ones you open when it falls:| Card | Why pair it with Marketplace Health Score |
|---|---|
| Buy-Box Win Rate (top-50 ASINs) | A primary input. A drop in Buy Box win rate is the most common reason the composite falls, and the fastest revenue lever to fix. |
| Suppressed Listings | An inverse input. Rising suppressions push the score down. Open this to see which ASINs went dark. |
| Account Health Status | The account-standing input. A drifting account-health signal drags the composite down before suspension risk becomes acute. |
| Account Health Creep | The trend version of account health that feeds the inverse-creep term in the composite. |
| Revenue at Risk (live) | The pound translation. Where the health score says “something is wrong”, this card estimates what it is costing. |
| Order Defect Rate | The most dangerous account-health signal. A rising ODR is the kind of drift that should pull the composite down hard. |
Reconciling against Amazon Seller Central
Where to look in Seller Central: There is no single native Amazon equivalent of this composite, because it is a Vortex IQ roll-up. To reconcile, check the inputs individually:Seller Central → Performance → Account Health for the account-health and defect signals; Catalogue → Manage All Inventory (filter Suppressed) for the suppression load; and the Buy Box / featured-offer columns in Manage Inventory or your business reports for the Buy Box signal.If each input matches its own card, the composite follows. The Account Health Rating that Amazon shows is conceptually similar in spirit (a single health read), but it is computed differently and is not the same number. Timing and reporting-lag table:
| Topic | Detail |
|---|---|
| Composite freshness | The score is recomputed from its inputs on each sync. It is only as fresh as the freshest of its underlying signals. |
| Input lag | Buy Box and suppression signals are close to real time; account-health signals can lag because Amazon updates some defect metrics on a rolling window. The composite inherits the slowest input’s lag for that term. |
| 7-day smoothing | The 7-day view smooths single-snapshot noise. Use it to judge a genuine trend rather than a momentary dip. |
| Weighting | The inputs are weighted by revenue impact, so a Buy Box drop on a top ASIN moves the score more than the same drop on a long-tail ASIN. |
| Reason | Direction | Why |
|---|---|---|
| Different formula | Not directly comparable | Amazon’s Account Health Rating and this composite use different inputs and weights. They tend to move in the same direction but will not match numerically. |
| Includes Buy Box and suppressions | Ours broader | The composite blends Buy Box and catalogue suppression, which Amazon’s account-health view does not directly include. |
| Input lag | Ours follows the slowest input | If an account-health signal is mid-update on Amazon’s side, the composite reflects the last synced value. |
| Marketplace scope | Mismatch if regions differ | Confirm both the composite and the underlying Amazon views are scoped to the same marketplace. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
amazon-share-of-total-revenue | Context, not reconciliation. If Amazon is a large share of total revenue, a falling health score is a bigger business risk and deserves faster action. | The score is Amazon-internal; revenue share is cross-channel. They inform each other but do not reconcile numerically. |
shopify.store_health | Independent health reads. Each channel has its own health composite built from channel-specific signals. | A healthy Shopify store says nothing about Amazon suppression or Buy Box, so the two scores can diverge widely and legitimately. |