You have the option of uploading your products to our system in several different file formats. We currently support the CSV, XLSX and XML formats. Please use the field or column names explained below in all formats.
You can find a sample file containing product data in your customer account or via the links below:
| Field name | Data type | Description |
|---|---|---|
| ordernumber* | String (100) | Product item number |
| brand | String (255) | Manufacturer |
| brand_ordernumber* | String (255) | Manufacturer’s item number |
| customer_ordernumber | String (255) | Customer’s item number |
| title* | String (255) | Product name |
| category* | String (255) | Product category |
| description* | Text | Short description of the product as unformatted text |
| description_long | Text | Long description of the product; can be formatted using HTML |
| image_url | String (255) | HTTPS address of the image to be displayed for this product |
| price* | Floating-point number | Net price of the product |
| graduated_prices | String | Graduated prices for this product (see below) |
| purchase_steps | Integer | Product tiering (see below) |
| min_purchase | Integer | Minimum purchase quantity (see below) |
| max_purchase | Integer | Maximum purchase quantity (see below) |
| currency | String(3) | ISO 4217 currency code |
| tax_rate* | Integer | Applicable tax rate for this product (e.g. 7 or 19) |
| purchase_unit | Floating-point number | Sales unit |
| reference_unit1 | Floating-point number | Reference quantity for base price calculation |
| unit2 | String (255) | Sales unit of measure (e.g. ml) |
| unit_name3 | String (255) | Sales unit of measure (e.g. millilitres) |
| packaging_unit* | String (255) | Sales unit (e.g. pieces) |
| weight | Floating-point number | Weight in kilograms, no further details |
| shipping_time* | Integer | Delivery time in days |
| classification_type | String (255) | Classification system, e.g. UNSPSC or eClass (note the spelling) |
| classification | String (255) | Value in the classification system, e.g. 43232403 for ‘Enterprise application integration software’ |
| custom_field1 | String (255) | Any additional field |
| custom_field2 | String (255) | Any additional field |
| custom_field3 | String (255) | Any additional field |
| custom_field4 | String (255) | Any additional field |
| custom_field5 | String (255) | Any additional field |
| custom_field6 | String (255) | Any additional field |
| custom_field7 | String (255) | Any additional field |
| custom_field8 | String (255) | Any additional field |
| custom_field9 | String (255) | Any additional field |
| custom_field10 | String (255) | Any additional field |
| active* | Boolean value (0/1) | Display of the product in the catalogue |
* This field is mandatory.
1 This field is required if the ‘purchase_unit’ field has been specified.
2 This field is required if the reference_unit field has been specified.
3 This field is required if the unit field has been specified.
Graduated prices must be specified in the graduated_prices field according to the following scheme. If min_purchase is provided, the first value provided must be less than or equal to the value in the min_purchase field.
<from validity>:<net price>;<from validity>:<net price>Example:
1:10.99;10:9.99;50:8.00
Tiered pricing
The purchase_steps field is set to the value 1 by default. The value of the min_purchase field must be equal to purchase_steps or a multiple of purchase_steps. The value of the max_purchase field must be greater than min_purchase and a multiple of purchase_steps.
We recommend using UN/CEFACT units when marking up items. A complete list of units can be found at the following link:
https://unece.org/fileadmin/DAM/cefact/recommendations/rec20/rec20_rev3_Annex3e.pdf
A category can be specified as a path of categories. The individual category names must be separated by a "|". The path is interpreted from left to right as a nested structure.
Example:
Home|Kitchen|Appliances becomes
