Zalando zDirect: Technical Feed Excellence for Fashion Marketplaces

For fashion brands in Europe, Zalando is more than just a marketplace; it is the dominant ecosystem for discovery and commerce. However, unlike the relatively flexible requirements of Google Shopping or Meta, Zalando operates on a principle of radical standardization.

As a member of the Zalando Partner Program (zDirect), your success depends almost entirely on your ability to map your internal product data into Zalando's rigid "Article Structure." This guide provides a deep-dive into the technical architecture of Zalando feeds, focusing on how to achieve high data quality and avoid the "silent rejections" that plague many fashion retailers.

1. Understanding Zalando’s Data Architecture

Zalando's catalog ingestion engine, part of the zDirect ecosystem, is designed for one thing: consistent customer experience. This means that every product, whether from a small boutique or a global conglomerate, must look and "feel" the same in the catalog.

The Article Structure Hierarchy

Zalando uses a three-tier hierarchy for product data:

1. Brand Model: The high-level concept of the product (e.g., "Classic Cotton T-Shirt"). This level contains the core DNA of the product.
2. Color Way (Article): The specific color variant of that model (e.g., "Classic Cotton T-Shirt in Navy"). This is where most visual data lives.
3. Simple (EAN/SKU): The specific size variant of that color (e.g., "Classic Cotton T-Shirt in Navy, Size Large").

Each level has its own mandatory attributes. Errors at the "Brand Model" level will suppress every child variant, while errors at the "Simple" level only affect that specific size. This hierarchical dependency is why Zalando is considered one of the most technically challenging channels to manage.

2. Technical Feed Requirements & Mandatory Attributes

Zalando is famous for its strictness. If your data is 99% correct, it is 100% rejected.

A. The Mandatory EAN (GTIN)

On Zalando, the EAN (European Article Number) is non-negotiable. Unlike Amazon, where you can sometimes apply for exemptions, Zalando uses the EAN as the primary key for product identity. If your EANs are not valid or are already registered by another partner for the same product, your feed will fail. For more on identifiers, see our guide on GTIN & Brand errors.

B. Material Composition (The 100% Rule)

One of the most frequent causes of feed rejection on Zalando is invalid material composition. Zalando requires extreme granularity here to comply with EU consumer protection laws.

• Requirement: You must specify materials at the "Article" level.
• The Math: The percentages must add up exactly to 100%. "95% Cotton, 5% Elastane" is valid. "90% Cotton" is not.
• The Syntax: Zalando requires specific material codes. Using "Poly" instead of "Polyester" will trigger a validation error.
• Nested Materials: If a product has a lining (e.g., a jacket), you must provide separate material compositions for the outer shell and the lining, each adding up to 100%.

C. Size Mapping & The Size Chart ID

Zalando uses its own global size charts. You cannot simply send "Large." You must map your internal size to the corresponding Zalando size code for the specific category. This is often the most labor-intensive part of the setup.

Every product must be associated with a Size Chart ID. This ID determines which set of valid sizes you can use. If you associate a Men's T-Shirt with a Women's Shoe size chart, the entire ingestion will fail.

3. Optimizing for the Zalando Algorithm

While Zalando is a "closed" marketplace, search relevance is still driven by data depth.

Technical SEO for Marketplace Search

1. Attribute Richness: Fill in every optional attribute possible. Zalando's filters (e.g., "Sleeve Length," "Neckline," "Sustainable") are powered by these attributes. If you don't provide the data, your product won't appear when customers use filters. This is "Dark SEO"—optimizing for filters rather than just keywords.
2. Title Construction: Zalando often auto-generates titles based on Brand + Category + Color. However, providing a clean, descriptive internal title helps the initial ingestion and mapping process. Avoid keyword stuffing; Zalando's quality team will reject titles that look like spam.
3. Bullet Points: Use the description or specific feature fields to highlight technical specifications. For fashion, focus on fit, fabric weight, and care instructions.

The Sustainability Factor

Zalando is pushing heavily for sustainable fashion. There are specific "Sustainability" attributes that require third-party certification (e.g., GOTS, Fairtrade). Mapping these correctly can give your products a "Sustainability" badge, which significantly increases CTR and conversion among European shoppers.

4. Technical Implementation & Automation

Managing a Zalando feed manually is a recipe for disaster. The sheer volume of mapping required—especially for size charts and material codes—requires a dedicated feed layer.

Why Automation Matters

Using a tool like 42feeds allows you to decouple your source data (e.g., from Shopify or Magento) from Zalando's requirements.

