X12

Inbound

COFC X12 404 Rail Carrier Shipment Information

COFC

The EDI 404 (Rail Carrier Shipment Information) document is used by COFC for electronic data interchange. It enables automated processing and compliance with COFC's trading partner requirements.

28segments

5loops

12mandatory

Book a demo

← All COFC transactions

Schema Reference

28 segments · X12 404 Rail Carrier Shipment Information

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

ZC101 Shipment Identification Number

O AN 1-30

ZC102 Equipment Initial

O AN 1-4

ZC103 Equipment Number

M AN 1-10

ZC104 Transaction Reference Number

M AN 1-15

ZC105 Transaction Reference Date

M DT 8-8

ZC106 Correction Indicator

M ID 2-2

ZC107 Standard Carrier Alpha Code

M ID 2-4

ZC108 Transportation Method/Type Code

M ID 1-2

BX01 Transaction Set Purpose Code

M ID 2-2

BX02 Transportation Method/Type Code

M ID 1-2

BX03 Shipment Method of Payment

M ID 2-2

BX04 Shipment Identification Number

O AN 1-30

BX05 Standard Carrier Alpha Code

O ID 2-4

BX06 Weight Unit Code

O ID 1-1

BX07 Shipment Qualifier

O ID 1-1

BNX01 Shipment Weight Code

O ID 1-1

BNX03 Billing Code

O ID 1-1

M301 Release Code

M ID 1-1

M302 Date

C DT 8-8

M303 Time

C TM 4-8

M304 Time Code

O ID 2-2

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

DTM03 Time

C TM 4-8

N7 Loop Repeat: 500

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

N711 Equipment Description Code

O ID 2-2

N715 Equipment Length

O N0 4-5

M701 Seal Number

M AN 2-15

IC01 Equipment Initial

M AN 1-4

IC02 Equipment Number

M AN 1-10

REF Loop Repeat: 99

REF01 Reference Identification Qualifier

M ID 2-3

REF03 Description

C AN 1-80

F902 City Name

M AN 2-30

F903 State or Province Code

M ID 2-2

D902 City Name

M AN 2-30

D903 State or Province Code

M ID 2-2

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

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

PER01 Contact Function Code

M ID 2-2

PER02 Name

O AN 1-60

PER03 Communication Number Qualifier

C ID 2-2

PER04 Communication Number

C AN 1-80

PER05 Communication Number Qualifier

C ID 2-2

PER06 Communication Number

C AN 1-80

R201 Standard Carrier Alpha Code

M ID 2-4

R202 Routing Sequence Code

M ID 1-2

R203 City Name

O AN 2-30

R205 Intermodal Service Code

O ID 1-2

R206 Transportation Method/Type Code

O ID 1-2

H301 Special Handling Code

C ID 2-3

H302 Special Handling Description

C AN 2-30

H303 Protective Service Code

O ID 1-4

H304 Vent Instruction Code

O ID 1-7

H305 Tariff Application Code

O ID 1-1

PS01 Protective Service Rule Code

M ID 3-9

PS02 Protective Service Code

M ID 1-4

LX Loop Repeat: 25

LX01 Assigned Number

M N0 1-6

L501 Lading Line Item Number

O N0 1-3

L502 Lading Description

O AN 1-50

L503 Commodity Code

C AN 1-30

L504 Commodity Code Qualifier

C ID 1-1

L0 Loop Repeat: 25

L001 Lading Line Item Number

O N0 1-3

L004 Weight

C R 1-10

L005 Weight Qualifier

C ID 1-2

L008 Lading Quantity

C N0 1-7

L009 Packaging Form Code

C ID 3-3

PI01 Reference Identification Qualifier

M ID 2-3

PI02 Reference Identification

M AN 1-30

PI03 Primary Publication Authority Code

O ID 2-2

PI05 Tariff Agency Code

O ID 1-4

PI06 Issuing Carrier Identifier

O AN 1-10

X101 Licensing Agency Code

O ID 1-1

X102 Export License Number

O AN 6-12

X103 Export License Status Code

O ID 1-1

X104 Date

O DT 8-8

X105 Export License Symbol Code

O ID 1-2

X106 Export License Control Code

O ID 1-1

X107 Country Code

O ID 2-3

X108 Schedule B Code

O ID 7-10

X109 International/Domestic Code

O ID 1-1

X110 Lading Quantity

O N0 1-7

X111 Lading Value

O R 2-9

X112 Export Filing Key Code

O ID 1-1

X113 Unit or Basis for Measurement Code

O ID 2-2

X114 Unit Price

O R 1-17

X115 U.S. Government License Type

O AN 1-1

X116 Identification Code

O AN 2-80

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating COFC EDI 404

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

Validate

Transform

Route

Monitor

Stacksync processes COFC EDI 404 (Rail Carrier Shipment Information) documents automatically — syncing data to your system in real time with no manual intervention required.

COFC EDI 404 FAQ

Common questions about 404 Rail Carrier Shipment Information transactions with COFC.

What is a COFC EDI 404 Rail Carrier Shipment Information?

The COFC EDI 404 Rail Carrier Shipment Information is an X12 transaction set used to exchange Rail Carrier Shipment Information data electronically between trading partners. As a inbound document, it standardizes the communication of Rail Carrier Shipment Information information between COFC and their suppliers, carriers, or partners. Stacksync processes COFC 404 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with COFC's requirements in real time.

How does Stacksync automate COFC EDI 404 Rail Carrier Shipment Information transactions?

Stacksync handles COFC EDI 404 Rail Carrier Shipment Information transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 404 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every COFC 404 document meets their specific formatting requirements before transmission or after receipt.

What are common COFC EDI 404 errors and how do I fix them?

Common errors in COFC EDI 404 Rail Carrier Shipment Information transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates COFC 404 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

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

Most COFC EDI 404 Rail Carrier Shipment Information integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between COFC's 404 format and your system, running test transactions, and completing COFC's certification process if required. Stacksync includes pre-built mappings for COFC's most common 404 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize COFC EDI 404 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how COFC EDI 404 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If COFC updates their 404 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate COFC EDI?