What Is EDI 940 and When Apparel Brands Actually Need It

It is Tuesday afternoon at a $15M wholesale brand. The ops coordinator has 47 Nordstrom POs that dropped overnight, a Bloomingdale’s allocation that got revised this morning, and a 3PL that takes shipping orders by emailed CSV. She is in her fourth hour of copying line items out of the order management screen, formatting them into the 3PL’s required template, and emailing them to a shared inbox in New Jersey. Two of yesterday’s orders shipped short because a SKU substitution did not make it from her email into the warehouse management system. The retailer will chargeback. The 3PL will say they shipped what was on the file.

What is EDI 940 and how does it actually work in apparel operations?

This is the situation EDI 940 exists to fix, and the question of what is EDI 940 apparel brands keep asking is really a question about when the manual workaround stops being viable.

EDI 940, formally the Warehouse Shipping Order, is the electronic transaction a brand sends to a third-party logistics provider or distribution center to instruct it to ship a specific order. The 940 carries the order header (ship-to, ship-from, carrier, service level, requested ship date), the line items (SKU, quantity, unit of measure, lot or season codes if relevant), and the routing instructions (retailer routing guide, BOL number if pre-assigned, special handling such as ticketing, GS1-128 carton labels, or floor-ready prep).

The 940 is half of a pair. The 3PL responds with a 945, the Warehouse Shipping Advice, which confirms what actually shipped: cartons, weights, tracking numbers, any short-ships or substitutions. The 940 plus the 945 is how a brand and its warehouse stay synchronized without humans retyping data. Some brands also use 943 (warehouse stock transfer shipment advice) and 944 (warehouse stock transfer receipt advice) for inbound replenishment to the 3PL, and 947 for inventory adjustments. The 940 and 945 are the load-bearing pair for outbound wholesale.

Why do most apparel brands not actually need EDI 940?

From the operational debrief I run with new customers in their first 90 days, the pattern is clear: about half the brands who ask about 940 in the sales process do not actually need it yet. They have read a retailer’s vendor compliance manual, seen 940 listed under warehouse integration, and assumed it is a requirement on them. It is not.

The retailer-facing EDI obligations are 850 (purchase order), 855 (PO acknowledgment), 856 (advance ship notice), 810 (invoice), and 997 (functional acknowledgment). These are between the brand and the retailer. The 940 is between the brand and its warehouse. If you ship from your own warehouse and your warehouse management system already lives inside your operations platform, the 940 is internal plumbing the system handles without a formal EDI document.

The brands that genuinely need 940 share three traits. First, the goods are physically held by a third party the brand does not control. Second, the volume of wholesale orders is high enough that emailed CSVs introduce data loss the team cannot manually reconcile. Third, retailer ship windows are tight enough that a 24-hour gap between order receipt and warehouse acknowledgment causes compliance failures.

When does EDI 940 actually become necessary?

The trigger is not a revenue number, it is an architectural one. A brand needs 940 when the warehouse stops being something the brand walks into.

For brands in the $5M to $20M band running their own warehouse, 940 is usually unnecessary. The OMS and the WMS are the same system or are tightly coupled, and a wholesale order routes from order entry to pick ticket without translation. For brands that move to a 3PL, even partially, the question changes. Now there is a system boundary between order capture and order execution. Something has to cross that boundary, and the choice is between an emailed CSV (fragile), a portal upload (slow, error-prone, manual), an API integration (works if the 3PL has one and it is good), or EDI 940 (the standardized version of the API, which most enterprise 3PLs prefer).

From the integration incidents we have triaged this year, the pattern is consistent: the 940 conversation arrives 6 to 12 months after the 3PL conversation. A brand goes live with a 3PL in March, runs on email and CSVs through their first peak, eats some chargebacks, and by Q1 of the following year is asking how to make this stop. By then the data is clear: the team is spending 6 to 9 hours a week reconciling inventory across Shopify, the 3PL, and wholesale, and the oversell rate at peak is in the 2 to 3 percent range. That entire load is one FTE doing data plumbing. The 940 and 945 pair is what removes most of it.

What does EDI 940 contain that a CSV does not?

A wholesale ship order is not a list of SKUs and quantities. It is a list of SKUs and quantities plus the retailer’s routing rules, prep requirements, label specifications, and ship-window dates, all of which have to make it from the brand’s order record to the warehouse floor without anyone retyping them.

A 940 carries:

• The retailer’s routing guide reference, so the warehouse books the correct carrier under the retailer’s account.
• The ship window (not ship date, ship window), so the warehouse knows the earliest and latest acceptable ship dates.
• The required label format (GS1-128 carton, UCC-128 with specific AI fields, retailer-specific SSCC structures).
• Prep instructions (hangered, flat-packed, ticketed with the retailer’s price ticket, polybagged with specific markings).
• Line-level details including style, color, size breakdown, and pack configuration (prepack vs eaches), which is where most CSV-based workflows break.
• Any allocation flags, so the warehouse does not pull from a pool reserved for another channel.

