Zalando

1. Preamble – Managing your Zalando feed on Lengow

This guide demonstrates how to configure and to manage your Zalando feed on a daily basis.  Before launching into configuring your Zalando feed, familiarise yourself with the following recommendations.

These are the steps to publishing your products and to retrieving your Zalando orders:

  • Contact Zalando to verify your partnership. Zalando chooses the sellers it wishes to work with.
  • Ask your Zalando account executive to provide us with your ‘MasterData’ file. This is a mandatory file necessary for your integration into Zalando. This file contains, among other things, the type of product that you are authorised to sell on Zalando.
  • Ask Lengow customer support to create a feed Zalando.
  • Separate out the products that you don’t want to advertise or that you are not authorised to sell on Zalando.
  • Complete the "Field Matching" in order to match your source feed fields with the existing Zalando fields.
  • Change the values of your feed source by using automatic rules and/or search-replace to adapt them to the publisher’s expectations.
  • Complete the mapping for variations to include your values according to the channel’s expectations.
  • Organise your categories so that they correspond with the Zalando categories.
  • Complete the mapping for features.
  • Configure the options for your Lengow feed (Indexing Frequency, Alerts…).
  • Check with your Zalando account executive that your Zalando back-office configurations are correct (Delivery time, shipping cost…).
  • Inform your Zalando account executive that you are ready to launch the product integration.
  • Supervise your product integration.
  • Manage your orders.

These steps are further detailed below.

2. Opening your Zalando feed on Lengow

Reminder: contact Zalando before opening your feed on Lengow, to confirm that you can sell your products on this marketplace.

2.1 Retrieving the ‘MasterData’ file

In order for Zalando to provide us with your ‘MasterData’ file, you must:

  • Ask your Zalando account executive to provide client support at Lengow with your ‘MasterData’ file. 

OR

  • Contact our client support team to notify us of your integration with Zalando. This notification must include the email address of your Zalando account executive to allow us to get in contact them.  

Observation: The values included in your ‘MasterData’ file may evolve over time. These changes will not automatically be updated on Lengow. As soon as your ‘MasterData’ changes, contact our client support team to update your new data on the Lengow feed.  

2.2 Creating the Zalando feed

After getting confirmation from Zalando, follow these steps to create a feed on Lengow:

Search for the title “Zalando V2” so that you can see all the available categories.

Alternatively, look for the French flag in the “Marketplaces” section and then choose the Zalando feed.

3. Set up your Zalando feed

Zalando asks merchants to use specific attributes in order to reference the products in their marketplace. You therefore need to duplicate these attributes in your Lengow source feed. 

3.1 Creating a feed segmentation

Before starting to change your attributes, first you need to filter your products so that you don’t send to Zalando

  • The products that you do not wish to sell in this marketplace. 
  • The products in your feed that you are not authorised to sell on Zalando.
  • "Parent products", if your source feed contains any.

3.2 Match the fields

Zalando requires a particular feed structure depending on the category chosen. 
In order to proceed with the field matching, you need to go to the page “Feed Management” then “Field matching”:

Check the field matching and complete the missing information. Carefully read the definition of a field, for additional help.

Certain fields require a valid date; refer to the following for further information:

Other fields have certain particularities:

  • specialDescription’: The values in this field are not published on the product page on Zalando. Use this field to send special information of your product that you cannot cover via  the data mapping in Lengow. Note that the pipe symbol "|" is blocking for this field, use commas to separate several pieces of information.
  • image’: seven images are possible by variations that must be separated by ‘I’. You may use the personalised field below in our example:

  • ean’: The EAN code is mandatory.  

The other fields have no particularities. It will suffice to make the connections with the fields from your source feed in order to input the most information as possible.

3.3 Configuring your variations

Zalando accepts variations according to size and/or colour.

Reminder: If your source feed contains parent products, you must filter them by creating a feed segmentation.

1 / Complete the following fields under the ‘Field Matching’ tab:

  • partnerArticleModelId’: your parent login (same login for variations of the same product).
    Note: This field is mandatory and needs to be filled-in for all products. If your product does not have variations, indicate here its unique identifier.

  • size’: the size of your products.

  • sizeRegister’: leave the virtual field matched with ‘zalando_sizeRegister’.

  • mainColorCode’: the colour of your products.

