Below you will find all steps necessary to connect to Coolblue via Onetrail using Onetrail EDIFACT D.97A, D.96A and OT XML.
Please note that Coolblue currently supports the following message types:
== Step 1: Fill in customer setup-form== A Onetrail employee will send a 'Customer Setup-Form', this form will contain all required EDI data, such as;
Please make sure to return the filled out Setup-Form as soon as possible. Onetrail will process the Setup-Form within 2 days.
== Step 2: Approve onboarding requirements Coolblue == Coolblue has a strict EDI policy, in reality this means Coolblue want to know exactly what happens with their orders in the order response message. It is therefore required to approve the Onboarding requirements.
*If the requirements are met, please send your approval in an email to TPN.Delivery@onetrail.com.
*If the requirements are not met, please contact your Onetrail TPN Implementation Consultant to discuss the possibilities.
Specific Coolblue business requirements:
Order Response:
*Suppliers must to be able to comply to all order response scenario's mentioned below step 5.
Despatch Advise:
*Suppliers ought to send product Serial Numbers in the Despatch Advise (DESADV) messages. Note: Coolblue is investigating if they have more requirements for the DesAdv message.
Invoice:
Product data:
*Product data has to be available (via Product Manager upload or Automated upload via FTP (PDE)).
Onetrail supports a wild array of communication options, they can be found on this page.
A Onetrail TPN Implementation Consultant will test the chosen communication protocol with you, both on the Onetrail Acceptance and Production environments.
While onboarding with Coolblue, Onetrail will test using a test account on the Onetrail Acceptance environment.
The test account is linked to an automatic validation process which provides automatic feedback about the currently performed tests.
The GLN codes which need to be used for this Acceptance test account are:
Onetrail EDIFACT D.96A / D.97A Format
Onetrail XML Format
*<toRole> = 8714253023366 - Onetrail XML Test Buyer Trading Partner GLN
*<shipTo> = 8714253023380 - Onetrail XML Test Buyer Ship To GLN
*<billTo> = 8714253023397 - Onetrail XML Test Buyer Invoice To GLN
Please also exactly communicate above GLN's in the test Order Response and Despatch Advise messages, otherwise the automatic validation process won't provide any feedback.
Please find all technical documentation below:
Onetrail EDIFACT D.96A MIG.
Onetrail EDIFACT D.97A MIG.
Onetrail Order Response XML-EDIFACT DOC.
Onetrail XSD-DOC.
It is mandatory that the outbound message (ORDRSP) supports the following scenario's - when applicable (it needs to reflect the physical delivery)
*Scenario 1: Order confirmed without changes
*:- The Seller accepts the purchase order with exactly the same prices, quantities and requested delivery dates as requested.
\- The Seller accepts the purchase order with either changes in
**prices (2.1)** and/or **requested delivery dates (2.2)** as
requested.
\- **2.1** Accept the purchase order with a deviating price
\- **2.2** Accept the purchase order with a deviating delivery
date. Test both known and unknown delivery date responses.
\- If there is a change in the requested **quantities**, please
use **Scenario 8: Order-Line is split** instead.
\- There is a blockage on the complete order, this can occur
when there are **financial**, **sales**, **stock** or other
**technical issues** with the purchase order which prevents
physical delivery of the products. This excludes normal
back-orders, because that is Scenario 2.
\- There is a blockage on one or more Order-Lines, this can
occur when there are **financial**, **sales**, **stock** or
other **technical issues** with the purchase order.
\- Purchase order is **cancelled** by either Seller or Buyer.
\- One or more Order-Lines have been **cancelled** by either
Seller or Buyer.
\- Seller adds a new Order-line on request of the Buyer or
because of a change by either Seller or Buyer.
\- When the Order will be partially delivered, the quantity
which is available for delivery will be shipped when requested,
the quantity which is not available will be either put in
**back-order (8.1)**, **blocked (8.2)**, or **cancelled (8.3)**.
\- **8.1** **(A)** Accept the purchase order with a split-order
line backorder response with either known and/or unknown
delivery dates.
**(B)** Also confirm in an update response that the on-stock
order line is partially shipped and the other order line is
still partially back-ordered.
\- **8.2** Accept the purchase order with a split-order line
on-hold/blocked response with unknown delivery date.
\- **8.3** Accept the purchase order with a split-order line
delete response with unknown delivery date.
Example files
Please find all files in ZIP format for the above scenario's
Onetrail TPN™ EDIFACT D.96A Example files
Onetrail TPN™ EDIFACT D.97A Example files
Onetrail TPN™ XML All Messages Example files
Onetrail TPN™ XML Order Response scenario Example files
For validation and simulation, please use the NAD segments as mentioned in the original ORDER.
Send in the ORDRSP and DESADV messages via the preferred communications channel and receive an validation report via E-mail.
If all scenario's are tested, your Onetrail TPN Implementation Consultant will inform Coolblue that onboarding is completed.
Before a full production GoLive is possible, Coolblue will first send an so-called "golden order".
This order must fully processed and delivered to the selected Coolblue warehouse and all developed response messages must be send back via Live EDI connection for that order.
If Coolblue receives the physical delivery correctly and on time as confirmed in the EDI Order Response and Despatch Advise message(s), Coolblue will inform you when a full GoLive with Coolblue is possible.
However, if this process wasn't completed satisfactory, Coolblue might opt to send another "golden order" to repeat and verify the process again.