Skip to main content
Card class: HeroCategory: Marketplace
Buy-box-loss × 30-day units × ASP, recoverable revenue if buy-box reclaimed.

At a glance

Estimated revenue you would have made on each ASIN if you’d held the Buy Box for 100% of the period, minus what you actually made. The recoverable upside if Buy Box is reclaimed. ASIN-level, summed to account-level for the card headline.
What it countsSUM_per_ASIN((1 − buy_box_win_rate) × trailing_30d_units × ASP), where buy_box_win_rate is from the SP-API Catalogue Items / Pricing API offer feed, units come from Reports API GET_FLAT_FILE_OPEN_LISTINGS_DATA, and ASP is your trailing 30-day average selling price for that ASIN.
API endpoint + reportSP-API Pricing API GET /products/pricing/v0/items/{Asin}/offers for Buy Box state, plus Orders API for unit history, plus Reports API report type GET_SALES_AND_TRAFFIC_REPORT for ASP backfill.
ASIN vs account scopeCalculated per ASIN, summed for headline. Click into the card for the per-ASIN drill. The top 10 ASINs typically drive 70 to 90% of the loss value.
Buy Box impactThis card IS the Buy Box impact, expressed in pounds. It is the financial translation of Buy Box Trend.
FBA vs FBMBoth. Buy Box loss can affect either. FBA-fulfilled ASINs typically hold Buy Box more reliably than FBM (Amazon weights Prime-eligibility heavily), so a Buy Box loss on an FBA ASIN is a stronger signal that something is genuinely wrong.
Fees / commissionGross. The number assumes you’d have captured the full ASP if you’d held the Buy Box. Real recoverable revenue is 12 to 15% lower after Amazon’s referral fee and FBA fee. Mentally discount this card by 13% for net.
RefundsNot applicable. This is a forward-looking estimate, not a settled order figure.
CancellationsNot applicable for the same reason.
CurrencySettlement currency. ASPs are sourced post-FX, in the seller’s settlement currency, before summation.
Marketplace feesEstimated headline ignores fees (gross). For the post-fee version multiply by ~0.87 (UK / EU, typical electronics) or ~0.83 (US / consumer apparel).
Time window30D (fixed, this is a 30-day forward-looking projection based on the prior 30 days of velocity).
Alert trigger>$1k/month, driven by sentiment_key: buy_box_win_rate.
Rolesowner, marketing, finance.

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 US Amazon-first DTC supplements brand. The brand sells 64 ASINs, but the top 6 SKUs drive 78% of revenue. Period: 02 Apr 26 to 01 May 26. The card is reading $8,420/month at risk as the headline. Drilling into the per-ASIN breakdown reveals where the loss is concentrated:
ASINProductBuy Box win %30D units soldASPImplied lost units$/month at risk
B08AAA1111Multivitamin (60ct)42%1,240$24.991,712$42,777 estimated, but the card caps it at the realistic recovery ceiling
B08AAA2222Magnesium glycinate88%920$19.99125$2,498
B08AAA3333Sleep stack96%480$34.9920$700
B08AAA4444Probiotic 50B73%380$29.99140$4,199
Other 60 ASINs (combined)mixed91% avg4,200$22 avg416$9,152
Cap-adjusted total$8,420 capped
Five things to notice that are specific to Amazon:
  1. One ASIN is dragging the entire card. B08AAA1111 (the multivitamin) is at 42% Buy Box win, far below the 88 to 96% win rates on every other top SKU. The headline “$8,420/month” is mostly this ASIN. The fix is operationally narrow: figure out why this ASIN lost Buy Box and recover it. Open Top Buy Box Loss ASINs for the prioritised list.
  2. Buy Box loss = sales loss, instantly. The card assumes that if you reclaim Buy Box you’ll capture the lost units at the same ASP. That’s broadly true on Amazon: the Buy Box winner gets ~80 to 90% of all sales for that ASIN; everyone else fights for scraps in the offer carousel. There’s no equivalent on Shopify or eBay; this dynamic is uniquely brutal on Amazon.
  3. Commission erodes 12 to 15%. The headline 8,420/monthisgross.AfterAmazons158,420/month is gross. After Amazon's 15% referral fee on supplements (the brand's category) and FBA pick/pack/ship of about 6 to 8% on a 25 unit, the net recoverable is closer to $6,500/month. Always discount this card mentally for net before pricing the recovery effort.
  4. The implied-lost-units is capped. The raw arithmetic for B08AAA1111 (1,240 units at 42% win = 1,712 lost units if you’d held 100%) is mathematically true but operationally optimistic, you would not have sold 2,952 units a month (real + implied) because demand isn’t infinite at this ASP. The card caps the per-ASIN figure at 1.5x your trailing 30D sales (whichever is lower), which is why the headline reads 8,420not8,420 not 58,000.
  5. Out-of-stock punishes you for weeks. If the Buy Box loss on B08AAA1111 was caused by a recent stockout (FBA inventory hit zero on 12 Apr 26 and replenished 19 Apr 26), the recovery curve is slow. Amazon de-prioritises the listing in search rank for 7 to 21 days post-replenishment. The “$8,420/month” headline can persist even after you fix the root cause; the recovery shows on Buy Box Trend, not here.

