You have the option of transferring your products to our system in several different file formats. We currently support CSV, XLSX, XLS and XML formats. In all formats, please use the field and column names explained below.
A sample file with product data can be found on each of your customers or under these links:
| field label |
data type |
Description |
| ordernumber* |
String(100) |
Article number of the product |
| fire |
String (255) |
manufacturer |
| brand_ordernumber* |
String (255) |
Manufacturer article number |
| customer_ordernumber |
String (255) |
Customer article number |
| title* |
String (255) |
Product name |
| category* |
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 |
String |
Graduated prices for this product (see below) |
| purchase_steps |
integer |
Graduation of the product (see below) |
| min_purchase |
integer |
Minimum order quantity (see below) |
| max_purchase |
integer |
Maximum purchase quantity (see below) |
|
String(3) |
ISO4217 Currency Code |
| 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 basic price calculation |
| unit2 |
String (255) |
Sales unit (e.g. ml) |
| unit_name3 |
String (255) |
Sales unit (e.g. milliliter) |
| packaging_unit* |
String (255) |
Sales unit (e.g. piece) |
| weight |
Floating point number |
Weight in kilograms without further details |
| shipping_time* |
Integer |
Delivery time in days |
| classification_type |
character string (255) |
classification system e.g. UNSPSC or eClass (note spelling) |
| classification |
String (255) |
Value in 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 (0/1) |
Presentation of the product in the catalog |
* This field is required.
1 This field is required if the purchase_unit field is specified.
2 This field is required if the reference_unit field is specified.
3 This field is required if the unit field is specified.
Graduated prices
Graduated prices must be specified in the graduated_prices field according to the following scheme. Where 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.00
Graduation
The field purchase_steps is preset with the value 1 by default. The value of the min_purchase field must be equal to 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.
Units of Measure
We recommend using UN/CEFACT units for labeling items. A full list of units can be found at the link below:
https://unece.org/fileadmin/DAM/cefact/recommendations/rec20/rec20_rev3_Annex3e.pdf
Category
A path of categories can be specified as a category. The individual category names must be separated by a "|" be separated from each other. The path is interpreted as nesting from left to right.
Example:
Living|Kitchen|Electronics
becomes
