How does the integration work?
Independent information exchange means: all parties can connect to TransFollow. To facilitate this, TransFollow offers a connection point to our platform via our API.
The technical implementation
All parties can connect to TransFollow – and together they shape the information exchange. The connection point, the API, serves as an entry point for you as a software supplier. The API is the public set of ‘endpoints’ or functional units, built on a backend application. The API specification describes the format and structure of the messages for those endpoints. The backend accepts information and editing commands from connected systems through our API.
Backend accepts information
The backend accepts customer information from external systems such as TMS, ERP and WMS. Customers can request or offer data in a standard syntactic format (JSON) and communicate with the “http” communication protocol. This is protected from third parties by a standard TLS encryption layer. Messages via the endpoints are stateless to the customer and backend.
TransFollow translates all the patented information into a set of TransFollow concepts. All parties agree to communicate company-relevant information in these terms. Together, we thus achieve successful data exchange. Here you can download a description of all the important TransFollow concepts, including practical examples of their use.
Coordinating the approach
TransFollow is an independent platform, built around a shared central consignment note. All parties involved in a transport can share information about the digital consignment note. If one of them initiates a change, the others are informed. The changes are available for the connected systems of all parties.
Objectives with the eCMR
Each party has its own objectives with the eCMR. One party uses it as a dynamic consignment note, another to manage returns. These choices influence, enrich and accelerate parts of the logistics process for all parties. Coordinate your working method efficiently with all parties. In this way, you can achieve a successful integration together. Your local distributor will be happy to support you in this.
The right sequence of information
Planning the step-by-step information exchange to TransFollow means: determining each transport-related action that requires information. And determine what information is sent from or to TransFollow. Each action in the information exchange happens in the order of the transport operation:
- For example, a transport planning system creates the freight document because it has the first information about the planned transport.
- The warehouse system, however, has more information about the nature and quantity of goods. It adds this information to the consignment note.
Exchange of information
TMS, WMS, FMS and ERP systems are managed by different companies, each with their own procedures and definition of transport. The available information varies in form and content. However, all parties must be able to connect to TransFollow. Parties mutually determine which information is relevant for a successful workflow. In this way they shape the information exchange together.
Creating a functional blueprint
The information flow in and out of TransFollow runs partly parallel to the most important logistics process. It is therefore useful to plan the exact timing and workflow of this information between the cooperating systems. Do you want to make such a functional blueprint? Your local distributor will be happy to support you.
The technical staff of TransFollow offers you support with the technical implementation of our API. Please contact our support department by sending an e-mail to support@TransFollow.org or call for +31 885525540 or +31 623909477 for more information.
In the development documentation, you will find the conditions and specifications of the TransFollow API.
The development documentation includes:
- API specifications for all public endpoints.
- A walkthrough section explaining the authentication and the first steps for using the TransFollow API.
- The lifecycle of a freight document and the freight transfer process.
- A description of the TransFollow eCMR and TransFollow Approval, the account structure and permissions.