Listing incident intelligence
When an ASIN goes down,start with the evidence.
ASINmd is being built to help Amazon sellers reconstruct listing incidents, understand what changed, separate marketplace-confirmed signals from inference, and know what to investigate first.
Evidence first. No invented answers.
Most likely cause
A required attribute became invalid after the product type changed.
- 10:15item_form became required
- 10:16ERROR 90220 reported
- 10:17Listing suppressed
The problem
A listing can disappear in seconds. The explanation rarely arrives with it.
Suppression. Lost buyability. Catalog changes. New requirements. Restrictions. A single incident can surface several signals at once. The hard part isn’t finding another warning — it’s figuring out what happened first, what Amazon actually confirms, and which signal matters.
Seller Central shows the symptoms. ASINmd is built to investigate the incident.
An incident record, not another alert
The evidence.
The timeline.
The next move.
What Amazon confirms
Surface issues, restrictions, listing states and other marketplace-reported evidence when it is available.
What changed
Preserve listing state over time so an incident doesn't begin with a blank page.
What the evidence suggests
Rank plausible causes without presenting an inference as fact.
What to investigate first
Turn scattered signals into a clear place to start.
From error to incident
See the sequence, not just the latest error.
A warning that appeared after a listing went down probably didn’t cause it. A change immediately before the incident might have. ASINmd is designed around chronology, provenance and counter-evidence, so the timeline matters as much as the error itself.
Most likely cause
Required attribute item_form became invalid after the product type changed.
Check first
Correct item_form and revalidate the listing.
Marketplace-confirmed signals
Timeline
- 10:00
Listing healthy
- 10:14
Product type changed
- 10:15
item_form became required
- 10:16
ERROR 90220 reported
- 10:17
Listing suppressed
Counter-evidence
We cannot establish who initiated the product-type change.
How ASINmd thinks
Four steps between “it’s down” and “start here.”
Observe
Preserve the listing state and marketplace signals that exist before something breaks.
Compare
Identify meaningful changes instead of treating every update as equally important.
Reconstruct
Put changes, issues, restrictions and listing-state transitions in chronological order.
Diagnose
Rank the strongest explanation, show the uncertainty, and identify what deserves attention first.
Built for the people on the hook
When the listing goes dark, somebody has to explain it.
Brands
Protect your most important listings with a history that doesn't start after the problem does.
Agencies
Walk into a client incident with evidence instead of another round of guesswork.
Operators
Replace screenshots, Slack threads and memory with a repeatable incident record.
Evidence has a confidence level
“We don’t know”
is a valid diagnosis.
ASINmd is designed to make the boundary between evidence and inference obvious. When the marketplace confirms something, we say so. When the evidence supports a conclusion but doesn’t prove it, we say that too. And when the available data can’t establish a cause, we don’t manufacture one.
- Marketplace confirmed
- The marketplace directly reported the signal.
- Evidence supported
- The available evidence supports the conclusion, but does not prove it.
- Unknown
- The available evidence cannot establish the cause.
Seller data isn’t ad data
Built to investigate your listings, not monetize your information.
ASINmd is being designed around least-privilege access, tenant isolation, secure server-side credential handling and data minimization. We don’t need your order or customer data to investigate listing incidents, so the architecture is designed not to ingest it.
- Tenant isolation
- Organization-scoped data access with database-level protections.
- Server-side credentials
- Marketplace credentials are kept outside browser clients.
- Data minimization
- Listing forensics should not require customer addresses, order details or buyer communications.
- Evidence integrity
- When monitoring is stale or data cannot be retrieved, the product is designed to say so rather than report a false healthy state.
Be ready before the next incident
The worst time to start keeping history is after your ASIN goes down.
ASINmd is in early development. We’re looking for Amazon sellers and agencies who deal with high-value listing incidents and want a better way to investigate them.