Skip to main content
Card class: Hero • Category: Marketplace
Sum of (suppressed_listings × velocity × ASP) + (no-buy-box ASINs × loss-share × velocity), recoverable revenue.

​
At a glance

Live, real-time projection of revenue your Amazon account is currently failing to capture, summed across two failure modes: (a) listings that exist in your catalogue but are suppressed (hidden from search) for missing or invalid attributes, and (b) ASINs where you do not hold the Buy Box. Account-level, settlement currency, refreshed every 15 to 60 minutes.
What it countsSUM(suppressed_listings.expected_velocity × ASP) + SUM(non_buy_box_ASINs.lost_share × velocity × ASP), capped at 1.5x trailing 30D per ASIN to keep the recoverable estimate operationally honest.
API endpoint + reportSP-API Listings API GET /listings/2021-08-01/items for suppression state, Pricing API GET /products/pricing/v0/items/{Asin}/offers for Buy Box state, Reports API report type GET_SALES_AND_TRAFFIC_REPORT for ASP and velocity.
ASIN vs account scopeCalculated per ASIN, summed for the live headline. The drill-down ranks ASINs by $/day at risk so the merchant can act on the top 3 to 5 first.
Buy Box impactHalf of this card IS the Buy Box impact (the second SUM term). The other half is suppression. Both are recoverable upside the moment the underlying issue is fixed.
FBA vs FBMBoth. FBA suppression is rarer (Amazon validates listings on intake) but FBA Buy Box loss is more punishing because Prime-eligible buyers default to the Buy Box winner.
Fees / commissionGross. Recoverable shown is pre-fee. Discount by ~13% (typical referral + FBA blended) for net.
RefundsNot applicable. This is a forward projection, not a settled order figure.
CancellationsNot applicable.
CurrencySettlement currency, post-Amazon-FX.
Marketplace dynamicsBuy Box can flip in minutes; suppressions can take hours to clear after a fix. The card weights both at their realistic recovery time.
Return-window vs refund-windowNot applicable to a forward-looking estimate.
Time windowRT (real-time, refresh interval 15 to 60 minutes depending on account size and SP-API rate-limit budget).
Alert trigger>$0, the card is designed to be quiet at zero. Any non-zero reading deserves attention.
Rolesowner, finance, marketing.

​
Calculation

Calculated automatically from your Amazon (Selling Partner) 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 UK FBA seller running 240 ASINs across home and kitchen on amazon.co.uk and amazon.de. Settlement currency GBP. Card snapshot at 14:22 BST on 22 Apr 26. The headline reads £12,840/month at risk. Drilling in:
Failure modeASINs affectedMonthly velocity (units)ASP$/month at risk
Suppressed (missing GTIN)4 ASINs220 units expected£18 avg£3,960
Suppressed (image policy)2 ASINs80 units expected£24 avg£1,920
Buy Box loss <60% (B07KIT0001)1 ASIN380 units£29.99£4,560
Buy Box loss 65-85% (5 ASINs)5 ASINs1,840 units£18 avg£2,400
Total live12 ASINs£12,840 capped
Five things to notice that are specific to Amazon:
  1. Half the loss is fixable in minutes. The two image-policy suppressions (£1,920) need a single replacement image upload through Listings API or Manage Inventory. The card highlights this as “fast wins” because the recovery curve on suppression-clearing is hours, not days.
  2. Buy Box loss = sales loss, instantly. B07KIT0001 alone accounts for £4,560/month. Investigation in Manage Pricing showed a German reseller had listed at £27.49 (£2.50 below the brand’s £29.99). The brand re-priced to £27.99 for 48 hours, reclaimed Buy Box at 92%, and the card dropped to £8,280/month within 4 hours.
  3. Commission erodes 12 to 15%. The £12,840 headline is gross. After Amazon’s 8% referral fee on home and kitchen and FBA pick/pack of about 4 to 6%, the net recoverable is closer to £10,900/month. Mentally discount before sizing the operational effort.
  4. GTIN suppressions are catalogue-side, not pricing-side. The 4 ASINs flagged “Suppressed (missing GTIN)” had been auto-suppressed by Amazon on 11 Apr 26 when Amazon tightened GTIN validation in the home category. The merchant didn’t know until the card flagged it. In the 11 days since, those 4 ASINs lost ~80 units of sales each, real money gone forever, not just at risk. The card flags future loss; past loss is not recoverable.
  5. Out-of-stock punishes you for weeks. This card includes only currently-suppressed and currently-non-Buy-Box ASINs. ASINs that recently came out of an OOS state but have not yet recovered Buy Box rank are NOT counted here (they’re held in Top Buy Box Loss ASINs instead). The full Amazon recovery curve from OOS often runs 14 to 28 days; this card captures only the live, fixable portion.

