Every time the Zalando "MasterData" file is changed by Zalando, they must provide it again to the Lengow Support for integration in your Lengow/Zalando feed.
Some Zalando attributes have certain peculiarities:
ID / SKU
The "partnerArticleSimpleID", "supplierSKU" and "partnerSKU" fields must be filled in with the same unique product ID.
Price
Zalando recommends updating prices using the Price Updates UI in zDirect.
Refer to Zalando's documentation for more information.
"specialDescription"
This field's values aren't displayed on Zalando product page. Use this field to send technical details to Zalando, which are specific to your product. Zalando requests the text to be written in English or German language.
Note: the pipe symbol "|" is blocking for this field, use commas to separate several pieces of information.
Material composition
There are mandatory attributes to provide for materials, depending on the category:
- material (mandatory): the main material only, to select from a list of valid values.
-
upper_material_clothing (mandatory): fill in the different materials of the product. Expected format: "CO|10000" for 100% cotton, or "CO|7000;EL|3000" for 70% cotton and 30% elastane.
However, no material should account for less than 10%; in such a case, adjust the other materials to attain 100% in total.
Download here the list of codes to use
Note: Materials which are actually a brand cannot be used. For Lycra and Spandex, use Elastane (EL), for Rayonne use Viscose (CV), and for Lurex use Metal (ME).
For shoes, all four main material parts must be specified: upper_material, lining, insole and sole.
Season
You cannot create a new product associated with an old season.
For example, a product onboarded in January 2024 must be associated in the "season" attribute with "AW23" or "SS24", but not with "SS23".
Zalando requires that products already online and associated with older seasons are on promotion.
All information on seasons is available in this Zalando documentation
Images
In the "images" fields, you can enter up to 7 images per variation ("images_01", "images_02", etc.).
Image requirements:
- A minimum of 3 images is required for most categories (2 for hosiery, socks and tights, and 1 for beauty products)
- Aspect ratio (width x height): 1:1.44
- Best practice size: 1800 x 2600 pixels (Minimum size: 762 x 1100 pixels)
- Upright format
- Image type: JPG/JPEG
- Grey/beige background for model views: recommended color code - R241 G241 B241
- White background for packshots: mandatory color code - R255 G255 B255
Read more in Zalando's Images Best Practice Guides and Zalando's Image and Content Guides.
Tip: If you modify an image, Zalando will only update it if the URL changes as well. In such a case, you may add "?v1" at the end of the URL when the image changes (add "?v2" if i changes again, and so on).
Quantity
Enter here the stock available in your own warehouses.
If you are using the ZFS fulfillment service, and thus Zalando is shipping your orders, enter the value "0" in this field for the ZFS products.
Stock: Switzerland and Belgium focus
You are selling your products in Switzerland on both German (de-CH) and French (fr-CH) versions and/or in Belgium on both Dutch (nl-BE) and French versions (fr-CH)?
You must update stock for the same article (EAN) with the same value for both languages/subchannels in Switzerland and/or Belgium.
If Zalando receives a stock update (EAN) that doesn’t map for the product, the latest stock update from a particular locale will then be taken and copied to its corresponding locale.
See this example for Switzerland:
General Product Safety Regulation (GPSR)
To comply with the General Product Safety Regulation (GPSR) applicable from December 13, 2024, you must provide Zalando with information on brand and article level, as explained in Zalando's documentation GPSR-related data requirements
Please check the full list of GPSR data requirements provided by Zalando for the detailed list of required data. Two types of data sharing methods are indicated by Zalando:
- zDirect UI: applies to the GPSR brand-level data, which must be submitted via the zDirect UI (Zalando back-office) to ensure compliance.
-
zDirect API, XML Feed: applies to SKU-level data, this information must be completed in the corresponding attributes in Lengow (ex: "test_report", "risk_assessment", etc.)
If the attributes are not present in your Zalando channel, please contact the Lengow Support team to update the feed structure according to the latest masterdata file provided by Zalando.
To read: Zalando's communication on 28th November 2024