TL;DR
The EDI X12 940 is the Warehouse Shipping Order — the electronic instruction a seller or retailer sends to a 3PL provider to release and ship goods to an end buyer.
It follows a Purchase Order Acknowledgment (855) and precedes a Warehouse Shipping Advice (945) in the logistics EDI cycle.
Getting 940 implementation right means understanding your partner’s companion guide, mapping it to your WMS or ERP, choosing the right transmission protocol, and validating before go-live.
Babelway handles all of this in a single self-service platform — no developer queue, no consultant dependency.
Related reads: What is EDI X12 850 and how to use it · Best EDI & B2B Integration Tools in 2026
Most people working in supply chain know about purchase orders and invoices. Fewer pay attention to the transaction that actually gets goods moving from a warehouse shelf to a customer’s door. That transaction is the EDI X12 940 — the Warehouse Shipping Order — and for any business that relies on a third-party logistics provider, getting it right is the difference between on-time delivery and a chargebacks-and-calls-to-the-warehouse kind of morning.
If you are setting up a 3PL integration for the first time, implementing 940 for a new retail channel, or trying to understand why your current setup keeps producing errors, this guide is for you. It covers what the 940 is, how it is structured, where it fits in the warehouse flow, and — crucially — how to implement it in a way that actually works in production.
👉 If you are still figuring out which EDI platform should power your warehouse integration, start with the companion guide:
How to Choose Your EDI & B2B Integration Tool Based on Your Business Objective
What is EDI X12 940?
EDI X12 940 — formally titled the Warehouse Shipping Order — is a transaction set defined under the ANSI ASC X12 standard. It is the electronic document a seller or retailer sends to a remote warehouse or 3PL provider to authorize and instruct the shipment of goods to a specific buyer.
In practical terms: when a customer places an order and your fulfillment sits in a 3PL facility, your system sends an EDI 940 to the warehouse telling it exactly what to pick, pack, and ship, and to whom. The 940 replaces phone calls, emails, and manual pick tickets with a structured, automated message that flows directly into the 3PL’s warehouse management system (WMS).
An EDI 940 typically carries:
- Purchase order number and order date
- Seller/supplier and buyer party identifiers
- Ship-to name and full delivery address
- Shipment transport instructions and carrier information
- Equipment and temperature requirements (where applicable)
- Special handling instructions
- Line-item detail: product ID, quantity, unit of measure
- Freight payment terms and FOB point
Beyond authorizing a shipment, the same 940 transaction can be used to modify or cancel a previously submitted order — making it the primary control document for warehouse operations in a 3PL-managed supply chain.
The Structure of an EDI 940: Key Segments
The EDI 940 follows the standard X12 envelope format: ISA interchange header, GS functional group, ST/SE transaction set, and IEA trailer. Inside the transaction set, the segments that matter most are:
The W66 segment controls how the carrier should handle the shipment: payment terms (prepaid vs. collect), transport method code, pallet exchange instructions, and FOB point. Partners vary significantly in how they use W66, so always check the companion guide before mapping.
| Segment | Name | Purpose |
|---|---|---|
| W05 | Warehouse Order Identification | Order number, release number, master order number |
| N1 | Name | Identifies parties: SF (ship from), ST (ship to), BT (bill to) |
| N2 | Additional Name Info | Additional address name lines |
| N3 / N4 | Address / Geographic | Street address, city, state, postal code, country |
| N9 | Reference Identification | PO number, line item number, customer order qualifiers |
| G61 | Contact | Contact name, type, and communication number |
| G62 | Date/Time | Requested ship date, delivery date |
| W66 | Warehouse Carrier Information | Freight terms, transport method, FOB point, routing |
| LX | Assigned Number | Line counter for item loop |
| W01 | Warehouse Item Detail | Quantity, unit of measure, product ID (GTIN/UPC/VPN) |
| G69 | Line Item Detail — Description | Free-form product description |
| W76 | Total Shipping Order | Summary: total weight, volume, number of lines |
Sample EDI 940 File
A condensed but realistic EDI 940 example. Real files will be longer depending on the number of line items and reference segments your partner requires.
ISA*00* *00* *01*BIGETP *01*035230000 *180327*0131*U*00401*000575103*0*P*^~
GS*OW*053980000*035230000*20180327*013134*575103*X*004010~
ST*940*0001~
W05*N*0080215659*4000207344~
N1*SF*American Company, Inc.*91*3010~
N1*ST*Atlanta Technology*91*0002965161~
N3*No 27 Huangping Road~
N4*Chicago*010*100096*CN~
N9*ZZ*DDP*CHICAGO~
G62*10*20180328~
W66*PL*ZZ********CALL~
LX*1~
W01*2*PC*000619002280*VN*E000169~
G69*ET1929LM-7BOO-1-WH-G~
W76*2*0*KG~
SE*15*0001~
GE*1*575103~
IEA*1*000575103~Where the 940 Fits in the 3PL Workflow
The 940 is not an isolated transaction. It is the pivot document in the warehouse portion of the supply-chain EDI cycle, and understanding its neighbours is essential for implementing it correctly.
EDI Transaction Flow: EDI 850 → EDI 855 → EDI 940 ★ → EDI 945 → EDI 856
The flow: a buyer sends an EDI 850 Purchase Order to the seller. Once the seller acknowledges it with an EDI 855, the seller sends an EDI 940 to the 3PL to release and ship the goods. The 3PL processes the 940 and, once the shipment leaves the dock, returns an EDI 945 Warehouse Shipping Advice to confirm execution.
Some 3PLs also generate an EDI 856 Advance Ship Notice directly to the end buyer — but only if the buyer’s contact data was passed through the 940. Missing that party data typically results in a chargeback. For a broader view of all logistics transaction codes, see the Babelway Logistics EDI Learning Hub.
How to Use EDI X12 940: A Step-by-Step Implementation Guide
Most 940 implementation failures aren’t caused by not knowing the standard. They’re caused by skipping steps that expose the gap between the published X12 standard and what a specific trading partner actually needs.
Step 1 — Get and read your partner’s 940 companion guide
Every warehouse and 3PL publishes a companion guide specifying which segments are mandatory, which qualifiers they accept, and how product identifiers (GTIN, UPC, vendor part number) should be populated. The X12 standard defines what a 940 can contain. The companion guide tells you what your specific partner requires. Start here, not with the standard.
Step 2 — Map the 940 to your WMS or ERP
Inbound 940s need translation into your warehouse management or ERP system’s order structure. Outbound 940s map your internal order data to the partner’s required X12 format. Babelway provides a graphical drag-and-drop mapping environment where this work is visible, documented, and repeatable — without writing a single line of code.
Step 3 — Choose your transmission protocol
Common options: AS2, SFTP, FTP, VAN. Your 3PL or retail trading partner specifies which they accept. AS2 is the most widely mandated in retail because it provides message-level receipts (MDNs) and is harder to spoof than FTP.
Step 4 — Build validation rules
A syntactically valid 940 can still be rejected if it fails business-rule validation — for example, if the product IDs don’t match what the warehouse has in its system. Build validation logic into your integration layer before go-live, not after your first production rejection.
Step 5 — Test with your partner before going live
Most warehouses and large retailers require a structured test cycle: you send test 940s, they validate them in their system, and both parties confirm results before any production traffic flows. After go-live, real-time monitoring and alerting on failed or delayed 940s is essential.
👉 Before starting any new 940 implementation, run through the EDI Integration Tune-Up Checklist — it covers the infrastructure checks that prevent most go-live surprises.
Common EDI 940 Implementation Pitfalls (and How to Avoid Them)
The X12 940 standard has been around for decades. Yet 940 implementations still regularly cause operational problems. Here are the failure patterns that come up most often.
Missing or mismatched product identifiers
The W01 segment carries the product identifier in elements W0104 and W0105. Partners use different qualifier codes: VN (vendor part number), UP (UPC), UK (GTIN), IN (buyer’s item number). If your system sends a UPC but the warehouse expects a vendor part number, the 940 will either reject outright or create a line the warehouse can’t pick. Always confirm the exact qualifier and format.
Incorrect party loop sequencing
The N1 loops carry the ship-from, ship-to, and bill-to party data. The order and qualifier codes matter. Some warehouse systems will reject a 940 if the ST (ship-to) loop appears before the SF (ship-from) loop, or if a BT (bill-to) loop is missing when the partner considers it mandatory.
Not passing buyer contact data for 856 generation
Some 3PLs send an EDI 856 ASN directly to the end buyer — but only if the 940 contains the buyer’s EDI contact information. If that data is missing, the ASN never goes out, the buyer doesn’t know the shipment is on its way, and the retailer’s compliance team generates a chargeback. This is one of the most expensive 940 mapping mistakes, and it’s entirely preventable.
Sending modification 940s incorrectly
The W05 segment’s transaction purpose code (W0501) distinguishes a new order (N) from a change (C) or cancellation (D). If your system sends an N for every 940 regardless of intent, the warehouse may process it as a duplicate new shipment order instead of a modification.
Testing against a spec that’s out of date
Trading partners update their companion guides more often than they notify their partners. Before any new implementation, ask for the current version of the spec. Testing against an old guide is how teams certify an integration that fails the moment production traffic flows.
Why Babelway is the Right Platform for Warehouse EDI and 3PL Integration
Every EDI platform will eventually transmit a 940. What separates them is how much friction sits between you and that outcome — and what happens the second time a partner changes their spec, a new warehouse joins your network, or your team needs to diagnose a failed shipment order at 11 PM.
Babelway was built specifically to eliminate that friction. The platform is cloud-native, self-service, and designed so that your integration and operations teams can own their channels without depending on a vendor queue for every change.
- Visual drag-and-drop mapping. Building or modifying a 940 map takes minutes in Babelway’s graphical environment. No XML editing, no custom scripting, no waiting for a professional services engagement. See the self-service EDI platform story for a real example.
- Full X12 format support. Babelway handles the complete X12 format library — 940, 945, 856, 850, 855, 810, 997, and beyond — alongside EDIFACT, XML, JSON, flat files, and more.
- Broad protocol coverage. AS2, SFTP, FTP, VAN, REST API — whatever your warehouse or retail partner requires, Babelway supports it natively.
- Real-time monitoring and alerting. Know the moment a 940 fails, why it failed, and what the fix is — without digging through log files.
- Transparent pricing. Babelway publishes its pricing plans openly. No surprise overage fees, no professional-services add-ons just to change a map.
For a broader comparison of how Babelway stacks up against IBM Sterling, Cleo, SPS Commerce, and other platforms, see the Best EDI & B2B Integration Tools in 2026 guide. And for the perspective of customers who’ve made the switch, the Martens Brewery case study is a good place to start.
👉 Want to understand how Babelway fits your broader EDI strategy? Read Taking Ownership of EDI and B2B Integrations with Babelway.
Check out what Babelway users say about Babelway’s EDI and B2B integration capabilities on G2 → Babelway reviews
Frequently Asked Questions
What is the difference between EDI 940 and EDI 850?
An EDI 850 Purchase Order is sent from a buyer to a seller to place an order. The EDI 940 Warehouse Shipping Order is sent from a seller (or retailer) to a warehouse or 3PL provider to authorize and instruct the physical shipment of goods already ordered. They operate at different points in the order cycle and between different trading partners.
Who sends the EDI 940?
The seller, brand, or retailer that holds the relationship with the 3PL warehouse sends the 940. In a drop-ship or retail fulfillment model, a retailer may send the 940 to a supplier’s designated 3PL on behalf of a consumer order.
What transaction follows an EDI 940?
Once the warehouse processes the 940 and ships the goods, it returns an EDI 945 Warehouse Shipping Advice to confirm execution. In some setups, the 3PL also generates an EDI 856 Advance Ship Notice directly to the end buyer if the buyer’s data was passed in the original 940.
Is EDI 940 mandatory for working with 3PLs?
For mid-to-large 3PL providers and virtually all retail-mandated fulfillment networks, yes. Manual alternatives don’t survive volume. See the Babelway 3PL EDI hub for a full overview of 3PL-specific requirements.
Can the EDI 940 be used to cancel a shipment?
Yes. The W05 segment’s transaction purpose code (W0501) controls whether a 940 represents a new order (N), a change (C), or a cancellation (D). Timing is critical: once a pick ticket is released in the WMS, a cancel 940 may not stop the shipment.
What EDI software do I need to send and receive 940s?
You need a platform that supports X12 format translation, field-level mapping to your WMS or ERP, and the transmission protocols your partners require. Babelway covers all of this in a single self-service cloud platform, with a free 30-day trial.
How long does it take to implement EDI 940 with Babelway?
Most Babelway customers implement a standard 940 channel in days to a week, including connectivity setup, mapping, validation rules, and partner testing. The self-service model means your team drives the timeline — not a vendor’s professional services backlog.
Where can I learn more about Babelway before booking a demo?
Explore the Babelway Product Tour, browse the Babelway Academy for free self-paced training, or explore the full Logistics EDI Learning Hub.
