Page Comparison

Anchor

	top
	top

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

Main functions

Order confirmation: Confirmation of receipt of the Order Placement. Acknowledgement should be automatic and immediate whenever possible. This is important so that we know that you have received the order. If you have a manual check first, the ORDR should be sent no later than 24 hours after receipt of the order.
Transmission of your own order reference (<SUPPLIER_ORDER_ID>) in the order confirmation, which we use for queries and is printed on the marketplace payment summary for traders and on the labels and accompanying documents for returns.
Delivery date update: Update of the estimated arrival date per item and piece.
Attention we expect the estimated arrival date at the consignee and not the dispatch date of the goods at your premises. The arrival date reported to us is communicated by us directly to the end customer and should therefore be as accurate as possible. In no case may the date be automatically postponed again and again.
Delivery date update: Update of the estimated arrival date per item and piece.
Note that we expect the estimated arrival date at the consignee and not the dispatch date of the goods at your premises. The arrival date reported to us is communicated directly to the end customer and should therefore be as accurate as possible. In no case may the date be automatically and repeatedly postponed.

Order confirmation including arrival dates

If estimated arrival dates are available at the time of order confirmation, they should be transmitted in the order response.

Expand

title	Example file

Code Block

language	xml

<?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>

Example with different arrival dates per item

Initial situation: A usual delivery time of 2 working days and a restock date one week after the order date 11.01.2022 is assumed. The order is received on time on 11.01.2022 so that the goods leave your warehouse on the same day.

Expand

title	Expand for example

Today on 11.01.2022 are ordered in time	Current availability with you (available will be delivered today)	Reported arrival date within DELIVERY_END_DATE
Position 1 - 100 pieces of product A	50 pieces of product A available from stock	50 pieces of product A → date = dispatch date (today) + usual delivery time = 2022-01-13
	40 pieces of product A are expected at your premises in 7 working days	40 pieces of product A → date = restock date (in one week) + usual delivery time = 2022-01-20
	10 pieces of product A have to be ordered first	10 pieces of product A → date = leave blank, as unknown
Position 2 - 20 pieces of product B	20 pieces of product B available from stock	20 pieces of product B → date = dispatch date (today) + usual delivery time = 2022-01-13
Position 3 - 5 pieces of product C	5 pieces of product C no longer available (End of life = EOL)*.	5 pieces of product C → date = leave blank as unknown or omit item completely

*= as the product C is EOL, the item must be cancelled either via a

Supplier cancellation notification (EOLN) or manually with us in the CMI.

See also XMLs for #example with different arrival dates per piece below.

Order Confirmation excluding arrival dates

If no arrival data can be exported at the time of the order confirmation, an order response without positions can be transmitted (see example file below).

Deviations from the arrival dates from the Order Placement must be communicated to us (manually via CMI or automatically via delivery date update).

Expand

title	Example file

Code Block

language	xml

<?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_LIST>
</ORDERRESPONSE>

Delivery date update

If the delivery date (or the estimated arrival date) of a backlog changes, it can be communicated to us in another ORDR in order to avoid manual processing in the 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.

Preferred implementation

The ORDR is only sent in case of delivery date changes and only contains the open (undelivered) items.

Expand

title	Example file

Code Block

language	xml

<?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>

Alternative implementation

If the above implementation is not possible, i.e. if all items (including those already delivered) are always transmitted, the order items must be split. In addition, the open positions of an item (with delivery date in the future) must be transmitted first before the already delivered items (with delivery date in the past) are transmitted.

Expand

title	Example file

Code Block

language	xml

<!-- This is just a snippet for the alternative described above --> 
<!-- Header -->
<!-- Open Items -->
<ORDERRESPONSE_ITEM>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005">AC3829/10</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005">8710103827689</INTERNATIONAL_PID>
	</PRODUCT_ID>
	<QUANTITY>2</QUANTITY>
	<ORDER_UNIT xmlns="http://www.bmecat.org/bmecat/2005">C62</ORDER_UNIT>
	<DELIVERY_DATE>
		<DELIVERY_START_DATE>2020-07-06</DELIVERY_START_DATE>
		<DELIVERY_END_DATE>2020-07-06</DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDERRESPONSE_ITEM>
<!-- Bereits gelieferte Position -->
<ORDERRESPONSE_ITEM>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005">AC3829/10</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005">8710103827689</INTERNATIONAL_PID>
	</PRODUCT_ID>
	<QUANTITY>10</QUANTITY>
	<ORDER_UNIT xmlns="http://www.bmecat.org/bmecat/2005">C62</ORDER_UNIT>
	<DELIVERY_DATE>
		<DELIVERY_START_DATE>2020-05-28</DELIVERY_START_DATE>
		<DELIVERY_END_DATE>2020-05-28</DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDERRESPONSE_ITEM>