​
Sibling cards merchants should reference together

This card is the action queue. It tells you what to fix today. Pair it with these to triage:
CardWhy pair it with Revenue at Risk (live)
Buy Box Loss ValueThe Buy Box-only subset of this card. Useful when you want to focus on pricing wars rather than catalogue issues.
Suppressed ListingsThe suppression-only subset. Catalogue-side fixes.
Top Buy Box Loss ASINsPer-ASIN priority list for the Buy Box subset.
Catalogue Drift vs DTCDrift between Amazon and DTC listings often correlates with suppression risk (price changed on DTC, didn’t sync to Amazon).
Days of CoverOOS = automatic Buy Box loss. Low days of cover predicts a near-future bump in this card’s headline.
Account Health StatusIf account health flips to “At Risk”, expect this card’s headline to spike (Amazon throttles Buy Box eligibility).
Total RevenueThe headline this card forecasts a recovery against. The ratio (Revenue at Risk ÷ Total Revenue) is your “leakage rate” and a useful KPI on its own.
Shopify Total RevenueDTC counterpart for hybrid brands. No equivalent “revenue at risk” exists on Shopify (you control the storefront entirely).

​
Reconciling against the vendor’s own dashboard

Where to look in Amazon Seller Central: Amazon does not publish a “live revenue at risk” figure. The card synthesises it from three Seller Central views:
  1. Inventory → Manage Inventory → Suppressed shows the live list of suppressed ASINs and the reason. This is the catalogue half of the card.
  2. Reports → Business Reports → Detail Page Sales and Traffic by Child Item shows the Buy Box Percentage per ASIN. ASINs at <85% are contributing to the Buy Box half.
  3. Pricing → Manage Pricing shows the Status column per ASIN with Buy Box-loss reasons.
Why our number may legitimately differ from anything you’d build manually in Seller Central:
ReasonDirectionWhy
Time zoneBoundary edges onlyAmazon’s reports run in Pacific Time. The “live” half of this card is timestamp-agnostic (it’s the current state, not a window), but velocity inputs use a 30-day trailing window which boundaries differ by 8 hours.
Settlement-period lagNot applicableThis card is forward-looking, not settlement-based. Disbursement timing is irrelevant.
API rate limitsOurs is sampled per ASINThe Pricing API is throttled. For 1,000+ ASIN catalogues the connector samples every 4 to 8 hours, not continuously. Brief Buy Box flips of <2 hours can be missed. The Listings API (suppressions) refreshes every 30 to 60 minutes.
Reports API generation latencyEitherVelocity and ASP inputs come from the Sales and Traffic Report which Amazon generates async, with up to 4-hour latency on first generation. Our card uses the most recent successful pull, so a sudden 30D velocity change shows here on a 4 to 8 hour lag.
ASP-cap arithmeticOurs is conservativePer-ASIN risk is capped at 1.5x trailing 30D sales to prevent infinite-demand arithmetic. Seller Central has no such cap and would produce wildly higher figures if you tried to compute this manually.
Cross-connector reconciliation:
CardExpected relationshipWhat causes legitimate divergence
shopify.total_revenueNo relationship.Shopify has no concept of suppression or Buy Box (you control the storefront). The only DTC-side analogue is “products with broken images / missing prices”, which is a different kind of catalogue health.
bigcommerce.total_revenueNo relationship.Same as Shopify.
amazon_ads.aads_acosLoose: ad spend on suppressed or non-Buy-Box ASINs is wasted.Use Ad Spend on OOS ASINs for the explicit overlap.
shipbob.fulfilment_rateIndirect, FBM onlySlow ShipBob fulfilment can cause Amazon to demote FBM listings, which can lead to Buy Box loss. Doesn’t apply to FBA.

