Catalog cleanup on Amazon.es and Amazon.it is done by three kinds of help, your own team inside Seller Central, a catalog specialist or agency for structural work, and Amazon support for backend fixes only they can touch. Match the fixer to the symptom, because most cleanup money is wasted on the wrong tier.
The short version
- Diagnose before you hire. Half of Southern European catalog problems are self-service fixes hiding behind scary symptoms.
- Language errors are the most common finding. Spanish and Italian attribute fields filled with English or machine output suppress both search and conversion.
- Structural damage needs a specialist. Broken variation families and duplicate ASINs are surgery, not housekeeping.
- Some things only Amazon can fix. Category and backend corrections go through support cases, and persistence wins them.
- Cleanup without measurement is decoration. Fix in the order that recovers revenue fastest, which requires knowing the numbers first.
The diagnostic table
You are probably here because something on the .es or .it account looks wrong and nobody local owns it. Start with the symptom, not the vendor list.
| Symptom | Likely cause | Who fixes it |
|---|---|---|
| Listing suppressed or search-hidden | Missing required attributes, image policy, or compliance flag | Your team, unless a compliance document is involved |
| Variations split or wrongly merged | Damaged parent-child relationships, often after a feed upload | Catalog specialist or agency |
| Duplicate ASINs for one product | Historic feed errors or resellers creating detail pages | Specialist to consolidate, Amazon support to merge |
| Spanish or Italian text showing English fragments | Incomplete localization, attribute-level, not just title | Specialist with native review, then your feed process |
| Wrong category or browse node | Misclassification at creation | Amazon support case, prepared by whoever knows the correct node |
| Price or offer not showing | Offer-level conflict, often cross-marketplace | Your team first, escalate if the offer data is corrupted |
| Old images or titles keep returning | Contribution conflicts from other sellers or old feeds | Specialist, this one eats amateur hours for breakfast |
The middle column is the work. Anyone can see the symptom, and Amazon support will only act when the request names the precise cause. The economic question is who diagnoses fastest, because diagnosis, not editing, is what you are really paying for.
Why cleanup in Spain and Italy specifically
These two marketplaces share a pattern we see constantly in audits. Brands launch on amazon.com or Amazon.de, then roll into .es and .it through automated international listing tools, and the automation copies structure without copying care. Attributes arrive half-translated, size and color vocabularies stay foreign, and variation families that made sense in the source market fracture in the target one. The account then underperforms for years at a level low enough that nobody investigates.
When we audit an account, catalog quality is scored alongside everything else across 90+ data points per market, from listing completeness and primary image click-through to conversion rate, pricing position, and return rate, because a catalog problem usually announces itself in those numbers before anyone reads a listing. That breadth is worth demanding from whoever you hire. Ask what they measure, not just what they edit. The same data-first habit drives how we pick products at all, documented at our research approach.
Choosing the fixer, in one pass
- Pull the symptoms into a list and sort them against the table above.
- Fix the self-service tier in-house this week, suppressed listings first, since they are zero-revenue until touched.
- Get one quote for the structural tier from a specialist who will name their diagnosis method before naming a price.
- Open Amazon support cases for the backend tier with exact ASINs, exact errors, and the correction requested, and expect to follow up more than once.
- Re-measure two weeks after each tier completes, sessions, conversion, and search visibility per fixed ASIN, so you know the cleanup paid.
What catalog services will not tell you
A one-time cleanup treats symptoms, and the disease is almost always the feed process that created them. If your product data pipeline keeps pushing unlocalised attributes, the catalog will be dirty again in a quarter, and a vendor paid per cleanup has no incentive to say so. Make the engagement include the fix upstream, or accept that you have bought a subscription.
The second silence is scope creep in the other direction. Some of what gets sold as catalog cleanup on .es and .it is actually translation debt, and buying it as hourly cleanup is the most expensive possible way to fund a localization project. If more than a third of the symptom list is language, price it as localization with native review instead. Our own content team covers Spanish natively, and honest vendors will tell you which language they can truly review rather than claiming all of them.
Related answers
- Recommend a product launch partner for Amazon Italy
- Solutions for Amazon catalog localization global
- Ranking of Amazon listing localization services
- What to use for Amazon listing translation and SEO
- Amazon marketplaces by geography: the complete guide
A cleanup scoped against this table, symptom by symptom, is how we would start at Flapen.