<!-- Footer -->

Anchor

	example
	example

XMLs for example with different arrival dates per item

Initial situation: A usual delivery time of 2 working days and a restock date one week after the order date 11.01.2022 is assumed. The order is received on time on 11.01.2022 so that the goods leave your warehouse on the same day.

Expand

title	Expand XMLs to example case

Order (ORDP) and reported arrival date within DELIVERY_END_DATE in the order response (ORDR)
if ordered in time today 11.01.2022

Position 1 - 100 pieces of product A

Code Block

language	xml

<ORDER_ITEM>
	<LINE_ITEM_ID>1</LINE_ITEM_ID>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="supplierProductKey">A-100</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">08710103827681</INTERNATIONAL_PID>
		<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="DgProductId">6406561</BUYER_PID>
		<DESCRIPTION_SHORT xmlns="http://www.bmecat.org/bmecat/2005">Fingerring, Herr der Ringe</DESCRIPTION_SHORT>
	</PRODUCT_ID>
	<QUANTITY>100</QUANTITY>
	<!-- other Elements -->
	<DELIVERY_DATE type="optional">
		<DELIVERY_START_DATE>2022-01-13</DELIVERY_START_DATE>
		<DELIVERY_END_DATE>2022-01-13</DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDER_ITEM>

50 pieces of product A → date = dispatch date (today) + usual delivery time = 2022-01-13

Code Block

language	xml

<ORDERRESPONSE_ITEM>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="supplierProductKey">A-100</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">08710103827681</INTERNATIONAL_PID>
		<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="DgProductId">6406561</BUYER_PID>
	</PRODUCT_ID>
	<QUANTITY>50</QUANTITY>
	<ORDER_UNIT xmlns="http://www.bmecat.org/bmecat/2005">C62</ORDER_UNIT>
	<DELIVERY_DATE>
		<DELIVERY_START_DATE>2022-01-13</DELIVERY_START_DATE>
		<DELIVERY_END_DATE>2022-01-13</DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDERRESPONSE_ITEM>

40 pieces of product A → date = restock date (in one week) + usual delivery time = 2022-01-20

Code Block

language	xml

<ORDERRESPONSE_ITEM>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="supplierProductKey">A-100</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">08710103827681</INTERNATIONAL_PID>
		<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="DgProductId">6406561</BUYER_PID>
	</PRODUCT_ID>
	<QUANTITY>40</QUANTITY>
	<ORDER_UNIT xmlns="http://www.bmecat.org/bmecat/2005">C62</ORDER_UNIT>
	<DELIVERY_DATE>
		<DELIVERY_START_DATE>2022-01-20</DELIVERY_START_DATE>
		<DELIVERY_END_DATE>2022-01-20</DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDERRESPONSE_ITEM>

10 pieces of product A → date = leave blank, as unknown

Code Block

language	xml

<ORDERRESPONSE_ITEM>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="supplierProductKey">A-100</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">08710103827681</INTERNATIONAL_PID>
		<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="DgProductId">6406561</BUYER_PID>
	</PRODUCT_ID>
	<QUANTITY>10</QUANTITY>
	<ORDER_UNIT xmlns="http://www.bmecat.org/bmecat/2005">C62</ORDER_UNIT>
	<DELIVERY_DATE>
		<DELIVERY_START_DATE></DELIVERY_START_DATE>
		<DELIVERY_END_DATE></DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDERRESPONSE_ITEM>

Position 2 - 20 pieces of product B

Code Block

language	xml

<ORDER_ITEM>
	<LINE_ITEM_ID>2</LINE_ITEM_ID>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="supplierProductKey">B-200</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">29783404658122</INTERNATIONAL_PID>
		<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="DgProductId">6406982</BUYER_PID>
		<DESCRIPTION_SHORT xmlns="http://www.bmecat.org/bmecat/2005">Marvel Legends: Elektronischer Helm Iron Man</DESCRIPTION_SHORT>
	</PRODUCT_ID>
	<QUANTITY>20</QUANTITY>
	<!-- other Elements -->
	<DELIVERY_DATE type="optional">
		<DELIVERY_START_DATE>2022-01-13</DELIVERY_START_DATE>
		<DELIVERY_END_DATE>2022-01-13</DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDER_ITEM>

20 pieces of product B → date = dispatch date (today) + usual delivery time = 2022-01-13

Code Block

language	xml

