Ad on OOS Detected, Amazon Seller Central

Ad on OOS Detected for Amazon Seller Central. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Cross-Platform Metrics • Category: Marketplace

At a glance

A cross-platform alert that catches the most wasteful failure in Amazon advertising: an active Sponsored Products or Sponsored Brands campaign still spending on an ASIN that is out of stock or has lost the Buy Box. Every click is paid for, but no sale can complete, you are buying traffic to a dead-end listing. This card joins the Amazon Seller catalogue / inventory state with the live Ads campaign state, which is why neither connector could produce it alone.

What it counts	The number of ASINs that currently have an active ad campaign running AND are out of stock (or ineligible to sell because the Buy Box is lost). Each detection is a unit of pure ad waste.
Why cross-platform	It needs two data sources: inventory / Buy-Box state from Amazon Seller Central, and live campaign / targeting state from Amazon Ads. The Seller connector knows the ASIN is unsellable; the Ads connector knows money is still flowing to it.
Two failure modes	(1) Out of stock: FBA inventory hit zero or FBM quantity ran out, but the campaign still targets the ASIN. (2) Buy Box lost: the listing is in stock but you no longer hold the Buy Box, so ad clicks rarely convert.
Why it matters	Ad spend on an unsellable ASIN is wasted twice: the click is paid for, and the impression could have served a sellable product. It also drags ACOS / TACOS upward with zero attributable sales.
Fulfilment scope	Both FBA and FBM. FBA stockouts are the most common trigger because replenishment lead times are long; FBM stockouts happen faster but are easier to fix.
The fix	Pause or reduce bids on the affected ASIN until stock returns or the Buy Box is recovered, then re-enable. Many sellers automate this rule once they see the leak.
Time window	RT (real time, a live detection rather than a period total)
Alert trigger	>0. A single detected ASIN flips the card and notifies owner, marketing, and finance.
Roles	owner, marketing, finance

Calculation

Calculated automatically by joining your Amazon Seller Central inventory and Buy-Box state with your live Amazon Ads campaign state. 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 supplements seller running Sponsored Products across an FBA range on amazon.com. Snapshot taken 18 Mar 26 at 14:00.

ASIN	Campaign state	Inventory / Buy Box	Detection
B0ASIN001	Active, $40/day	FBA units = 0 (out of stock)	Ad on OOS
B0ASIN002	Active, $25/day	In stock, Buy Box lost to 3P offer	Ad on Buy-Box-lost
B0ASIN003	Active, $30/day	In stock, Buy Box held	Healthy, not flagged
Ad on OOS Detected (this card)			2

Detected ASINs (this card)   =  2  (B0ASIN001 out of stock, B0ASIN002 Buy Box lost)
Daily budget at risk         =  $40 + $25  =  $65/day of spend with little or no sellable outcome
Healthy ASIN                 =  B0ASIN003 (in stock, Buy Box held), correctly not flagged

Four things to notice:

1. Two ASINs, two different failure modes. B0ASIN001 is out of stock, so every click lands on a listing that cannot fulfil. B0ASIN002 is in stock but lost the Buy Box, so clicks land on a listing where a competitor wins the sale. Both burn budget; the card catches both.
2. The waste is roughly $65/day until someone acts. That is the combined daily budget pointed at unsellable ASINs. Over a week of inattention, that is real money with almost no attributable sales, and it inflates ACOS / TACOS with no return.
3. The out-of-stock case is the classic FBA trap. FBA replenishment lead times are long, so an ASIN can sit at zero for days while the campaign keeps spending. Pairing this with stockout-forecast cards lets you cut the budget before the inventory runs dry.
4. The Buy-Box case is sneakier. B0ASIN002 looks fine in the inventory report, it is in stock. Only by joining the Buy-Box state does the waste become visible. This is exactly why the card is cross-platform.

The seller pauses both campaigns, expedites an FBA replenishment for B0ASIN001, and investigates the third-party offer undercutting B0ASIN002’s Buy Box. The detected count drops to zero and the daily leak stops.

Sibling cards merchants should reference together

This alert sits at the seam of inventory, Buy Box, and ad spend. Pair it with cards on all three sides:

Card	Why pair it with Ad on OOS Detected
Ad Spend on Out-of-Stock ASINs	The £/$ figure behind this count. This card tells you how many ASINs; that card tells you how much you are wasting.
ASINs Stocking Out <7 Days	The early-warning list. Cutting ad budget on these before they hit zero prevents this alert from firing at all.
Buy-Box Win Rate (top-50 ASINs)	The Buy-Box side of the failure. A falling win rate means more in-stock ASINs are becoming ad-waste candidates.
Top Buy-Box-Loss ASINs	Names the specific ASINs losing the Buy Box, the ones most likely to show up here as in-stock-but-unsellable.
Replenishment Recommendations	The supply-side fix. Restocking the flagged ASINs is what ultimately clears the out-of-stock detections.
Days of Cover (avg)	Inventory runway context. Low days-of-cover on an advertised ASIN is the leading indicator of this alert firing soon.

