At a glance
The single number that tells an owner how much revenue is leaking right now, and is recoverable if acted on. It estimates the run-rate revenue tied up in two fixable failures: listings currently suppressed (selling zero while live demand exists) and ASINs that have lost the Buy Box (the offer exists but the order is going to someone else). It is deliberately a live, recoverable figure, not a forecast of lost sales. Any value above zero is money on the table that a same-day fix could win back.
| What it estimates | Recoverable revenue at risk = the revenue from suppressed listings that cannot sell (velocity x average selling price) plus the revenue from ASINs without the Buy Box (Buy-Box loss share x velocity x price). Both components are conditions you can fix. |
| Suppressed-listing component | For each currently suppressed ASIN: its recent velocity multiplied by its average selling price, projected over the period. A suppressed listing is live in your catalogue but not buyable, so it converts at zero until the suppression is cleared. |
| Buy-Box-loss component | For each ASIN not holding the Buy Box: the share of its demand you are losing to other offers, multiplied by velocity and price. The listing sells, but the order routes to whoever holds the Buy Box. |
| Why “recoverable” | Both drivers are operational, not market. Fix the suppression (correct the listing, restore compliance) or win back the Buy Box (price, stock, seller metrics) and the revenue returns. This is not lost-forever demand. |
| Why “live” | It reads current state, not a historical window. Clear a suppression at noon and the figure drops the same day. |
| What it is not | Not a guarantee, an estimate built on velocity x price assumptions. Not a measure of demand you never had. Not the same as actual lost sales already booked. |
| Time window | RT (real time) |
| Alert trigger | >$0, any non-zero recoverable risk fires the card |
| Roles | owner, finance, marketing |
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 consumer-electronics-accessory seller checks the card at 09:00 on 14 Apr 26. Figures are illustrative.| Driver | ASIN(s) affected | Velocity (units/day) | Avg selling price | Loss share | Daily revenue at risk |
|---|---|---|---|---|---|
| Suppressed listing | Bestselling charger (image policy flag) | 60 | $22 | 100% (zero sales) | $1,320 |
| Suppressed listing | Cable 3-pack (missing attribute) | 18 | $15 | 100% (zero sales) | $270 |
| Buy-Box loss | Wall adapter (priced above competing offer) | 40 | $18 | 70% | $504 |
| Buy-Box loss | Car mount (out of stock, FBM offer winning) | 25 | $20 | 90% | $450 |
| Revenue at Risk (live) | 4 ASINs | $2,544 / day |
- The suppressed charger alone is most of the risk. A single bestselling ASIN, suppressed on an image-policy flag, is leaking $1,320 a day because it converts at zero while live. Suppressions on high-velocity ASINs dominate this number; clearing them is almost always the highest-leverage action. See New Suppressions (24h).
- Buy-Box loss is partial, not total. The wall adapter still sells; it just loses 70% of its demand to a cheaper competing offer. The recoverable figure is the lost share, not the whole velocity. Win the Buy Box back (reprice or restock) and most of that returns. See Buy-Box Win Rate (top-50 ASINs).
- Stockouts cause Buy-Box loss too. The car mount lost the Buy Box because it went out of stock and an FBM third-party offer is winning. That is a replenishment problem masquerading as a Buy-Box problem. See Replenishment Recommendations.
- The 30-day projection is the wake-up number. 76,320 a month is not. The card surfaces the daily run-rate precisely because owners under-react to per-day leakage.
- It drops the moment you fix something. This is a live figure. Clear the charger suppression at 11:00 and the card falls by $1,320/day immediately, no waiting for a reporting cycle. That instant feedback is the point.
Sibling cards merchants should reference together
This is the executive headline. These are the cards you open to act on each component:| Card | Why pair it with Revenue at Risk (live) |
|---|---|
| New Suppressions (24h) | The freshest input to the suppression component. New suppressions are the fastest-rising part of this number. |
| Suppressed Listings | The full standing list of suppressed ASINs driving the suppression component. |
| Buy-Box Win Rate (top-50 ASINs) | The Buy-Box health behind the loss component. A falling win rate pushes this card up. |
| Estimated Revenue Lost to Buy-Box Loss | The Buy-Box component in standalone form, useful to isolate that driver. |
| Top Buy-Box-Loss ASINs | The specific ASINs to reprice or restock to recover the Buy-Box share. |
| Revenue Over Time | The actuals. If revenue at risk is rising, expect realised revenue to soften unless the risks are cleared. |
Reconciling against Amazon Seller Central
Where to look in Seller Central: There is no single Amazon-native tile for this; it is a Vortex IQ composite. To reconcile its inputs:Inventory → Manage All Inventory (filter to Suppressed / Inactive) for the suppressed-listing list, and the Buy Box / Featured Offer column in Manage Inventory plus pricing tools for the ASINs not holding the Buy Box.There is no Amazon report that multiplies these by velocity and price into a recoverable-revenue figure; that synthesis is the value the card adds. You can sanity-check the components (count of suppressions, count of no-Buy-Box ASINs) against Seller Central directly. Timing, settlement, and reporting-lag table:
| Topic | Detail |
|---|---|
| Live vs reported | The card reads current suppression and Buy-Box state plus recent velocity. It is live; Amazon’s reports are periodic. Expect the card to react before any Seller Central report updates. |
| Velocity basis | The revenue-at-risk math uses recent velocity as the demand proxy. A suppressed ASIN’s “lost” velocity is its pre-suppression run rate, which is an estimate of demand it would still capture. |
| Buy-Box loss share | The loss component uses the estimated share of demand going to competing offers. This is modelled, not directly reported per order, so it is an estimate. |
| Suppression clearing | When a suppression is fixed, the listing may take a short time to become fully buyable again in Amazon’s systems even after the flag clears; the card will drop on flag clear, slightly ahead of full restoration. |
| Reason | Direction | Why |
|---|---|---|
| No native equivalent | Not directly comparable | Amazon does not publish a recoverable-revenue-at-risk figure. Only the component counts (suppressions, no-Buy-Box ASINs) can be reconciled, not the dollar synthesis. |
| Velocity assumption | Estimate | The card assumes a suppressed ASIN would still sell at its recent run rate. Real recoverable demand may be higher or lower depending on seasonality and substitution. |
| Loss-share modelling | Estimate | Buy-Box loss share is modelled from offer and pricing signals, not read per order, so the Buy-Box component is an approximation. |
| Price drift | Small | Average selling price used in the math is recent; a price change since then shifts the figure slightly. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
amazon.estimated_revenue_lost_to_buy_box_loss | Subset relationship. That card is the Buy-Box component of this one, isolated. This card adds the suppression component on top. | If suppressions are zero, the two converge on the Buy-Box figure. |
amazon.suppressed_listings | Driver, not dollar match. The count of suppressed listings drives the suppression component; this card monetises it by velocity x price. | A suppressed slow-mover adds little revenue at risk; a suppressed bestseller adds a lot. Count and dollars do not move together. |