Versions Compared

Version Old Version 4 New Version 5
Changes made by

Digitec Galaxus AG

Digitec Galaxus AG

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

← Order Placement (ORDP)

Anchor
top
top

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

Main functions

  1. Order confirmation: Confirmation of the 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.

  • 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.  
    (warning) Attention we expect the estimated arrival date at the consignee and not the dispatch date of the goods at your premises. The arrival

    1. order and the estimated arrival date per item

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

    by us directly

      1. directly to the end customer and should therefore be as accurate as possible

    . In no case may the date

      2. The date must not be automatically

    postponed

      1. pushed back again and again

    .

  • Delivery date update: Update of the estimated arrival date per item and piece.
    (warning) 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.

    • Panel
    panelIconId21a9
    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
    titleExample file
    Code Block
    languagexml
    <?xml version="1.0" encoding="utf-8"?> <ORDERRESPONSE xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http

      1. in any case

    Panel
    panelIconId21a9
    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
    titleExample file
    Code Block
    languagexml
    <?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
    titleExpand 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.

    Panel
    panelIconId21a9
    panelIcon:leftwards_arrow_with_hook:
    panelIconText↩️
    bgColor#FFFAE6

    Order confirmation WITHOUT 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
    titleExample file
    Code Block
    languagexml
    <?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>
    Panel
    panelIconId1f504
    panelIcon:arrows_counterclockwise:
    panelIconText🔄
    bgColor#FFFAE6

    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
    titleExample file
    Code Block
    languagexml
    <?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
    titleExample file
    Code Block
    languagexml
    <!-- 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>
	<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>
	<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 -->
    Info

    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
    titleExpand 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
    languagexml
    <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
    languagexml
    <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
    languagexml
    <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
    languagexml
    <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
    languagexml
    <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
    languagexml
    <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
    languagexml
    <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
     Panel
    panelIconId1f504
    panelIcon:arrows_counterclockwise:
    panelIconText🔄
    bgColor#FFFAE6
    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.
     Expand
    titleExample file
     Code Block
    languagexml
    <?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">39783404658423</INTERNATIONAL
    >A375-129</SUPPLIER_PID>
				
    <BUYER
    <INTERNATIONAL_PID xmlns="http://www.bmecat.org/bmecat/2005"
     type="DgProductId">6406783</BUYER
    >09783404175109</INTERNATIONAL_PID>
				
    <DESCRIPTION
    <BUYER_
    SHORT
    PID xmlns="http://www.bmecat.org/bmecat/2005"
    >Spider-Man: No Way Home UHD BluRay</DESCRIPTION_SHORT>
	
    >6406567</BUYER_PID>
			</PRODUCT_ID>
	
    <QUANTITY>5<
    		<QUANTITY>2</QUANTITY>

    	<!-- other Elements -->

    			<DELIVERY_
    DATE type="optional">

    DATE>
				<DELIVERY_START_
    DATE>2022
    DATE>2017-
    01
    06-
    13<
    21</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
    _END_DATE>2017-06-21</DELIVERY_END_DATE>
			</DELIVERY_DATE>
		</ORDERRESPONSE_ITEM>
	</ORDERRESPONSE_ITEM_LIST>
</ORDERRESPONSE>
     Panel
    panelIconId21a9
    panelIcon:leftwards_arrow_with_hook:
    panelIconText↩️
    bgColor#F4F5F7
    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).
    XML 
     Expand
    titleExample file
     Code Block
    languagexml
    <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">C-300</SUPPLIER_PID>
		<INTERNATIONAL_PID xmlns
    2001/XMLSchema" xmlns:xsi="http://www.
    bmecat
    w3.org/
    bmecat/2005" type="gtin">39783404658423</INTERNATIONAL_PID>
		<BUYER_PID
    2001/XMLSchema-instance" xmlns="http://www.
    bmecat
    opentrans.org/
    bmecat
    XMLSchema/
    2005
    2.1" 
    type
    version="
    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.
    Documentation
     Expand
    titleXML Schema Diagram
    Image Removed
    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>
    Image Added
    If possible do always send all three sub-elements SUPPLIER_PID, INTERNATIONAL_PID und BUYER_PID.
    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[25025]
    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 Merchantsmerchants: The id ID will be printed onto our return labels as Code-39-Barcode and must comply with ISO/IEC 16388 norm.
    The SupplierThe SUPPLIER_OrderORDER_Id ID is also displayed on the marketplace sales fee reports.
    . ORDERRESPONSE_ITEM_LIST
    -
    -
    Should
    . . ORDERRESPONSE_ITEM
    -
    -
    Should
     
    . . . PRODUCT_ID
    -
    -
    Must
    . . . . 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
    Can
    Galaxus product IDkey
    . . . 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.> 0
    . . . 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 dateDate 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
    2017-06-21
    dtDATETIME
    Should
    Estimated arrival date:
    • If 
     you can provide an exact date where DELIVERY_START_DATE = DELIVERY_END_DATEAlso compare this date with the requested DELIVERY_DATE in our order with the different type attributes (optional and fixed). 
    • the arrival date is unknown, the segment must be left blank
      (warning) In the EU, «unknown» or «fake» delivery dates are not allowed to be transmitted
    • A date in the past does not trigger date updates
    • For orders with DELIVERY_DATE type="fixed" this must be confirmed
    . . . . DELIVERY_END_DATE
    2017-06-21
    dtDATETIME
    Should
    Estimated arrival date, please provide an exact date with the same Same value as in DELIVERYDELIVERY_START_DATE

    ↑ Top