# EDI 866 Production Sequence Guide > What the EDI 866 Production Sequence is, how just-in-sequence (JIS) delivery works, its key segments, and a real X12 example. Covers JIT vs JIS in automotive. The EDI 866 Production Sequence is the X12 transaction an automaker sends a supplier to specify the exact order parts must arrive at the assembly line. It communicates just-in-sequence (JIS) delivery requirements, supplementing the 862 shipping schedule by adding sequence to firm demand. ## What Is an EDI 866? **An EDI 866 is a Production Sequence transaction, the X12 transaction set defined by the [ASC X12 standards body](https://x12.org/products/transaction-sets) that a manufacturer sends a supplier to communicate the exact order in which parts must arrive at the assembly line.** It is the backbone of just-in-sequence (JIS) delivery. The 866 is used almost entirely in automotive. On a mixed-model assembly line, a red sedan with a leather interior might be followed by a white truck with cloth seats. The supplier of seats has to deliver them in that exact build order, so the right seat reaches the right vehicle at the right moment. The 866 tells the supplier what that sequence is. In EDIFACT, the equivalent is the DELJIT message used in just-in-sequence mode, often called DELJIT-JS, defined in the [UN/EDIFACT message directory](https://unece.org/trade/uncefact/unedifact). Both carry line-side sequence detail. **Who sends it?** The manufacturer (the automaker or OEM) sends the 866 to a component supplier. **When is it sent?** Close to production, once the build sequence for the line is set, often hours ahead of the actual assembly slot. **Why does it matter?** A wrong or late 866 stops the line. In sequenced production there is no buffer stock to fall back on, so the delivery order is as important as the delivery itself. ## JIT vs JIS **Just-in-time (JIT) delivers the right parts in the right quantity at the right time. Just-in-sequence (JIS) adds one more constraint: the right order.** The 866 is what makes JIS possible. | Model | What it controls | Example | |-------|------------------|---------| | **JIT** (Just-in-Time) | Quantity and timing, so parts arrive as needed without excess inventory | 200 brake calipers delivered at 8am for the morning shift | | **JIS** (Just-in-Sequence) | Quantity, timing, and the exact build order | Seat sets delivered in the precise order vehicles hit the line | JIT reduces inventory. JIS reduces both inventory and line-side sorting. With JIS, the supplier does the sequencing off-site, so parts come off the truck already in build order and go straight to the line. The 866 carries the sequence that makes that work. ## Where the 866 Fits with the 830 and 862 **The 866 does not stand alone. It supplements the planning and shipping schedules that come before it.** Automotive suppliers usually receive a cascade of three documents, each firmer and closer to production than the last: 1. **[830 Planning Schedule](/guides/edi/830-planning-schedule)** - Longer-range forecast, used for capacity and material planning 2. **[862 Shipping Schedule](/guides/edi/862-shipping-schedule)** - Firm, short-term shipping requirements that authorize actual delivery 3. **866 Production Sequence** - Adds the exact build sequence to the 862's firm requirements Think of it as zoom levels. The 830 says "here is roughly what we will need over the coming weeks." The 862 says "ship these exact quantities on these exact days." The 866 says "and deliver them in this exact order." After delivery, the supplier sends an [856 ship notice](/guides/edi/856-ship-notice) to confirm what left the dock. ## Key Segments Explained Here is a breakdown of the segments you work with in an 866 transaction set: | Segment | Name | Purpose | |---------|------|---------| | **ST** | Transaction Set Header | Identifies the start of the 866 and assigns a control number | | **BSS** | Beginning Segment for Production Sequence | Carries the purpose code, reference number, dates, and schedule type | | **LIN** | Item Identification | Identifies the part being sequenced | | **PRS** | Part Release Status | Carries the production sequence detail and release status for the part | | **REF** | Reference Identification | Ties the line to a job number, VIN, or serial reference | | **SE** | Transaction Set Trailer | Marks the end of the 866 | ### BSS - Beginning Segment for Production Sequence The BSS segment sets the context for the sequence. It states the purpose, the reference number, and the schedule dates. - **BSS01**: Transaction Set Purpose Code (00 = Original, 05 = Replace) - **BSS02**: Reference number for the sequence schedule - **BSS03**: Date the schedule was generated - **BSS04**: Schedule Type Qualifier - **BSS05-BSS06**: Schedule start and end dates ### LIN and PRS - Part and Sequence Detail The LIN segment names the part. The PRS segment carries the production sequence and release status that tell the supplier where in the build order the part belongs. - **LIN02-LIN03**: Product ID qualifier and part number - **PRS01**: Part Release Status Code (the sequence or release indicator) - **REF**: Job number, VIN, or serial reference that pins the part to a specific vehicle ## Example: Complete 866 Transaction Here is what a typical 866 looks like in raw X12 format. This example sequences two parts against specific job references: ```edi ISA*00* *00* *ZZ*AUTOMAKEROEM *ZZ*SEATSUPPLIER *260724*0700*U*00401*000000082*0*P*:~ GS*SQ*AUTOMAKEROEM*SEATSUPPLIER*20260724*0700*82*X*004010~ ST*866*0001~ BSS*00*SEQ-55120*20260724*DL*20260724*20260724~ LIN**BP*SEAT-FRONT-LH~ PRS*A~ REF*RN*JOB-001~ LIN**BP*SEAT-FRONT-LH~ PRS*A~ REF*RN*JOB-002~ SE*9*0001~ GE*1*82~ IEA*1*000000082~ ``` The GS01 functional identifier code for an 866 is `SQ` (Production Sequence). Each LIN and PRS pair is tied to a job reference in the REF segment, so the supplier knows which vehicle each part feeds. Validate the file structure with the [free EDI Inspector](/edi-inspector) before you send or accept an 866. ## Why Sequence Errors Are Expensive **In sequenced production, a delivery in the wrong order is as bad as no delivery at all.** There is no line-side inventory to cover a mistake, which is the whole point of JIS. If the seats arrive out of sequence, the assembly line either stops or installs the wrong seat in a vehicle. Both outcomes are costly. Automotive OEMs measure supplier performance on sequence accuracy, and a supplier that repeatedly breaks sequence risks losing the contract. That is why the 866 has to be processed the moment it arrives, mapped straight into the supplier's line-side delivery system without manual re-keying. For suppliers running a mix of EDI schedules and other order formats, OrderSync handles [multi-format order processing](/multi-format-orders) and [ERP integration](/erp-integration) through a single pipeline. ## Frequently Asked Questions ### What is the difference between an EDI 866 and an EDI 862? The 862 shipping schedule tells a supplier what quantities to ship and when. The 866 production sequence adds the exact order in which those parts must arrive at the line. The 862 is firm demand. The 866 layers sequence on top of it, so the two work together in just-in-sequence production. ### What is just-in-sequence (JIS) delivery? Just-in-sequence is a delivery model where parts arrive at the assembly line already sorted into the exact build order of the vehicles they feed. It goes one step beyond just-in-time, which controls quantity and timing but not order. The EDI 866 carries the sequence information that makes JIS work. ### Which industries use the EDI 866? The 866 is used almost entirely in automotive manufacturing, where mixed-model assembly lines demand sequenced part delivery. Component suppliers to automakers receive 866 documents alongside the [830 planning schedule](/guides/edi/830-planning-schedule) and [862 shipping schedule](/guides/edi/862-shipping-schedule). It rarely appears outside automotive and its close supply tiers. ### Is the EDI 866 the same as EDIFACT DELJIT? They serve the same purpose. The 866 is the X12 (North American) transaction set for production sequence. The equivalent [UN/EDIFACT](https://unece.org/trade/uncefact/unedifact) message is DELJIT used in just-in-sequence mode, often written DELJIT-JS. Both communicate sequenced line-side delivery requirements to a supplier. ## Related Transaction Sets - **[EDI 862 Shipping Schedule](/guides/edi/862-shipping-schedule)** - The firm shipping requirements the 866 sequences - **[EDI 830 Planning Schedule](/guides/edi/830-planning-schedule)** - The longer-range forecast that precedes both - **[EDI 856 Ship Notice](/guides/edi/856-ship-notice)** - The supplier's confirmation of what shipped - **[EDI order lifecycle](/guides/edi/edi-order-lifecycle)** - The full document chain across the order process ## Need Help? Use our [free EDI Inspector](/edi-inspector) to validate your 866 documents before you send them, or see how OrderSync connects EDI schedules to your [ERP integration](/erp-integration).