Skip to main content
Metrics type: Key Metrics • Category: Executive Command Centre

​
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.

​
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.
Five things to notice:
  1. 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).
  2. 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).
  3. 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.
  4. The 30-day projection is the wake-up number. 2,544adayiseasytoignore;2,544 a day is easy to ignore; 76,320 a month is not. The card surfaces the daily run-rate precisely because owners under-react to per-day leakage.
  5. 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:

​
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: Why our number may legitimately differ from Seller Central: Cross-connector reconciliation against other connectors the same seller may run:

​
Known limitations / merchant FAQs

Is this lost revenue or revenue at risk? At risk and recoverable. It estimates revenue you are currently leaking from fixable conditions (suppressions and Buy-Box loss), not sales already lost in the past. Fix the cause and the figure drops; that is the whole design. It is not a tally of demand you never had. Why does any value above zero trigger an alert? Because both drivers are operational and fixable. A suppressed bestseller or a lost Buy Box on a high-velocity ASIN is money walking out the door that a same-day action recovers. The card is deliberately sensitive so leakage never sits unnoticed. How is the dollar figure built? Suppression component: each suppressed ASIN’s recent velocity x its average selling price (it sells zero while suppressed). Buy-Box component: each no-Buy-Box ASIN’s lost demand share x velocity x price. Both are estimates grounded in recent run-rate, not precise forecasts. Why is it an estimate and not exact? Two reasons. Velocity is a proxy for demand a suppressed listing would still capture, and Buy-Box loss share is modelled from offer and pricing signals rather than read per order. Treat the figure as a well-grounded estimate of recoverable upside, accurate enough to prioritise action. It dropped suddenly, what happened? Almost certainly a suppression cleared or a Buy Box was won back. Because the card is live, the moment a high-velocity ASIN becomes buyable again the figure falls. That instant feedback is intentional, it confirms your fix worked. Where do I start when this is high? Suppressions on high-velocity ASINs first, they leak 100% of the ASIN’s revenue and are usually a quick listing fix. Then Buy-Box losses, which are partial leaks fixable by repricing or restocking. Use New Suppressions (24h) and Top Buy-Box-Loss ASINs as your worklists.

​
Tracked live in Vortex IQ Nerve Centre

Revenue at Risk (live) is one of hundreds of KPI pulses Vortex IQ tracks across Amazon Seller Central and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.