Page Comparison

Anchortoptop

🇩🇪 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>

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

Anchorexampleexample

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

← Order Placement (ORDP)

Anchor

	top
	top

🇩🇪 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

Panel

panelIconId	21a9
panelIcon	:leftwards_arrow_with_hook:
panelIconText	↩️
bgColor	#FFFAE6

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

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"

type="gtin">08710103827681</INTERNATIONAL

>A375-129</SUPPLIER_PID>

<BUYER

<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005"

type="DgProductId">6406561</BUYER

>09783404175109</INTERNATIONAL_PID>

<DESCRIPTION

<BUYER_

SHORT

PID xmlns="http://www.bmecat.org/bmecat/2005"

>Fingerring, Herr der Ringe</DESCRIPTION_SHORT>

>6406567</BUYER_PID>
			</PRODUCT_ID>

	<QUANTITY>2</QUANTITY>
			<DELIVERY_

DATE type="optional">

DATE>
				<DELIVERY_START_

DATE>2022

DATE>2017-

01

06-

13<

21</DELIVERY_START_DATE>
				<DELIVERY_END_

DATE>2022

DATE>2017-

01

06-

13<

21</DELIVERY_END_DATE>
			</DELIVERY_DATE>

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


		</ORDERRESPONSE_ITEM>
	</ORDERRESPONSE_ITEM_LIST>
</ORDERRESPONSE>

Panel

panelIconId	1f504
panelIcon	:arrows_counterclockwise:
panelIconText	🔄
bgColor	#FFFAE6

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

title	Example file

Code Block

language	xml

<ORDERRESPONSE_ITEM> <PRODUCT_ID> <SUPPLIER_PID xmlns

<?xml version="1.0" encoding="utf-8"?>
<ORDERRESPONSE xmlns:xsd="http://www.

bmecat

w3.org

/bmecat/2005" type="supplierProductKey">A-100</SUPPLIER_PID> <INTERNATIONAL_PID xmlns

/2001/XMLSchema" xmlns:xsi="http://www.

bmecat

w3.org/

bmecat/2005" type="gtin">08710103827681</INTERNATIONAL_PID> <BUYER_PID

2001/XMLSchema-instance" xmlns="http://www.

bmecat

opentrans.org/

bmecat

XMLSchema/

2005

2.1"

type

version="

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>

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"

type="supplierProductKey">A-100<

>A375-129</SUPPLIER_PID>
				<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005"

type="gtin">08710103827681<

>09783404175109</INTERNATIONAL_PID>
				<BUYER_PID xmlns="http://www.bmecat.org/bmecat/2005"

type="DgProductId">6406561<

>6406567</BUYER_PID>

</PRODUCT_ID>

	</PRODUCT_ID>
			<QUANTITY>2</QUANTITY>
			<DELIVERY_DATE>
				<DELIVERY_START_

DATE>2022

DATE>2017-

01

06-

20<

21</DELIVERY_START_DATE>
				<DELIVERY_END_

DATE>2022

DATE>2017-

01

06-

20<

21</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

		</ORDERRESPONSE_ITEM>
	</ORDERRESPONSE_ITEM_LIST>
</ORDERRESPONSE>

Panel

panelIconId	1f500
panelIcon	:twisted_rightwards_arrows:
panelIconText	🔀
bgColor	#FFFAE6

Additional: Cancellation

Cancellation via Order Response is optional and disabled by default (function analog to ORDCHG EDIFACT).

If activated:

Quantities not confirmed in the Order Response are cancelled (this always refers to the quantity initially ordered)
Complete positions can be cancelled by confirmation with QUANTITY=0
Positions not included remain in the backorder

Expand

title	Example file

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)

Code Block

language	xml

<?xml version="1.0" encoding="utf-8"?>
<ORDERRESPONSE xmlns:xsd="http://www.

bmecat

w3.org/

bmecat

2001/

2005

XMLSchema"

type="DgProductId">6406982</BUYER_PID> <DESCRIPTION_SHORT

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.

bmecat

opentrans.org/

bmecat

XMLSchema/

2005

2.1"

>Marvel Legends: Elektronischer Helm Iron Man</DESCRIPTION_SHORT> </PRODUCT_ID> <QUANTITY>20</QUANTITY>  <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>

 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"

type="supplierProductKey">B-200</SUPPLIER_PID> <INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005" type="gtin">29783404658122</INTERNATIONAL_PID> <BUYER

>A375-129</SUPPLIER_PID>
				<INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005"

type="DgProductId">6406982</BUYER

>09783404175109</INTERNATIONAL_PID>

</PRODUCT_ID>

<ORDER

<BUYER_

UNIT

PID xmlns="http://www.bmecat.org/bmecat/2005"

>C62<

>6406567</

ORDER

BUYER_

UNIT>

PID>

<DELIVERY

</PRODUCT_

DATE>

