EDI 862 Shipping Schedule: The Complete Guide (2026)

Where the 830 planning schedule sketches the coming months, something has to say ship now — precisely, and with authority. In schedule-driven manufacturing that instruction is the EDI 862 Shipping Schedule: the firm, near-term release that converts a standing forecast into freight on a truck this week, tomorrow, or this afternoon.

Firm means firm

A BSS header opens the schedule with its dates and purpose; LIN loops name each part; FST segments carry the requirement quantities against dates — and unlike the 830's mixed horizon, these are ship authorizations. Dock codes, delivery windows, and reference numbers tie each requirement to a receiving location and, in tighter programs, a time slot. Where an 862 and the standing 830 disagree, the 862 wins: it exists precisely to give the buyer a faster steering wheel than the weekly forecast cycle.

That authority cuts both ways. Quantities on an 862 are what the customer's line is counting on, so both over-shipping and under-shipping against it are visible failures — this isn't retail, where a fill rate in the nineties earns a stern email. A missed release in a just-in-time program can idle an assembly line, and supplier scorecards in these industries treat delivery performance accordingly.

Cumulative-quantity conventions raise the stakes further. Many programs track requirements as running totals against the blanket agreement, so a missed or double-counted release doesn't just affect one shipment — it skews every subsequent schedule until the discrepancy is found and reconciled with the customer.

Built for execution, not planning

The practical distinction between the two schedule documents is which department consumes them. The 830 belongs to planners — capacity, procurement, inventory strategy. The 862 belongs to the warehouse: it should flow directly into pick-and-ship execution with as little human translation as possible. Programs running at daily cadence leave no room for a coordinator re-keying releases into the WMS; the schedule lands, allocations update, pick lists reflect it, and the dock works to it.

Two integration details make or break that flow:

• Net-change against the prior schedule. Like its planning sibling, each 862 supersedes the last. The system must compute what changed — a pulled-ahead date, a bumped quantity — and adjust open work, not append duplicates.
• Reference discipline. Release, part, and dock references from the 862 must ride through to the 856 ASN announcing the shipment. JIT receiving reconciles arrivals against releases; an ASN that can't be tied to its authorization is a discrepancy even when the parts are right.

It's worth rehearsing the failure path once: a schedule arrives during a plant shutdown, nobody processes it, and the customer's expediter calls before your planner has seen the release. High-cadence programs need coverage rules — alerts on unprocessed schedules, not just on failed ones.

Every inbound schedule also gets receipted with a 997 within minutes — table stakes, but in high-cadence programs the absence of one is often the first sign a transmission path failed.

Where EDISQ fits

EDISQ lands 862s straight into your ERP's release structures — net-changed, cross-referenced, and linked to the governing 830 — and generates the ASN leg from your ship confirmations, with the segment-level requirements of each customer's spec handled in the map. The whole schedule-driven pattern, from forecast through release to ship notice, is laid out in our manufacturing solution.

Cost at cadence

Daily schedules from multiple plants add up to real document counts over a month, which is exactly the shape EDISQ's pricing favors: after 25 free documents, the per-document rate starts at $0.50 and declines through the tiers to $0.10, billed marginally, with no mapping or setup charges — network connectivity included. High-cadence programs get cheaper per document as they grow, which is how it should work.

FAQ