COFC EDI 322 Terminal Operations and Intermodal Ramp Activity

Schema Reference

14 segments · X12 322 Terminal Operations and Intermodal Ramp Activity

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Interchange Control Standards Identifier

M ID 1-1

ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

Q501 Shipment Status Code

O ID 1-2

Q502 Date

O DT 8-8

Q503 Time

C TM 4-8

Q504 Time Code

C ID 2-2

Q505 Status Reason Code

O ID 3-3

Q506 City Name

C AN 2-30

Q507 State or Province Code

O ID 2-2

Q508 Country Code

O ID 2-3

N7 Loop Repeat: 1,000

N701 Equipment Initial

O AN 1-4

N702 Equipment Number

M AN 1-10

N703 Weight

C R 1-10

N704 Weight Qualifier

C ID 1-2

N708 Volume

C R 1-8

N709 Volume Unit Qualifier

C ID 1-1

N711 Equipment Description Code

O ID 2-2

N712 Standard Carrier Alpha Code

O ID 2-4

N715 Equipment Length

O N0 4-5

N717 Weight Unit Code

O ID 1-1

N718 Equipment Number Check Digit

O N0 1-1

N720 Height

O R 1-8

N721 Width

O R 1-8

N722 Equipment Type

O ID 4-4

N723 Standard Carrier Alpha Code

O ID 2-4

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

DTM03 Time

C TM 4-8

DTM04 Time Code

O ID 2-2

M701 Seal Number

M AN 2-15

M702 Seal Number

O AN 2-15

M703 Seal Number

O AN 2-15

W201 Equipment Initial

M AN 1-4

W202 Equipment Number

M AN 1-10

W203 Commodity Code

O AN 1-30

W204 Equipment Description Code

M ID 2-2

W205 Equipment Status Code

M ID 1-2

W211 Equipment Initial

C AN 1-4

W212 Equipment Number

C AN 1-10

NA03 Equipment Initial

M AN 1-4

NA04 Equipment Number

M AN 1-10

NA05 Cross Reference Type Code

O ID 1-1

R4 Loop Repeat: 20

R401 Port or Terminal Function Code

M ID 1-1

R402 Location Qualifier

C ID 1-2

R403 Location Identifier

C AN 1-30

R404 Port Name

O AN 2-24

R405 Country Code

O ID 2-3

R406 Terminal Name

O AN 2-30

R407 Pier Number

O AN 1-4

R408 State or Province Code

O ID 2-2

H301 Special Handling Code

C ID 2-3

H302 Special Handling Description

C AN 2-30

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

N903 Free-form Description

C AN 1-45

N904 Date

O DT 8-8

N905 Time

C TM 4-8

N906 Time Code

O ID 2-2

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating COFC EDI 322

Stacksync validates, transforms, and delivers your 322 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync processes COFC EDI 322 (Terminal Operations and Intermodal Ramp Activity) documents automatically — syncing data to your system in real time with no manual intervention required.

COFC EDI 322 FAQ

Common questions about 322 Terminal Operations and Intermodal Ramp Activity transactions with COFC.

How long does it take to set up COFC EDI with Stacksync?

Most suppliers are fully connected and processing live COFC EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with COFC?

No. Stacksync handles the entire EDI transport layer. We connect directly to COFC's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with COFC compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for COFC?

Stacksync supports all EDI document types required by COFC — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect COFC EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between COFC's EDI network and your system in real time.

What happens when COFC updates their EDI specifications?

Stacksync monitors COFC's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.