TMS Documentation
      Back to home
      1. Knowledge Base
      2. Tai Software Write Ups
      3. TMS Documentation

      Customer Facing EDI Support

      Streamlined EDI Integration for Seamless Shipment Management and Tracking

      Tai TMS offers robust EDI functionality tailored to meet your end customers' needs for automating shipment creation, tracking, and invoicing processes. Our Integration Team ensures a seamless setup, which may include applicable setup fees.

      Tai TMS is built to process EDI files using the X12 - 4010 Standard as its foundation. However, we can customize our processing to support other X12 standards based on your specific requirements. File transmissions are supported via FTP, SFTP, FTPS, or AS2 protocols.

      To get started, please complete and return the following form:   Tai Software EDI Information Sheet along with any sample files or specifications provided by your customer.

      Table of Contents

      1. Supported EDI Documents

      2. EDI Workflow For Shipments

      3. EDI Project Discovery/Integration Workflow

      Supported EDI Documents:

       

      • 204 (Load Tender - Incoming): Customers send a load tender, and Tai creates a shipment.

        • Transaction Purposes:
          • 00 (Original): Creates shipments within the TMS, and will trigger a notification email.
          • 04 (Change): Notifies users of requested updates via email; changes require manual updates but are logged in the activity log for reference.
          • 01 (Cancellation): Sends email notifications; cancellations must be handled manually.

      • 997 (Functional Acknowledgment): Confirms receipt of the 204.

      • 990 (Load Tender Response):

          • Accepts/rejects shipments.
      • 214 (Status Updates - Outgoing): Provides shipment status updates (e.g., In Transit, Out for Delivery, Delivered).
      • 210 (Invoicing): Submits invoices (210) to customers when enabled.

       

      EDI Workflow For Shipments:


      Key Points to Keep in Mind

      • Dispatch Requests (204):
        Customers initiate the process by sending a dispatch request, which builds the shipment in Tai TMS.
        • Shipment Creation:
          The shipment is created in Quote status within the TMS.
      • Acknowledgment (997):
        Tai confirms receipt of the dispatch request by returning a functional acknowledgment.
      • Shipment Updates (990):
        • Moving the shipment from Quoted to Committed generates a 990 Acceptance.
        • Canceling the shipment triggers a 990 Rejection.
      • Status Updates (214):
        Tai offers two flexible processes for status updates, tailored to shipment needs:

        • Status-Based Updates:

          • Optimized for First Pick/Last Drop shipments.
            • Status changes trigger specific EDI codes for streamlined updates.

        • Stop-Based Updates:

          • Ideal for Multi-Stop shipments.
            • Each date and time entry generates a distinct 214 file, ensuring accurate tracking for every stop.

      Refer to your specific EDI project sheet to confirm which process is configured for your integration.

      • Invoicing (210):
        When an invoice is generated in the TMS, Tai submits it via EDI (210).
        • Customers set up for EDI 210s can regenerate invoices through the Generate Digital Invoice button. This feature is available when the preferred invoicing method is set to Digital.

       

      EDI Project Discovery/Integration Workflow:

       

      1. Project Initiation and Requirement Gathering:

        • Upon receiving a project request and specifications from the partner, we initiate the process by thoroughly reviewing the provided specifications.

      2. Scope Definition:

        • A comprehensive scope is drafted based on the specifications received, outlining the project's objectives, requirements, and deliverables.

      3. Scope Review and Confirmation:

        • The drafted scope is shared with the broker for review and discussion. Any necessary changes, including hardcoding or default settings, are addressed during this phase to ensure alignment with project goals.

      4. Dynamic Scope Document Management:

        • The scope is maintained as a live document using Google Docs, facilitating real-time updates and additions. This serves as a centralized repository for all project-related information, enabling easy access and future reference.

      5. Statement of Work (SOW) Preparation:

        • Upon approval of the scope, we proceed with the preparation of the Statement of Work, outlining the project's terms, deliverables, and timelines.

      6. SOW Approval and Commencement:

        • Once the Statement of Work is finalized and signed by both parties, we initiate the mapping process on our end in accordance with the agreed scope and SOW.

      7. Mapping and Configuration:

        • Our team completes the mapping process to configure the necessary systems and interfaces as per the agreed-upon specifications and requirements.

      8. Testing and Feedback:

        • We engage with the EDI partner/customer to commence testing, allowing for any necessary tweaks or additions to be addressed. Testing is preferably conducted in a production environment to ensure accurate evaluation and feedback for all parties.

      9. Finalization and Go-Live Planning:

        • Following successful testing and validation, we collaborate with the partner/customer to determine the optimal go-live date, ensuring alignment and readiness across all stakeholders.