​
Known limitations / merchant FAQs

The card says £8,000/month at risk but I’m not sure how to think about that vs my actual Amazon revenue. The right frame is “leakage rate”. Divide this card’s headline by Total Revenue. A healthy Amazon book runs at <2% leakage. 5 to 10% means you have a small, fixable list of ASINs to address. >15% means there’s a structural problem (catalogue migration gone wrong, hijacker spree, account-health flag). The absolute pound figure matters less than the ratio. My number just dropped from £12,000 to £4,000 in an hour. Did something break? Most likely the card just refreshed after a Pricing API sample cycle and one or two top ASINs reclaimed the Buy Box. This is normal volatility for the live view; recovery on Buy Box can be near-instant once a competitor reseller goes out of stock or you re-price. The other common cause is a suppression clearing: if you fixed a missing GTIN on 4 ASINs at the same time, those four lines disappear from the card simultaneously. Less likely: an SP-API outage where suppression data temporarily isn’t returning, in which case the card under-reports. Check Account Health Status if you suspect an outage. How is this different from Buy Box Loss Value? This card is the superset. Buy Box Loss Value is the second SUM term only. Revenue at Risk also includes suppressions (the first SUM term, often the larger of the two for catalogues that haven’t been audited recently). Use Revenue at Risk for the morning headline; use Buy Box Loss Value when you’ve already cleared suppressions and need to focus on pricing wars. Does Amazon’s commission affect what I can recover? The headline is gross, before Amazon’s referral fee (8 to 15% by category) and FBA fee (4 to 8% on most physical SKUs). Net recoverable is roughly 13% lower. Pair with Net Revenue for the post-fee view. Don’t mistake this card for “money you’ll bank if you fix it”; bank is roughly 87% of the headline. ACOS spikes when this card spikes. Why? Because ad spend on a suppressed or non-Buy-Box ASIN is largely wasted. The click sends shoppers to a product page where the “Buy Now” button hands the order to the Buy Box winner, not you. ACOS (ad cost ÷ ad-attributed sales) inflates because attribution drops. This is so consistent that a sudden ACOS rise is often diagnosed by checking this card first. Cross-check on Ad Spend on Out-of-Stock ASINs. I sell on amazon.co.uk, amazon.de, and amazon.com. Are all marketplaces aggregated? Yes, account-level, in your settlement currency. But suppression and Buy Box state are per-marketplace; the same ASIN can be suppressed on amazon.de and live on amazon.co.uk. The drill-down splits by marketplace. Note: amazon.com (US) is a separate seller account from Amazon Europe; if you operate both, you have two SP-API connectors, and this card’s headline sums both connectors when you view the account-rollup view. Settlement timing, when will the recovered money actually land? Standard 14-day Amazon disbursement cycle from the moment the recovered orders begin flowing. So if you fix the suppressions today and orders start tomorrow, the cash hits your bank account around 14 to 16 days from today (depending on where you are in the disbursement window). Use Pending Settlement for the cash-flow view; use this card for the operational queue. Why does the return-window not affect this card? Because this card forecasts gross revenue you’d capture if you fixed the listed issues, not net revenue you’d retain after returns. Amazon’s 30-day return window will erode the realised recovery, but the card doesn’t haircut for that. If your category has a high return rate (apparel ~30%, electronics ~10%, supplements ~3%), discount the headline by your category’s typical return rate before sizing the operational effort. Can I trust the live volatility, or should I look at a moving average? The card is intentionally live (RT). Spikes and drops are signal, not noise: they mean a competitor just changed price, a suppression just cleared, an ASIN just went OOS. If you want a smoother view, look at the daily peak headline as your daily KPI, or reference Buy Box Loss Value which uses 30-day inputs and is structurally less jumpy. The two cards together give you both the live alarm and the steady trend.

​
Tracked live in Vortex IQ Nerve Centre

Revenue at Risk (live) is one of hundreds of KPI pulses Vortex IQ tracks across Amazon (Selling Partner) 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.