Marketplace
Selling on Zalando: upload guide & common errors
zDirect, Tradebyte, Channable or direct API: the upload paths, the technical pitfalls, and how to fix the most common validation errors.
Read the article →Feed management
The ideal data structure for Zalando: how to prepare your catalogue for success.
Published
Anyone who's worked in e-commerce for a while knows Zalando is the most demanding marketplace out there when it comes to data quality. Having a good product isn't enough: you need a flawless data structure behind it. My advice is always the same three words: centralize, normalize, automate.
zalandofeed-managementcatalog-data
Start by exporting from your e-commerce platform
The first step is pulling your data out of your CMS. If you run Shopify, you can export the catalogue to CSV, but be careful, because Shopify's native fields are rarely enough on their own for Zalando. Zalando asks for specific attributes most storefronts don't manage natively: detailed material composition (95% cotton, 5% elastane, not just "cotton blend"), brand-specific colour codes mapped to Zalando's own standard colour codes, and full size groups organized by size chart, not just a free-text size field.
This gap is exactly where most catalogues stall in onboarding. The data isn't wrong: it's just not structured for what Zalando's validation actually checks.
The real heart of the strategy: a feed management tool
Uploading a spreadsheet straight to Zalando by hand is risky and doesn't scale past a few dozen SKUs. The professional way to do this is through a feed management tool: Channable and Lengow are the two I see most often, alongside other feed-mapping platforms built for exactly this job. Here's why it's not optional past a certain catalogue size:
- Dynamic mapping. You tell the tool, once: "take the 'Colour' field from Shopify and transform it into the 'Colour Code' Zalando requires." It applies that rule to every SKU, forever, without you touching a spreadsheet again.
- Exclusion rules. You can decide, for example, not to send products with fewer than 3 units in stock to Zalando, so you never sell something you can't actually fulfill.
- Real-time updates. Change a price on Shopify and the feed updates it on Zalando automatically, instead of you remembering to sync it manually.
Building the master file: the attributes that can't be missing
If you'd rather start from a clean Excel structure before moving to full automation, these are the columns that have to be perfect before you go anywhere near an upload:
GTIN (EAN)
This is your product's passport. Without valid, properly registered EAN codes, Zalando will never accept the catalogue. This is the single most common hard blocker I see.
Merchant SKU
Your internal identification code. It has to be unique, every time, with no duplicates and no reused codes from discontinued products.
Colour and pattern
Don't just write "blue." Specify "navy," "cobalt" or "denim," and map each one to the correct Zalando colour family so search and filtering actually work for shoppers.
Size and dimension
This is where most errors happen. You have to map your manufacturer's size label (say, "M") to the specific size on Zalando's own scale (say, "M/INT"). That mapping changes by category and sometimes by market.
"A good product isn't enough on Zalando. What gets you approved, and keeps you approved, is a data structure that was built for their validation from day one."