Integrated Seller - TransportOrders
Introduction
Below you will find the steps a Seller should take to setup an ingestion channel with Eclic to upload transport order information using the NxtPort International ingestion channel. In this document we assume that the seller is already pre-registered on NxtPort International and is subscribed to the eECD application via a valid eECD admin account.
The process of setting up a transport order ingestion channel is described in following steps:
Initiating the process
The Seller contacts ECLIC (info@eclic.eu) to initiate a change request and to formally request to become an “integrated seller”. An “on-boarding” meeting is set up with NxtPort and any other required stakeholders to discuss the following:
The minimum required eECD data fields (XML message) are reviewed and the change request describes in more detail how the transport orders ingestion channel will be fed with new transport order data (via message broker, direct via SAP,…), (XML structure below).
Note: In case a message broker is involved, the “on-boarding” meeting is extended with the message broker like Transporeon/Elemica contact.The timeline of the change request and estimated set up cost are reviewed with the Seller (not with the broker).
The set up of an ingestion channel requires the seller to register with an eECD test account in the test/staging system.
Setting up an ingestion channel (in STG)
Receiving credentials
To obtain the ingestion channel authorization keys, you need to create a support ticket and provide the information below:
Your company name
The VAT number of your company
Mention you want to setup an ingestion channel for the eECD application
Mention the environment you want to start the integration for (in this case Staging)
NxtPort support will provide you with technical information and the ingestion channel url (by e-mail) for the correct environment. Please note that this information will be different between Staging and Production environment.
With the above information you can Retrieving a security Token to make API calls and use the TransportOrders Ingestion to send your TransportOrders to NxtPort.
Using a data broker / ISV / Third party software supplier
A data broker who, on behalf of the Eclic member, will setup the ingestion channel will have to be provided with the same information to be able to request an access token. It is advised however to create a separate company on the NxtPort Platform for the data broker. This to ensure that the data broker does not have access / rights to other use cases the seller is involved in on the NxtPort platform.
Testing the ingestion channel
To test the ingestion channel, it is best that all parties involved are aware when the testing will take place. The Seller (or data broker) will need to inform NxtPort when testing is planned to take place. Before testing can take place, the following steps need to be taken:
Data message structure: NxtPort will provide information to the seller or data broker on the data structure of the XML order as soon as a formal change request is approved.
Create a support ticket and provide NxtPort a list of all DUNS numbers as carrier identifier in an excel file that includes the following columns:
Carrier Name
DUNS Number; or
VAT Number
The list of Carriers have already been setup for the ingestion channel.
Carrier Name | Carrier Subname | Code Type | Carrier ID for ingestion channel | |
|---|---|---|---|---|
| 1 | ADPO | ADPO NV | DUNS | 768565392 |
| 2 | ADPO | ADPO NV | VAT | BE0436622536 |
| 3 | Bertschi AG | Bertschi Belgium NV | DUNS | 399576156 |
| 4 | Bertschi AG | Bertschi BV | DUNS | 480722420 |
| 5 | Contank S.A. | Contank S.A. | DUNS | 467068334 |
| 6 | Contank S.A. | Contank S.A. | VAT | A08957912 |
| 7 | De Decker - Van Riet nv | De Decker - Van Riet nv | DUNS | 283274827 |
| 8 | Den Hartogh Logistics | Den Hartogh Logistics | DUNS | 315928440 |
| 9 | Gartner Tankspedition GmbH | Gartner Tankspedition GmbH | DUNS | 507333040 |
| 10 | Gruber GmbH | Gruber gmbh | DUNS | 315662189 |
| 11 | Haesaerts Intermodal | Haesaerts Intermodal | DUNS | 373031293 |
| 12 | Hoyer GmbH | Hoyer GMBH | DUNS | 326533858 |
| 13 | Hoyer GmbH | Hoyer Global Transpo | DUNS | 405412321 |
| 14 | Hoyer GmbH | Hoyer GmbH | DUNS | 344092916 |
| 15 | Hoyer GmbH | Hoyer GmbH Internati | DUNS | 315230458 |
| 16 | Hoyer GmbH | Hoyer Nederland B.V. | DUNS | 405378142 |
| 17 | Huktra | Huktra | DUNS | 283248581 |
| 18 | Huktra | Huktra (H.ESSERS) | DUNS | 374839637 |
| 19 | IDT - Ingo Dinges Tankreinigungs GmbH | Ingo Dinges | DUNS | 342740778 |
The Seller needs to setup its product master data and integrated loading location table. In case master data is missing, a transport order error message will be generated.
To send the xml order, do a POST call to your channel (URL as received in step 2) and add the access token in the header of the call, here is an example:
A transport order (original, change or cancellation) is sent successfully when it is visible within the eECD application (under menu “Transport Orders”). In case you do not have access to this menu, please contact info@eclic.eu to ensure the Seller is setup as “integrated seller”.