Content Comparison

To be announced

02 Jun 2023

Added extra information authorisation: “Basic ”||"Base64 encoding of username and password joined by a single colon : "

03 May 2022

Media Order B2C: Yaml file version 1.3.0. Changelog version 1.2.0 to version 1.3.0:

• Add Article with ArticleId as product identification for dedicated stock

• Use either EAN or Article in placeOrder (EAN is now optional), if both are supplied the EAN is used and Article is ignored

• Report either EAN or Article in getOrderStatus based on provided input in placeOrder

MediaShipment: Yaml file version 1.0.0 version 1.1.0. Changelog version 1.0.0 to version 1.1.0:

• Add ArticleId as product identification for dedicated stock

• Report either EAN or ArticleId in getShippingUnit based on provided input in placeOrder

25 Jan 2022

Test and order simulation added

15 Dec 2021

Add Tag matrix for Green and Standard option

19 Oct 2021

Update yaml file MediaOrderNotify v.1.0.2.yaml

19 Aug 2021

Update generic error messages

07 May 2021

Align with updated order notifications

12 Nov 2020

Update yaml file MediaOrderB2C v1.2.0.yaml

08 Jun 2020

Update MediaOrderB2C version; Correct resource for notifyOrder and notityShipment

28 Apr 2020

Update yaml versions

12 Mar 2020

Add volume limits and error messages; Correct typo in process flow diagrams

13 Jan 2020

Add flows and sequence diagrams

11 Nov 2019

Add operations

30 Aug 2019

Initial document

Tag matrix for Green and Standard option

CB has two options for submitting e-commerce orders:

• Green option no document attached to shipment

• Standard option packing slip or invoice included with shipment

The entire set for the standard data exchange with CB consists of the following documents and files:

File versus webservice. Communication about orders is based on the receiving channel, i.e. file base communication is used for orders received via file based interfaces and webservice communication is used for orders received via the webservice MediaOrderB2C. Order are processed independent from the receiving channel

Mapping berichten naar webservices B2C.xlsx

The mapping from file based to webservice based messages

File based

Webservice operation

OPDNAW

placeOrder

ANNOPD

cancelOrder

UITOPD

notifyOrder / getOrderStatus + notifyShipment / getShippingUnit

NUITOP

notifyOrder / getOrderStatus

Migration strategy from batch file to webservice

Suggested migration strategy from batch file to webservice:

• Verify technical and functional process with a live connection to the CB test environment.

• Arrange for shadow-run(s) in a combination of production and test environments,, i.e. send an OPDNAW message to the CB production environment, extract a few orders and send them via the webservice to the CB test environment. CB can verify the received data in the test environment against the production data from the OPDNAW.

• Arrange for go-live date

• Send a limited number of orders via the webservice to the CB production environment. CB can monitor the processing of these orders.

• Verify the information in the order status and shipping unit operations.

• Step-by-step increase the webservice load until the required level is reached.

• If applicable then disable the file based flow.