X12 transaction code
X12 404 Rail Carrier Shipment Information
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 404
- Trading partners
- 8
Specification summary
X12 404 Rail Carrier Shipment Information at the element level
The X12 404 specification defines 117 segments carrying 755 data elements, 124 of which are mandatory.
- Segments
- 117
- Data elements
- 755
- Mandatory elements
- 124
| Segment | Elements | Mandatory |
|---|---|---|
| ZC1 | 9 | 6 |
| BX | 12 | 3 |
| M3 | 4 | 1 |
| N9 | 6 | 1 |
| M1 | 12 | 1 |
| DTM | 4 | 1 |
| N7 | 19 | 1 |
| VC | 8 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| M7 | 4 | 1 |
| IC | 9 | 2 |
- Equipment Number
- Transaction Reference Number
- Transaction Reference Date
- Correction Indicator Code
- Standard Carrier Alpha Code
- Transportation Method/Type Code
- Transaction Set Purpose Code
- Shipment Method of Payment Code
Trading partners that support X12 404
8 partners, 8 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 404 Rail Carrier Shipment Information
404 is used most heavily in logistics & transport.
The X12 404 transmits rail-carrier-specific bill of lading information to a railroad and is the initial tender of a shipment between a consignor and a rail carrier. It can serve as notification of equipment release and as the legal bill of lading. The receiving railroad uses it to create the waybill that releases the equipment, set up the revenue document, generate operating instructions, and, on interline moves, pass shipment data to the next rail carrier. The shipper (consignor) or its agent sends the 404 to the railroad that will move the equipment, either directly or through a value-added network. A shipper finishes loading a railcar or intermodal unit and releases the equipment to the railroad for movement.
By industry
- logistics & transport 8 channels
FAQ
X12 404 questions
What is X12 404 Rail Carrier Shipment Information?
X12 404 (Rail Carrier Shipment Information) is an EDI transaction set defined by ANSI ASC X12 for exchanging rail carrier shipment information between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 8 Stacksync trading partners support this code across 8 channels.
Which trading partners use X12 404?
8 Stacksync partners accept X12 404: Burlington Northern Santa Fe Railway (BNSF), Canadian National Railway, Canadian Pacific Railway, COFC, CPKC (formerly Kansas City Southern), CSX Transportation, Norfolk Southern, Union Pacific Railroad. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 404 with my ERP?
Stacksync handles the full X12 404 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.
