01
2 France SKUs
Start with the two obvious rows
A PPC manager saw 2 zero-sales France SKUs that still had live ads.
Case StudyMetricsMay 20264 min read
30 days of zero sales, surfaced in a few minutes
How a built-in Opus agent caught an Amazon platform bug that quietly killed a listing before it stayed buried for months.
2 weeks free - no credit card
propamp.ai / metrics / listing-health
Agent anomaly
Zero-sales listing outage
Sales trace
found
Day 1Agent spotlight
Evidence rows
FR-REDACTED-A
FBA units - New unavailable
FR-REDACTED-B
FBA units - New unavailable
16-market scan
catalog-wide - zero-sales filter
0 days
zero sales before the anomaly was caught
0
France SKUs affected
0
marketplaces checked in the widened query
- to surface the bug with the built-in agent
- a few min
As featured in
The catch
A flatline that looked quiet was actually a platform failure.
The agent did not start with a grand audit. It started with 2 zero-sales France SKUs that still had live ads, then asked whether the pattern existed anywhere else.
Listing signal
30 days zeroa few minutessurfaced
Review scope
2 FR SKUs16 marketplaceswidened
0
SKUs affected
0
marketplaces checked
- plan includes the built-in agent
- Pro
Zero-sales flatline with anomaly spotlight
Signal quality
Zero sales plus available stock is the kind of mismatch a human review often misses after the listing is already optimized.
The built-in agent
Opus widened a small PPC question into a catalog check.
The PPC manager did not need a separate AI subscription. The built-in agent took the first suspicious rows and checked them against the wider marketplace and stock context.
02
all zero-sales SKUs
Expand the question
The built-in Opus agent widened the query to every zero-sales SKU instead of staying inside the ad view.
03
16 marketplaces
Cross-check the catalog
It checked the same pattern across 16 marketplaces and compared each result against stock.
04
FBA units available
Separate stock issues from platform failure
Two SKUs still had plenty of FBA units, so the problem was not inventory.
agent / zero-sales-query / expanded
12 France SKUs
2all zero-sales SKUs
316 marketplaces
4FBA units available
Query widening from two France SKUs to the full catalog
How the agent connects to your dataWhat it turned out to be
FBA had units. France could not buy them as New.
The agent found the contradiction: two SKUs had plenty of units sitting in FBA, but the France listing showed the New condition as unavailable. Amazon later confirmed a deeper platform bug.
amazon.fr / listing-condition / evidence
France listing
New condition unavailable
FBA stockLive ads0 sales
France listing New condition unavailable flag
Marketplace
France
Condition
New unavailable
FBA stock
plenty of units
Sales
0 for 30 days
Why it would have stayed buried
Nothing in the normal workflow made someone re-check a working listing.
The listing was already optimized
After launch and optimization, nobody had a reason to re-open the listing just to check that Amazon had not broken it.
Ads were still live
The ad signal made the SKUs look active, so the listing failure did not announce itself as an obvious setup problem.
Stock was not the obvious culprit
FBA still had units, so a normal inventory review would not have raised the same alarm.
"Once"Onceaalistinglistingisisoptimized,optimized,nobodynobodygoesgoesbackbackininjustjusttoto'check''check'thatthatnothingnothingbroke...broke...withoutwithoutthetheagent,agent,thisthiscould'vecould'vestayedstayedburiedburiedforformonths."months."PPC-agency pull-quote with listing outage timeline
Your move
Start your free PROPAMP AI trial.
Let an agent watch the quiet contradictions in your Amazon data before a silent listing issue turns into another lost month.
agent / anomaly-watch / listing-health
Agent watching listing metrics for silent anomalies
Seller Central data
MCP connection
Listing anomaly watch