Skip to content
EDI X12 322

X12 transaction code

X12 322 Terminal Operations and Intermodal Ramp Activity

The EDI 322 (Terminal Operations and Intermodal Ramp Activity) document is used by Burlington Northern Santa Fe Railway (BNSF) for electronic data interchange. It enables automated processing and compliance with Burlington Northern Santa Fe Railway (BNSF)'s trading partner requirements.

Standard
X12
Code
322
Trading partners
6

Trading partners that support X12 322

6 partners, 6 channels. Click a channel for the full segment guideline.

FAQ

X12 322 questions

What is X12 322 Terminal Operations and Intermodal Ramp Activity?

X12 322 (Terminal Operations and Intermodal Ramp Activity) is an EDI transaction set defined by ANSI ASC X12 for exchanging terminal operations and intermodal ramp activity between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 6 Stacksync trading partners support this code across 6 channels.

Which trading partners use X12 322?

6 Stacksync partners accept X12 322: Burlington Northern Santa Fe Railway (BNSF), Canadian National Railway, Canadian Pacific Railway, COFC, CPKC (formerly Kansas City Southern), CSX Transportation. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.

How do I integrate X12 322 with my ERP?

Stacksync handles the full X12 322 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.