Order Response ORDR

Zur Anleitung in Deutsch wechseln / Dispatch Notification (DELR) →

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:
1. We expect the arrival date at the recipient of the goods and not the shipment date
2. The date reported to us is communicated directly to the end customer and should therefore be as accurate as possible
3. The date must not be automatically pushed back again and again in any case

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.

<?xml version="1.0" encoding="utf-8"?>
<ORDERRESPONSE xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.opentrans.org/XMLSchema/2.1" version="2.1">
	<ORDERRESPONSE_HEADER>
		<ORDERRESPONSE_INFO>
			<ORDER_ID>9316271</ORDER_ID>
			<ORDERRESPONSE_DATE>2017-06-14T15:53:18</ORDERRESPONSE_DATE>
			<SUPPLIER_ORDER_ID>191919</SUPPLIER_ORDER_ID>
		</ORDERRESPONSE_INFO>
	</ORDERRESPONSE_HEADER>
	<ORDERRESPONSE_ITEM_LIST>
		<ORDERRESPONSE_ITEM>
			<PRODUCT_ID>
				<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005">A375-129</SUPPLIER_PID>
				<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005">09783404175109</INTERNATIONAL_PID>
				<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005">6406567</BUYER_PID>
			</PRODUCT_ID>
			<QUANTITY>2</QUANTITY>
			<DELIVERY_DATE>
				<DELIVERY_START_DATE>2017-06-21</DELIVERY_START_DATE>
				<DELIVERY_END_DATE>2017-06-21</DELIVERY_END_DATE>
			</DELIVERY_DATE>
		</ORDERRESPONSE_ITEM>
	</ORDERRESPONSE_ITEM_LIST>
</ORDERRESPONSE>

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.

<?xml version="1.0" encoding="utf-8"?>
<ORDERRESPONSE xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.opentrans.org/XMLSchema/2.1" version="2.1">
	<ORDERRESPONSE_HEADER>
		<ORDERRESPONSE_INFO>
			<ORDER_ID>9316271</ORDER_ID>
			<ORDERRESPONSE_DATE>2017-06-14T15:53:18</ORDERRESPONSE_DATE>
			<SUPPLIER_ORDER_ID>191919</SUPPLIER_ORDER_ID>
		</ORDERRESPONSE_INFO>
	</ORDERRESPONSE_HEADER>
	<ORDERRESPONSE_ITEM_LIST>
		<ORDERRESPONSE_ITEM>
			<PRODUCT_ID>
				<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005">A375-129</SUPPLIER_PID>
				<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005">09783404175109</INTERNATIONAL_PID>
				<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005">6406567</BUYER_PID>
			</PRODUCT_ID>
			<QUANTITY>2</QUANTITY>
			<DELIVERY_DATE>
				<DELIVERY_START_DATE>2017-06-21</DELIVERY_START_DATE>
				<DELIVERY_END_DATE>2017-06-21</DELIVERY_END_DATE>
			</DELIVERY_DATE>
		</ORDERRESPONSE_ITEM>
	</ORDERRESPONSE_ITEM_LIST>
</ORDERRESPONSE>

Use cases:

Ordered ORDP: Product xy quantity 12
Confirmed ORDR: Product xy quantity 9
--> 3 of product xy were cancelled (9 open backorder)
Ordered ORDP: Product xy quantity 10
Confirmed ORDR: Product xy quantity 0
--> Of product xy all [10] were cancelled (no [0] open backorder)
Ordered ORDP: ORDP: Product xy quantity 5
Confirmed ORDR: Item for product xy is not included in the Order Response
--> None [0] of product xy was cancelled (all [5] open backorder)

<?xml version="1.0" encoding="utf-8"?>
<ORDERRESPONSE xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.opentrans.org/XMLSchema/2.1" version="2.1">
	<ORDERRESPONSE_HEADER>
		<ORDERRESPONSE_INFO>
			<ORDER_ID>9316271</ORDER_ID>
			<ORDERRESPONSE_DATE>2017-06-14T15:53:18</ORDERRESPONSE_DATE>
			<SUPPLIER_ORDER_ID>191919</SUPPLIER_ORDER_ID>
		</ORDERRESPONSE_INFO>
	</ORDERRESPONSE_HEADER>
	<ORDERRESPONSE_ITEM_LIST>
		<ORDERRESPONSE_ITEM>
			<PRODUCT_ID>
				<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005">A375-129</SUPPLIER_PID>
				<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005">09783404175109</INTERNATIONAL_PID>
				<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005">6406567</BUYER_PID>
			</PRODUCT_ID>
			<QUANTITY>7</QUANTITY>
			<DELIVERY_DATE>
				<DELIVERY_START_DATE>2017-06-21</DELIVERY_START_DATE>
				<DELIVERY_END_DATE>2017-06-21</DELIVERY_END_DATE>
			</DELIVERY_DATE>
		</ORDERRESPONSE_ITEM>
		<ORDERRESPONSE_ITEM>
			<PRODUCT_ID>
				<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005">B475-140</SUPPLIER_PID>
				<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005">18683404175109</INTERNATIONAL_PID>
				<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005">5506561</BUYER_PID>
			</PRODUCT_ID>
			<QUANTITY>0</QUANTITY>
		</ORDERRESPONSE_ITEM>
	</ORDERRESPONSE_ITEM_LIST>
</ORDERRESPONSE>

XML tree view

XML Element Minimum With arrival date		M/C/S	Sample values	Data type [maxLength]	Description

XML Element Minimum With arrival date	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. The SUPPLIER_ORDER_ID is also displayed on the marketplace sales fee reports.
. 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: If the arrival date cannot be met, we require an update of the date via Order Response or CMI If this date can not be sent, the ORDERRESPONSE_ITEM_LIST must be omitted completely
. . . . DELIVERY_START_DATE	Should	2017-06-21	dtDATETIME	Estimated arrival date: If the arrival date is unknown, the segment must be left blank or should be sent without see "Minimum: Order confirmation WITHOUT arrival date" «unknown» or «fake» delivery dates are not allowed A date in the past does not trigger date updates missing DELIVERY_DATE element or no value sets the availability to unknown For orders with DELIVERY_DATE type="fixed" this must be confirmed
. . . . DELIVERY_END_DATE	Should	2017-06-21	dtDATETIME	Same value as DELIVERY_START_DATE

↑ Top