Skip to main content
Metrics type: Key Metrics • Category: Ad Platform
Spend on ASINs that can’t convert. Pause immediately or reroute to in-stock siblings.

​
At a glance

Count of ASINs that have active ad spend AND zero available inventory (across all FBA / FBM warehouses). The shopper clicks your ad, lands on the product page, and sees “Currently unavailable”, you paid for the click and they bounce. The single fastest-moving fix on the dashboard, every dollar here is recovered the moment you pause.

​
Calculation

Calculated automatically from your Amazon Ads 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 home-goods seller, daily check on 12 Apr 26. Two ASINs are flagged. What’s interesting:
  1. **224ofwastedspendinasingleday∗∗= 224 of wasted spend in a single day** = ~6,720/month if not paused. The 30-second fix recovers all of it.
  2. B0DXY5678 is the chronic-bleed pattern. 4 days OOS with no inbound, and an auto-campaign is still serving. Amazon’s auto-bidder doesn’t proactively pause OOS ASINs. The lifetime spend while OOS is $580; that’s pure waste.
  3. B0FFF3456 is the temporary-OOS pattern. Stock arrives 18 Apr (6 days). Best practice: pause until stock arrives, OR keep ads running at low spend to maintain rank (some sellers accept 5-10% wasted-spend cost as the price of preserving search rank during short OOS gaps). For OOS > 7 days, always pause; for shorter, judgement call.
  4. The cross-card pattern: an ASIN at zero inventory will also lose Buy Box (so it lights up Active Ads on No-Buy-Box ASINs too). The two cards together usually cover all structural waste.
  5. Auto-campaigns are the chronic offender. Amazon’s Auto Targeting doesn’t honour ASIN-level OOS by default, it keeps serving ads. Manual Sponsored Products campaigns can be set to “pause on OOS” via API automations; auto-campaigns require ASIN-level exclusions.
Quick sanity tests:
  • Count = 0: clean. The goal state.
  • Count 1-3 isolated ASINs with stock-on-the-way: short pause, schedule resume.
  • Count >5 ASINs: structural inventory failure or supply-chain disruption. Cross-check with Amazon SP Inventory Health.
  • Same ASINs reappearing weekly: chronic stock-out cycle, fix the supply chain, not the ads.
  • Count rising during seasonal demand (e.g. pre-Christmas): supply chain didn’t keep up; immediate restock priority.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in Amazon Ads Console + Seller Central: Amazon Ads Console > Campaign Manager does NOT natively flag OOS. Amazon Ads and inventory data live in different consoles. Seller Central > Inventory > FBA Inventory, the “Available” column shows on-hand stock. Filter to ASINs with Available = 0 and cross-check against your active ad campaigns. Seller Central > Reports > Inventory and Sales > FBA Inventory, the canonical FBA stock report. Amazon Ads Console > Recommendations, sometimes flags “out-of-stock, advertising paused” suggestions, but unreliably. Why our number may legitimately differ from a manual cross-check: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

Why does this card require both Amazon Ads and Selling Partner connectors? Inventory state lives in Seller Central; ad spend lives in Amazon Advertising. Joining them is the whole point. If only one is connected, this card shows “data incomplete”. Why doesn’t Amazon Ads automatically pause OOS ASINs? Amazon Advertising and Seller Central are operated by different product teams; the integration is partial. Amazon offers an “Inventory-aware bidding” feature that lowers bids on low-inventory ASINs but doesn’t pause OOS outright. The structural waste is by design. Amazon takes your money on every click. Should I pause for a 1-day gap or wait it out? Judgement call. Pausing kills your search rank momentarily; rebuilding rank takes 1-3 days. Rule of thumb: pause for OOS > 3 days, run-low-bid for OOS 1-3 days, ignore OOS < 24h (likely a snapshot lag). My ASIN shows 0 inventory but I know I have stock, why? Three causes: (a) Inbound shipment in transit but not yet received at FBA; the card considers this OOS until the warehouse acknowledges receipt. (b) Stock allocated to pending orders is sometimes excluded from “available”. (c) Inventory snapshot lag. Selling Partner Inventory API can be 4-6h stale. If you just received stock, give it 6 hours to clear. Can I auto-pause OOS ads? Yes, via Amazon’s Sponsored Products API or third-party tools. The pattern: webhook on inventory-zero → API call to pause campaign keyword targeting that ASIN. Vortex IQ can fire the alert; the auto-pause itself is a separate automation. Worth setting up if this card fires more than once a month. My count is rising during Q4 / Prime Day, is this normal? Yes, demand spikes outpace inventory. The fix is supply-chain (more inbound) not ad-side. Don’t react to high-demand-OOS by raising ad budgets; you’ll just waste more. Multi-warehouse aggregation, what counts as “available”? This card sums on-hand inventory across all FBA fulfilment centres globally for the marketplace. An ASIN with stock in only one warehouse is still in-stock. An ASIN with 0 across all warehouses is OOS. FBM (Fulfilled by Merchant), does that count? Yes. The card sums FBA + FBM. If you have 0 FBA but 50 FBM, the ASIN is in stock and not in this card. My count is zero every day, is that healthy? Yes, ideal state. Common for sellers with strong inventory operations or for FBM-only sellers (who can adjust stock-on-hand more quickly). Why is the alert threshold ”>0>0 ASINs” rather than a dollar amount? Because every dollar in this card is recoverable in 30 seconds (pause). There’s no business reason to tolerate ANY non-zero count.

​
Tracked live in Vortex IQ Nerve Centre

Active Ads on Out-of-Stock SKUs is one of hundreds of KPI pulses Vortex IQ tracks across Amazon Ads 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.