Tai TMS can add EDI Functionality to support the needs of your end customers when automating shipment creation, tracking, and invoicing functionality. This will require a setup by the Integration Team. Setup fees may be incurred.
Tai TMS will process EDI files based on the X12 - 4010 Standard
Files can be transmitted via FTP / SFTP / FTPS / AS2
Please fill out and return the following form: Tai Software EDI Information Sheet along with any sample files or specs the customer needs us to adhere to.
Table of Contents
1. Supported EDI Documents:
- 204 (Load Tender - Incoming) Customers send Tai a load tender and we Create Shipment (Requires setup and mapping to customer).
- 997 (Functional Acknowledgement) We send an acknowledgment indicating that we received the 204.
- 990 (Load Tender - Response) We do support sending both an acceptance and rejection for Truckload shipments; LTL auto-accepts.
- 214 (Status Updates - Outgoing) When we receive status updates from Carriers and the status of shipment changes, we submit this change to the customer in this file.
- 210 (Invoicing) When this is active (Customer Invoicing Method = EDI), we will submit a 210 for the customer.
2. EDI Workflow For Shipments:
The key points to keep in mind are:
- The customer will be sending over the dispatch request (204) which will build the shipment in the TMS.
- Once we receive the dispatch request we'll send them an automatic response (997) essentially just letting them know that the file was successfully received.
- At that point, the created shipment will be in "Quote" status.
- From there when a shipment is moved from Quoted to Committed, we'll generate an Acceptance file (990 acceptance)
- When a shipment is moved to Canceled, we'll generate a Rejected file (990 Rejected)
- Then as the shipment's status gets updated, we'll send the status updates (214). These are triggered with the In transit, Out for Delivery, and Delivered statuses.
- Lastly, once the invoice is created in the TMS, we'll send over the Invoice via EDI (210).