2 / Under the ‘Variations’ tab > ‘Mains Colors’ tab, create a connection between the values from your source feed and the colours imposed by Zalando. For more information, refer to ‘3.4.1.1 Particularities as to colours’.

3 / Under the ‘Variations’ tab > ‘Sizes’ tab, create a connection between the values from your source feed and the sizes imposed by Zalando.

Be careful: Zalando sizes are classed under grids. For example, the sizes for men and for children are not under the same grid. If you have the same size for an item of clothing for men and for children (e.g. M), you must use automatic rules to input the size (‘size’ field) and the grid for your size (‘sizeRegister’ field). For more information, refer to ‘3.4.1.2 Particularities as to size’.

Observation 1: All of your varied products must be correctly configured. If a variation is configured incorrectly (for example, with a size value that is not expected by Zalando), then all of your variations for that product will not be published.

Observation 2: The titles of varied products must not contain any notion of variation. Where necessary, remove them using Search/Replace.

3.4 Fields that require valid Zalando values

Certain fields must contain valid Zalando values. These are values contained in your ‘MasterData’ file provided by Zalando. These values are integrated into your Lengow feed upon creation. Below is a list of the relevant fields:  

  • ‘brand’: the product brand.
  • ‘season’: the seasonality of your product.
  • ‘gender’: the product’s sex (male/female).
  • ‘ageGroup’: the age range of your product.
  • ‘mainMaterial’: the composition of your product.
  • ‘mainColorCode’: the main colour of your product.
  • ‘secondColorCode’: the secondary colour of your product.
  • ‘thirdColorCode’: the tertiary colour of your product.
  • ‘size’: the size of your product.
  • ‘length’: the length of your product.
  • ‘vatCode’: the VAT rate of your product.

There are several methods of correctly inputting these fields:  

3.4.1 You have a dedicated field within your source feed

If you have a dedicated field within your source feed, follow these steps:

1 / Under the ‘Feed Management’ tab > ‘Field Matching’, match these fields with the corresponding fields from your source feed.

2 / Under the ‘Variations’ tab, create a connection between the values from your source feed and the Zalando values.

This is the connection between the ‘Field Matching’ tab and the ‘Variations’ tab. The values that you map under the ‘Variations’ tab will crop up in different optimised fields, as is shown below:

  • ‘brand’ field: ‘Marques’ tab.
  • ‘season’ field: ‘Saison’ tab.
  • ‘gender’ field: ‘Genres’ tab.
  • ‘ageGroup’ field: ‘Tranche d'age’ tab.
  • ‘mainMaterial field: ‘Matières’ tab.
  • ‘mainColorCode’ field: ‘Couleurs Principales’ tab.
  • ‘secondColorCode’ field: ‘Couleurs Secondaires’ tab.
  • ‘thirdColorCode’ field: ‘Couleurs Tertiaires’ tab.
  • ‘size’ field: ‘Tailles’ tab.
  • ‘length’ field: ‘Longueur’ tab.
  • ‘vatCode’ field: ‘TVA’ tab.

Observation: it is possible to select several values for certain tabs. To do this, click ‘Ctrl’ (‘cmd’ for mac users) and left click on the mouse at the same time. 

3.4.1.1 Particularities as to colours

There are three different platforms for colours:

  • mainColorCode' field: ‘Couleurs Principales’ tab (mandatory).
  • secondColorCode’ field: ‘Couleurs Secondaires’ tab (optional).
  • thirdColorCode’ field: ‘Couleurs Tertiaires’ tab (optional).

You must have three ‘Couleur’ fields in your source feed to input these three platforms.

If you only have one ‘Couleur’ field in your source feed, only match the mandatory ‘mainColorCode’ field. If you wish to input the ‘secondColorCode’ and ‘thirdColorCode’ fields, you must:

  • Create a virtual field.
  • Match this virtual field.
  • Input this virtual field using an automatic rule. The values that must be inputted into this field can be found in your ‘MasterData’ file.

3.4.1.2 Particularities as to size

