EDI 862 Shipping Schedule: Near-Term Release Guide

The EDI 862 Shipping Schedule is how a buyer turns a longer-range 830 forecast into exact, dated ship instructions for the next few days. It does not set prices or create a new agreement. It points back at a blanket purchase order and the planning schedule already in play, then says: deliver these quantities, to this dock, on these days and at these times. In just-in-time manufacturing, the 862 is the document that keeps an assembly line fed.

This guide covers what the 862 contains, how it differs from the 830 and 866, a live example you can open segment by segment, every segment you will map (BSS, LIN, UIT, FST, JIT, SHP), and the mistakes that cause premium freight and line-down calls.

What Is an EDI 862?

An EDI 862 is the Shipping Schedule transaction set defined by the ASC X12 standards body, used by a customer to give a supplier precise shipping schedule requirements. The X12 definition says it is meant to supplement the 830 Planning Schedule: it can supersede certain shipping and delivery information from a previous 830, but it does not replace the 830, and it "shall not be used to authorize labor, materials or other resources." Because it can be sent far more often than the 830, it supports just-in-time manufacturing.

Authoritative references for 862 work:

• The X12 transaction set catalog lists the 862 with the 830 and 866 schedules
• The Stedi X12 004010 reference for the 862 shows the segment order and loops, including the JIT loop, and its BSS segment page defines each header element
• The EDI Academy 830 and 862 reference explains how the 862 supplements the 830
• Each OEM publishes its own 862 implementation guide, which sets the horizon, cadence, codes and how it reports cumulative receipts

Who sends it? The buyer (an OEM, assembler or other manufacturer), often from the individual plant rather than the central planning group.

When is it sent? On a short cadence, commonly daily and sometimes more than once a day, covering a horizon of days to a couple of weeks.

Why does it matter? The 862 is the call-off. Reading it wrong, or shipping to a stale schedule, leads directly to premium freight, a line stoppage, or parts the plant did not ask for.

EDI 862 vs EDI 830: Plan vs Ship

The 830 and 862 work as a pair, and confusing them is the most common mistake on the supplier side. For the longer comparison, see EDI 830 vs 862.

The 830 lets a supplier buy material and reserve capacity. The 862 then says which of that demand to deliver now. Where the two disagree inside the 862's horizon, the 862 is the instruction for that window. If an 862 asks for more than the 830 ever authorized, treat it as a question for the buyer's scheduler before you ship.

When parts must also arrive in build order, the 866 Production Sequence adds the sequence on top of the 862's quantities and times.

Interactive Example: OEM Shipping Schedule (862, BSS01 05)

The assembly plant from our 830 example sends a replacement shipping schedule (BSS01 05) for November 10 to 13. BSS07 is release REL-0458, BSS08 points to the 830 it supplements (SCH-2026-W45) and BSS10 is the blanket PO. Each of the four days has a firm (C) discrete (D) requirement of 400. The first two days split into two JIT deliveries: 200 at 06:00 and 200 at 14:00. REF*DK names the dock, and SHP reports the last receipt and the cumulative received.

Use the Plain English tab for a readable summary, or click any segment to break it down element by element.

862 Structure at a Glance

UIT is mandatory in every 862 LIN loop, which is a difference from the 830, where it is optional.

Key Segments Explained

BSS: Beginning Segment for Shipping Schedule

BSS*05*SS-20261106-01*20261106*DL*20261110*20261113*REL-0458*SCH-2026-W45**4500188421*A~

At least one of BSS07 and BSS08 must be present. Your 856 ASN usually has to quote the release or PO from here, so map both.

LIN and UIT

LIN**BP*430-00012-A*VP*SHROUD100~
UIT*EA~

LIN carries the buyer's part number (BP) and the vendor's (VP), the same pair as in the 830. Map on the buyer's part number, because that is what the plant's receiving system matches against. UIT is the unit of measure for every quantity in the loop.

FST: Forecast Schedule

FST*400*C*D*20261110~

The same FST segment and code lists as the 830 apply. In an 862 the near-term quantities are normally firm. If your partner also sends planning (D) buckets for a short look-ahead, treat them exactly as you would on an 830: information, not a release.

JIT: Just-In-Time Schedule

JIT*200*0600~
JIT*200*1400~

JIT follows an FST and splits its quantity by time of day: JIT01 is the quantity and JIT02 the time on a 24-hour clock. Here the 400 for November 10 arrives as 200 at 06:00 and 200 at 14:00. Whether the time is a ship time or a dock arrival time follows BSS04.

REF: Dock and Line References

REF*DK*DOCK 7~ names the receiving dock. Plants also use REF in the LIN loop for line-feed locations, storage locations or kanban numbers, with qualifiers set in their guide.

SHP: Shipped/Received Information

SHP*01*400*050*20261105~
SHP*02*42200*051*20260105**20261105~

The plant last received 400 on November 5 and has received 42,200 cumulative since January 5. If that does not match your shipped cumulative, find the difference before you ship. Parts still in transit are not in the plant's received total yet, so they explain part of any gap; anything beyond that needs a call to the plant's scheduler. For the full reconciliation, see cumulative quantity and CUM accounting.

SDP: Ship/Delivery Pattern

Some plants send a routine pattern instead of, or as well as, exact dates: SDP*O*D~ reads "daily, Monday to Friday, mornings". The codes are the same as on the 830.

CTT: Transaction Totals

CTT*1*1600~ reports one LIN item and FST quantities that add up to 1,600. Check it on receipt; a mismatch means a bucket went missing.

Where the 862 Sits in the Order Lifecycle

In a blanket-PO, just-in-time manufacturing relationship, the 862 is the trigger to ship:

1. Blanket 850 Purchase Order: the buyer establishes the agreement, pricing and item list
2. 830 Planning Schedule: rolling forecast, firm releases and authorizations
3. 862 Shipping Schedule: exact near-term ship or delivery requirements
4. 866 Production Sequence (sequenced parts only): the build order
5. 856 Ship Notice/ASN: you report each shipment, quoting the release and PO
6. 810 Invoice: you bill against the blanket PO

A late or misread 862 ripples straight into the ASN and the delivery itself, which is why supplier schedulers watch it closely.

Common 862 Errors and How to Prevent Them

862 Implementation Checklist

• Get the plant's 862 guide and confirm the X12 version
• Confirm BSS01 purpose codes and whether every 862 replaces the last
• Confirm BSS04 (delivery or ship dates) and BSS11 (discrete or cumulative)
• Confirm FST02 and FST03 codes, and whether it sends JIT times or SDP patterns
• Confirm the references it expects back on your 856 (release, PO, dock)
• Agree the cumulative start date and how SHP is reported
• Test a replace, a cancellation and a JIT schedule before going live
• Monitor 997s and alert on missing schedules

Reading 862s With OrderSync

Paste any 862 into the free EDI inspector to see it parsed segment by segment, with a plain-English summary of each day's firm quantity, the JIT delivery times under it, and the cumulative received. It also explains structural errors when a file will not load.

OrderSync's main work is on the orders around your schedules. Suppliers who ship to an OEM on 830s and 862s usually also take POs from aftermarket, distribution and smaller industrial customers as 850s, emails, PDFs and spreadsheets. OrderSync reads those in any format, matches customers, items and units to your catalog, and outputs valid X12 or clean data for your ERP. Read more about EDI for automotive parts suppliers and contract manufacturers, or book a 15-minute walkthrough.

Frequently Asked Questions