1. Source feed format
You can provide us with your source feed in CSV, TXT or XML format. We recommend, however, that you use the CSV format.
2. Source feed encoding
It is preferable to encode your feed using UTF-8 format in order to guarantee maximum compatibility with all character sets.
3. Source feed content
Before generating your source feed, here are a few points to note, especially since certain things may damage or block indexation of your feed in the Lengow solution.
- Never insert spaces in the titles of fields (instead, use _).
- Never use special characters (accents, %, /, etc.) in the titles of fields.
- The unique ID must not contain any special characters (accents, %, &, /, etc.).
- Category names must not contain / or & (instead, use > symbols).
- Never change the IDs of your products. The product IDs are used to save your optimizations in the solution. If you change your product IDs, you will lose all your optimizations.
- Never modify the structure of your source feed once it is being used in the solution. If you need additional fields, add them at the end of your structure.
- A field must not appear twice in your source feed. Each header must be unique.
3.1 In CSV or TXT format
Accepted delimiters are the vertical bar/pipe, comma, semi-colon and tab.
|Title of the field||Content of the field||Type||Example||Recommendation|
|Unique_ID||Permanent reference number specific to each product and used to identify it in a unique way over time. A single product must always have the same identifier. The ID must not be reassigned to another product (maximum of 25 characters).||Alphanumeric||1235RES56||Mandatory|
|Title||Product title||Alphanumeric||Samsung 100 Hertz LCD Television||Mandatory|
|Description||Product description||Alphanumeric||Samsung 100 Hertz LCD Television, 47-inch screen, etc.||Mandatory|
|Price_including_tax||Corresponds to the price of the product on your site (54.40, 60.30, etc.). Without the € symbol and the delimiter must be a full stop.||Numeric||799.90||Mandatory|
|Barred_price||If the price has been reduced (promotion, clearance sale, etc.), indicate in this field the old price of the product including tax in Euros. Without the € symbol and the delimiter must be a full stop.||Numeric||900.99||Highly recommended|
|Sale_price||Price of the product during the sale period. Without the € symbol and the delimiter must be a full stop.||Numeric||699.90||Highly recommended|
|Category||Category to which the product belongs. You can also refer to “product family” (field with a maximum of 250 characters). This field will be used to organise your products by category. (Washing machine, MP3 player, etc.).||Alphanumeric||High tech > Televisions > LCD Televisions > 100 Hertz||Mandatory|
|Sub_category1||Sub-category to which the product belongs.||Alphanumeric||LCD Televisions||Highly recommended|
|Sub_category2||Sub-category to which the product belongs.||Alphanumeric||100 Hertz||Highly recommended|
|Product_URL||Corresponds to the URL of the product page on your site||URL||http://monsitemarchand.com/produit.html||Mandatory|
|Image_URL||Corresponds to the URL of the product image on your site GIF or JPG format. Minimum size depends on the channel.||URL||http://monsitemarchand.com/image_produit.html||Mandatory|
|EAN||This field is made up of 13 figures and corresponds to the bar code commonly used for consumer goods. It identifies the product in a unique manner and enables better indexation of your product in our product categories. European article number.||Numeric||1234567891011||Highly recommended|
|MPN||Manufacturer product number||Alphanumeric||PRD567HT||Highly recommended|
|Brand||Corresponds to the brand of the product or the name of the product manufacturer.||Alphanumeric||SAMSUNG||Mandatory for Google AdWords, highly recommended for other distributors.|
|Delivery_costs||Corresponds to the product's delivery costs. The price, including tax in Euros, for all charges related to the order must be entered in this field: shipping, processing and order preparation fees, etc. Without the € symbol and the delimiter must be a full stop in the description.||Numeric||5.00||Highly recommended|
|Delivery_time||Maximum delivery time. Numeric value which will be interpreted by default as a number of days. If the unit is not day(s), please specify (accepted units: hour(s); day(s); week(s); month(s)). For delivery times covering a range, separate the minimum and maximum by a dash. Indicate the unit only if this is not day(s).||Numerique||12||Highly recommended|
|Delivery_description||Additional description of the delivery. Details regarding the delivery.||Alphanumeric||Same day delivery for Paris.||Highly recommended|
|Quantity_in_Stock||Corresponds to the number of products currently in stock||Numeric||23||Highly recommended|
|Availability||Product availability Numeric value which will be interpreted by default as a number of days. 0 = in stock. If the unit is not day(s), please specify (accepted units: hour(s); day(s); week(s); month(s)). Where availability covers a range, separate the minimum and maximum values by a dash. Indicate the unit only if this is not day(s).||Numeric||0||Recommended|
|Warranty||Warranty period for the product. In years by default. If the warranty is not expressed in year(s), specify the unit used (accepted units: month(s); year(s))||Numeric||2||Highly recommended|
|Size||Corresponds to product sizes. List available sizes for a product, separating them with commas.||Alphanumeric||M||Highly recommended|
|Colour||Corresponds to product colour (red, white, blue, etc.). List the available colours for a product, separating them with commas.||Textual||Blue, Red, Green||Highly recommended|
|Material||Corresponds to the material of the product (leather, velvet, imitation leather, cotton, etc.). List the materials available for a product, separating them with commas. Mandatory for sales on Amazon Clothing||Textual||Leather, Cotton||Highly recommended|
|Gender||Corresponds to product gender. Men's, Women's, etc.||Textual||M||Highly recommended|
|Weight||Corresponds to the weight of the product in grams. Without the measurement unit and the delimiter must be a full stop.||Numeric||20.55||Highly recommended|
|Condition||Corresponds to the condition of the product. You can indicate 0 or 1 (0= new, 1 = used) or simply new or used.||Alphanumeric||0 or new||Highly recommended|
|Sales||Only applies during sale periods. 0 = product not on sale, 1 = product on sale||Numeric||1||Highly recommended|
|Promo_text||Corresponds to the promotional text for a product, (field limited to 80 characters, including spaces)||Alphanumeric||Buy three products, get one free!||Recommended|
|Promo_percentage||Corresponds to the percentage reduction applied to a product. In figures, for example: 30, 40, 50, etc.||Numeric||30||Highly recommended|
|Start_date_for_promo||Corresponds to the start of the promotion||Date field: DD-MM-YYYY HH:MM:SS||26-06-2008 08-00-00||Highly recommended|
|End_date_for_promo||Corresponds to the end of the promotion||Date field: DD-MM-YYYY HH:MM:SS||10-07-2008 23-59-59||Highly recommended|
|Ecotax||Amount in Euros of the eco-participation for Waste from Electrical and Electronic Equipment (WEEE). Without the € symbol and the delimiter must be a full stop.||Numeric||2.33||Highly recommended|
|Currency||Corresponds to the currency of the price of the product. Only use the standard three-letter ISO 4217 codes. You can find all the currency codes on the iso.org website.||Textual||EUR||Highly recommended|
3.2 In XML format
The required fields are identical to those required in CSV format. Lengow cannot take into consideration XML feeds containing a multiple-level node structure or RSS XML feeds. You must send us a structure where all of the XML nodes are at the same level. Each <product> node must contain the same number of XML sub-nodes. Any empty nodes must also appear in the feed even if they do not contain any values. The file must, for example, be in the following format:
<product> <Category><![CDATA[ Billets d'avion ]]></category> <Unique_ID><![CDATA[ 2 ]]></Unique_ID> <Title><![CDATA[ Couette Ultra Light Sleep 240x200]]></title> <Description><![CDATA[Frais de livraison offerts Cette couette conviendra particulièrement aux personnes qui recherchent un produit naturel et extrêmement léger pour les chaudes nuits d'été]]></description> <Price><![CDATA[ 399 ]]></Price> <Product_URL><![CDATA [http://tracking.lengow.com/shortUrl/14-15062-2115/]]></Product_URL> <Image_URL><![CDATA[http://www.monsite.com/Photos/Products/000004/000001.jpg]]></Image_URL> <Delivery_costs><![CDATA[ 0 ]]></Delivery_costs> <Availability><![CDATA[ 0 ]]></Availability> <Delivery_time><![CDATA[ 7 ]]></Delivery_time> <Warranty><![CDATA[ 3 ]]></Warranty> <Ecotax><![CDATA[ 0 ]]></Ecotax> <Brand><![CDATA[ Plumka ]]></Brand> <EAN/> <Barred_price/> <Currency><![CDATA[ EUR ]]></Currency> <Condition><![CDATA[ 0 ]]></Condition> <Promotion_type><![CDATA[ 0 ]]></Promotion_type> <Colour><![CDATA[ rouge ]]></Colour> <Material/> <Size/> <Gender/> </product>
You must encapsulate all of the values in CDATA (<![CDATA[ 2 ]]>)
3.3 Adding specific fields – for the marketplaces and Google Shopping
Your product catalogue does not contain any product variations?
The following fields must be added to the general structure of your source feed in order to meet the various requirements of the marketplaces.
|Field Heading||Field definition|
|EAN||Mandatory for Google Shopping (except for the fashion section or when MPN + Brand are already populated), Amazon, Fnac, Cdiscount, PixPlace, La Redoute, Priceminister (according to section) - 13-figure number.|
|MPN||Mandatory for Google Shopping (except for the fashion section or when EAN + Brand are already populated), optional for the other distributors.|
|ISBN||Mandatory if the products are books.|
|ASIN||Optional (but mandatory for Amazon if EAN, UPC or GTIN missing)|
|UPC||Optional - 12-figure number (but mandatory for Amazon if EAN, ASIN or GTIN missing)|
|GTIN||Optional - 14-figure number (but mandatory for Amazon if EAN, ASIN or UPC missing)|
|Quantité||Mandatory (for parents, indicate the total quantity of children's products)|
This list is not exhaustive and can be amended/replaced accordingly. We advise you to add to it the attributes that you have available to you in your database. This is especially the case for data related to your product variations, which will not be mentioned in the above table.
Your product catalog contains product variations?
You can provide us with a source feed only designed for the marketplaces containing the fields mentioned above. In this case, your variations can be managed as described below.
If your feed contains product variations, each version of a product must have a unique ID and a parent ID. The parent ID must be shared by all of the product variations. It must correspond to the unique ID of one of the variations.
Diesel trousers size 36 ⇒ Unique_ID = 127 / Parent_ID =127
Diesel trousers size 38 ⇒ Unique_ID = 128 / Parent_ID =127
Diesel trousers size 40 ⇒ Unique_ID = 129 / Parent_ID =127
Products that do not have variations must not be linked to a parent ID.
Your feed must also contain the variant attributes in specific fields. If your products vary by size, for example, your feed must contain a Size field with a value for each variant.
If you decide to sell on Amazon, La Redoute or eBay, your feed must contain the “parent product” without any notion of attribute (size, colour) and the “child products”, which are the variant products. The parent product must contain all of the required information except for the variant attributes (size, colour, etc.).
In this case, the parent ID corresponds to the unique ID of the parent product:
Diesel trousers ⇒ Unique_ID = 127 / Parent_ID =127 (parent product)
Diesel trousers size 36 ⇒ Unique_ID = 128 / Parent_ID =127 (children's product)
Diesel trousers size 38 ⇒ Unique_ID = 129 / Parent_ID =127 (children's product)
Diesel trousers size 40 ⇒ Unique_ID = 130 / Parent_ID =127 (children's product)
Products without variations must not be linked to a parent ID.
Diesel Love broach ⇒ Unique_ID = 131 / Parent_ID =
Diesel Peace broach ⇒ Unique_ID = 132 / Parent_ID =
Types of multiple variations
When there are various types of variations in your source feed (size, colour, size and colour, etc.), your source feed must contain a field named something like “variant_type”, which must be completed for the parent and child lines with the relevant type of variant (the value of the field is unrestricted but must be shared with other variations of the same type).
Specific case of La Redoute and product variation
To be able to publish in variant mode on La Redoute: Your source feed must only contain one size field and one colour field. You will not be able to publish your variations if there are several fields, such as Trouser_size, Shirt_size, etc. All these values must be grouped together in a single field.
3.3.3 Adding product attributes
Your source feed must contain as much information as possible about your products in the specific fields. You will therefore have a solid and full working base which will make it a lot easier to integrate your catalogue in the various marketplaces.
Sample attributes: length, width, number of places, capacity, etc.
You should therefore find the following additional fields for product variations
|Field heading||Field definition|
|Parent ID||Mandatory for variations; leave the field empty if it is not a variant product.|
|Size||Mandatory if the product variant relates to size (1 size per field/variant) - You cannot have several Size fields for La Redoute (e.g.: Trouser_Size, Jumper_Size)|
|Colour||Mandatory if the product variant relates to colour (1 colour per field/variant) - You cannot have several Colour fields for La Redoute (e.g.: Trouser_Colour, Jumper_Colour)|
|Material||Mandatory if the product variant relates to the material; Mandatory for Amazon.|
|Variante_type||Mandatory for Amazon. To be completed in the parent form and child form. Sample values: Size, Colour, SizeColour, etc.|
4. Technical Contact Person
Do you have any questions about creating your source feed?
Don't hesitate to contact our support team