Live $/day burning on ASINs that can’t convert. The pause-now alert.
At a glance
Live ad spend, last 7 days, that landed on ASINs which were either out of stock or suppressed at the time of the click. Money paid to Amazon for traffic that could not convert. The “pause now” alert.
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 FBA-only seller running a 95-ASIN pet supplies book on amazon.com. Amazon Ads spend roughly 842 wasted in last 7 days**. Drilling into the per-ASIN drill:
Five things to notice that are specific to Amazon:
- Sponsored Ads do NOT auto-pause when an ASIN goes OOS. Amazon Ads will happily keep spending on an ASIN that has been zero-stock for days, the campaign-level setting “pause on OOS” is OFF by default. Most sellers don’t know this. The fix is to enable that setting in every campaign, plus monitor this card. The single biggest source of wasted Amazon Ads spend across the SMB seller base is this exact mechanism.
- Buy Box loss = sales loss, instantly, but ad waste is delayed. When B07PET0001 went OOS on 14 Apr 26, organic sales dropped to zero same day. Ad spend continued for 7 days at roughly $55/day until this card flagged it on 21 Apr 26. Speed of detection matters; the wasted-spend clock is constant until you see the alert and act.
- Commission erodes 12 to 15% of headline, but ad waste is 100% loss. Fees are charged on revenue you make. Wasted ad spend on OOS ASINs is charged on revenue you don’t make. Net-net, every 1 of pure margin loss; a 0.85 of margin. Wasted ad spend is 6 to 7x worse per dollar than fees on the same order.
- ACOS is the wrong number to watch for this. A wasted-spend ASIN often shows infinite ACOS (clicks > 0, attributed sales = 0) which can be hidden in the keyword-level ACOS view if the campaign also has performing ASINs. The card joins click stream against per-ASIN inventory state at click time, which is more reliable than ACOS-based detection.
- Out-of-stock punishes you for weeks even after the spend is paused. Pausing the campaign stops the bleed but doesn’t recover the lost organic rank from the OOS period. B07PET0001 took 19 days post-replenishment to recover its organic search rank to pre-OOS levels, even with this card’s intervention. The card prevents future waste; it does not undo past damage.
Sibling cards merchants should reference together
This card is inherently cross-platform, joining Amazon Ads spend against SP-API ASIN state. Pair with these to act:Reconciling against the vendor’s own dashboard
Where to look in Amazon Seller Central: There is no native Seller Central or Amazon Ads view that shows “ad spend on OOS or suppressed ASINs”. The closest workflow is:- Amazon Ads → Sponsored Products → Advertised Products shows per-ASIN ad performance. ASINs with high spend and zero attributed sales are candidates; the page does not tell you why (OOS / suppressed / non-Buy-Box).
- Inventory → Manage Inventory cross-references the live OOS / suppressed list. Reconcile the two views manually.
- Performance → Inventory Health shows OOS ASINs and stock-on-hand levels.
_xc_) card and not native to either Amazon Ads or SP-API alone.
Why our number may legitimately differ from anything you’d build manually:
Cross-connector reconciliation:
This card is inherently cross-connector: it does not exist without both Amazon Ads and Amazon SP-API connectors. The reconciliation IS the metric.
Known limitations / merchant FAQs
The card says I wasted $1,200 last week. Why didn’t Amazon Ads pause my campaigns automatically? Because Sponsored Ads campaigns have an opt-in “pause on OOS” setting (also known as “automatic targeting paused when out of stock”), and it is OFF by default. Most sellers never enable it. The fix: enable it on every campaign. Do this once and the bleed shrinks dramatically. If your category sees frequent OOS events, also set up a same-day Slack or email alert from this card so you can pause campaigns before they accumulate spend. How does this card differ from looking at Amazon Ads ACOS? ACOS hides this. A campaign with 5 ASINs, where 1 is OOS and burning spend with zero attributed sales while the other 4 perform normally, will still show a “reasonable” campaign-level ACOS because the performing ASINs mask the wasted ASIN. The card joins click-by-click ad spend against per-ASIN inventory state, surfacing the wasted slice that ACOS averages over. Use Amazon Ads ACOS for campaign-level efficiency; use this card to find the specific ASINs to pause. ACOS vs ROAS terminology, which is right? ACOS (Ad Cost of Sale) =ad spend ÷ ad-attributed sales, the inverse of ROAS. A 25% ACOS = 4x ROAS. Amazon writes ACOS because lower-is-better fits how the Sponsored Ads console presents data; Google and Meta write ROAS because higher-is-better fits theirs. They’re the same arithmetic, different framing. For a wasted-spend ASIN, ACOS is infinite (zero sales attributed); ROAS is zero. This card sidesteps both and reports raw wasted dollars, which is harder to misread.
Commission, FBA fees, do they enter this card?
No. This card reports raw Amazon Ads spend, not net economics. Net wasted economics would be: wasted ad spend minus the (negative) referral fee and FBA fee that you didn’t pay because there was no order. But since you didn’t get the order at all, the fees question is moot; the wasted ad spend is a pure margin loss. Pair with Net Revenue when reasoning about overall margin impact.
FBA vs FBM, does the card distinguish?
The card distinguishes the cause of wasted spend (OOS, suppression, optionally non-Buy-Box) but not the fulfilment channel directly. You can filter by FulfillmentChannel in the drill-down. FBA OOS is the most common driver because FBA inventory drops are slower to detect than FBM (you can’t physically see your FBA shelves). FBM OOS happens when stock-on-hand feed reports zero, which is faster to detect on your side.
Multi-marketplace, does the card aggregate UK + DE + FR + IT + ES?
Yes, but converting to settlement currency for the headline. The drill-down splits by marketplace because Amazon Ads accounts are per-marketplace (you have separate ad accounts for amazon.co.uk and amazon.de, each with its own currency and budget). When OOS is per-marketplace (common with replenishment lag in one country only), the card flags the affected marketplace cleanly.
Settlement timing, does this card affect cash flow?
Indirectly. Wasted ad spend is debited on Amazon Ads’ billing cycle (typically monthly or weekly), separately from order settlement. Pausing wasted-spend campaigns reduces the next ad invoice but doesn’t accelerate any pending order settlements. Pair with Pending Settlement for cash-flow planning; this card for ad-budget planning.
Return-window confusion, do return-window issues show up here?
No. This card looks at the ASIN state at click time (OOS / suppressed / optionally non-Buy-Box). Returns happen post-click, post-purchase; they don’t affect this card. If a high return rate triggers Amazon to flag and suppress the ASIN under “customer-reported defect”, that flag will then show up in this card via the suppression path. So return-window issues are an upstream cause of suppression, which then causes wasted spend, but they don’t directly enter the calculation here.
Why isn’t the Shopify-Amazon channel app a useful tool here?
Because Shopify has no concept of Amazon Ads. The channel app pushes Shopify product data to Amazon catalogue listings; it does not interact with Amazon Sponsored Ads campaigns. The cross-platform join required for this card is between Amazon Ads and Amazon SP-API, both Amazon-internal. Shopify is irrelevant to this calculation.
Why does today’s number sometimes show zero even when I know I have OOS ASINs with active campaigns?
Two reasons. (1) The Amazon Ads Reports API is async with up to 4-hour latency; today’s spend may not be available yet for joining against today’s inventory state. (2) The card requires both data inputs to be fresh; if either side is mid-rate-limit-backoff, the card displays the last-known value, which may be zero if the prior poll cycle was clean. If you suspect under-reporting, wait 4 to 6 hours and re-check; persistent zero with known OOS plus active campaigns is worth raising as a connector data-freshness issue.