EDI 940 / 945 — Warehouse Shipping Order & Shipping Confirmation (2025 Fulfillment Execution Standard) Updated Dec 2025
Source: WinsBS Research, ANSI ASC X12 transaction set references (940/945), WMS/OMS integration guides, and warehouse fulfillment execution standards (2025).
Industry Standard Definition — EDI 940 / 945
View Standard Definition
EDI 940 (Warehouse Shipping Order) is an electronic instruction sent from an Order Management System (OMS) or ERP to a warehouse or Third-Party Logistics (3PL) provider. It authorizes the warehouse to pick, pack, and ship specific orders, typically including ship-to address, ship method, and line-item SKU quantities.
EDI 945 (Warehouse Shipping Advice / Shipping Confirmation) is the execution response sent back from the warehouse Warehouse Management System (WMS) to the OMS/ERP after shipping. It confirms what actually shipped (line-item quantities) and commonly includes shipment identifiers and carrier/tracking details when they are available at confirmation time.
— ANSI ASC X12, Warehouse Shipping Order (940) & Warehouse Shipping Advice (945)
Key Use Cases for EDI 940 / 945 in 2025: When Warehouses Need a Reliable Execution Loop
View Common Applications
EDI 940 / 945 is most valuable when an OMS must issue clear warehouse instructions and receive a dependable confirmation record. It is widely used in ecommerce fulfillment, retail distribution, and 3PL operations where auditability and consistency matter.
- Shopify + 3PL fulfillment: OMS releases orders to a warehouse via 940; WMS confirms shipment via 945 so customers receive accurate shipping status and tracking.
- Multi-warehouse fulfillment: An OMS routes orders based on inventory allocation and carrier cutoff times, then reconciles confirmations across sites. See Multi-warehouse Fulfillment.
- High-volume batch shipping: 940/945 is commonly used to reduce operational variance when real-time APIs create ordering, retry, or rate-limit issues.
- B2B and retail distribution: Order release and shipment confirmation records support downstream invoice matching, claims handling, and compliance audits.
Integrating EDI 940 / 945 for Maximum Reliability: Best Practices (2025)
View Integration Best Practices
Most EDI 940/945 failures are not “EDI formatting” problems. They come from missing alignment on how orders are released, how confirmations are triggered, and how exceptions are represented between the OMS and WMS.
- Lock a shared SKU identity: Ensure OMS and WMS agree on SKU, UPC/EAN (if used), and pack configuration to avoid shipped-vs-ordered mismatches.
- Define idempotency for 940: Establish resend rules so duplicate 940 transmissions do not generate duplicate pick work or duplicate shipments.
- Make partial shipments explicit: If split shipments or backorders can happen, define how 945 reports them and how the OMS updates customers.
- Standardize carrier and service mapping: Align carrier codes and ship methods so “2-Day” or “Expedited” means the same thing across systems.
- Clarify tracking availability timing: Decide whether 945 must include tracking at confirmation time, or whether tracking can arrive later via API Integration or Webhook.
- Monitor the loop: Alert on “940 sent but no 945 received” within a defined time window, and “945 received without tracking” by carrier/service level.
Risks and Challenges of EDI 940 / 945 Implementation: Navigating Common Pitfalls
View Risks
Even if your EDI exchange is “connected,” operational details can still break fulfillment outcomes. These are common failure modes teams should design for:
- Duplicate 940 releases: Duplicate pick tasks, double shipments, forced cancellations, and inventory reconciliation churn.
- 945 delayed or missing: Inventory is not deducted on time, customer notifications fail, and marketplace tracking compliance can degrade.
- SKU mapping mismatches: Shipped confirmations cannot reconcile with orders, causing claims, returns disputes, and support escalations.
- Partial shipment not represented: Customers see “shipped” but receive only part of the order, driving negative feedback and ticket volume.
- Tracking gaps: Tracking numbers are missing, incorrect, or tied to the wrong carrier/service, leading to late tracking uploads and SLA risk.
A common confusion is mixing outbound execution messages (940/945) with inbound shipment notices (856). If you are also working on inbound receiving, see: EDI 856 / ASN.
Related Terms
Critical Risk Terms (2025)
EDI 940 / 945 FAQ — Common Questions
What is the difference between EDI 940 and EDI 945?
EDI 940 is a warehouse shipping order that instructs a warehouse to pick, pack, and ship an order. EDI 945 is the shipping confirmation sent after execution to report what actually shipped, including quantities and shipment details.
When is EDI 940 sent in the fulfillment process?
EDI 940 is typically sent after an order is finalized and released by the OMS. It represents the formal authorization for the warehouse or 3PL to begin fulfillment work.
What triggers an EDI 945 shipping confirmation?
EDI 945 is generated after shipment execution, usually once items are packed and handed off to a carrier or after shipment is confirmed in the WMS, depending on system configuration.
Is EDI 945 the same as a tracking update?
No. EDI 945 is a shipment confirmation record focused on confirming shipped quantities and order execution. Tracking numbers may be included, but tracking updates can also be delivered separately through APIs or webhooks.
How do EDI 940 / 945 differ from EDI 856 (ASN)?
EDI 940 and 945 are used for outbound fulfillment execution between an OMS and a warehouse. EDI 856 (ASN) is a shipment notice used primarily to inform receiving parties about inbound shipment details.
What are common causes of “EDI 940 sent but no EDI 945 received”?
Common causes include warehouse holds, wave release delays, carrier label generation issues, shipment confirmation being tied to a later event such as manifest close, or integration failures between the WMS and OMS.
WinsBS Blog Insights
EDI 940 Warehouse Shipping Order: Designing a Clean OMS → WMS Order Release
How to define SKU identity, ship method mapping, and resend rules so warehouse execution does not create duplicate picks, double shipments, or label rework.
Read Full Guide →
EDI 945 Shipping Confirmation: Tracking, Partial Shipments, and Reconciliation
Practical patterns to reconcile shipped quantities vs ordered quantities, handle split shipments, and prevent tracking gaps in customer-facing updates.
Explore Full Analysis →
EDI 940 vs 945 vs 856: The Fulfillment Execution Loop, End-to-End
A clear mapping of outbound order release, outbound shipment confirmation, and shipment notices so teams do not mix message semantics across workflows.
Learn the Full Loop →Content Attribution & License
General definitions and public references are shared under the CC BY-SA 4.0 License.
Analytical insights and technical interpretations labeled as “WinsBS Research” are original works © WinsBS Research (2025) and licensed exclusively to WinsBS Wiki.
Information verified as of December 2025.