Motor Carrier Load Tender
The X12 204 is a shipper's offer (tender) of a freight load to a carrier, specifying origin, destination, equipment, and commodity details.
In this guide
204 Load Tender moves from Shipper / Freight Broker / 3PL to Motor Carrier (Shipper → Carrier) via AS2, SFTP, API. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How 204 Load Tender Works
Sender
Shipper / Freight Broker / 3PL
Receiver
Motor Carrier
Direction
Shipper → Carrier
Standard
ANSI ASC X12
Version
005010
Transport
AS2 / SFTP / API
Business Purpose
Logistics & Fulfillment
Sender — Shipper / Freight Broker / 3PL
EDI Transmission
204
Motor Carrier Load Tender
ANSI ASC X12 004010 / 005010
Receiver — Motor Carrier
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →204 Load Tender workflow. Steps: Identify Load, Generate 204 EDI, Tender to Carrier, Carrier Receives Tender, Accept or Decline, Execute & Report Status. Transmitted from Shipper / Freight Broker / 3PL to Motor Carrier via AS2, SFTP, API, following ANSI ASC X12 004010 / 005010.
Overview
Automates the load-tendering process between shippers/brokers and carriers, replacing phone or email tenders with a structured, trackable transaction.
Sender
Shipper / Freight Broker / 3PL
Receiver
Motor Carrier
Direction
Shipper → Carrier
Standard / Version
ANSI ASC X12 004010 / 005010
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| B2 | Beginning Segment for Shipment Information Transaction | Shipment ID and SCAC codes for shipper and carrier. |
| B2A | Set Purpose | Indicates original tender, cancellation, or update. |
| S5 | Stop Off Details | Pickup and delivery stop sequence. |
| L11 | Business Instructions and Reference Number | PO, BOL, or other reference numbers. |
Interactive example
Click any segment below to see its business meaning.
ST
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
ST*204*0001~
B2**FEDX*SHIP-99201***PP~
B2A*00~
S5*1*LD*20230920*0800**Columbus*OH~
S5*2*UL*20230921*1400**Cleveland*OH~
L11*PO-2024-88213*PO~
SE*6*0001~Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| TMS Load Record | load.pickup_date | S503 (Date) at LD stop |
| TMS Load Record | load.reference_po | L11 (Reference Number) |
Validation rules
- Stop sequence numbers in S501 must be sequential without gaps.
- Each load must have at least one LD (load) and one UL (unload) stop.
- Carrier SCAC code in B2 must be an active, contracted carrier for the shipper.
Common errors & troubleshooting
Carrier's system rejects the tender
Cause: Equipment type requested isn't available in the carrier's fleet or contract terms.
Fix: Validate equipment type against the carrier's contracted capabilities before tendering.
Stops appear out of order at the carrier
Cause: S501 sequence numbers weren't assigned in pickup/delivery order.
Fix: Always number stops in the intended physical route order, starting at 1.
Frequently asked questions
The carrier typically responds with a 990 (Response to a Load Tender) accepting or declining the load before movement begins.
Still have questions about 204?
Ask EDI AI →