Skip to main content
Card class: HeroCategory: Marketplace

At a glance

A high-priority alert that fires when several of your top-revenue ASINs lose the Buy Box within a short window, the signature of a competitor price drop, a stock issue, or a hijacked listing. On Amazon, losing the Buy Box is close to losing the sale: the vast majority of orders go to whoever holds it. A burst across your best ASINs is a fast, direct hit to revenue, which is why this is a Hero card watched in real time.
What it countsThe number of top-revenue ASINs that have transitioned from holding the Buy Box to losing it within the last 24 hours. It is a burst detector, not a static win-rate, it looks for clustered, recent losses.
Why “burst”A single ASIN losing the Buy Box is routine noise. Several top earners losing it at once signals a systemic cause: a competitor re-priced, a supplier flooded the listing with offers, your price drifted above the threshold, or you slipped out of stock.
Why the Buy Box mattersThe Buy Box is the default “Add to Cart” offer. The large majority of Amazon sales flow through it, so losing it on a top ASIN usually means that ASIN’s sales collapse to near zero for your offer.
Common causesCompetitor undercutting your price, a third-party seller winning on price or fulfilment, your own price set above the Buy-Box-eligible range, low inventory, or a drop in your seller metrics that affects eligibility.
ScopeFocused on the top-revenue ASINs, where a loss does the most financial damage. The full win-rate picture lives on the dedicated win-rate card.
The fixRe-price to recover eligibility, restock, or investigate a new competing offer. Repricing tools and alerts let you respond within minutes.
Time window24H (a rolling 24-hour burst window)
Alert trigger>3 top-revenue ASINs lost 24h. More than three top earners losing the Buy Box in a day flips the card and notifies owner and marketing.
Rolesowner, 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 UK consumer-electronics seller on amazon.co.uk. Burst detected on 19 Mar 26 between 08:00 and 12:00.
ASINRevenue rankBuy Box beforeBuy Box nowSuspected cause
B0TOP01#2HeldLostCompetitor dropped price 6%
B0TOP02#4HeldLostCompetitor dropped price 6%
B0TOP03#5HeldLostNew 3P offer on the listing
B0TOP04#9HeldLostYour price above eligible range
Buy-Box Loss Burst (this card)4 ASINs lost in 24h
Top-revenue ASINs lost in 24h  =  4   (threshold is >3, so the alert FIRES)
Pattern                         =  B0TOP01 and B0TOP02 lost together to the same competitor price move
Estimated exposure              =  these four ASINs normally drive a large share of daily revenue;
                                   with the Buy Box gone, their orders fall toward zero until recovered
Five things to notice:
  1. Four top earners lost the Buy Box in one morning. That is past the >3 threshold, so the Hero card fires. The clustering, two of them to the same 6% competitor price move, is the tell that this is systemic, not random.
  2. Buy-Box loss is near-total revenue loss for those ASINs. Because most Amazon sales go through the Buy Box, these four ASINs effectively stop selling for this seller until they recover it. That is why the card outranks slower metrics.
  3. The causes are mixed, so the fixes differ. Two are a competitor undercut (re-price to compete or hold margin and accept the loss), one is a new third-party offer (investigate the seller, check for a hijack), and one is self-inflicted, the seller’s own price drifted above the eligible range and just needs lowering.
  4. The financial scale lives on a sibling card. This card counts ASINs; Estimated Revenue Lost to Buy-Box Loss puts a number on the exposure. Read them together to decide how aggressively to respond.
  5. Speed is everything. Buy-Box competition is continuous and automated. The longer the seller waits, the more orders flow to competitors. A repricing response within minutes recovers far more revenue than one made the next day.
The seller re-prices B0TOP01, B0TOP02, and B0TOP04 to recover eligibility, opens an investigation on the new offer against B0TOP03, and the burst clears as Buy-Box ownership returns.

Sibling cards merchants should reference together

A burst alert is the trigger; these cards give you scale, names, and trend:
CardWhy pair it with Buy-Box Loss Burst
Estimated Revenue Lost to Buy-Box LossPuts a £/$ figure on the burst. The count tells you how many ASINs; this tells you how much money.
Buy-Box Win Rate (top-50 ASINs)The steady-state gauge. A burst is a sudden drop in the same underlying signal this card tracks over time.
Top Buy-Box-Loss ASINsNames the specific ASINs in the burst so you can act on the right listings.
Buy-Box Trend (top revenue ASINs)Shows whether the burst is a blip or part of a longer slide in Buy-Box ownership.
ASINs with Third-Party OffersIdentifies listings where competing offers exist, the most common reason you lose the Buy Box.
Ad Spend on Out-of-Stock ASINsIf a burst coincides with stockouts, ad spend may be flowing to ASINs you can no longer win. Check both together.

