From 200 to 600 SKUs in Spain, then three new EU marketplaces: master catalogue and AI localisation
How a Python-built master catalogue and an AI localisation pipeline took a brand from Amazon.es to 600 SKUs per market in Germany, France and Italy.
Gazi El Halabi ·
In short
As Amazon Country Manager at Dnipro-M Spain, I grew the brand’s Amazon.es catalogue from 200 to 600 SKUs, built a Python master catalogue from live listing data, and used it to localise and publish those 600 SKUs on Amazon DE, FR and IT with an AI pipeline (Claude, OpenAI, Gemini) and native review. Listing output went from a few products a day to hundreds.
From 200 SKUs in one country to 600 SKUs in 10 stores.

Stage 1 of 4
Starting point: 200 SKUs, one store
When I joined, Dnipro-M sold 200 SKUs, only on Amazon.es.
As Amazon Country Manager at Dnipro-M Spain, I took the catalogue from one Amazon store to ten storefronts in four languages, from one master catalogue.
- SKUs
- 200
- Storefronts
- 1
- Languages
- 1
- Listings live
- 200
Dnipro-M Spain, March–September 2026. Listings = SKUs × storefronts.
The problem
The brand had a catalogue to sell across Europe, but its product content lived in the marketplace itself, one listing at a time. Every new market meant rewriting listings by hand, in another language, from scratch. That does not scale to hundreds of SKUs and several countries.
Context
I was Amazon Country Manager for Dnipro-M Spain from March to September 2026, responsible for the Amazon account and its expansion. When I joined, the brand had 200 SKUs, only on Amazon.es. The work started there and then extended to Germany, France and Italy, and beyond Amazon to ManoMano, Leroy Merlin and Carrefour in Spain and France: the same 600 SKUs on ten storefronts.
Approach
Treat the catalogue as data, not as listings. Build one master catalogue that is independent of any single marketplace, check it against the brand’s official information, and generate every market’s content from it.
Tools
| Need | Tool |
|---|---|
| Extract live listing content | Python scraper |
| Single source of product truth | Master catalogue (PIM structure) |
| Native ES / IT / FR / DE content | Claude, OpenAI and Gemini |
| Publication | Marketplace-ready flat files |
| Images with text | A batch image-text localiser (Python + AI) |
Process
- Grow the base market. The Amazon.es catalogue went from 200 to 600 SKUs.
- Extract. A Python scraper pulled the live listing content into a structured master catalogue.
- Verify. Each SKU was cross-referenced against the brand’s official website to flag data discrepancies before anything was published elsewhere.
- Localise. An AI pipeline generated native Spanish, Italian, French and German content from the catalogue — written from the data, never beyond it — with human review. The approach is explained in Amazon listing localization for Europe.
- Publish. Content was exported as marketplace-ready flat files for each store.
- Localise images. Text inside product images was localised in batches, keeping design and layout.
Result
- Amazon.es catalogue grown from 200 to 600 SKUs: 400 new listings.
- The same 600 SKUs published per market on Amazon DE, FR and IT from the master catalogue.
- Listing production went from a few products per day to hundreds.
- Catalogue discrepancies caught before publication, not after.
- Expansion extended beyond Amazon: the same 600 SKUs on ManoMano, Leroy Merlin and Carrefour, in Spain and France.
Lessons
- The catalogue is the product. Once product data is structured and verified, each new market is an export, not a rewrite.
- AI is a drafting engine, not a source. It is only as good as the attributes it is given, and it needs native review.
- Rules belong in the pipeline. Limits such as Amazon’s 75-character titles are enforced at generation time and validated again before upload — the Amazon Title Checker runs the same checks.
- Verify against the brand’s own data. Marketplaces drift; the brand’s official information is the reference.
Since September 2026 I work as an independent Amazon and marketplace consultant, and I am open to senior roles: see my profile as an Amazon Marketplace Manager.
Stack: Python · Web scraping · Master catalogue / PIM · Claude · OpenAI · Gemini · Flat files · Seller Central
Want a similar workflow for your catalogue?
Discuss a project