Zalando sizes are classed under grids. For example, sizes for men and for children are not under the same grid. The different grids can be found under the ‘Variations’ tab > ‘Taille’ tab > drop down menu from ‘Tailles Zalando’. In the example below, you can see the different sizes under the grids.

  • ‘Clothing, Kids, US [XXS-XXL]’
  • ‘Sports, Damen, Textil, US [3XS - 6XL]’

When you match a Zalando size, we will automatically update the following:

  • The size of your product in the ‘size’ field.
  • The corresponding grid in the ‘sizeRegister’ field.

If you have the same size for two different grids, for an item of clothing for children and for men (for example: M), you must use automatic rules to input your size (‘size’ field) and the grid for your size (‘sizeRegister’ field):

1 / Be sure to leave ‘Toutes (Sans Taille)’ under the ‘Variations’ > ‘Taille’ tab for the relevant value. 

2 / Create an automatic rule to input the following:

Make sure to change the condition for the automatic rule to correspond with the values of your source feed. 

3.4.1.3 Particularities as to materials

The field "upper_material_clothing" (mandatory) is used to set the material type of one product. Specific values (alpha type code) are expected by Zalando here. The material codes are in your ‘MasterData’ file.

  • Example of expected format for several values:

CO | 70; EL | 30 for 70% cotton and 30% elastane.


The "MainMaterial" field is optional and can only contain one material code (numeric type code).

  • Here is the expected format:

021 for Cotton

The corresponding codes for materials can be found in your ‘MasterData’ file

3.4.2 You do not have a dedicated field within your source feed.

There are two possibilities if you do not have a dedicated field within your source feed:

3.4.2.1 The expected value is the same for all of the products

In this case, use the ‘personalized Field’ of the ‘Field Matching’ to input the value required by Zalando (available in your ‘MasterData’ file).

For example, if I wish to input the value of ‘100’ (=Full Tax’) for all of my products, this is how I would proceed:

3.4.2.2 The expected value is different according to my products

In this case, this is how to proceed:

1 / Create a virtual field under ‘Feed Management’ > ‘Source Feed’ tab.

2 / Match this virtual field with the required field under ‘Feed Management’ > ‘Field Matching’ tab. Register by clicking on ‘Modifier les champs du flux’ at the bottom of the page.  

3 / Create an/several automatic rule(s) to input the required value by Zalando into the virtual field. (available in your ‘MasterData’ file).

3.5 Configuring your prices/promotions/ sales

The management of promotions and of sales is configured in the same way for Zalando. Your products under a promotion or in a sale must have values in the following fields:

  • currentSalesPrice’: the sale price of your product.  
  • previousSalesPrice’: the original price of your product, mandatory field. Complete this field with the same value as "currentSalesPrice" if the product is not promoted.  

Click here for the configuration of your sales.

3.6 Configuring your shipping costs

Contact your Zalando account executive to configure your shipping sales.

3.7 Mapping categories

For your products to be published in the correct Zalando categories, you must use the Zalando taxonomy to create connections between your categories and those of the marketplace. To do this, you must go to ‘Product Management’ under Lengow:

  • Open the Zalando taxonomy 
  • Find your category by hitting Ctrl+F, for example, on the key word in the taxonomy.
  • Click the corresponding line. 
  • Click ‘SAVE’

Observation: Only the categories in your ‘MasterData’ file (Silhouettes) provided by Zalando appear in the taxonomy. If the required category cannot be found, this means that Zalando does not permit the sale of products in this category. If this is unusual, contact your Zalando account executive directly.

You can also use the Automatic Rule tool to complete your categorisation. 

3.8 Mapping features

Features allow for a better description of a product and optimise the search of the product on the site by the user.

To define these features, you must first select a category, then enter the category to see the listing of your products.

Next, open a window to manage the features of each product:

In this window, you will find the following:

  • A reminder of the category at the top.
  • The name of the feature (the value found in between brackets corresponds to the code of the selected feature).
  • The list of valid values per feature:
    • A drop-down menu of possible values.
    • Tick boxes if several values are possible.
    • A text-box if the feature to input is an open value.
  • The mandatory (’Requis’) or optional (‘Optionnel’) character of the feature for the creation of the product.
  • The possibility of registering these features for all products in this category.
  • You may register the features or remove them at the bottom of the page.

