Transportation and logistics

Transportation EDI for carriers, brokers, forwarders and shippers

Freight moves on four documents. A shipper or broker tenders a load, the carrier accepts or declines, reports status as the freight moves and bills when it is delivered. ECOM connects those documents to your transportation management system, whichever side of the tender you are on, and onboards each partner that requires EDI or APIs. Rail, ocean and air freight follow the same pattern with their own documents.

Talk to an EDI/API Expert Request a Demo

Summary: Transportation and Logistics

  • Freight moves on four documents: a load is tendered, accepted or declined, tracked with status and billed after delivery.
  • For carriers and trucking companies, freight brokers, shippers, and rail, ocean, air and forwarding teams.
  • ECOM connects those documents to your TMS from either side of the tender and onboards each partner requiring EDI or APIs.
  • Typical documents: 204 tender, 990 response, 214 status, 210 freight invoice, 997 acknowledgment; TMS, tracking, ERP, partner APIs.
  • Talk to an EDI/API Expert: bring the partner requiring EDI, the TMS you run and the date you need to be live.

At a glance

Key documents

Systems we integrate

  • TMS
  • Dispatch, telematics and tracking
  • ERP and accounting
  • Partner APIs and portals

PRISM products

  • PRISM-EDI
  • PRISM-API Gateway
  • PRISM-SCV
  • PRISM-DriveSync

What is transportation EDI?

Transportation EDI is the set of standardized documents that shippers, brokers and carriers use to tender loads, respond to tenders, report shipment status and bill for freight. In ANSI X12 the core documents are the 204 motor carrier load tender, 990 response to a load tender, 214 shipment status message and 210 motor carrier freight invoice. Rail, ocean and air freight have their own documents, such as the 404 rail shipment information, the 300 series for ocean bookings and status, and IATA Cargo-XML messages for air cargo. Many partners also offer APIs for tracking and rating, so carriers and shippers often run EDI and APIs side by side.

Who it's for

Different roles, different workflows

  • Carriers and trucking companies

    You receive 204 tenders from shippers and brokers, answer each with a 990 inside the partner's response window, report pickup and delivery with 214s and bill with 210s, ideally straight from your TMS.

  • Freight brokers

    You sit in the middle. Tenders come in from shippers and go out to carriers, status flows back in both directions, and freight invoices are received from carriers and issued to shippers.

  • Shippers

    You tender loads to contracted carriers and brokers, track the responses and status messages, and audit the freight invoices you receive before paying them.

  • Rail, ocean, air and forwarding

    Railroads, ocean carriers, airlines and freight forwarders exchange bookings, shipping instructions, status and freight invoices in their own mode-specific documents.

How the workflow runs

From load tender to freight invoice

The same four documents run in both directions depending on your role. What makes them work is a shipment reference that every partner carries from the tender to the invoice.

  1. 204Load tenderShipper or broker offers the loadStops, dates, equipment, weight
  2. 990Tender responseCarrier accepts or declinesWithin the partner's response window
  3. 214Shipment statusCarrier reports milestones
    • X3Arrived at pickup
    • AFDeparted pickup
    • X1Arrived at delivery
    • D1Delivered
  4. 210Freight invoiceCarrier bills the loadAudited against tender and status

Shipment ID · SCAC carried through every document so tender, status and invoice can be matched

Typical X12 workflow. Each trading partner's implementation guide defines its own documents, versions and timing.
  1. 01

    Tender the load (204)

    The shipper or broker sends stops, dates, equipment, weights and references. Updates and cancellations use a purpose code on a new 204 rather than a new load.

  2. 02

    Respond in time (990)

    The carrier accepts or declines, echoing the shipment identification and SCAC. Many tendering processes move the load to another carrier if no 990 arrives within the window.

  3. 03

    Report status (214)

    Pickup, in-transit, appointment and delivery events with status and reason codes, times and locations. Each partner may use the codes differently, so they are mapped to consistent milestones.

  4. 04

    Bill the load (210)

    The carrier invoices with base freight and accessorial charges, referencing the same shipment, so the payer can audit it against the tender and status history.

  5. 05

    Reconcile and pay

    Invoices that match tenders, rates and status are paid. Mismatched references, unapproved accessorials or duplicates go back to the carrier for correction.

Challenges

Integration challenges in transportation and logistics

01

Tenders that expire

A tender without a timely 990 is often re-tendered to another carrier. Manual review of tenders costs loads and damages scorecards.

02

Status codes that mean different things

Shippers and brokers expect different 214 events and codes. Without consistent mapping, customers lose visibility and carriers lose credibility.

03

Freight invoices that cannot be matched

A 210 that does not carry the tender's references cannot be audited automatically, so payment waits for manual review.

04

Every partner onboards differently

Each shipper or broker has its own implementation guide, versions, connection method and test process, and some prefer APIs.

