972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Master data

EDI 435 Standard Transportation Commodity Code Master

The X12 document used to transmit Standard Transportation Commodity Codes (STCC) and associated information.

Sent by
Code maintenance authority or rail industry reference site
Received by
Railroads, shippers and other code users
Standard
ANSI ASC X12

What is an EDI 435?

The EDI 435 Standard Transportation Commodity Code Master is the ANSI X12 transaction set used to transmit Standard Transportation Commodity Codes and associated information.

STCC codes classify the commodities moved by rail in North America. They appear on waybills, rates and statistics, and hazardous materials have their own code ranges. Distributing the master file keeps every party classifying freight the same way. Shippers must classify each product with the right code, since it affects rates, statistics and hazardous materials handling. Code updates should be loaded before new codes appear on shipments.

How the EDI 435 worksDiagram of the EDI 435 Standard Transportation Commodity Code Master. Code maintenance authority or rail industry reference site sends it to railroads, shippers and other code users. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required SID loop with SID (Standard Transportation Commodity Code Identification). 2 optional loops are listed by their first segment.How the EDI 435 worksStandard Transportation Commodity Code Master: who sends it, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 435SENDERCode maintenanceauthority or railindustry reference siteRECEIVERRailroads, shippersand other code users997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RKGS … GETransaction set 435ST … SEHEADINGRequired loop SID · repeats up to 9,999SIDStandard Transportation Commodity Code Identification+ 2 optional loops, starting with:LQLXBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 435. Your trading partner's implementation guide adds its own requirements.
How the EDI 435 worksDiagram of the EDI 435 Standard Transportation Commodity Code Master. Code maintenance authority or rail industry reference site sends it to railroads, shippers and other code users. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required SID loop with SID (Standard Transportation Commodity Code Identification). 2 optional loops are listed by their first segment.How the EDI 435 worksStandard Transportation Commodity CodeMaster: who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 435SENDERCodemaintenanceauthority or railindustryreference siteRECEIVERRailroads,shippers andother code users997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code RK (GS … GE)Transaction set 435 (ST … SE)HEADINGRequired loop SID · repeats up to9,999SIDStandard TransportationCommodity CodeIdentification+ 2 optional loops, starting with:LQLXBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 435. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 435, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 435 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Distributing STCC code updates
  • Loading commodity master data
  • Updating hazardous materials code information

Where it fits in the document flow

This document 435 Standard Transportation Commodity Code Master
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 435 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • SID
  • LQ
  • LX
  • SE

Practical example

The 435 in practice

New commodity codes are added and some descriptions change. The code master update is distributed with a 435, and a shipper loads it so its rail bills of lading use the current codes for each product.

Implementation

Implementation considerations for the 435

  • Load updates before codes appear on shipments.
  • Map product master data to the correct STCC codes.
  • Pay particular attention to hazardous materials codes.
  • Retire obsolete codes carefully, with effective dates.

How ECOM helps

Automate the 435 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related master data documents

All 25 master data documents

Need help with the EDI 435?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us