Observation: There is a text-box available for materials, but the values are not open. You must input the material code and the percentage of the material as is provided in ‘Observation 2’ under ‘7.1.1 Les silhouettes’.

3.9 The options tab

In the “Options” tab of your Zalando feed, check the various points and modify them if needed. For more details about this tab, consult our tutorial "Options" tab.

3.10 Check the attributes in your updated feed 

To check the data sent to the distributer, consult the optimised feed. All the updating that you have done in Lengow will be visible IMMEDIATELY (automatic rules, search/replace, matching etc.).

Observation: Check your optimized feed as regularly as possible to ensure that your settings have been correctly applied to all of your new products.

4. Integrating your catalogue to Zalando

4.1 Contact your Zalando account executive

When your feed is ready to be integrated, contact your Zalando account executive to launch the broadcast of your products.

4.2 Sending your catalogue

Zalando retrieves your catalogue every day at 1am.

Stocks only, are updated every 30 minutes.

4.3 Integration reports

There are two steps to check your catalogue:

  • The first step is Lengow checking your data. The incorrectly configured products will not be available to Zalando.
  • The second step is Zalando analysing the available products.

An integration report is available for each step under the ‘Indexing History’ tab:

Lengow integration report

Observation 1: ‘Codes’ are explained in this document: artikelstatus-code-definitionen.xls and are found under the ‘Detail Status Definition’ tab.

Observation 2: If a variation of the same product is incorrectly configured, none of the products will be put online.

Zalando integration report

5. Removing a product

There are several ways of deactivating/deleting a product from Zalando:  

Note: Putting zero as a quantity for a product will not delete the product but will publish it as ‘sold out’ on Zalando.

6. Order management

6.1 Order retrieval times 

Lengow retrieves orders made on the Zalando site every 30 minutes.

6.2 Processing your orders

1 / When a new order is placed on Zalando, it falls under the Lengow ‘New Orders’ tab. Zalando accepts the order in the first step. The order is then automatically placed under the ‘Orders waiting for shipment’ tab.

2 / When your order is placed under the ‘Orders waiting for shipment’ tab, you have  two possible options:

  • Prepare your order to be sent to the client. Once this is done, confirm the delivery by updating the parcel tracking. Be careful, you must complete these steps for every product if the order contains several products. If you send these products in the same package, it is possible to update the parcel tracking several times. The order is then put under the ‘Orders sent’ tab.
  • Cancel the order if you do not have the ordered product in stock. The order is then put under the ‘Orders cancelled’ tab. Zalando then tells the client that their order has been cancelled.

Observation 1: If you use one of our units or out web-service to import the orders in your back-office e-commerce, the order may be imported to your back-office once the ‘Approved’ status under the ‘Orders waiting for shipment’ tab has been given. Once you have processed the order and confirmed the delivery from your back-office, the order is automatically placed under the ‘Orders Sent’ tab in Lengow.  

Observation 2: Zalando requests that some documents are sent with the order package. These are available for download on Lengow once your order has obtained ‘Approved’ status under the ‘Orders waiting for shipment’ tab:  

  • The invoice.
  • The delivery.
  • The return policy.

3 / Once your order is put under the ‘Orders sent’ tab, we will inform Zalando that your order has been sent to the client. Zalando then informs the client that their order has been sent.

If the client returns your product, you must go back to the order on Lengow and confirm the return of the product by clicking on ‘Return’. Wait until you have received the product to do this. We will inform Zalando that the product has been returned and that the client can be refunded.

6.3 Different statuses for your Zalando orders

Below are the varying steps of an order:

  • New: new order. Zalando is charged with approving new orders, not the seller.
  • Approved: the order is approved. The seller can then send the order or cancel it (list of actions).
  • Shipped: the order is sent. The seller can then note it as returned. 
  • Returned: the order was returned.
  • Cancelled: the order is cancelled.

Annex

Understanding your MasterData file

