EDI 866 vs 862: Production Sequence vs. Shipping Schedule

That gap is the difference between the EDI 862 Shipping Schedule and the EDI 866 Production Sequence. If you've just been awarded a sequenced program, or a customer has asked whether you can "receive 866s," this article explains what the 866 does, how it works alongside the 862, and what it demands from your shipping floor.

Both documents come from your customer, and both can cover the same parts on the same day. They answer different questions.

The 866 Production Sequence is an ANSI X12 transaction set that lets the receiver of goods specify the order in which shipments arrive, the order in which goods are unloaded, or both, so that parts enter material handling or production in a defined sequence. In automotive, that sequence is usually the order vehicles will move down the customer's assembly line. You'll also hear it called a line sequence, a sequenced call-off, or in-line vehicle sequencing (ILVS).

Why sequenced supply exists

Mixed-model assembly lines build different trims, options and configurations back to back. For large or high-variant parts such as seats, consoles, cockpit modules or bumpers, the plant can't hold every variant at the station. Instead, it asks the supplier to deliver parts already sorted into build order, so each part arrives at the station just before the vehicle it belongs to. That's just-in-sequence (JIS) supply: just-in-time controls quantity and timing, and just-in-sequence adds order.

The trade-off is that there's little or no line-side buffer. A part in the wrong position doesn't sit in a rack until someone notices. It shows up at the station, on the wrong vehicle, right away.

What an 866 typically carries

At a conceptual level, most 866s include:

• A header with the schedule number, issue date, horizon and whether this is an original or a replacement sequence.
• The parties: the plant or line receiving the parts and the supplier shipping them.
• Delivery windows, each opening a block of sequenced parts.
• Sequenced line items: a load or job sequence number, the buyer's part number and, in many programs, a vehicle reference such as a VIN or chassis number.
• Totals that let you check the file is complete.

Here's a simplified, illustrative excerpt. It isn't any customer's specification.

Which qualifiers a customer sends, where the vehicle reference lives, and in what order, all vary. Map by qualifier, not by position, and test against the plant's real files. If you're new to how X12 transaction sets are built, our overview of EDI standards is a good starting point.

Why some definitions sound different

If you search for the 866, you'll find two descriptions that don't seem to match. Some describe it as a request for the order in which shipments arrive at a dock or are unloaded from a truck. Others describe it as the vehicle build sequence. Both come from the same standard. The X12 definition is written broadly enough to cover dock arrival and unloading order. In automotive, OEMs use it for the narrower, higher-stakes case: the order parts must reach the line to match the vehicles being built.

Think of your customer's schedules as layers, each closer to the moment of production than the one before. Your 856 then confirms what actually left your dock.

Not every program sends all three schedules. Some customers send an 830 and an 866 with no 862. Others carry sequence detail in a different document or standard. For customers that issue purchase orders instead of releases, see how the EDI 850 works in automotive. For how the 830 and 862 divide planning and shipping, and how CUMs connect them, read EDI 830 vs 862.

Here's the scenario from the top of this article, laid out position by position. One part family, three variants, one delivery window. All part numbers and quantities are illustrative.

What doesn't change: your CUMs

Notice that both loads ship the same quantity of each part. In this example, the 866 changes the order, not the demand. Your CUM shipped still reconciles against the customer's CUM received and the quantities on the 830 and 862, exactly as it would without sequencing. That's the practical meaning of the standard's rule that the 866 doesn't authorize material: release accounting stays with your planning and shipping schedules, and the 866 adds a second requirement, order, on top of it.

Some customers define the relationship differently. In programs with no 862, for example, the 866 may be the nearest-term signal you have for what to ship. Confirm how each customer intends the documents to work together before you build your process around one model.

The worked example is the clean case. In practice, the two documents won't always line up. These are the situations to plan for, and the questions to settle with your customer before they happen.

