Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 transaction set reference
X12 862 — Shipping Schedule
The X12 862 shipping schedule is sent by a buyer to a supplier to authorize precise ship/delivery quantities and timing, typically supplementing the 830 planning schedule in just-in-time manufacturing.
EDI 862 facts
- GS01 functional ID for 862 groups is SS — shipping-schedule traffic is grouped separately from purchase orders.
- 862 firm ship authorizations typically override or refine the near-term portion of the 830 planning schedule.
- SignalEDI normalizes BSS/FST schedule data into structured JSON so planners can reconcile firm vs forecast demand.
Where EDI 862 fits
- Direction
- Buyer / manufacturer → supplier
- GS functional ID
- SS
- Workflow position
- 862 refines the longer-range 830 planning schedule with firm short-term ship authorizations; suppliers ship against it and confirm with 856 ASN.
Related sets: 830, 850, 856, 997 · Document guide
Key segments in EDI 862
| Segment | Role |
|---|---|
| ST | Opens transaction set 862 and assigns ST02 control number. |
| BSS | Beginning segment — purpose code, schedule/release number, and date. |
| N1 | Ship-to and supplier party identification with qualifier codes. |
| LIN | Item identification for the scheduled part or product. |
| FST | Forecast/ship schedule detail — quantity, qualifier, and date. |
| SE | Closes the transaction set; segment count must match. |
Sample EDI 862
ST*862*0001~ BSS*05*REL2026*20260609*DL*20260601*20260630~ N1*ST*ASSEMBLY PLANT*92*PLANT01~ LIN*1*BP*PART-100~ FST*500*C*D*20260615~ SE*6*0001~
Validate samples with the free EDI validator.
Send EDI 862 with SignalEDI
// Webhook: document.received (inbound 862) // Correlate BSS release number and FST dates to planning schedule (830)
Your side can reach partner-ready setup in days, not weeks — partner certification calendars may still take longer. See the API quickstart.
Common EDI 862 errors
- FST quantities or dates conflicting with the underlying 830 planning schedule
- Missing LIN item identification for a scheduled part
- BSS purpose code mismatch (add vs replace) against partner expectation
- Ship-to N1 ID not matching the plant/dock enrolled by the partner
Related reference
FAQ
EDI 862 FAQ
The 830 is a planning/forecast schedule over a longer horizon; the 862 provides firm, near-term shipping authorizations that suppliers ship against.
The buyer or manufacturer sends the 862 to the supplier, most often in automotive and just-in-time manufacturing programs.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees on core plans, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
Supports HIPAA complianceBAA path documentedSecure API + webhooksNo per-document fees on core plans
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with handling that supports HIPAA compliance and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”