Skip to content
EDI X12 940

X12 transaction code

X12 940 Warehouse Shipping Order

Stop Mapping. Start Trading.

Standard
X12
Code
940
Trading partners
18

Specification summary

X12 940 Warehouse Shipping Order at the element level

The X12 940 specification defines 33 segments carrying 106 data elements, 53 of which are mandatory.

Segments
33
Data elements
106
Mandatory elements
53
Segments with mandatory elements
Segment Elements Mandatory
W05 4 2
N1 4 1
N2 2 1
N3 2 1
PER 8 1
N9 6 1
NTE 2 1
W66 3 2
W6 2 1
LX 1 1
W01 8 2
G69 1 1
Key identifiers in 940
  • Order Status Code
  • Depositor Order Number
  • Entity Identifier Code
  • Name
  • Address Information
  • Contact Function Code
  • Reference Identification Qualifier
  • Description

Usage breakdown

Who trades X12 940 Warehouse Shipping Order

940 is used most heavily in logistics & transport, grocery & food and electronics & technology.

The 940 instructs a warehouse to make a shipment, confirm a shipment, or modify or cancel a previously transmitted shipping order. It is the document a brand or supplier (the depositor) uses to direct outsourced fulfillment: without it a 3PL has no structured pick, pack, and ship instruction to load into its WMS. Orders routed through third-party warehouses depend on it to start fulfillment, so warehouses require it as the system-of-record instruction for every outbound order. Sent by the supplier or manufacturer that owns the inventory (the depositor) to the 3PL warehouse or fulfillment center holding the stock. A customer order lands in the brand's ERP or order-management system and must be fulfilled from inventory held at a third-party warehouse.

By industry

  • logistics & transport 10 channels
  • grocery & food 5 channels
  • electronics & technology 4 channels
  • manufacturing & industrial 1 channel

FAQ

X12 940 questions

What is X12 940 Warehouse Shipping Order?

X12 940 (Warehouse Shipping Order) is an EDI transaction set defined by ANSI ASC X12 for exchanging warehouse shipping order between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 18 Stacksync trading partners support this code across 20 channels.

Which trading partners use X12 940?

18 Stacksync partners accept X12 940: Americold Logistics, LLC., ASUSTeK Computer Inc. (dba ASUS), AT&T Inc., Atlanta Bonded Warehouse, Dot Foods, Inc., Dow Inc., Expeditors, Fraser Direct, and more. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.

How do I integrate X12 940 with my ERP?

Stacksync handles the full X12 940 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.

Ready to automate your EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.