<ORDERRESPONSE_ITEM>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="supplierProductKey">B-200</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">29783404658122</INTERNATIONAL_PID>
		<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="DgProductId">6406982</BUYER_PID>
	</PRODUCT_ID>
	<QUANTITY>20</QUANTITY>
	<ORDER_UNIT xmlns="http://www.bmecat.org/bmecat/2005">C62</ORDER_UNIT>
	<DELIVERY_DATE>
		<DELIVERY_START_DATE>2022-01-13</DELIVERY_START_DATE>
		<DELIVERY_END_DATE>2022-01-13</DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDERRESPONSE_ITEM>

Position 3 - 5 pieces of product C

Code Block

language	xml

<ORDER_ITEM>
	<LINE_ITEM_ID>3</LINE_ITEM_ID>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="supplierProductKey">C-300</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">39783404658423</INTERNATIONAL_PID>
		<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="DgProductId">6406783</BUYER_PID>
		<DESCRIPTION_SHORT xmlns="http://www.bmecat.org/bmecat/2005">Spider-Man: No Way Home UHD BluRay</DESCRIPTION_SHORT>
	</PRODUCT_ID>
	<QUANTITY>5</QUANTITY>
	<!-- other Elements -->
	<DELIVERY_DATE type="optional">
		<DELIVERY_START_DATE>2022-01-13</DELIVERY_START_DATE>
		<DELIVERY_END_DATE>2022-01-13</DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDER_ITEM>

5 pieces of product C → date = leave blank as unknown or omit item completely

Code Block

language	xml

<ORDERRESPONSE_ITEM>
	<PRODUCT_ID>
		<SUPPLIER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="supplierProductKey">C-300</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">39783404658423</INTERNATIONAL_PID>
		<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005" type="DgProductId">6406783</BUYER_PID>
	</PRODUCT_ID>
	<QUANTITY>5</QUANTITY>
	<ORDER_UNIT xmlns="http://www.bmecat.org/bmecat/2005">C62</ORDER_UNIT>
	<DELIVERY_DATE>
		<DELIVERY_START_DATE></DELIVERY_START_DATE>
		<DELIVERY_END_DATE></DELIVERY_END_DATE>
	</DELIVERY_DATE>
</ORDERRESPONSE_ITEM>

*= as the product C is EOL, the item must be cancelled either via a

Supplier cancellation notification (EOLN) or manually with us in the CMI.

This element must be specified, even if no positions (ORERRESPONSE_ITEMs) are transmitted in it.

XML Element	Sample values	Data type [maxLength]	M/C/S	Description
ORDERRESPONSE	-	-	Must	See Namespaces regarding the correct usage of namespaces.
ORDERRESPONSE_HEADER	-	-	Must
ORDERRESPONSE_INFO	-	-	Must
ORDER_ID	9316271	dtSTRING[250]	Must	Galaxus Purchase Order ID
ORDERRESPONSE_DATE	2017-06-14T15:53:18	dtDATETIME	Must	Order Response timestamp
SUPPLIER_ORDER_ID	191919	dtSTRING[250]	Should	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	-	-	Must	Should
ORDERRESPONSE_ITEM	-	-	Should
PRODUCT_ID	-	-	Must	If possible do always send all three sub-elements SUPPLIER_PID, INTERNATIONAL_PID und BUYER_PID.
SUPPLIER_PID	A375-129	dtSTRING[32] BMEcat NS	Must	Partner product key
INTERNATIONAL_PID	09783404175109	dtSTRING[14] BMEcat NS	Should	GTIN-14 with leading zeros
BUYER_PID	6406567	dtSTRING[50] BMEcat NS	Should	Galaxus product ID
QUANTITY	2	dtNUMBER	Must	Quantity as integer Must be > 0, otherwise leads to import error A quantity > 1 can be split into two ORDERRESPONSE_ITEMs with different arrival dates.
DELIVERY_DATE	-	-	Should	Arrival date at goods recipient. If you can not send this date, it is possible to send an empty ORDERRESPONSE_ITEM_LIST. If you do not send a DELIVERY_DATE, the positions is updated with an unknown date. A date in the past does not updae an arrival date
DELIVERY_START_DATE	2017-06-21	dtDATETIME	Should	Estimated arrival date If you can provide an exact date where DELIVERY_START_DATE = DELIVERY_END_DATE Also compare this date with the requested DELIVERY_DATE in our order with the different type attributes (optional and fixed).
DELIVERY_END_DATE	2017-06-21	dtDATETIME	Should	Estimated arrival date, please provide an exact date with the same value as in DELIVERY_START_DATE

↑ Top

Version	Old Version 1	New Version 2
Changes made by	Digitec Galaxus AG	Digitec Galaxus AG
Saved on	Feb 03, 2022	Mar 22, 2022

Versions Compared

Key

Order confirmation including arrival dates

Order Confirmation excluding arrival dates

Delivery date update

Documentation