Skip to main content
Card class: Hero • Category: Marketplace

​
At a glance

A burst alert that fires when more than 3 of your top-revenue ASINs lose Buy Box in the same 24-hour window. Designed to catch coordinated reseller attacks, FBA-replenishment failures, and account-health-driven Buy Box throttling before the revenue impact hits the headline.
What it countsCOUNT(top_30_revenue_ASINs WHERE buy_box_win_rate dropped > 30 percentage points in last 24H). Uses the prior 30 days to define “top-revenue ASINs” and the last 24 hours of Pricing API samples to detect the burst.
API endpoint + reportSP-API Pricing API GET /products/pricing/v0/items/{Asin}/offers for current Buy Box state, plus the trailing 30-day order history from the Orders API to identify which ASINs are top-revenue.
ASIN vs account scopeASIN-level events, summarised in a list. The card lists each ASIN that breached the 30-percentage-point loss threshold in the last 24h.
Buy Box impactThis card IS the Buy Box impact, expressed as a list of ASINs to act on right now.
FBA vs FBMBoth. FBA bursts are usually driven by replenishment failures (stock dipped, Buy Box re-allocated to a third-party reseller); FBM bursts are usually driven by competitor reseller pricing attacks.
Fees / commissionNot applicable.
RefundsNot applicable.
CancellationsNot applicable.
CurrencyNot applicable.
Marketplace dynamicsBurst attacks happen most often around major sale events (Prime Day, Black Friday, Q4 cyber week) when resellers and arbitrage sellers hunt for under-priced Buy Boxes to undercut.
Return-window vs refund-windowNot applicable.
Time window24H (the alert checks for a burst of Buy Box losses within the last 24 hours; the burst itself can compress into 1 to 4 hours within that window).
Alert trigger>3 top-revenue ASINs lost 24h, driven by sentiment_key: buy_box_win_rate.
Rolesowner, 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 Amazon-first DTC homewares brand. 110 active ASINs on amazon.co.uk. The brand woke up to this alert at 07:14 BST on 16 May 26, with the dashboard showing 5 top-revenue ASINs lost Buy Box overnight. The drill-down:
ASINProductBuy Box win % (yesterday)Buy Box win % (now)Trailing 30D revenueLikely cause
B07HOM0001Throw blanket (cream)96%14%£8,420German reseller listed at £29.49 vs your £32.99
B07HOM0002Cushion cover (sage)91%22%£6,200Same reseller; bundled-listing attack
B07HOM0003Linen sheet set (king)88%47%£11,800FBA replenishment hit zero overnight, Buy Box reallocated
B07HOM0004Throw blanket (charcoal)95%18%£7,100Same German reseller as B07HOM0001
B07HOM0005Bath towel set92%51%£4,900Hijacker (counterfeit) listed on the ASIN
Total revenue affected£38,420 (trailing 30D)mixed
Five things to notice that are specific to Amazon:
  1. Buy Box loss = sales loss, instantly. Within 6 hours of the alert firing, Total Revenue for the affected ASINs collectively dropped 67% vs the prior day’s same-hour baseline. Speed of response is the entire game; an alert acted on at 07:30 saves significantly more revenue than the same alert acted on at 17:30.
  2. Three different root causes, three different fixes. The five ASINs split into: 3 reseller pricing attacks (B07HOM0001, 0002, 0004), 1 inventory failure (B07HOM0003), 1 hijacker (B07HOM0005). Each needs a different response. The pricing attacks are addressable via temporary re-pricing or by reporting the reseller to Brand Registry. The inventory failure needs a same-day expedite to FBA. The hijacker needs a Brand Registry takedown request and is the slowest fix (2 to 7 days).
  3. Commission erodes 12 to 15% of headline, but the alert is about Buy Box not fees. Fees are commercial; this alert is performance. Don’t chase fee optimisation while ASINs are losing Buy Box; the cost of inaction on Buy Box loss dominates any fee saving by an order of magnitude.
  4. Amazon-first buyers don’t migrate to your DTC site. The brand sent a same-day Klaviyo campaign promoting the affected products on their Shopify store. Click-through was 1.7%, conversion was 0.4%. The Amazon-shopper cohort is functionally separate from the DTC cohort. The Shopify campaign generated £620 of recovered revenue against the £38,420 trailing-30D Amazon book at risk.
  5. Out-of-stock punishes you for weeks. B07HOM0003 (the inventory-failure ASIN) recovered Buy Box within 4 days of replenishment, but its organic search rank took 17 days to fully recover. Daily revenue for that ASIN ran 30 to 45% below baseline for the full 17 days even after Buy Box returned. The alert caught the failure fast; the cost was still in the thousands of pounds because Amazon’s organic-rank recovery is slow.

