Anchor | ||||
---|---|---|---|---|
|
Main functions
Order confirmation: Confirmation of the receipt of the order and the estimated arrival date per item
Delivery date update: Update of the estimated arrival date per item:
We expect the arrival date at the recipient of the goods and not the shipment date
The date reported to us is communicated directly to the end customer and should therefore be as accurate as possible
The date must not be automatically pushed back again and again in any case
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Order confirmation WITH arrival dates If estimated arrival dates are available at the time of order confirmation, they should be transmitted in the order response. |
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Additional: Delivery date update If the delivery date (or estimated arrival date) of a backorder changes, this can be communicated to us in another ORDR, eliminating the need for manual updating in CMI. Any number of ORDRs can be sent to us per order. Each additional ORDR updates the arrival date of the items in the backlog. 💡 If the backorder delivery for marketplace/direct delivery orders takes longer than 30 days, the order item must be canceled. |
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Additional: Cancellation Cancellation via Order Response is optional and disabled by default (function analog to ORDCHG EDIFACT). If activated:
|
Expand | |||||
---|---|---|---|---|---|
| |||||
Use cases:
|
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Minimum: Order confirmation WITHOUT arrival date If no arrival data can be exported, an order response without positions can be transmitted (see example file below). |
Expand | |||||
---|---|---|---|---|---|
| |||||
|
XML Element | M/C/S | Sample values | Data type [maxLength] | Description |
---|---|---|---|---|
ORDERRESPONSE | Must | - | - | See Namespaces regarding the correct usage of namespaces. |
. ORDERRESPONSE_HEADER | Must | - | - | |
. . ORDERRESPONSE_INFO | Must | - | - | |
. . . ORDER_ID | Must | 9316271 | dtSTRING[25] | Galaxus Purchase Order ID |
. . . ORDERRESPONSE_DATE | Must | 2017-06-14T15:53:18 | dtDATETIME | Order Response timestamp |
. . . SUPPLIER_ORDER_ID | Should | 191919 | dtSTRING[250] | Order ID from your ERP Important for merchants: The ID will be printed onto our return labels as Code-39-Barcode and must comply with ISO/IEC 16388 norm. |
. ORDERRESPONSE_ITEM_LIST | Should | - | - | |
. . ORDERRESPONSE_ITEM | Should | - | - |
|
. . . PRODUCT_ID | Must | - | - | |
. . . . SUPPLIER_PID | Must | A375-129 | dtSTRING[32] BMEcat NS | Partner product key |
. . . . INTERNATIONAL_PID | Should | 09783404175109 | dtSTRING[14] BMEcat NS | GTIN-14 with leading zeros |
. . . . BUYER_PID | Can | 6406567 | dtSTRING[50] BMEcat NS | Galaxus product key |
. . . QUANTITY | Must | 2 | dtNUMBER | Quantity as integer > 0 |
. . . DELIVERY_DATE | Should | - | - | Date of arrival at the recipient of the goods:
|
. . . . DELIVERY_START_DATE | Should | 2017-06-21 | dtDATETIME | Estimated arrival date:
|
. . . . DELIVERY_END_DATE | Should | 2017-06-21 | dtDATETIME | Same value as DELIVERY_START_DATE |