ID>

<DELIVERY_START_DATE>2022-01-13</DELIVERY_START

<QUANTITY>7</QUANTITY>
			<DELIVERY_DATE>
				<DELIVERY_

END

START_

DATE>2022

DATE>2017-

01

06-

13<

21</DELIVERY_

END

START_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

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

type="DgProductId">6406783</BUYER

>B475-140</SUPPLIER_PID>

<DESCRIPTION

<INTERNATIONAL_

SHORT

PID xmlns="http://www.bmecat.org/bmecat/2005"

>Spider-Man: No Way Home UHD BluRay</DESCRIPTION_SHORT> </PRODUCT_ID> <QUANTITY>5</QUANTITY>  <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

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

Panel

panelIconId	21a9
panelIcon	:leftwards_arrow_with_hook:
panelIconText	↩️
bgColor	#F4F5F7

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).
Deviations from the arrival data from the Order Placement must be communicated to us (manually in the CMI or automatically via delivery date update).

Expand

title	Example file

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

<?xml version="1.0" encoding="utf-8"?>
<ORDERRESPONSE xmlns:xsd="http://www.

bmecat

w3.org/

bmecat/2005" type="gtin">39783404658423</INTERNATIONAL_PID> <BUYER_PID xmlns

2001/XMLSchema" xmlns:xsi="http://www.

bmecat

w3.org/

bmecat/2005" type="DgProductId">6406783</BUYER_PID> </PRODUCT_ID> <QUANTITY>5</QUANTITY> <ORDER_UNIT

2001/XMLSchema-instance" xmlns="http://www.

bmecat

opentrans.org/

bmecat/2005">C62<

XMLSchema/2.1" version="2.1">
	<ORDERRESPONSE_HEADER>
		<ORDERRESPONSE_INFO>
			<ORDER_ID>9316271</ORDER_

UNIT> <DELIVERY

ID>
			<ORDERRESPONSE_DATE>2017-06-14T15:53:18</ORDERRESPONSE_DATE>

<DELIVERY

<SUPPLIER_

START

ORDER_

DATE><

ID>191919</

DELIVERY

SUPPLIER_

START

ORDER_

DATE>

ID>

<DELIVERY_END_DATE></DELIVERY_END_DATE>

</ORDERRESPONSE_INFO>
	</

DELIVERY

ORDERRESPONSE_

DATE>

HEADER>
</

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.

Documentation

Expand

title	XML Schema Diagram

Image Removed

XML Element

ORDERRESPONSE>

Image Added

XML Element

Status

colour	Blue
title	Minimum

Status

colour	Purple
title	With arrival date

M/C/S

Sample values

Data type [maxLength]

M/C/S

	Description
ORDERRESPONSE		Must	-	-

Must

	See Namespaces regarding the correct usage of namespaces.
. ORDERRESPONSE_HEADER	Must	-	-

Must


. . ORDERRESPONSE_INFO	Must	-	-

Must


. . . ORDER_ID	Must	9316271	dtSTRING[

250

25]

Must

	Galaxus Purchase Order ID
. . . ORDERRESPONSE_DATE	Must	2017-06-14T15:53:18	dtDATETIME

Must

	Order Response timestamp
. . . SUPPLIER_ORDER_ID	Should	191919	dtSTRING[250]

Should

Order ID from your ERP

Important for

Merchants

merchants: The

id

ID will be printed onto our return labels as Code-39-Barcode and must comply with ISO/IEC 16388 norm.

The Supplier

The SUPPLIER_

Order

ORDER_

Id

ID is also displayed on the marketplace sales fee reports.
. ORDERRESPONSE_ITEM_LIST		Should	-	-

Should


. . ORDERRESPONSE_ITEM	Should	-	-

Should


. . . PRODUCT_ID	Must	-	-

Must

If possible do always send all three sub-elements SUPPLIER_PID, INTERNATIONAL_PID und BUYER_PID.

. . . . SUPPLIER_PID

Must

A375-129

dtSTRING[32]

BMEcat NS

Must

Partner product key

. . . . INTERNATIONAL_PID

Should

09783404175109

dtSTRING[14]

BMEcat NS

Should

GTIN-14 with leading zeros

. . . . BUYER_PID

Can

6406567

dtSTRING[50]

BMEcat NS

Should

Galaxus product

ID

key
. . . QUANTITY	Must	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.

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

updae an arrival

trigger 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).

Estimated arrival date, please provide an exact date with the same

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

Should

Same value as

in DELIVERY

DELIVERY_START_DATE

↑ Top

Version	Old Version 2	New Version Current
Changes made by	Digitec Galaxus AG	Digitec Galaxus AG
Saved on	Mar 22, 2022	Nov 19, 2024

Page Comparison

Versions Compared

Key

Order confirmation including arrival dates

Order Confirmation excluding arrival dates

Delivery date update

Documentation