To start and identify an interchange of zero or more functional groups and interchange-related control segments
Burlington Northern Santa Fe Railway (BNSF) X12 322 Terminal Operations and Intermodal Ramp Activity
X12 322 (Terminal Operations and Intermodal Ramp Activity) is the EDI transaction exchanged between Burlington Northern Santa Fe Railway (BNSF) (Burlington Northern Santa Fe Railway (BNSF)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 15
- Loops
- 3
- X12 322
- All partners ↗
Transaction context
Where 322 Terminal Operations and Intermodal Ramp Activity fits on Burlington Northern Santa Fe Railway (BNSF)
- Burlington Northern Santa Fe Railway (BNSF) channels
- 1 of 1
- Trading partners
- 6
- Channels
- 6
1 of Burlington Northern Santa Fe Railway (BNSF)'s 1 channel carries 322
partners across the Stacksync network trade 322
channels network-wide carry 322
Most common alongside 322
The 322 reports terminal and intermodal ramp activity, chiefly ingate and outgate events, to the parties authorized on a shipment. Each event identifies the equipment initial and number, seal numbers, event status with date and time, and the terminal or port location, so carriers and shippers can track custody of a container or trailer as it moves through marine terminals and rail ramps. A terminal operator, port authority, or intermodal ramp sends the 322 to authorized parties to the shipment, such as ocean carriers, railroads, motor carriers, and shippers.
When it fires: A container or trailer passes an ingate or outgate at a marine terminal or intermodal rail ramp and the gate system records the movement.
Common 322 rejection causes
- Equipment identification mismatches: the equipment initial and number in N7 must match the equipment master and related shipment records, and keying differences leave gate events unmatched to a shipment.
- Seal numbers missing or inconsistent between the ingate and outgate events, which triggers seal-integrity exception handling.
- Wrong or missing terminal or ramp location coding in the R4 segment, which attributes the gate event to the wrong facility.
- Late event transmission: gate timestamps drive equipment tracking and time-based charges, so delayed 322s distort dwell measurement and dispute resolution.
Specification summary
X12 322 Terminal Operations and Intermodal Ramp Activity at the element level
The X12 322 specification defines 26 segments carrying 113 data elements, 43 of which are mandatory.
- Segments
- 26
- Data elements
- 113
- Mandatory elements
- 43
| Segment | Elements | Mandatory |
|---|---|---|
| N7 | 14 | 1 |
| M7 | 4 | 1 |
| W09 | 3 | 1 |
| W2 | 11 | 4 |
| NA | 5 | 2 |
| R4 | 6 | 1 |
| DTM | 4 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| K1 | 2 | 1 |
| N9 | 6 | 1 |
| H1 | 1 | 1 |
Key identifiers in 322
- Equipment Number
- Seal Number
- Equipment Description Code
- Equipment Initial
- Equipment Status Code
- Port or Terminal Function Code
- Date/Time Qualifier
- Entity Identifier Code
Full segment guideline — 15 segments 3 loops · X12 322 Terminal Operations and Intermodal Ramp Activity
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 specify the status of the shipment in terms of dates, time, reference numbers, and location
N7 Loop Repeat: 1,000
To identify the equipment
To specify pertinent dates and times
To record seal numbers used and the organization that applied the seals
To identify equipment and the commodity being carried
To cross-reference additional equipment to a primary piece of equipment
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 provide vessel details and voyage number
R4 Loop Repeat: 20
Contractual or operational port or point relevant to the movement of the cargo
To specify special handling instructions in coded or free-form format
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To transmit identifying information as specified by the Reference Identification Qualifier
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
Burlington Northern Santa Fe Railway (BNSF) Burlington Northern Santa Fe Railway (BNSF) EDI 322 FAQ
Common questions about 322 Terminal Operations and Intermodal Ramp Activity on the Burlington Northern Santa Fe Railway (BNSF) channel.
What is X12 322 Terminal Operations and Intermodal Ramp Activity?
X12 322 (Terminal Operations and Intermodal Ramp Activity) is the EDI transaction set used to exchange terminal operations and intermodal ramp activity data. Burlington Northern Santa Fe Railway (BNSF)'s Burlington Northern Santa Fe Railway (BNSF) channel requires it from trading partners.
Does Burlington Northern Santa Fe Railway (BNSF) Burlington Northern Santa Fe Railway (BNSF) require 322 for trading partners?
Yes, Burlington Northern Santa Fe Railway (BNSF) (Burlington Northern Santa Fe Railway (BNSF)) supports X12 322 Terminal Operations and Intermodal Ramp Activity. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Burlington Northern Santa Fe Railway (BNSF) 322 with Stacksync?
Most companies go live with Burlington Northern Santa Fe Railway (BNSF) 322 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 322 on Burlington Northern Santa Fe Railway (BNSF)?
On Burlington Northern Santa Fe Railway (BNSF), X12 322 is typically exchanged alongside 404 Rail Carrier Shipment Information, 410 Rail Carrier Freight Details And Invoice. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Burlington Northern Santa Fe Railway (BNSF) EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
