Skip to content
EDI X12 862

X12 transaction code

X12 862 Shipping Schedule

Stop Mapping. Start Trading.

Standard
X12
Code
862
Trading partners
3

Specification summary

X12 862 Shipping Schedule at the element level

The X12 862 specification defines 22 segments carrying 74 data elements, 50 of which are mandatory.

Segments
22
Data elements
74
Mandatory elements
50
Segments with mandatory elements
Segment Elements Mandatory
BSS 8 7
N1 3 1
LIN 4 2
REF 2 1
PER 4 1
FST 6 4
JIT 2 2
TD3 2 1
CTT 2 1
Key identifiers in 862
  • Transaction Set Purpose Code
  • Reference Number
  • Date
  • Forecast Type Qualifier
  • Forecast Quantity Qualifier
  • Entity Identifier Code
  • Product/Service ID Qualifier
  • Product/Service ID

Usage breakdown

Who trades X12 862 Shipping Schedule

862 is used most heavily in agriculture, manufacturing & industrial and automotive.

The 862 carries a buyer's firm, near-term shipping requirements: exact quantities, ship or delivery dates, and ship-to locations, down to time-of-day via the JIT segment. It supplements a previously issued 830 planning schedule, superseding the forecast's shipping and delivery detail without replacing the 830 itself. It exists to support just-in-time manufacturing, where releases are issued daily or more often and can be triggered by inventory falling below a restock level. Sent by the buyer, typically a manufacturing plant running just-in-time replenishment, to its supplier; the 830 forecast and 862 releases operate as a pair. Inventory of a component at the buyer's plant drops below its restock threshold, or the plant firms its short-term build plan, and the scheduling system releases an 862 to the supplier.

By industry

  • agriculture 10 channels
  • manufacturing & industrial 1 channel
  • automotive 1 channel

By network

  • Saicits 1 channel
Largest 862 implementations

FAQ

X12 862 questions

What is X12 862 Shipping Schedule?

X12 862 (Shipping Schedule) is an EDI transaction set defined by ANSI ASC X12 for exchanging shipping schedule between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 3 Stacksync trading partners support this code across 12 channels.

Which trading partners use X12 862?

3 Stacksync partners accept X12 862: Ford Motor Company, John Deere, John Deere Mexico. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.

How do I integrate X12 862 with my ERP?

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