The ‘MasterData’ file is directly provided by Zalando and is integrated into your feed on Lengow. This file contains all the valid Zalando values that are relevant to you. Every ‘MasterData’ file is unique and personalised by your Zalando account executive.

The values contained in your ‘MasterData’ file may evolve over time. These changes will not automatically be updated in Lengow. As soon as your ‘MasterData’ changes, contact our client support service for us to add the new data to your Lengow feed.

The ‘MasterData’ contains the information expected by Zalando for your products:

  • Your silhouettes, meaning the categories in which you may sell your products (‘silhouettes’).
  • Your brands (‘brands’).
  • Your seasons (‘seasons’).
  • Your genders (‘genders’).
  • Your age groups (‘ageGroups’).
  • Your colours (‘colors’).
  • Your materials (‘materials’).
  • Your sizes (‘sizeGrids’).
  • Your lengths (‘lengthGrids’).

If you do not use our matching functions (‘Product management’ tab for silhouettes, and ‘Variations’ tab for everything else), you will be able to collect the values that must be input into your Zalando feed from this file.

Master Data: The silhouettes

The silhouettes correspond with the Zalando categories that you may sell your products under. These silhouettes can be found under the ‘Product Management’ tab on Lengow.

  • In the ‘MasterData’ file

  • In Lengow

Each silhouette requires several features. Each feature is presented in the following way in the ‘MasterData’ file:  

 ‘multiSelect’:

  • ‘true’: it is possible to select several values.
  • ‘false’: you must select only one value.

 ‘attributeType’:

  • ‘OPTION’: there are valid values.
  • ‘METRIC’: the value is open and must be a number.
  • ‘TEXT’: the value is open and must be in text.
  • ‘MATERIAL’: refer to ‘Observation 2’ of this part.

 ‘required’:

  • ‘true’: mandatory features for the creation of your product.
  • ‘false’: optional features for the creation of your product.

 ‘description’: name of the feature.  

 ‘attributKey’: the feature code as it appears under the ‘Field Matching’ tab.

 The value expected by Zalando.

 The name of the value expected by Zalando.

Observation: You will find the values  for of your ‘MasterData’ in the solution, under the feature management section.

By selecting them from this tab, we will automatically send Zalando the expected value for .

If you wish to send Zalando a value through different means (by inserting it into your source feed, through a personalised field, or automatic rules, or search/replace, by inputting values…), you must:

  • Contact our client support team to publish the requested field under the ‘Field Matching’ tab.
  • Complete the listed field with the value in . Once this has been authorised, (multiSelect = ‘true’), you can input several values by separating them by a pipe: ‘valeur1|valeur2|valeur3...’. The example below shows that if I would like to note that my product is ‘side zip’ and ‘fordable leg’, I must input ‘bootleg_detail_4533|bootleg_detail_4534’.

Observation 2: When the feature is ‘MATERIAL’, the expected value is the composition of your product. Zalando requests that you input the percentage of material for each product. You must follow the same method as that highlighted in ‘3.4.1.3 Particularities as to material’, but the expected values are different.

For example: If your product is: ‘90% Cotton, 10% Alpaca’, then Zalanda expects the value to be ‘CO|90;WP|10’.

Master Data: Colours

The colours that are accepted by Zalando:

If you do not use the Lengow mapping for colours, you must input the value of ‘205’ for example, for the colour ‘orange’ on Zalando.

To know the specificity of Color setting click here!

Master Data: Materials

The materials that are accepted by Zalando (Optional):

To know the specificity of Material setting click here!

Master Data: Sizes

Zalando expects two values for sizes:

The grid for size under 
The value for size under 

If you do not use the Lengow mapping for size, you must input the two values into your Zalando optimized feed. For example, to input the size 36 for women, you must complete the following fields:

  • ‘size’: 36.
  • ‘sizeRegister’: 1FE2000EOA.

To know the specificity of Size setting click here!

Master Data: Lengths

Zalando expects two values for lengths:

The grid for length under 
The value of the length under 

If you do not use the Lengow mapping for lengths, you must input the two values into your Zalando feed. For example, to input a length of 31 for women, you must complete the following fields:

  • ‘length’: 31.
  • ‘lengthRegister’: 2FHU000U3A.