We have a client, a women's apparel brand, that moved into our Ontario, California warehouse in November 2024 — and the EDI 940 945 message pair was about to teach us all a lesson. First shipment before peak season: 200 cartons, 24 pieces per carton, 4,800 pieces in total. The EDI 940 came in, we picked, packed, shipped, and sent the 945 back. Clean run. Three days later the brand called, voice shaking. The store had received its 200 cartons, sure — but the retailer's system was expecting 4,800 cartons. They had planned inbound dock space for 4,800 cartons. The receiving plan was built on a number 24 times too big.

The picking was right. The packing was right. The 940 was wrong. The quantity field said 4,800 and the unit of measure said cartons. Their system had exported the piece count and left the unit code as cartons. The warehouse did exactly what the message said. The retailer expected what the message said. The gap between those two readings was 24x, and the first peak-season order paid for it.

That is the personality of EDI 940 and 945. Invisible when they work. Expensive when they don't.

The EDI 940 is the Warehouse Shipping Order: the brand or cargo owner telling the third-party warehouse what to ship, how much, to whom, by when, on which carrier, with which labels. The EDI 945 is the Warehouse Shipping Advice: the warehouse reporting back what actually left the dock — how many cartons, which tracking numbers, what short-shipped, what got substituted. The 940 is the instruction. The 945 is the receipt. The loop only closes when the two agree.

Inside our warehouse the flow is four steps: receive the order, pick, verify, send the advice back. The 940 arrives, gets translated through a mapping table into an order our warehouse system understands, then picking, packing, labeling, weighing, and finally the actual shipped data gets assembled into a 945. It sounds orderly. Every step has a trap, and every trap lives in a field.

The most common failure is the unit of measure. The apparel client above is the textbook case. "Carton" in the brand's system can mean "each" in the warehouse's system if the mapping table never aligned them. The quantity can be perfect and still wrong. When we onboard a new client, the first thing we do is run three historical 940s through the map — cartons, eaches, pallets — and check what the warehouse system actually reads. Never trust anyone saying "our units are always eaches." What the message says is what counts.

The second failure is the ship-to address. A 940 carries several address blocks, and a retailer's distribution center, store address, and returns address often look alike. Put the wrong one in the ship-to field and the freight lands in the wrong state. In March 2025 a beauty client of ours shipped to a Midwest chain's regional warehouse. The 940's address field held the headquarters address; the regional warehouse only appeared in a notes field. We shipped to the address field. Headquarters signed, transferred internally, four days lost, and the retailer docked them for late receipt. The brand said the note spelled it out. The warehouse said the address field is the authority. Both were right, and the mapping guide was wrong, because it never stated the rule: the ship-to address comes from the address field only, never from notes.

The third is the cancellation window. A 940 is not a sacred text. Brands change and cancel orders, usually by sending a revised 940. But once picking starts, a change costs real labor and packaging. Our contracts typically say cancellation is free before picking starts, and billed at incurred labor and materials after. How long that window is varies by warehouse. Ask before you sign. If you don't, every peak-season change becomes an argument.

The 945's problems run the other way: not wrong, but late and vague. If the 945 comes back two days late, the brand cannot send the 856 advance ship notice to the retailer, the retailer cannot receive the goods, and the chargeback follows. That same beauty client in March 2025 got its 945 two days late, its 856 went out late, and the retailer charged them for it. The amount was small. It was their first order together, and the trust took the hit.

Quantity mismatches on the 945 are even more common. The 940 asks for 100 pieces, the warehouse ships 96, and the 945 says 96 — but the status code decides everything. Partial shipment with no backorder means the order is closed. Partial shipment with backorder means the brand is still waiting. Many warehouses send the quantity without a meaningful status code, or mark everything complete. The brand reconciles against that and never balances. When you investigate a 945, read the status code first, the quantity second, the carton numbers third. Reverse that order and you will spend three days chasing nothing.

Reconciling the EDI 940 and 945 pair

Here is the reconciliation table I give clients. Tape it to the desk of whoever does the matching:

Check What to read on the 940 What to read on the 945 Check first when they disagree
Order number Brand order number Warehouse-returned order number The order-number mapping
Item and quantity SKU, quantity, unit of measure Shipped quantity, unit, status code Unit mapping, then inventory
Ship-to Ship-to address field Returned ship-to party The 940 address field, not the notes
Carrier Specified carrier and service level Actual carrier and tracking number Whether the warehouse followed the routing
Dates Requested ship date Actual ship date The 945 transmission timestamp

Systems can reconcile automatically, but when the system flags a mismatch, a person needs to know which row to check first.

Running many clients out of one warehouse adds another quiet risk: mapping version control. We serve a dozen-plus brands from one building, and every brand's 940 differs — different versions, different field positions, different unit habits. One client's quantity unit sits in one segment, another's in a different one, a third uses a custom segment entirely. The only way to manage it is one mapping table per client, version-stamped, with any change signed by both sides. The nightmare scenario is a brand upgrading its system and quietly moving a field. Messages keep flowing, the warehouse keeps receiving, and two weeks pass before anyone notices. It happened to us once. Now our contracts carry a clause: before any system release, the brand must send three test 940s through the full flow, or it shares the cost of mis-shipments. The client's face was not happy the day we added that clause. It has since saved them real money.

What one bad EDI 940 costs

How much does one bad shipment cost? Using our warehouse's real fee structure, here is an illustrative example — a hypothetical scenario, for reference only. One order of 200 cartons shipped to the wrong address: return freight, re-picking, re-labeling, a second outbound run, plus the retailer chargeback, comes to roughly two to three times the normal fulfillment cost of that order. The fulfillment itself was not expensive. The mistake cost two or three orders' worth of margin. And that excludes the invisible cost: the retailer putting you on a watch list. Skimp on anything, but never skimp on test messages.

The counterintuitive part

Most brands think a faster 945 is always better, and they push the warehouse to send it the moment the truck leaves. My experience says the opposite: a wrong 945 sent early is worse than a correct 945 sent late. Once a wrong 945 goes out, the brand issues invoices and sends the 856 based on it. Then a corrected version arrives and the whole chain has to be redone, and the retailer may still charge back on the first version. Wait two hours, finish verification, and send one correct message. Speed is not the value of the 945. Accuracy is. Accurate, it is the evidence a brand uses to reconcile with the retailer and dispute chargebacks. Inaccurate, it is a document that causes trouble.

Next time you negotiate a warehousing contract, ask these three questions: first, who maintains the 940 mapping table, and how many days' notice before a version change; second, is the 945 turnaround time written into the service level agreement, and what happens when it is missed; third, when exactly does the cancellation window start, and what marks the start of picking. Ask those three and the other side will know this is not your first warehousing contract.

By Susan, 3PL Sales Director