The transport order is the booking that you place at us for us to transport your cargo. We need this at least 24 hours before pick-up of the cargo. Transport orders consist of one or more shipments, which is the level on which we track progress and which shows up on invoices. It will instruct our team on what needs to be shipped from where to where. Information about pick-up and delivery dates can be added, as well as the additional requirements we need to consider when we are planning the transport.
Note that orders we receive end up in status “PENDING”. our planners review all orders we receive and match those against the agreed SOP criteria. Once confirmed, they can be used by our planners. When your order can not be accepted, you will be contacted by one of our planners or someone from the customer service department.
You can find the documentation regarding our standard format for transport orders here. From there you can also download the JSON schema to aid in the development. Even if you do not want to send us this format but wish to use your own format instead, the documentation is still worth looking at as it will show our information needs.
For Airline customers we have created a standard for when orders are send with FFM/FBL messages. If your company is able to send the order with the FFM/FBL format, we can make sure everything for your company is set-up within Jconnect. This will make sure that your orders will processed automatically, and gives you a perfect overview of the status of your order. The only thing you need to do is provide us with your SITA address, and to make sure that your orders are send to our SITA address SPLJRCR.
The shipment event message is triggered whenever a relevant event occures on a shipment. For instance, we can send you a message whenever one of your shipments arrives at the pick-up location. As part of the integration project a determination will be made which events will be sent to you, and this will be filtered out our end.
You can find the documentation regarding our standard format for the shipment event message here. From there you can also download the JSON schema to aid in the development. Even if you want us to send you the messages in your own format rather than in ours, the documentation is still worth looking at as it will show you which information we are able to send.
The shipment position message is triggered regularly for shipment which are in progress. It contains information on the current location of the cargo related to the shipment, as well as an update an expected arrival date/time at the delivery location.
You can find the documentation regarding our standard format for the shipment position message here. From there you can also download the JSON schema to aid in the development. Even if you want us to send you the messages in your own format rather than in ours, the documentation is still worth looking at as it will show you which information we are able to send.
The invoice message is triggered whenever we send a customer an invoice. It has both financial and operational information regarding the invoice.
You can find the documentation regarding our standard format for the invoice message here. From there you can also download the JSON schema to aid in the development. Even if you want us to send you the messages in your own format rather than in ours, the documentation is still worth looking at as it will show you which information we are able to send.
We also support sending invoices in UBL format. Optionally we can send these via the Peppol framework as well.