Requirements for your catalog file
In this article, you'll find helpful recommendations for building and generating an optimal product catalog with regards to format, encoding, and expected content.
To learn about the different ways to submit your catalog, see our article .
Your source data can be transmitted as a master catalog for the creation of new products, or as an update to enrich the publications of your poleepo products.
The following information applies to both types of uses.
Supported encoding and formats
Your catalog must be:
In CSV format
UTF-8 encoding
How to save your file as UTF-8 CSV using a spreadsheet?
In Excel: Click "Save As", and select the "CSV UTF-8" format.
In LibreOffice or OpenOffice: Click "Save As", and select the
"CSV Text" format while checking the "Edit filter settings" box.
After saving, you will be able to choose the "Unicode (UTF-8)" character set in the dialog box.
Product catalog content
Advice
Never include special characters (accents, %, /, or other symbols) in field titles.
Do not use spaces or commas in field names or product IDs. - and _ can be used instead.
In case of path to explain your categories:
Do you prefer symbols > or / or | (Example values: Shoes > Men's shoes > sneakers
Otherwise use one column for each category level.
Never change the IDs used as your product upload keys.
Product IDs are used to save customizations made on the platform and are used as an interface to share data with various channels
Never change the field names of your already mapped file
All field labels in your product catalog must be unique. Each header must be unique.
General structure
Here's a non-exhaustive list of fields we recommend having in your Product Catalog. Some fields are required: "id," "title," "price," and "category."
The content and structure are adaptable to your needs.
For each field type, we indicate its definition, the type of expected values with an example, and our recommendations.
SKU | A specific reference number for each product used to uniquely identify it over time within Poleepo. A single product must always have the same identifier. The ID must not be reassigned to another product and must contain a maximum of 25 characters.
Expected value type: Alphanumeric (no spaces or commas)
Expected Value Type: Alphanumeric
Example: 100 Hertz
Recommendation: This field is strongly recommended if it is not filled in Poleepo will create a new unique value. |
Title | Product Title Expected Value Type : Alphanumeric
Example : Samsung 100 Hertz LCD TV
Recommendation : Required to create a product |
Description | Product Description
Expected Value Type : Alphanumeric
Example : Samsung 100 Hertz LCD TV, 47 inches, etc.
Recommendation : Highly recommended for creating or updating your catalog |
Selling price | Product selling price
You can map the value with or without VAT. It corresponds to the standard selling price of
NB a column with the VAT value is also required, if it is not present in the file you
Expected value type for price : Numeric without other symbols, decimal separated by period or comma
Expected value type for vat : Numeric with no other symbols
Example : 799.90
Recommendation: Required to create a product |
Discounted price | If the price has been reduced (promotion, sale, etc.), indicate the new discounted price in this field, indicating in the mapping whether it is without or with VAT.
Expected value type : Numeric, decimal point or comma delimiter
Example : 900.99
Recommendation : This field is highly recommended if you need to update promotions. |
Main IMAGE or 2, 3, 4 and following | Corresponds to the URL of the product image on your site. All formats are accepted, however, some channels have restrictions and do not accept all formats.
Example: http://mysite.com/product_image.jpg
Recommendation: Highly recommended |
EAN | This field consists of 13 digits and corresponds to the barcode commonly used for consumer goods in Europe. It uniquely identifies the product and allows for better indexing of your product in our product categories. It is the European Article Number.
Expected Value Type : Numeric
Example : 1234567891011
Recommendation : This field is required for all Marketplace channels. |
Parent SKU | A common identifier for all variants of a product
Expected Value Type : Alphanumeric
Example : 1235RES56
Recommendation : This field is required to manage product variations. |
Variant Attribute: Size / Color / Material, etc. | These are declination values that characterize the product.
Corresponds to the size of the product (S, XL, XXL 37, 38, 41, 42, ...), or its color (red, white, blue,)
Favor one field per declension type to avoid mixing the displayed characteristics.
Expected Value Type : Alphanumeric / Text
Recommendation : This field is required to display your products with variants. |
Brand | Corresponds to the brand of the product or the name of the manufacturer of the product.
Expected Value Type : Alphanumeric
Example : SAMSUNG
Recommendation: Required to integrate your catalog into many marketplaces. |
Quantity in Stock | Corresponds to the number of products currently in stock
NB In this phase Poleepo will ask you to specify the behavior of the field in configuration: indicating whether the Poleepo action will have to REPLACE, ADD or SUBTRACTE the numeric value in the file with respect to the present number (if other
Expected Value Type : Numeric
Example : 23
Recommendation : This field is highly recommended to integrate your catalog with the Poleepo platform |
MPN | Another optional identifier, it can be an alphanumeric value. |
CSV format
UTF8 encoding:
with or without "
Optimal text delimiters are ; | or tab