• The counts differ. The 866 for a window adds up to more or fewer pieces of a part than the 862 shows. Know which document your customer expects you to follow for that window, and how it wants the difference reflected in your ASN and CUMs.
• A replacement sequence arrives. Many customers resend the sequence when the build order changes. A replacement supersedes the earlier sequence for its horizon. If your process doesn't recognize that, you'll build or stage to an order the plant has already abandoned.
• A vehicle is held or pulled from the line. Its sequence position may be skipped, moved or reissued later. Ask how the customer communicates holds and what it expects you to do with parts already built for that position.
• Sequence numbers are missing or duplicated. A gap means a vehicle with no part. A duplicate means a vehicle with two. Check every window before you stage it, not after the truck leaves.
• The file is late. Sequenced windows leave little slack. Know what you're expected to do if an 866 doesn't arrive when it should, and who to call.

Receiving an 866 is the easy part. Executing to it touches almost every step between your EDI inbox and the trailer door.

Process the sequence the moment it arrives

The time between receiving a sequence and the delivery window can be short. Any step that waits for someone to open a file, rekey it or print it eats into that window. Sequenced programs work best when inbound 866s are processed automatically, checked for gaps and duplicates, and pushed straight to the floor.

Build, pick or stage to sequence

Depending on the part, you may build to sequence, pick finished goods into sequence, or stage them in sequenced racks or containers. Whichever model you use, the sequence number has to travel with the part from the moment it's assigned until it's on the truck. Sorting by part number at any step breaks the chain.

Labels that match the sequence

Sequenced parts usually carry labels that identify their position, and often the vehicle they're built for, in addition to the standard part, quantity and supplier data. The content and format are set by each customer. When labels are generated from the same data as the sequence, they stay in step. When they're built separately, they drift. AIM's AIAG barcode labeling software page covers how customer-specific label requirements are typically managed.

Load the trailer in the right order

The order parts come off the truck has to match the order the line needs them. That often means loading in reverse, so the first sequence position is the last one in and the first one out. Racks and containers need to be loaded with the same discipline as the parts inside them.

An ASN that reflects what's on the truck

Your EDI 856 confirms what you shipped. For sequenced programs, customers may expect the ASN to reflect the shipment by window or by load, in addition to part and quantity. Check how your customer wants sequenced shipments represented, and make sure the ASN is built from what was actually scanned onto the trailer, not from what was planned. If you're unsure what a rejected ASN is telling you, our article on EDI 997 vs. 824 explains why a clean acknowledgment doesn't mean the ASN was accepted.

When you ship through a third-party sequencer

Not every sequenced program has you delivering straight to the line. Some customers use a third-party sequencing center near the plant. In that model, you may ship to the sequencer rather than to the line, and the sequencer handles the final order. Your EDI requirements, labels and ASN expectations may then come from the sequencer as well as, or instead of, the OEM plant. Confirm who sends what, and who you're shipping to, before the program launches.

Customers outside North America, and some global Tier 1s, send sequence requirements in UN/EDIFACT or VDA formats rather than X12. The concepts carry over. The message structures don't.

Most sequencing problems trace back to an assumption about how a customer uses its documents. Ask these during program launch, and again when a customer changes its EDI version or adds a plant or line.

Whatever software you run, sequenced programs need these capabilities:

• Receive and process 866s automatically, without rekeying.
• Check each sequence for gaps, duplicates and late arrival, and alert someone when they occur.
• Apply replacement sequences correctly, so the floor always works to the latest build order.
• Keep sequence logic separate from release accounting, so CUMs and net requirements stay accurate.
• Generate sequence labels from the same data as the sequence and the shipment.
• Verify what's loaded by scanning, and build the ASN from what was scanned.
• Handle each customer's rules individually, rather than one global rule for every trading partner.

Generic ERP systems often handle orders and inventory well, but weren't designed around automotive release accounting or sequenced shipping. That's where rekeying and side spreadsheets creep in, and why shipping errors cluster around the documents a supplier's core system wasn't built to understand.