How we help

How ECOM supports transportation and logistics companies

  • TMS integration

    204 tenders created in your TMS or loaded into it, 990 responses from TMS decisions, 214 events from dispatch and tracking data, 210 invoices from billing.

  • Partner onboarding

    Specifications, connections, test documents and scenario testing for each shipper, broker or carrier that requires EDI.

  • Reference integrity

    Shipment identification, SCAC, PRO and bill of lading references carried consistently across tender, status and invoice.

  • Status code mapping

    Each partner's 214 status and reason codes mapped to the milestones your customers and systems expect.

  • EDI and APIs together

    Carrier and shipper APIs for tracking or rating alongside EDI where a partner offers them.

  • Monitoring

    Unanswered tenders, missing status updates and rejected invoices visible as exceptions before a partner calls about them.

PRISM products

Which PRISM products apply

Each partner connects in the way it can support. These products cover the connections and visibility this industry needs most.

  • PRISM-EDI

    Exchange of 204, 990, 214 and 210 documents with each partner over AS2, SFTP or a VAN, translated to and from your TMS.

  • PRISM-API Gateway

    API integration and connectivity for partners that offer tracking, tendering or rating APIs alongside or instead of EDI.

  • PRISM-SCV

    Monitoring of transactions and exceptions such as tenders without responses or loads without recent status.

  • PRISM-DriveSync

    ECOM's product for routing and delivery optimization. Ask ECOM how it applies to your delivery operations.

Systems integration

What transportation EDI connects to

The documents are only as good as the systems behind them. Integration typically covers these.

SystemWhat flowsWhat to plan for
TMSLoads, tenders, acceptances, status events and freight bills.ECOM integrates TMS environments including Oracle Transportation Management. Connector availability depends on the product and version.
Dispatch, telematics and trackingPickup, departure, arrival and delivery events for 214s.Event timing and time zones matter; partners measure on-time performance from them.
ERP and accountingFreight invoices, payments and remittance.Shippers audit 210s against rates and tenders; carriers reconcile payments against invoices.
Partner APIs and portalsTracking, tendering or rating where partners offer APIs or require portal entry.Partners differ; the connection method is chosen per partner.

Modes

Documents by mode of transport

Truckload and LTL use the four documents above. Other modes have their own standard documents, and many shippers and forwarders work across several.

  • Carriers & Freight Transportation hub

    One place to compare road, rail, ocean, air, intermodal and cross-border workflows, with carrier onboarding, systems integration, exception handling and shipment documents.

    Carriers & Freight Transportation hub in detail
  • Road freight and trucking

    Truckload, LTL, parcel and last-mile tenders, status, proof of delivery and invoices, with simpler carrier onboarding.

    Road freight and trucking in detail
  • Intermodal

    Truck, rail and ocean legs on one shipment, with references, equipment identifiers, handoff events and documents carried across them.

    Intermodal in detail
  • Rail

    The 404 gives the railroad shipment details, the 417 interchanges the waybill between railroads, and the 410 bills the freight. Intermodal ramps report container moves in the 322.

    Rail in detail
  • Ocean

    The 300 requests a booking and the 301 confirms it, the 304 sends shipping instructions, the 315 reports container status and the 310 is the freight receipt and invoice.

    Ocean in detail
  • Air freight

    Airlines and forwarders exchange air waybill and status data in IATA's Cargo-XML messages, which IATA developed to address the limitations of the older Cargo-IMP format. The X12 110 bills air freight.

    Air freight in detail
  • Freight forwarding

    Forwarders sit between shippers and carriers in every mode, often exchanging X12 with North American shippers and EDIFACT with international partners.

    Freight forwarding in detail
  • Third-party warehousing

    Warehouse orders, shipping advice and inventory between brands and 3PLs are covered on the 3PL page.

    Third-party warehousing in detail

Carrier and logistics guides

Guides for carriers and logistics providers

Integration guides for carriers and logistics providers that shippers and brokers commonly connect with.

All carrier guides
  • UPS

    Parcel and freight carrier; the guide covers the documents and connection options it offers.

    UPS in detail
  • FedEx

    Parcel and freight carrier; the guide covers documents and connection options.

    FedEx in detail
  • J.B. Hunt

    Transportation and intermodal provider; the guide covers documents and planning points.

    J.B. Hunt in detail
  • Hub Group

    Intermodal and logistics provider; the guide covers documents and planning points.

    Hub Group in detail

Implementation

What to plan for in a transportation EDI project

