Existing customer? log in now
You have the option of transferring your products to our system in several different file formats. We currently support the CSV, XLSX, XLS and XML formats. Please use the field and column names explained below in all formats.
You will find a sample file with product data for each of your customers or under the following links:
| Field name | Data type | Description |
|---|---|---|
| ordernumber* | character string (100) | article number of the product |
| brand | character string (255) | manufacturer |
| brand_ordernumber* | character string (255) | manufacturer article number |
| customer_ordernumber | character string (255) | customer article number |
| title* | character string (255) | name of the product |
| category* | Character string (255) | Category of the product |
| 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 | character string | graduated prices for this product (see below) |
| purchase_steps | Integer | Graduated price of the product (see below) |
| min_purchase | Integer | Minimum purchase quantity (see below) |
| max_purchase | Integer | Maximum purchase quantity (see below) |
| currency | character string(3) | ISO4217 currency abbreviation |
| tax_rate* | Integer | Valid tax rate for this product (e.g. 7 or 19) |
| purchase_unit | floating point number | sales quantity |
| reference_unit1 | Floating point number | Reference quantity for base price calculation |
| unit2 | character string (255) | sales unit (e.g. ml) |
| unit_name3 | character string (255) | sales unit (e.g. millilitre) |
| packaging_unit* | character string (255) | sales unit (e.g. piece) |
| weight | floating point number | weight in kilograms without further specification |
| shipping_time* | integer | delivery time in days |
| classification_type | character string (255) | classification system e.g. UNSPSC or eClass (note spelling) |
| classification | character string (255) | value in classification system e.g. 43232403 for "Enterprise application integration software" |
| custom_field1 | Character string (255) | Any additional field |
| custom_field2 | Character string (255) | Any additional field |
| custom_field3 | Character string (255) | Any additional field |
| custom_field4 | Character string (255) | Any additional field |
| custom_field5 | Character string (255) | Any additional field |
| custom_field6 | Character string (255) | Any additional field |
| custom_field7 | Character string (255) | Any additional field |
| custom_field8 | Character string (255) | Any additional field |
| custom_field9 | Character string (255) | Any additional field |
| custom_field10 | Character 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 passed, the first value passed must be less than or equal to the min_purchase field.
<from validity>:<net price>;<from validity>:<net price>
Example:
1:10,99;10:9,99;50:8,00Staggering
The purchase_steps field is pre-assigned 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 for labelling items. You can call up a complete list of units under the following link:
https://unece.org/fileadmin/DAM/cefact/recommendations/rec20/rec20_rev3_Annex3e.pdf
A path of categories can be specified as a category. The individual category names must be separated from each other by a "|". The path is interpreted as nesting from left to right.
Example:
Living|Kitchen|Electrical appliancesbecomes
