Start with the conclusion: edi 862 shipping instructions do not authorize picking. They tell you how a shipment must move — who picks it up, in what window, on which route, and with what packing rules. Treat the message as an outbound order and you will ship the right goods the wrong way. I have seen this exact pit three times, and none of them was a software bug.

In October 2024, at a 3PL site near Columbus, Ohio, a shipment arrived with a pre-assigned PRO number and a pickup window of 7:00 to 9:00 a.m. the next day. The night supervisor saw the SKUs and quantities, pulled the freight to the dock early, and printed labels for the warehouse's usual carrier. When the assigned driver arrived at 7:20 a.m., his system could not match the labels. The pallets went back for relabeling, the dock backed up for more than 40 minutes, and two later pickups slipped. Nothing was short. Nothing was mispicked. The instructions had simply not been read to the end.

What edi 862 shipping instructions actually control

An 850 purchase order answers what was bought. A 940 warehouse shipping order answers what the warehouse must pick. EDI 862 shipping instructions answer the execution questions in between: pickup date and time window, carrier SCAC code, routing and service level, pickup reference or PRO number, and special packing or labeling requirements.

Think of the 850 and 940 as the menu and the 862 as the serving instructions. Serve the right dish late, cold, or to the wrong table and the customer still complains. In many operations the 850 creates an order and the 940 releases a wave, while the 862 lands in an EDI inbox that nobody links to the outbound order. That gap is the risk. The instruction arrived, but the people executing the shipment never saw it in context.

A second case makes the packing point clear. In March 2025, at an apparel warehouse in Dallas, Texas, the retailer used the 862 to require a retailer-specific carton label and a maximum of six layers per pallet. The warehouse picked correctly from the 940, built pallets to its usual eight layers, and applied its standard label. The carrier picked up without a detailed check. At the retailer's distribution center the load was rejected for packing non-compliance and sent back for rework. When the team reopened the raw message, the requirement was there in plain text. The parser had treated that segment as a general note and skipped it.

EDI 862 shipping instructions: a step-by-step warehouse workflow

Step one, link before you act. Match every 862 to an existing 850 or 940 using the purchase order number, outbound reference, or pickup reference. If it matches nothing, hold it. My rule for clients is simple: an 862 adds execution detail to an existing order; it never creates freight on its own. If your WMS cannot link automatically, build a cross-reference view so a supervisor can see all three references before release.

Step two, extract five hard fields and block release if any is missing: 1) pickup window with date and start and end times, not just a date; 2) carrier, with SCAC code matched to the carrier name; 3) routing and service level; 4) pickup credential — PRO number, appointment number, or pickup number — and which one the driver will present; 5) packing execution items such as layer limit, carton rule, label placement, and photo evidence. These fields belong in wave release and dock scheduling checks, not just in a free-text note nobody opens.

Step three, verify instructions against physical freight before sealing. After picking and before final packing, the lead checks carton count, label type, and pallet build against the 862 packing section. Fixing a pallet after it is wrapped costs multiples of fixing it at the pack bench. Step four, protect changes. If a carrier reschedules or a customer changes packing by phone, require an updated 862 or at least a written confirmation. Do not change the window in the system on a verbal request alone. When a delay dispute starts two weeks later, the message history is your evidence.

This comparison table is the one I put on the wall during go-live:

Message Question it answers Warehouse action If it is missing
850 What was bought Create order expectation No source order context
940 What to pick and ship Create outbound order, release wave No picking task
862 How, when, and by whom it moves Lock window, carrier, and packing rules Right goods, wrong execution
856 ASN What actually shipped Notify receiver after shipment Receiver cannot plan receiving

Most arguments end with this table. If someone says the order never mentioned a packing rule, look in the 862 first, not in the 940.

The three fields that misalign most often are the pickup window, the PRO number, and packing specifications. Windows may be sent in the sender's local time, or split into not-before and not-after values. Convert the window to warehouse local time for execution and keep the original value for audit. A pre-assigned PRO number must flow to the bill of lading and labels unchanged; letting the warehouse generate a second number breaks the driver's lookup, as it did in Columbus. Packing rules are the sneakiest because they often mix coded values with free text. During testing, review real customer samples line by line and decide which free-text lines must become operator prompts.

Here is the counter-intuitive point: the more automated your 862 parsing becomes, the more you need one deliberate human confirmation at release. Automation is excellent for staging freight. Locking the carrier and the window is different. Instruction messages change often and carry exceptions. One wrong pickup costs far more than the two minutes a supervisor spends confirming the five hard fields.

Go-live checklist and fallback rules

My night-before checklist, every item ticked, no exceptions: take at least three real customer 862 samples including one reschedule and one special-packing case; confirm all five hard fields have a home in the WMS and screenshot each one; prove the 850, 940, and 862 references can be looked up from each other; confirm label printing cannot overwrite a pre-assigned PRO number; confirm the dock board shows local time; confirm held messages alert a supervisor after two hours; and prepare a manual fallback log for link failures, with pickup number, window, and carrier recorded and entered the next day. No verbal release without a log entry.

For exceptions, keep three rules short enough to remember on a busy dock: no match, no ship; window missed, get a new window in writing before moving freight; packing rule unclear, photograph it and ask, do not guess. Warehouses rarely get in trouble for pausing. They get in trouble for guessing confidently. Exact segment definitions and version differences vary by trading partner, so always follow your partner's implementation guide and your EDI provider's current documentation as the final authority.

By Lin Xiao, WMS Implementation Consultant