What Is EDI 940? Warehouse Shipping Order Explained

The ANSI X12 warehouse shipping order transaction sent to a warehouse or 3PL to authorize fulfillment.

EDI 940 The ANSI X12 warehouse shipping order transaction sent to a warehouse or 3PL to authorize fulfillment. This transaction is the electronic instruction a shipper or trading partner sends to a warehouse to request picking, packing, staging, and shipping of specified goods to a consignee or carrier.

The 940 is not a purchase order; it is an operational authorization for physical movement and shipment. It typically references purchase orders, item identifiers (SKUs), quantities, shipping dates, carrier instructions, and packaging requirements. Warehouses consume the 940 in their WMS to create work tasks, schedule dock appointments, and apply carrier labels or documentation.

How The Transaction Works

A sender prepares an ANSI X12 940 message with structured data fields that describe what to ship and how. Common elements include ship-to address, order number, line-level SKUs, quantities, unit of measure, requested ship dates, and special handling codes. The sender transmits the 940 over an agreed communications protocol—AS2, SFTP, or VAN—to the warehouse or 3PL.

On receipt, the warehouse system parses the 940, validates the data against inventory and business rules, and converts the instruction into pick and pack work. After execution, the warehouse typically returns a 945 Warehouse Shipping Advice or a shipment notice and may also send a 997 Functional Acknowledgement to confirm receipt of the 940.

Why It Matters

Using the EDI 940 reduces manual paperwork, speeds fulfillment, and increases accuracy by moving structured instructions directly into the warehouse management system. For retailers and high-volume shippers, 940-driven automation shortens lead times, improves on-time shipments, and reduces labor for picking and paperwork.

For 3PLs, clear 940 messages establish expectations about packing standards, palletization, carrier preferences, and routing—critical for billing, compliance, and SLA adherence. The transaction also supports audit trails and traceability when combined with shipment confirmations.

How It Varies

• Version And Segmentation: Different EDI X12 versions (e.g., 4010, 5010) and trading partners may use different segment layouts or optional fields.
• Custom Requirements: Retailers often add partner-specific qualifiers for item IDs, cartons, serial numbers, or return instructions that require mapping logic.
• Transmission Method: Partners may prefer AS2 for real-time interchange or VAN for legacy connections; this affects processing speed and acknowledgements.

Who Sends And Who Receives

Senders are typically shippers, merchants, wholesalers, or retailers that need a warehouse to prepare and dispatch goods. Receivers are warehouses, distribution centers, and third-party logistics providers (3PLs) that operate picking, packing, staging, and carrier handoff functions.

Large retail chains and e-commerce platforms often require their fulfillment partners to support the 940 as part of onboarding. Small merchants may use a transport or integration provider to translate simpler requests into 940 transactions on their behalf.

Practical Example

A national retailer sends an EDI 940 to a 3PL to authorize shipment for a weekend promotion. The 940 includes three purchase order references, 12 line items with SKUs, palletization instructions, and a requested ship date. The 3PL WMS validates inventory, creates pick tickets, reserves stock, and schedules carrier pickup.

When the pallets are staged and loaded, the 3PL sends a 945 Warehouse Shipping Advice stating the actual quantities and carrier details and a 997 acknowledging receipt of the 940. The retailer uses the 945 to reconcile invoicing and inventory.

Common Pitfalls And How To Avoid Them

• Missing Or Mismatched Identifiers: Incorrect SKU or PO references cause pick failures—validate identifiers before transmission and maintain a shared master item list.
• Unclear Packaging Instructions: Vague carton or pallet instructions lead to rework—use explicit packaging and unit-of-measure fields in the 940.
• No Acknowledgement Process: Skipping 997 or 945 exchanges leaves senders blind to issues—establish mandatory acknowledgements and exception messaging.

Implementation Tips

• Map Carefully: Create detailed field mappings between the sender’s ERP and the warehouse WMS, including optional segments used by trading partners.
• Test Thoroughly: Run end-to-end test cycles with sample orders, carrier labels, and confirmations to catch format and business-rule mismatches.
• Use Middleware: Consider an EDI translator or integration platform to handle version differences, envelope wrapping, and protocol conversions.
• Document Exceptions: Agree on SLA responses for short-ship, over-ship, or inventory shortages and include them in the 940 business rules.

In short, the EDI 940 is the operational instruction that tells a warehouse or 3PL what to pick, pack, and ship. When implemented with clear mappings, acknowledgements, and testing, it streamlines fulfillment and reduces manual error.