A CSV can carry some of this, in theory. In practice it carries the SKU and the quantity and the ship-to, and everything else lives in someone’s head or in an attached PDF of the routing guide. That is the failure mode. The chargeback for shipping in the wrong carton label format does not care that the team meant to do it right.

How does EDI 940 connect to the inventory truth problem?

This is where the 6 Breakpoints framework anchors the diagnosis. Breakpoint 5, warehouse execution gets less predictable, is where the 3PL blind spot lives. The brand sees an order go out the door in its OMS. The 3PL sees an order arrive in its WMS. Without a 940 and 945 pair, those two events are connected by a human and a spreadsheet, and the brand’s view of inventory drifts from the 3PL’s view by a little bit every day.

Lufema, a multi-entity wholesale distributor, is a good case in point. After consolidating wholesale operations onto one platform with proper warehouse and order integration, inventory accuracy moved from the 90 to 95 percent range to roughly 99 percent, excess stock dropped about 20 percent, and the team onboarded 3 new brands and over 100 new retailer accounts without adding ops headcount. None of that is possible if every wholesale ship order is being retyped between systems. The 940 and 945 are not the whole story, but they are the part of the story where the warehouse stops being a black box.

If a brand cannot answer the question “as of right now, what shipped today, what is committed but not picked, and what is available to promise” in under thirty seconds, the warehouse integration is the problem. Eight times out of ten the missing piece is a 945 coming back from the 3PL on the same day the goods leave the dock, not the next morning when someone at the 3PL gets around to emailing a shipped report.

What is the difference between EDI 940 and EDI 856?

This trips up brands new to wholesale EDI. The 940 goes from the brand to the warehouse. The 856 goes from the brand to the retailer. They carry overlapping data but they are different documents with different audiences and different timing.

The 940 is sent when the brand wants the warehouse to ship. The 945 comes back when the warehouse has shipped, with carton-level detail. The brand then uses the 945 data to generate the 856 (advance ship notice) to the retailer, which has to arrive before the goods arrive at the retailer’s DC, with carton SSCC labels that match what is physically on the trailer. If the 945 does not flow back to the brand cleanly, the 856 will be wrong, and the chargeback will hit at the retailer’s receiving dock.

This is why retailer compliance is rarely a warehouse problem in isolation. If retailer chargebacks exceed 1 percent of wholesale revenue, the EDI integration is the problem, not the warehouse. The warehouse is shipping what it was told to ship. The data path between the WMS and the retailer is what is breaking.

Should a brand build 940 integration or wait for the 3PL to push it?

The default assumption is that the 3PL drives this. Most enterprise 3PLs (DCL, Quiet, Radial, ID Logistics, Saddle Creek) have 940 and 945 capability and will quote a setup fee to enable it. Smaller 3PLs, particularly the ones that win brands in the $5M to $15M band on price and flexibility, often do not have it natively, or have a half-built version that requires the brand to send a custom flat file.

The right architecture is to treat 940 and 945 as a capability the operations platform owns, not a capability the 3PL provides. The brand should be able to send 940s in standard X12 format to any warehouse partner, and parse 945s coming back, without rebuilding the integration each time it changes 3PLs or adds a second one. Brands that build 940 as a one-off integration with their current 3PL discover the cost when they switch 3PLs and have to rebuild it. Brands that own the 940 capability at the platform layer treat the 3PL as a swappable execution partner.

This matters more than it sounds. The brands in the $10M to $20M predictable breakpoint zone are exactly the brands most likely to add a second 3PL (one for DTC, one for wholesale, or one for domestic and one for international) within 18 months. If the 940 lives at the 3PL relationship level, every new 3PL is a new project. If it lives at the platform level, every new 3PL is a configuration.

What this means for an apparel operations team

If you are running your own warehouse, you do not need 940. If you are emailing CSVs to a 3PL and your wholesale volume is under 50 orders a week, you do not yet need 940, but you should know the day is coming. If you are above that line and you are eating chargebacks, the question is not whether to implement 940, it is how fast.

The practical sequence is: confirm the 3PL supports 940 and 945 in standard X12 format, confirm your operations platform can send and receive those documents without a custom build per retailer, map the routing guide requirements for your top three retailers into the 940 fields they actually populate (SAC codes, prep instructions, label specs), and run a 30-day parallel period where the warehouse receives both the email and the 940 so you can compare what each one carried.

The deeper point is that 940 is not a wholesale EDI question. It is a warehouse architecture question that happens to use an EDI transaction set. The brands that get this right treat the 3PL as part of the operations stack, with the same data discipline they apply to inventory and orders. The brands that get it wrong treat the 3PL as a vendor at the end of an email thread, and pay for it in chargebacks, oversells, and the slow erosion of the team’s confidence that anyone actually knows what shipped today.