• Rule-Based Material Mapping: Automatically convert "95/5 Cotton/Span" into Zalando's required format using regex or lookup tables.
• Dynamic Size Conversion: Build lookup tables that map your internal SKUs to Zalando's global size IDs. This ensures that "EU 42" always maps to the correct Zalando internal code.
• Validation Before Submission: Catch "Article Structure" errors before they reach zDirect, reducing the time-to-live for new collections.
• Image Management: Zalando has strict image requirements (1:1.33 ratio, no watermarks). An automated feed tool can flag non-compliant images before they trigger a rejection.

5. Common Zalando Feed Errors (and how to fix them)

6. Detailed Technical Workflow for zDirect

To successfully onboard products, you must follow this sequence:

1. Brand Authorization: Ensure your brand is authorized in zDirect.
2. Category Mapping: Map your products to the most granular Zalando category.
3. Attribute Transformation: Transform your raw data into the "Article Structure" (Model -> Article -> Simple).
4. Delta Updates: Once the initial catalog is created, only send "Delta" updates (changes in stock or price) to minimize API overhead.

7. Conclusion: The Fashion Feed Standard

Success on Zalando is a game of precision. By treating your feed as a piece of technical infrastructure rather than a simple file export, you can reduce rejection rates and ensure your products are visible to Zalando's 50 million+ active users.

If you are struggling with complex size mappings or material validations, consider using a dedicated feed management tool. Automation isn't just about saving time; it's about maintaining the "Article Structure" integrity that Zalando demands. This precision leads to higher "Buy Box" wins and better organic ranking within the Zalando app.

---

FAQ

Does Zalando require a specific feed format?

Yes, Zalando primarily uses JSON-based APIs (zDirect) or CSV/XML via SFTP. Regardless of the format, the data structure must follow the Brand-Article-Simple hierarchy. API is the preferred method for high-volume partners.

How often should I update my Zalando feed?

Inventory (stock levels) should be updated as close to real-time as possible (at least every 15-30 minutes) to prevent overselling. Product data (titles, descriptions) can be updated daily.

Why are my products "Approved" but not "Visible"?

This usually happens due to "Silent Rejections" where the data passed validation but failed a secondary quality check. Check the zDirect "Article Status" dashboard for specific warnings regarding image quality or brand-category inconsistencies.

Can I use the same feed for Zalando and Google Shopping?

No. Google Shopping is flat, while Zalando is hierarchical. You need a transformation layer like 42feeds to restructure your data for Zalando's Article Structure.

What is the most important attribute for Zalando?

The EAN (GTIN). It is the unique identifier that connects your stock to the Zalando catalog. Without a valid EAN, you cannot sell on the platform, and incorrect EANs will lead to your products being merged with the wrong items.

How do I handle size mapping for different countries?

Zalando operates in multiple regions. You should provide the "Supplier Size" (your internal size) and map it to the Zalando "Size ID" which is universal across their platform.

---

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does Zalando require a specific feed format?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, Zalando primarily uses JSON-based APIs (zDirect) or CSV/XML via SFTP. Regardless of the format, the data structure must follow the Brand-Article-Simple hierarchy. API is the preferred method for high-volume partners."
      }
    },
    {
      "@type": "Question",
      "name": "How often should I update my Zalando feed?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Inventory (stock levels) should be updated as close to real-time as possible (at least every 15-30 minutes) to prevent overselling. Product data (titles, descriptions) can be updated daily."
      }
    },
    {
      "@type": "Question",
      "name": "Why are my products 'Approved' but not 'Visible'?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "This usually happens due to 'Silent Rejections' where the data passed validation but failed a secondary quality check. Check the zDirect 'Article Status' dashboard for specific warnings regarding image quality or brand-category inconsistencies."
      }
    },
    {
      "@type": "Question",
      "name": "Can I use the same feed for Zalando and Google Shopping?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Google Shopping is flat, while Zalando is hierarchical. You need a transformation layer like 42feeds to restructure your data for Zalando's Article Structure."
      }
    },
    {
      "@type": "Question",
      "name": "What is the most important attribute for Zalando?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The EAN (GTIN). It is the unique identifier that connects your stock to the Zalando catalog. Without a valid EAN, you cannot sell on the platform, and incorrect EANs will lead to your products being merged with the wrong items."
      }
    },
    {
      "@type": "Question",
      "name": "How do I handle size mapping for different countries?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Zalando operates in multiple regions. You should provide the 'Supplier Size' (your internal size) and map it to the Zalando 'Size ID' which is universal across their platform."
      }
    }
  ]
}

---

Note: For brands looking to scale, technical feed observability is key. Monitor your zDirect error logs and use transformation rules to stay ahead of Zalando's changing requirements.