Catalog
Make variation families easier to audit
Audit a supplied catalog export for parent-child relationships, orphaned items, possible duplicates, and attribute inconsistencies. Claude produces a proposed change set for human review rather than editing catalog records.
Works with Amazon
Describe the task
Start with a bounded request
Audit a supplied catalog export for parent-child relationships, orphaned items, possible duplicates, and attribute inconsistencies. Claude produces a proposed change set for human review rather than editing catalog records.
Audit the catalog export for [BRAND / PRODUCT FAMILY] in [MARKETPLACE]. Review ASINs, SKUs, parent-child links, variation themes, and core attributes against the intended family structure I describe. Identify orphaned children, ambiguous parents, likely duplicates, and inconsistent attributes. Return an evidence table and a proposed correction sequence, marking anything that needs Seller Support or more proof. Do not change any catalog record or open a case.Ask Claude
Provide the working context
Bring the source material Claude should trust
- A current catalog export with ASINs, SKUs, parentage, variation themes, and core attributes
- The intended product families and the real differences between each child
- Known support cases or catalog symptoms affecting the set
Review what Claude does
Inspect the reasoning and the proposed output
- Maps the current family structure and highlights broken or ambiguous relationships
- Compares child attributes for naming, unit, and value inconsistencies
- Separates likely duplicates from products that are materially different
- Produces an ordered correction proposal with evidence references
Ready to run it?
Open the prepared prompt, then keep the final call with the operator.
FAQ
Review the working boundaries
How does Claude distinguish a variation problem from a real product difference?
Claude compares the intended family logic with the supplied parentage, variation theme, and product attributes. A difference is treated as real only when the catalog evidence supports it; unclear cases remain flagged for review. The result is a proposed correction set, not an automatic restructuring of the catalog.
What context should I provide first?
Start with a current catalog export with ASINs, SKUs, parentage, variation themes, and core attributes. Then provide the intended product families and the real differences between each child. Keep dates, marketplaces, ASINs, and source definitions attached to the material so Claude can distinguish current evidence from background context.
What should be reviewed before acting?
A catalog-hygiene report and reviewable correction plan organized by family, ASIN, issue, evidence, and priority. Before approval, check the source records, stated assumptions, and every proposed change against the current account context.