Supplier Integration

Outbound Message Types (Jan de Rijk Logistics to Supplier)

Consignment

In order to receive the right instructions to execute the agreed transport, Jan de Rijk will send charter companies a consignment.

This message contains information about the loading and unloading locations, and local contact persons. To allocate the shipment to a driver with the right license and/or asset, information about the specifications of the cargo is added. Cargo quantities, weight and dimensions are added to determine co-loading options on your end. Please note that some cargo is not allowed to be loaded with others, this is also flagged. Also, the agreed pricing is added to the message, please look at those ahead of acknowledging the transport.

You can find the documentation regarding our standard format for the consignment message here. From there you can also download the JSON schema to aid in the development.

Inbound Message Types (Supplier to Jan de Rijk Logistics)

Consignment Event Updates

The standard service arranging transport requires physical execution, in-time and accurate information about the transport/parcel delivery as well as documents to be available. Thus, to inform our customers in time, we require to know which processes have been completed and are about to take place. The most important activities for Jan de Rijk Logistics are:

Actual Time of Arrival at the loading location
Actual Time of Departure at the loading location
Actual Time of Arrival at the unloading location
Completion of the unloading tasks, which we consider cargo has been delivered.

To access premises and cross borders we usually need to announce which driver will deliver the cargo, and by which vehicle. This information is shared with external parties to grant the required access and documents. For GDPR (General Data Protection Regulation) reasons we only require the driver(s) full name, and license plates of the truck.

You can find the documentation regarding our standard format for the consignment event message here. From there you can also download the JSON schema to aid in the development.

Consignment Position Updates

To avoid unnecessary mail and phone contact, we prefer to receive GPS updates from your trucks as well in addition to the events.

CMR pdf

No transport is completed when documents are not in place. Therefore, we would also like to set up a connection to receive the PDF for any Proof of Delivery, like the CMR. We require our 12-digit shipment number to be able to process it, so that should be in the file name.

Note an alternative to sending the CMR as a PDF file is to embed the PDF in the "Consignment Event Updates" message as mentioned above.

Chartering Process

See below for a detailed overview of the chartering process, when managed via EDI.

1	Jan de Rijk creates a booking and sends out event “bookingCreated” to the carrier.
2	If at any point in the process a change in the booking is needed, Jan de Rijk sends out event “bookingUpdated”.
3	If at any point in the process a cancellation of the booking is needed, Jan de Rijk sends out event “bookingCancelled”.
4	The charter determines if they will execute the booking. They send back a message indicating acceptence via the “accepted” Y/N property. If this is “false”, the process ends.
5	The charter plans the execution of the consignment. They send vehicle license plate, pulled unit (trailer) license plate (if not pre-determined by Jan de Rijk) and driver name(s).
6	The charter executes the activities on the consignment. They send the relevant milestones when they happen. Mandatory milestones are: Arrival Start End
7	The charter gathers and sends the required documents.
8	Jan de Rijk evaluates the documents for readability and document type. If a document is not readable or is of an irrelevant type, it is document is rejected and Jan de Rijk sends back event “documentRejected” with information as the reason of the rejection.
9	If the document is deemed OK, Jan de Rijk sends event “documentApproved”.
10	If a document was approved, but the consignment requires more or other documents, the “documentApproved” event is accompanied by a “moreDocumentsRequired” event. Note the “tasks” section of the consignment-main file will detail which documents are missing.
11	De Jan de Rijk Planning department completes the consignment information in the system and confirms the final price.
12	When all above mentioned tasks are done and confirmed in the system, Jan de Rijk sends the “bookingConfirmedChargeable” event. This file will also be the first file that includes the PO number. As PO number is mandatory on invoices for Jan de Rijk, this is required for invoicing to be possible.