EDI 322 vs. 301: what your gate systems need

Terminal operations messaging leans on a small set of EDI transactions, and the two that cause the most confusion during onboarding are the 322 terminal operations activity message and the 301 booking confirmation.

"Most onboarding delays are mapping problems, not connectivity problems." (Illustrative)

The 322 reports what physically happened to a container at the terminal — gate-in, gate-out, discharge, load. The 301 confirms a booking against a vessel and voyage before any of that movement begins. Feeding one into a workflow expecting the other is the single most common cause of a stalled integration.

What to verify before go-live

• Container check digit and ISO type mapping agreed with the carrier
• Event codes matched to your terminal move types
• Acknowledgement handling for rejected and duplicate messages

With the mapping settled up front, a new carrier connection is a configuration exercise rather than a project.