Reconciling against Amazon Seller Central

Where to look in Seller Central:
Business Reports → Detail Page Sales and Traffic by Child Item shows the Buy Box percentage per ASIN. The Manage Inventory page and the live listing also indicate whether you currently hold the Buy Box (the “featured offer”).
Amazon reports Buy-Box percentage over a period rather than a real-time burst. To reconcile, look for top ASINs whose Buy-Box percentage dropped sharply in the recent window, those are the ones this card flagged. Timing and reporting-lag table:
TopicDetail
TimezoneBusiness Reports use the marketplace’s local timezone. The card’s 24-hour burst window is evaluated consistently; a loss near a day boundary can fall differently between the two views.
Real-time vs reportedThe card detects losses close to real time by sampling Buy-Box state. Amazon’s Business Reports aggregate Buy-Box percentage daily, so a same-day burst may not yet be fully visible in the reported percentage.
Sampling cadenceBuy-Box state is sampled on a frequent cycle (with caching to respect SP-API rate limits). A very brief loss between samples can be missed; a sustained loss is reliably caught.
Eligibility lagAfter you re-price or restock, Buy-Box recovery can take a short while to register. The burst may persist briefly after you have already acted.
Why our number may legitimately differ from Seller Central:
ReasonDirectionWhy
Real-time vs daily aggregateOurs fasterThe card flags the burst as it happens; Amazon’s Buy-Box percentage settles over the day. Same-day, ours leads.
Sampling gapsOurs can miss flickersVery short Buy-Box losses between samples may not register. The card is tuned to catch sustained, revenue-relevant losses, not every momentary flicker.
Top-revenue scopeOurs narrowerThe burst focuses on top-revenue ASINs. A loss on a long-tail ASIN may not count toward the burst even though it shows in Amazon’s full report.
Cross-connector reconciliation against other connectors the same seller may run:
CardExpected relationshipWhat causes legitimate divergence
amazon-ads.active-ads-on-no-buy-box-asinsDirect tie-in. ASINs in the burst that also have live ads are exactly the wasted-spend candidates the Ads connector flags. The two cards should overlap.Timing and scope differences; the Ads card anchors on campaign state, this card on Buy-Box transitions.
ebay.revenue-at-riskConceptual peer. eBay does not have a Buy Box, but its revenue-at-risk framing captures the same “sudden threat to live sales” idea. Used as a pattern peer.Entirely different mechanics; no shared data.

Known limitations / merchant FAQs

What is the Buy Box and why does losing it hurt so much? The Buy Box is the featured offer behind the “Add to Cart” and “Buy Now” buttons. The large majority of Amazon sales go through it. If you lose it on an ASIN, shoppers buy from whichever offer wins it instead, so your sales on that ASIN drop sharply even though the listing is unchanged. Why does this card focus on “bursts” rather than a win rate? Because a single ASIN losing the Buy Box is normal churn. A cluster of top earners losing it at once signals a real event, a competitor re-pricing, a hijack, a stock problem, that needs an immediate response. The burst framing filters out the noise. What are the most common reasons for a burst? A competitor dropping prices across several of your listings, a new third-party seller winning offers, your own prices drifting above the Buy-Box-eligible range, low inventory affecting eligibility, or a dip in your seller metrics. How fast should I respond? Within minutes if you can. Buy-Box competition is continuous and largely automated by repricers. Every hour you wait, more orders flow to competitors. Many sellers run automated repricing precisely so they never have to react manually. Can losing the Buy Box be self-inflicted? Yes, often. If you raise your price above the eligible range, or if your seller metrics dip, you can lose the Buy Box with no competitor involved. The fix in that case is simply to re-price or repair the metric. Why does the burst still show after I re-priced? Buy-Box recovery is not instant; eligibility takes a short while to re-register after a price or stock change. The burst usually clears on the next sampling cycle once Amazon recognises your offer as the featured one again. What if a third-party offer I do not recognise appears? Investigate it as a possible hijack or unauthorised reseller. Cross-check with ASINs with Third-Party Offers. For own-brand ASINs, Brand Registry gives you tools to act on unauthorised sellers.

Tracked live in Vortex IQ Nerve Centre

Buy-Box Loss Burst 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.