​
Sibling cards merchants should reference together

This alert is the wake-up call. Pair it with these to triage:
CardWhy pair it with Buy Box Loss Burst
Top Buy Box Loss ASINsThe persistent priority list. The burst alert tells you “today’s emergency”; this card tells you “the standing list.”
Buy Box TrendThe smooth trend. Useful to confirm whether a burst is real or a one-day measurement artefact.
Buy Box Loss ValueTranslates the burst into £/month at risk. Use this to prioritise within the burst list.
Days of CoverIf a burst-flagged ASIN also has low days of cover, the cause is probably FBA replenishment, not pricing.
Hijack RiskCounterfeit listings are a slower-moving but persistent driver of Buy Box loss.
Account Health StatusIf account health flipped to At Risk recently, the burst may be an Amazon-side throttling response, not a competitor attack.
Total RevenueThe downstream consequence. Watch this card the day after a burst alert to size the actual revenue impact.
Amazon Ads ACOSACOS spikes during a Buy Box burst. Tell your Amazon Ads team before they panic about creative or bidding issues.

​
Reconciling against the vendor’s own dashboard

Where to look in Amazon Seller Central: Amazon does not publish a “Buy Box loss burst” alert. The closest equivalents:
  1. Inventory → Manage Inventory shows the Featured Offer (Buy Box) Price per ASIN. Eyeball your top SKUs against this column.
  2. Pricing → Manage Pricing flags ASINs where you don’t currently hold the Buy Box, with the reason in the Status column.
  3. Reports → Business Reports → Detail Page Sales and Traffic by Child Item shows the Buy Box Percentage per ASIN over time. The async report lags 24 to 48 hours, so it’s NOT a real-time alert source; use this card instead.
Why our number may legitimately differ from anything you’d build manually:
ReasonDirectionWhy
Time zoneBoundary hoursAmazon timestamps the Pricing API in UTC at the API level but Seller Central reports in PST/PDT. The 24-hour rolling window for this alert is computed on UTC; when reconciling against the Business Report’s daily figure, the boundary is offset by 7 to 8 hours.
Settlement-period lagNot applicableThis is a real-time state alert, not a settled-revenue figure.
API rate limitsOurs is sampled per ASINThe Pricing API is throttled. For 1,000+ ASIN catalogues the connector samples every 4 to 8 hours per ASIN; brief Buy Box flips of <2 hours can be missed entirely. The alert is calibrated for sustained losses (>30 percentage points held for at least one sample cycle).
Reports API generation latencyNot applicableThis card uses the live Pricing API, not the async Business Report.
Top-revenue cohort definitionCould differWe define “top-revenue ASIN” as the top 30 by trailing 30D revenue; you may use a different threshold (top 10, top 50). The burst threshold (>3) scales accordingly. Toggle the cohort size in Nerve Centre → Alert Settings.
Cross-connector reconciliation:
CardExpected relationshipWhat causes legitimate divergence
shopify.total_revenueNo relationship.Buy Box is Amazon-only. Shopify has no equivalent (you control the storefront).
bigcommerce.total_revenueNo relationship.Same as Shopify.
amazon_ads.aads_acosSharp inverse correlation during burstsACOS spikes within hours of a burst alert because clicks no longer convert to your seller. Pair with Ad Spend on OOS ASINs.
shipbob.fulfilment_rateIndirect, FBM onlySlow ShipBob fulfilment can cause Amazon to reallocate Buy Box on FBM ASINs. Doesn’t apply to FBA.