Sibling cards merchants should reference together

This card is the financial translation of Buy Box state. Pair it with these to act:
CardWhy pair it with Buy Box Loss Value
Buy Box TrendThe leading indicator. Loss on the Trend card precedes loss on this card by 24 to 72 hours.
Buy Box AvgThe point-in-time win rate. Useful as the “today” version of Trend.
Top Buy Box Loss ASINsThe per-ASIN priority list. Action starts here.
Hijack RiskHijackers (counterfeit listings on your ASIN) are a common Buy Box-loss cause. Check first.
Days of CoverOut-of-stock = automatic Buy Box loss. If days of cover is below 14 on a top ASIN, that’s why.
Total RevenueThe headline that this card forecasts a recovery upside against.
Net RevenueThe post-fee figure. Discount this card by ~13% to estimate net recoverable.
Amazon Ads ACOSIf you’re advertising an ASIN you don’t hold the Buy Box on, the ad spend is largely wasted (the click goes to the Buy Box winner, not you). Cross-check on Ad Spend on OOS ASINs.

Reconciling against the vendor’s own dashboard

Where to look in Amazon Seller Central: Amazon does not publish a “Buy Box loss revenue” figure directly. The closest equivalents are stitched together from three views:
  1. Reports → Business Reports → Detail Page Sales and Traffic by Child Item. Pick a 30-day window and look at the Buy Box Percentage column per ASIN. ASINs at <85% Buy Box are the ones contributing to this card.
  2. Inventory → Manage Inventory. The Featured Offer (Buy Box) Price column shows the current Buy Box price per ASIN; if your price is higher than this, you’ve lost the Buy Box on price.
  3. Pricing → Manage Pricing. The Status column flags ASINs where you do not hold the Buy Box and the reason (price, eligibility, etc.).
Why our number may legitimately differ from anything you’d build manually in Seller Central:
ReasonDirectionWhy
Time zoneBoundary daysAmazon’s Buy Box Percentage report is in Pacific Time regardless of seller location. Vortex IQ Nerve Centre uses UTC. The 30-day window can shift by up to 8 hours, causing different ASIN snapshots near the period boundary.
Settlement-period lagTheirs lower (sometimes)Seller Central may not show Buy Box state for orders still in the unshipped queue. Vortex IQ pulls Buy Box state in real time from the Pricing API.
API rate limitsOurs is sampledThe Pricing API is throttled to about 10 calls/second across the seller account. For 5,000+ ASINs the connector samples Buy Box state every 4 to 8 hours, not continuously. Brief Buy Box flips of <2 hours can be missed.
Reports API generation latencyEitherThe Business Report behind Seller Central’s Buy Box Percentage column is async-generated and lags 24 to 48 hours. Our card is closer to live, so a sudden Buy Box loss shows here before it shows in Seller Central.
ASP-cap arithmeticOurs is conservativeWe cap implied-lost-units at 1.5x trailing 30D sales per ASIN. Seller Central’s raw maths (Buy Box loss × demand) has no cap and can produce wildly optimistic numbers. The cap exists to keep the recoverable estimate operationally honest.
Cross-connector reconciliation:
CardExpected relationshipWhat causes legitimate divergence
amazon_ads.aads_acosInverse: rising Buy Box loss usually inflates ACOSAds on a non-Buy-Box ASIN burn money. The click goes to the Buy Box winner, not the advertiser. Pair this card with Ad Spend on OOS ASINs.
shopify.total_revenueNo relationship.Buy Box is an Amazon-only construct. Shopify has no concept of it (your DTC site is your only listing).
shipbob.fulfilment_rateIndirect, FBM onlyIf FBM-fulfilled ASINs are losing Buy Box on shipping-time signals, ShipBob’s fulfilment rate is the upstream cause. Doesn’t apply to FBA.

Known limitations / merchant FAQs

