For users integrated with Chaine Booking, understanding how posts are created from your Transportation Management System (TMS) is crucial. This process involves translating data from your TMS into Chaine's standard format and then deciding whether to create a post based on this data. Let's break down this process for a clearer understanding.
What happens when Chaine receives a request from your TMS
Each TMS has different data fields, so when we receive a request, we first map it into our data format. To see our exact fields, refer to these docs. Here is how the process works.
Integration Mapping
Initially, when a request from your TMS enters Chaine's system, it undergoes a process called 'integration mapping'. This involves translating the TMS data into Chaine's standardized format.
Customizations
The way data is mapped from your TMS to Chaine's format can vary depending on the specific integration setup for each customer. This ensures that the unique requirements and data formats of different TMS systems are accurately represented in Chaine Booking.
The logic for creating a post
Once the data is mapped to Chaine's format, the system uses specific logic to determine whether a post should be created. This logic is crucial in ensuring that only relevant and necessary posts are created. Here's how it works:
Checking the status of the shipment
In Chaine Booking, when integrating data from a TMS, a crucial step is verifying the status of each shipment. This verification is essential to determine whether a post should be created in Chaine's system. Keep in mind that when we say status, we are referring to the status of the Chaine standard shipment. To understand what your TMS shipment statuses map to in the Chaine standard, reach out to support or contact your system admin.
Here's a closer look at how this works:
Criteria for post-creation: The system has predefined criteria to assess whether a shipment's status qualifies for post-creation. These criteria revolve around the shipment's current state within the logistics cycle.
Key Statuses Checked:
Assigned: If a shipment is already assigned to a carrier, it typically does not necessitate a new post, as the load is already being handled.
In Transit: Shipments that are in transit are actively being moved to their destination and, therefore, do not require a new post.
Delivered: A delivered shipment has completed its journey, rendering a new post unnecessary.
Canceled: Canceled shipments are no longer active and hence do not need a post.
Outcome: The system creates a post only if the shipment status falls outside these categories, implying that the load is available and requires a carrier.
Scope Confirmation Explained
Scope confirmation is another critical step in the process, ensuring that only relevant data leads to post-creation:
Understanding Scopes: 'Scopes' in this context refers to whether or not your workspace has the booking feature enabled.
Necessary Scopes for Post-Creation:
Post Scope: Your workspace should have the Chaine booking feature enabled.
Created Scope: This scope signifies that your workspace allows the creation of posts in Chaine.
Process: The system checks for these scopes within the shipment data. If both 'post' and 'created' scopes are present and validated, the system proceeds with post creation.