​
Known limitations / merchant FAQs

The alert just fired with 5 ASINs. What do I do in the next hour? Open the per-ASIN drill-down and look at three things for each ASIN: (1) competing offer price (Pricing API or Manage Pricing in Seller Central), (2) FBA inventory level and last replenishment date on Days of Cover, (3) any new offer from a non-authorised seller (potential hijacker, see Hijack Risk). The fix paths split: pricing wars need a re-pricing decision (or a Brand Registry violation report); inventory failures need a same-day expedite; hijackers need a Brand Registry takedown request. My burst alert fires every Monday morning. Why? Almost certainly an FBA replenishment cadence issue. Many sellers ship FBA replenishment loads to land Mon to Wed; if a top SKU runs out over the weekend before the load lands, the Buy Box flips to a third-party reseller and the alert fires Mon morning. The fix: increase the safety stock buffer on top SKUs, or shift replenishment cadence to land Fri/Sat. Pair with Days of Cover to identify which SKUs. The alert mentioned commission, but I thought this was about Buy Box. What’s the relationship? The alert itself is purely about Buy Box state, not fees. But the downstream impact compounds: Buy Box loss removes the order from your account, so you also lose the (negative) Amazon referral fee and FBA fee on that order. Net-net you lose roughly 87% of the gross unit revenue (the order goes to the competitor at a similar net margin). Don’t think about fees during burst triage; act first, reconcile later. ACOS, what should my Amazon Ads team do during a burst? Pause campaigns on the affected ASINs immediately. Ads on a non-Buy-Box ASIN burn money because clicks send shoppers to a product page where the “Buy Now” button hands the order to a competitor. Once Buy Box recovers, restart the campaigns; until then, the ad spend is largely wasted. Cross-check on Ad Spend on Out-of-Stock ASINs, the same logic applies. FBA fees question, would lowering FBA fee tier help me hold Buy Box? No, FBA fees don’t directly affect Buy Box allocation; price, Prime-eligibility, fulfilment performance, and seller rating do. The fee question is downstream. If you’re contemplating a smaller-size-tier reclassification to save FBA fee dollars, that’s a margin decision unrelated to Buy Box. See FBA Fees. Multi-marketplace, does the alert fire across UK + DE + FR + IT + ES separately? Yes. Each marketplace has its own Buy Box state per ASIN; the alert evaluates each independently. A burst on amazon.de is a different operational event from a burst on amazon.co.uk; the resellers are different and the fix may be different (some EU resellers operate cross-marketplace, others are country-specific). The drill-down splits by marketplace. Settlement timing, does the burst affect when I get paid? Yes, indirectly. Pending settlements continue to clear on the standard 14-day cycle for orders already placed. But the burst means future orders go to competitors, so future settlements are smaller. The cash impact lags the revenue impact by 14 days both on the way down and on the way back up. See Pending Settlement. Return-window confusion, do return-window issues cause Buy Box bursts? Sometimes, on FBM. If your fulfilment partner is missing the promised handling time, Amazon’s algorithm can mark the listing as poorly-performing and flip Buy Box to a competing reseller with cleaner metrics. Once you’re below the Account Health Late Shipment Rate threshold, this becomes systematic rather than per-ASIN. Pair with Late Shipment Rate and Account Health Status. Why isn’t the Shopify-Amazon channel app a useful tool here? Because the channel app is publishing-only; it has no signal on Buy Box state. Buy Box is governed by SP-API; the channel app cannot detect or remediate Buy Box loss. Use this alert and the underlying Pricing API directly; the channel app is unrelated. Why does today’s alert sometimes mention the same ASIN twice in one day? Because the burst can flip back and forth multiple times within 24 hours during an active reseller pricing war. The alert de-duplicates within the same 24-hour window so you’ll see each ASIN listed once, but if the same ASIN flips again on the next 24-hour boundary the alert can re-fire. If you see persistent flicker on one ASIN over multiple days, that’s a structural pricing war; consider whether to engage on price or escalate the reseller relationship via Brand Registry.

​
Tracked live in Vortex IQ Nerve Centre

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