To start and identify an interchange of zero or more functional groups and interchange-related control segments
Schneider National Carriers, Inc. X12 204 Motor Carrier Load Tender
X12 204 (Motor Carrier Load Tender) is the EDI transaction exchanged between Schneider National Carriers, Inc. (Schneider SNFO) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 18
- Loops
- 3
- X12 204
- All partners ↗
Transaction context
Where 204 Motor Carrier Load Tender fits on Schneider SNFO
On Schneider SNFO, the X12 204 Motor Carrier Load Tender precedes the 990 Response To A Load Tender and 210 Motor Carrier Freight Details And Invoice in the Logistics cycle.
- Schneider National Carriers, Inc. channels
- 2 of 2
- Trading partners
- 386
- Channels
- 534
2 of Schneider National Carriers, Inc.'s 2 channels carry 204
partners across the Stacksync network trade 204
channels network-wide carry 204
Most common alongside 204
The 204 carries a shipper's or broker's offer of a truckload shipment to a motor carrier, including pickup and delivery scheduling, stop-off details, equipment requirements, commodities, and shipping instructions. It opens the routing-guide tender cycle: the carrier answers with a 990 Response to Load Tender, then reports movement on 214 status messages and bills on a 210 freight invoice. Trading partners require it because dispatch, tracking, and freight-pay matching all key off the tender's reference numbers. A shipper, freight broker, or 3PL responsible for contracting the move sends the 204 to a full-truckload motor carrier.
When it fires: A shipper's TMS plans a truckload and tenders it to the next carrier in the routing guide, requesting acceptance before the stated respond-by time.
Common 204 rejection causes
- Missing or wrong mandatory header data: ST, B2, and B2A are must-use segments, and an incorrect Standard Carrier Alpha Code in B2 routes the tender to the wrong carrier or fails validation.
- Slow or missing 990 responses: shippers expect acceptance or rejection within a defined window (the header G62 carries the must-respond-by date and time), and late answers damage the carrier's standing with the shipper.
- Stop-level weight reconciliation failures: totals in the stop-off AT8 segment (loop 0300) must equal the accumulated commodity-level AT8 amounts (loop 0320), and mismatches break rating and downstream invoice audit.
- Loop misuse: specifications require the LAD lading detail and G62 dates in either loop 0300 or loop 0350, not both, and order-level detail sent in the wrong loop fails partner validation.
Specification summary
X12 204 Motor Carrier Load Tender at the element level
The X12 204 specification defines 82 segments carrying 470 data elements, 63 of which are mandatory.
- Segments
- 82
- Data elements
- 470
- Mandatory elements
- 63
| Segment | Elements | Mandatory |
|---|---|---|
| B2 | 12 | 1 |
| B2A | 2 | 1 |
| MS3 | 5 | 2 |
| PLD | 4 | 1 |
| NTE | 2 | 1 |
| N1 | 6 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| G61 | 5 | 2 |
| N7 | 24 | 1 |
| M7 | 5 | 1 |
| S5 | 11 | 2 |
Key identifiers in 204
- Shipment Method of Payment
- Transaction Set Purpose Code
- Standard Carrier Alpha Code
- Routing Sequence Code
- Quantity of Pallets Shipped
- Description
- Entity Identifier Code
- Name
Full segment guideline — 18 segments 3 loops · X12 204 Motor Carrier Load Tender
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit basic data relating to shipment information
To allow for positive identification of transaction set purpose
To specify instructions in this business relationship or a reference number
To specify pertinent dates and times
To transmit information in a free-form format, if necessary, for comment or special instruction
N1 Loop Repeat: 5
To identify a party by type of organization, name, and code
To specify additional names or those longer than 35 characters in length
To specify the location of the named party
To specify the geographic place of the named party
N7 Loop Repeat: 10
To identify the equipment
S5 Loop Repeat: 999
To specify stop-off detail reference numbers and stop reason
To transmit detailed lading data pertinent to a pickup or delivery
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To identify a person or office to whom communications should be directed
Trading partners
1+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
Trading partners
2+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
No trading partner matches your search.
Browse the full directory
Schneider National Carriers, Inc. Schneider SNFO EDI 204 FAQ
Common questions about 204 Motor Carrier Load Tender on the Schneider SNFO channel.
What is X12 204 Motor Carrier Load Tender?
X12 204 (Motor Carrier Load Tender) is the EDI transaction set used to exchange motor carrier load tender data. Schneider National Carriers, Inc.'s Schneider SNFO channel requires it from trading partners.
Does Schneider National Carriers, Inc. Schneider SNFO require 204 for trading partners?
Yes, Schneider National Carriers, Inc. (Schneider SNFO) supports X12 204 Motor Carrier Load Tender. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Schneider National Carriers, Inc. 204 with Stacksync?
Most companies go live with Schneider National Carriers, Inc. 204 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other Schneider National Carriers, Inc. channels accept 204?
X12 204 runs on 2 of Schneider National Carriers, Inc.'s 2 channels. Besides Schneider SNFO, it is accepted on Schneider via Mercury Gate. Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.
Ready to automate your Schneider National Carriers, Inc. EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
