EDI 940 vs Purchase Order: Who Controls Fulfillment?

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. Use of the 940 focuses on directing physical fulfillment work rather than initiating a procurement or billing relationship.

Understanding the difference between an EDI 940 and a purchase order is critical for operational clarity. A purchase order (PO) is a commercial document that creates an obligation to buy and often lives in the buyer and supplier ERP systems. A 940, by contrast, is a logistics instruction to a warehouse to execute shipping tasks. Both can reference each other: a 940 often cites PO numbers so the warehouse can reconcile items to order quantities.

Primary Functional Differences

• Purpose: PO: authorizes purchase and payment. 940: authorizes fulfillment and shipment.
• System Of Record: PO: buyer and seller ERPs. 940: warehouse WMS and operations systems.
• Timing: PO: issued when goods are ordered. 940: issued when goods are ready to be prepared for shipment.

When You Need A 940 In Addition To A PO

Many supply chains flow PO → ASN → 940 → 945, but not every scenario requires every message. You need a 940 when the physical fulfillment step is managed by a separate warehouse or 3PL that requires explicit instruction to perform picking, packing, and carrier handoff. Examples include drop-ship programs, retail distribution centers, and outsourced e-commerce fulfillment.

How They Work Together In Practice

A seller receives a PO from a retailer and acknowledges it in their ERP. When stock is earmarked for that order and the ship date nears, the seller or retailer issues an EDI 940 to the warehouse specifying what items to ship and how. The warehouse executes the work and returns a 945 shipping advice. This separation keeps procurement and physical logistics processes independent and auditable.

Responsibility And Control

• Buyer-Controlled Fulfillment: When a retailer controls the fulfillment process, they send the 940 to the 3PL with explicit instructions and SLAs.
• Supplier-Controlled Fulfillment: A supplier may send a 940 to its own warehouse or a contract packer to ship directly to the customer.
• Shared Control: Complex programs often require mutual agreement on references, packaging, and carrier preferences within both PO and 940 mappings.

Common Integration Patterns

Integration patterns depend on where the PO is created and who fulfills the order. Typical setups include:

• ERP-to-WMS: The seller’s ERP generates a 940 for the warehouse; the WMS acknowledges with 997 and sends 945 after shipment.
• Retailer-to-3PL: Retailer systems produce 940s directly to 3PLs for drop-ship or replenishment flows, independent of supplier POs.
• Middleware Translation: EDI translators or iPaaS platforms map POs and internal order formats into 940s for external warehouses.

Practical Considerations For Warehouse Managers

• Validate References: Use PO numbers on the 940 to cross-check expected inventory and allocations before picking.
• Define Business Rules: Agree on how to handle short-ships, partial picks, or overages between the PO process and the 940 execution.
• Automate Acknowledgements: Require 997s and 945s so senders know the 940 was received and shipments completed.

Negotiating Responsibilities

Because POs carry commercial terms and 940s carry logistical instructions, contracts or SLAs should specify who issues which messages and who is responsible for discrepancies. Clarify billing triggers (e.g., shipment vs. receipt) and who handles carrier disputes to prevent finger-pointing when issues arise.

In short, the EDI 940 is the operational command for fulfillment—distinct from a purchase order’s commercial intent—and the two work together to move goods accurately and on time. Clear mappings, agreed references, and defined acknowledgements keep both procurement and fulfillment aligned.