Reference
- Data flow: from ERP to LNB
- Data types: order
- File naming: see orders in the flat files automation instructions
File processing rules
Orders and their order lines (the ordered product and quantity details) are sent along within one CSV file. Each row of the file carries a combination of an order (identified by its order reference), a product (identified by its model), a variant and a size. An orders CSV file can therefore contains the same order on multiple rows with a distinct product/variant/size on each row.
An orders CSV file can contains multiple orders. The order reference column is used as an order identifier, so please make sure to use a unique order reference across all customers: 100001-FW19 seems a valid order reference, FW19 does not seem valid as it is will probably be used for other customers.
File schema / Main fields (see full schema in file template)
Field | Description | Type | Required |
Order reference |
The order ref. (order identifier)
|
string | ✓ |
Retailer reference
|
The retailer ref. (retailer identifier) | string | ✓ |
Buyer email
|
The buyer email (buyer identifier) | string | ✓ |
Assigned collection
|
The collection code / sales catalog code (restrict products to this collection / sales catalog)
|
string | |
Price catalog
|
The price catalog name (price catalog identifier)
|
string | |
Model | The ordered product model (product identifier) | string | |
Color | The ordered fabric name (variant identifier) | string | |
Size | The ordered size label (size identifier) | string | ✓ |
EAN13 | The ordered EAN1.
Mandatory if model/color/size not set.
|
||
Quantity | The ordered quantity | integer | ✓ |
Unit price | The unit price or fetched from the price catalog if not set | number |
Comments
0 comments
Please sign in to leave a comment.