My Buy Box Loss Value just spiked to $5,000/month. What do I do first? Open Top Buy Box Loss ASINs and look at the top 1 to 3 entries. In nearly every case, 70 to 90% of the loss is concentrated on a small handful of ASINs. For each: (1) check your offer price vs the current Buy Box price (Pricing API or Manage Pricing in Seller Central), (2) check FBA inventory level and last replenishment date on Days of Cover, (3) check for hijackers via Hijack Risk, (4) confirm Prime eligibility (delisted FBA = no Prime badge = Buy Box risk). The fix is rarely “lower your price”; far more often it’s an inventory or eligibility issue masquerading as a price problem. Why is the recoverable number capped at 1.5x my current sales? My pre-loss numbers were higher. The cap exists because the raw arithmetic ((1 − Buy Box win) × current units) treats demand as infinite at the current price. In reality, if you reclaim Buy Box you’ll recover toward your historic baseline, not infinitely beyond it. The 1.5x cap is calibrated against historic recovery curves on similar ASINs and gives an operationally honest number. If your pre-loss baseline was 3x your current Amazon sales, the recovery will likely take 30 to 60 days even after Buy Box returns; the headline figure here is the 30-day estimate, not lifetime upside. ACOS vs ROAS, why does Amazon talk about Buy Box impact in ad-cost terms? Because the relationship is direct. ACOS (Ad Cost of Sale) is ad spend ÷ ad-attributed sales. If you’re advertising an ASIN you don’t hold the Buy Box on, your clicks send shoppers to a product page where the “Buy Now” button hands the order to a competitor. Your ad spend goes up; your attributed sales fall; ACOS spikes. A persistent ACOS above 50% on top ASINs almost always indicates a Buy Box problem, not an ad targeting problem. Cross-check on Ad Spend on Out-of-Stock ASINs and Amazon Ads ACOS. FBA fees keep eroding the recoverable amount. Should I switch to FBM to keep more margin? Almost never on top ASINs. FBA-fulfilled ASINs win Buy Box at roughly 2 to 3x the rate of FBM ASINs at similar price points (Amazon’s algorithm heavily favours Prime-eligible offers). Switching a top ASIN from FBA to FBM to save 6 to 8% in fees will typically halve your Buy Box win rate, costing 30 to 50% of unit volume. The maths almost never works on volume SKUs. FBM makes sense for: (a) very-high-margin / low-volume / heavy / oversized items, (b) hazmat or restricted items, (c) seasonal closeouts where you’d rather not pay long-term storage fees. See FBA Fees and Storage Fees for the cost view. I sell on multiple marketplaces (UK + DE + FR). Does this card aggregate Buy Box loss across all of them? Yes, account-level. But Buy Box is per-marketplace; you can hold Buy Box at 95% on amazon.co.uk and 40% on amazon.de for the same ASIN if a German reseller is undercutting. The drill-down view splits by marketplace. The headline figure sums all marketplaces in your settlement currency. Common pattern: amazon.de loses Buy Box first because EU resellers are more aggressive on price; amazon.co.uk usually holds longer. When Amazon takes 14 days to settle, does this card account for that? Not directly. This is a forward-looking estimate of recoverable revenue at the headline (gross) level, not a settled-cash figure. The settlement lag matters for cash flow planning (Pending Settlement), not for sizing the Buy Box recovery opportunity. Once you reclaim Buy Box, the orders flow through normally and settle on Amazon’s standard 14-day cycle. Why does the return-window matter, and does this card factor it in? Amazon’s standard 30-day return window means a recovered order today might be partially refunded 30 days later, eroding the realised recovery. This card does NOT haircut for expected refunds; it shows gross recoverable. If your category has a high return rate (apparel typically 25 to 40%, electronics 8 to 12%, supplements 2 to 5%), discount the headline by your category’s typical return rate before sizing the operational effort. Pair with Return Rate for your real number. My Shopify-Amazon channel is connected, will Buy Box recovery double-count revenue? Only if you’re using the Shopify Amazon channel app, which most brands aren’t. If you are, Amazon orders flow into both your Amazon SP-API connector and your Shopify connector at delay, double-counting. The Buy Box recovery here is for Amazon-side revenue only; if Shopify Amazon channel app is on, you’ll need to filter tags = "amazon" orders out of Shopify Total Revenue to avoid double-counting the recovery. See the FAQ on the Total Revenue card for the channel-app gotcha. Why is today’s number so volatile? Buy Box state can flip multiple times an hour during pricing wars between resellers. The Pricing API samples every 4 to 8 hours per ASIN (rate-limit constrained), so “today’s” reading is stale within minutes of any flip. The 30-day rolling figure is what’s stable. Use the daily figure as a directional signal only; size your operational response on the 7-day or 30-day trend, not the spot reading.

Tracked live in Vortex IQ Nerve Centre

Estimated Revenue Lost to Buy-Box Loss 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.