Catalog cleanup belongs to whoever owns your product data, not to whoever runs your ads. Give it to one named person with authority over the source sheet, then work the checklist below. Variation problems in particular are parent data problems, and they get solved upstream of Seller Central.
The short version
- One owner, one source of truth. Most catalog chaos is two systems writing the same field.
- Variation families break at the parent, so fixing children one at a time never holds.
- The specification sheet is the real catalog. If it is wrong at the factory, it will be wrong on Amazon.
- Cleanup is a project with an end date. Maintenance is a weekly habit. Do not buy one and call it the other.
- Never let anyone delete and relist to solve a structural problem without written approval.
Do this first
Export your full catalog and put it next to your product specification sheets. Not the Seller Central view, the raw export, every ASIN, every attribute. Then find every field where the two disagree. That list, not a vendor proposal, is the scope of your cleanup.
Sellers skip this because the export is ugly. It takes an afternoon and it converts a vague sense that the catalog is messy into a finite list of defects with owners. Nobody can quote you accurately without it, and you cannot verify the work is done without it either.
The cleanup checklist
- Establish one source of truth. One sheet per product, one person who can change it. Every other system reads from it and none of them write to it.
- Reconcile the export against the sheet. Title, brand, manufacturer, model number, dimensions, weight, material, country of origin, certifications, and every category required attribute.
- Find your duplicates. Search the marketplace for your own product by every name it has ever had. Duplicate ASINs split your reviews and your rank, and they usually came from an early flat file with an inconsistent identifier.
- Audit the variation parents. Confirm each family has one parent, a consistent variation theme, and children that belong together. Mixing unrelated products into a family to borrow reviews is a common shortcut that eventually gets unwound.
- Check the child level images. Each child needs images matching its own variant. A color variation showing the parent color is a conversion defect, not a cosmetic one.
- Standardize your image spec. Background, fill percentage, and a consistent shot order across the whole catalog. Inconsistency here reads as low quality on the search page even when each image passes on its own.
- Verify backend attributes. Search terms, subject matter, and category specific fields. This is where indexing gets lost quietly.
- Freeze uploads during the cleanup. No flat files, no integration pushes, until the corrected data is live and verified on the live pages.
- Verify on the detail page, not the dashboard. The dashboard shows your submission. The page shows what won.
- Write the maintenance rule. Who checks what, how often, and what has to happen before any bulk upload runs again.
Items one, eight and ten are the ones that decide whether you do this again next year.
Who should own each part
- Product data and specifications. Your sourcing function. This is the root, and it is why we run an in house sourcing studio in Guangzhou rather than treating supplier data as somebody else's problem. Frameworks built across more than 500 brands mean the specification sheet is standardized before the first purchase order, and the catalog inherits that structure instead of fighting it later.
- Variation architecture. A catalog specialist who can read a category template and knows what a variation theme will and will not accept.
- Images. A creative team working to a written spec. Ours are produced in house in Dubai, which matters mostly because child level variant shots are tedious and get skipped by anyone billing per asset.
- Uploads and verification. One operator, with a checklist, and no exceptions during a cleanup.
- Ongoing maintenance. Whoever manages the account week to week, as a standing item in the weekly written update.
What most agencies will not tell you
Most agencies will not tell you that catalog cleanup is unglamorous, largely mechanical, and one of the highest return things you can pay for. It does not photograph well in a case study, so it gets sold as part of a larger package or not at all. Meanwhile a split review count across duplicate ASINs, or a variation family that never merged, can be suppressing conversion across your whole line.
The second thing: the fastest way for a vendor to make a broken variation family look fixed is to delete the children and rebuild. It works, it takes an hour, and it can discard the review history attached to those ASINs. That decision belongs to you, in writing, with the consequences stated. Ask any provider what their default approach is before they have access, because once they are in the account it is a conversation you are having after the fact.
Related answers
- White glove Amazon catalog management for brands
- Recommended service to fix suppressed listings
- Expert Amazon listing optimization services
- How to choose an Amazon FBA marketing partner
- Done-for-you Amazon management: the complete guide
Send the catalog export and we will scope the cleanup in writing at Flapen.