Reconciling against Amazon Seller Central

Where to look in Seller Central and the Ads console:

Inventory state: Inventory → Manage FBA Inventory (or Manage Inventory for FBM) shows the available quantity per ASIN. Buy-Box state: visible on the listing and in Business Reports. Campaign state: the Advertising → Campaign Manager console shows which campaigns and ASINs are active and spending.

Because this is a cross-platform detection, there is no single Amazon page that shows it. Reconcile by confirming, for a flagged ASIN, that (a) the inventory page shows zero or lost Buy Box, and (b) the campaign console shows the campaign active and spending.

Timing and reporting-lag table:

Topic	Detail
Timezone	Inventory and ad reports use the marketplace’s local timezone. Vortex IQ joins the two states on a common clock; a detection near a boundary can read slightly differently between the two consoles.
Inventory refresh	FBA available-quantity updates can lag real inbound / outbound movement. An ASIN may briefly read as in stock just after selling out, or as out of stock just before a replenishment posts.
Ad spend reporting lag	Amazon Ads spend and click data can lag by a number of hours. The detection (active + unsellable) is real-time, but the exact wasted-spend figure on the sibling card settles as Amazon finalises spend.
Buy-Box volatility	Buy-Box ownership can change minute to minute on competitive ASINs. The card samples the current state; a flicker in and out of the Buy Box can cause a detection to appear and clear quickly.

Why our number may legitimately differ from a manual check:

Reason	Direction	Why
Cross-source timing	Either direction	The inventory state and the ad state are read on slightly different clocks. A just-replenished ASIN may still flag for a short window until both sources agree.
Buy-Box flicker	Ours can fluctuate	On a hotly contested ASIN, Buy-Box ownership changes rapidly. The detection reflects the latest sampled state and can appear or clear between checks.
Sampling scope	Ours may focus on top spenders	To respect API limits, the join can prioritise the highest-spend / highest-revenue ASINs. A tiny-budget campaign on a long-tail OOS ASIN may not be flagged.

Cross-connector reconciliation against other connectors the same seller may run:

Card	Expected relationship	What causes legitimate divergence
amazon-ads.active-ads-on-out-of-stock-skus	Direct counterpart on the Ads side. Same failure, viewed from the Ads connector. The two should broadly agree on which ASINs are flagged.	Different sampling windows or scope can cause minor count differences. The Seller-side card anchors on inventory / Buy-Box truth; the Ads-side card anchors on campaign truth.
google-ads.active-ads-on-out-of-stock-skus	Same pattern, different channel. Google Ads can waste spend on out-of-stock products too. Used as a pattern peer, not a reconciliation.	Entirely separate ad accounts and product feeds.

Known limitations / merchant FAQs

Why is this a cross-platform card? Because no single connector can detect it. The Amazon Seller connector knows an ASIN is out of stock or has lost the Buy Box; the Amazon Ads connector knows a campaign is still spending on it. Only by joining both do you see the waste.

What counts as “OOS” here? Two things: a true out-of-stock (FBA units at zero or FBM quantity exhausted) and a Buy-Box loss (in stock, but a competitor holds the Buy Box so your ad clicks rarely convert). Both make the advertised ASIN effectively unsellable for your offer.

How much money is actually at risk? This card gives the count of ASINs; the Ad Spend on Out-of-Stock ASINs card gives the £/$ figure. The risk is the daily budget pointed at the flagged ASINs until you pause them.

Why did a detection appear and then disappear quickly? Usually Buy-Box flicker. On competitive ASINs, Buy-Box ownership can change within minutes. The card reflects the latest sampled state, so a brief loss-and-recovery can cause a short-lived detection.

Should I just delete these campaigns? No, pause or lower bids until stock returns or the Buy Box is recovered, then re-enable. Deleting loses the campaign’s history and ranking. Many sellers automate a pause-on-stockout rule once they see how often this leaks.

Does FBA or FBM trigger this more often? FBA out-of-stock is the most common trigger because replenishment lead times are long, an ASIN can sit at zero for days. FBM runs out faster but is quicker to restock, so it self-corrects sooner.

My Ads console shows the campaign as active but converting, why is it flagged? Check the Buy-Box state, not just stock. An in-stock ASIN that has lost the Buy Box can still take clicks; the conversions you see may be on a different ASIN in the campaign. The flag is specific to the unsellable ASIN.

---

Tracked live in Vortex IQ Nerve Centre

Ad on OOS Detected 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.