Assess your transportation EDI environment
  • Know your role in each relationship

    A broker sends and receives the same documents on different sides of each load. Maps and processes are designed per direction and per partner.

  • Agree the response window and events

    Each shipper or broker defines how fast 990s must arrive and which 214 events it expects. These requirements drive the TMS integration design.

  • Keep references consistent

    The shipment identification from the 204 has to reach the 214 and 210 unchanged, so it must be stored and reused, not re-keyed.

  • Test with each partner

    Most partners test documents before production. Plan scenario tests for updates, cancellations, partial deliveries and rejected invoices.

Perspectives

Shipper, broker and carrier each see the same load differently

One truckload creates documents on three sides. Knowing which one you send helps you scope an integration.

  • Shippers

    Tender loads, receive acceptances and status, and match freight invoices to what was moved.

  • Brokers and 3PL transportation teams

    Receive tenders, tender onward to carriers, and send status and invoices back to the shipper.

  • Carriers

    Accept or decline tenders, send status events and invoice, often to many shippers with different requirements.

  • Freight audit and payment

    Invoices are matched to tenders and status before payment, so disputes are about data, not paper.

Documents and standards

Common transactions

Core X12 transportation documents. Partners may also use others, such as the 211 bill of lading.

CodeDocumentWhat it does
204Motor Carrier Load TenderOffers a load to a carrier.
990Response to a Load TenderAccepts or declines the tender.
214Transportation Carrier Shipment Status MessageReports shipment events.
210Motor Carrier Freight Details and InvoiceBills for freight.
997Functional AcknowledgmentConfirms receipt of each document.

Scenarios

Typical integration scenarios

Carrier adding a new shipper

Meet a shipper's or broker's EDI requirement quickly, with responses and status sent from the TMS rather than typed into a portal.

Broker connecting both sides

Exchange tenders, status and invoices with shippers and carriers of very different technical capability.

Shipper standardizing carriers

Receive consistent responses, status and invoices from every carrier, by EDI or API, and audit freight bills automatically.

Trading partners

Transportation and Logistics partners we connect with

Examples of carriers trading partners ECOM can connect your business with.

See all 45 carriers partners

Logos are trademarks of their respective owners. Their display does not imply endorsement of ECOM Specialist.

Case studies

Where ECOM provides these services today

Anonymous profiles of ECOM customers in this industry, each showing the services ECOM provides and how the work is set up.

  • North American truckload carrier

    Protecting business continuity when a trucking company’s EDI expertise approaches retirement

    Managed EDI operations, API Gateway, Reconcile360 and PRISM-SCV for a large truckload carrier whose EDI knowledge sat with a few people nearing retirement.

    EDI operations · API Gateway · Reconcile360 · PRISM-SCV

    Read the profile
  • Freight and logistics services company

    Modernizing a decades-old EDI environment without disrupting complex freight operations

    Managed EDI operations, API Gateway, Reconcile360 and PRISM-SCV for a multimodal freight provider whose reliable EDI platform was nearing end of vendor support.

    EDI operations · API Gateway · Reconcile360 · PRISM-SCV

    Read the profile

All case studies

Frequently asked questions

What is the difference between the 204, 990, 214 and 210?

The 204 offers a load to a carrier, the 990 accepts or declines it, 214 messages report the shipment's status as it moves, and the 210 invoices for the freight after delivery.

How quickly must a carrier answer a 204?

It depends on the shipper or broker. Each sets a response window in its requirements, and loads without a timely 990 are often tendered to another carrier.

Can small carriers meet EDI requirements?

Yes. Requirements can be met through an integrated TMS connection or, where a partner allows it, through simpler file, API or browser-based options. The right approach depends on volume and the partner's rules.

Do tracking APIs replace the 214?

Not always. Many partners accept or prefer APIs for tracking, while others still require 214 messages. Carriers and shippers often support both.

Which documents do rail, ocean and air freight use?

Rail uses documents such as the 404, 417 and 410; ocean uses the 300, 301, 304, 315 and 310; air cargo uses IATA Cargo-XML messages and the X12 110 for freight invoices. Each partner's guide confirms its set.

Which TMS platforms does ECOM integrate?

ECOM integrates transportation management systems including Oracle Transportation Management environments. Integration options for your TMS and version are confirmed during scoping.

Which documents do shippers and carriers exchange?

Commonly the 204 load tender, 990 response, 214 shipment status and 210 freight invoice, though some partners use APIs for tracking and status instead.

Does ECOM provide transportation management software?

No. ECOM integrates your transportation, ERP and carrier systems. It does not replace the transportation management system you already use.

How to get started

Tell us who you trade with and what you run

  1. Send the basics. Your trading partners, the documents they require, your ERP or other systems, and any deadline.
  2. We review the requirements. An ECOM specialist looks at the partner programs, document formats and connections involved.
  3. You decide how to proceed. We outline the options, including managed services or software, for you to compare.

Connect your next shipper, broker or carrier

Tell us which partner requires EDI, what TMS you run and when you need to be live. An ECOM specialist will outline the documents, testing and timeline.