Skip to content
EDI X12 204

X12 transaction code

X12 204 Motor Carrier Shipment Information

Stop Mapping. Start Trading.

Standard
X12
Code
204
Trading partners
1

Specification summary

X12 204 Motor Carrier Shipment Information 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
Segments with mandatory elements
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

Trading partners that support X12 204

1 partner, 1 channel. Click a channel for the full segment guideline.

Usage breakdown

Who trades X12 204 Motor Carrier Shipment Information

204 is used most heavily in grocery & food.

This is the same X12 transaction set 204 under its earlier title: in older releases such as 003020 the set was named Motor Carrier Shipment Information and provided the motor carrier with bill of lading, rating, and scheduling data for a shipment. Later releases renamed it Motor Carrier Load Tender and scoped it to truckload tendering. Partners still mapped to legacy releases trade under the older name, and the document serves the same purpose of handing the carrier the shipment details it needs to move the load. The shipper or another party contracting for the transportation sends it to the motor carrier that will move the shipment. A shipper transmits bill of lading, rating, and scheduling details to a motor carrier for a load it is arranging, typically on a trading relationship still mapped to an older X12 release.

By industry

  • grocery & food 1 channel
Largest 204 implementations

FAQ

X12 204 questions

What is X12 204 Motor Carrier Shipment Information?

X12 204 (Motor Carrier Shipment Information) is an EDI transaction set defined by ANSI ASC X12 for exchanging motor carrier shipment information between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.

Which trading partners use X12 204?

1 Stacksync partner accepts X12 204: Anheuser-Busch Companies, LLC. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.

How do I integrate X12 204 with my ERP?

Stacksync handles the full X12 204 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.

Ready to automate your EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.