To start and identify an interchange of zero or more functional groups and interchange-related control segments
NLS (National Logistics Services) X12 940 Warehouse Shipping Order
X12 940 (Warehouse Shipping Order) is the EDI transaction exchanged between NLS (National Logistics Services) (NLS (National Logistics Services)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 18
- Loops
- 3
- X12 940
- All partners ↗
Transaction context
Where 940 Warehouse Shipping Order fits on NLS (National Logistics Services)
On NLS (National Logistics Services), the X12 940 Warehouse Shipping Order precedes the 945 Warehouse Shipping Advice in the Warehouse fulfillment cycle.
- NLS (National Logistics Services) channels
- 1 of 1
- Trading partners
- 18
- Channels
- 20
1 of NLS (National Logistics Services)'s 1 channel carries 940
partners across the Stacksync network trade 940
channels network-wide carry 940
Most common alongside 940
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.
When it fires: 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.
Common 940 rejection causes
- Missing mandatory segments or X12 version/release mismatches between the depositor's map and the warehouse's map, rejecting the order before it reaches the WMS.
- Line-item defects: wrong item numbers, incorrect quantities, or missing units of measure that break the match against the warehouse item master.
- Invalid ship-to addresses or missing facility codes that route goods to the wrong destination.
- Wrong or invalid requested ship and delivery dates, or missing carrier and transportation-mode instructions, which stall routing and appointment scheduling.
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
| 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
Full segment guideline — 18 segments 3 loops · X12 940 Warehouse Shipping Order
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit identifying numbers and other basic data for this transaction set
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To identify a person or office to whom administrative communications should be directed
To transmit identifying information as specified by the Reference Identification Qualifier
To specify pertinent dates and times
To transmit information in a free-form format, if necessary, for comment or special instruction
To specify transportation instructions relating to shipment
LX Loop
To reference a line number in a transaction set
W01 Loop
To transmit basic and most frequent shipment-related line-item data elements
To describe an item in free-form format
To specify summary details of total items shipped in terms of quantity, weight, and volume
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To indicate the total monetary amount
Trading partners
7+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
NLS (National Logistics Services) NLS (National Logistics Services) EDI 940 FAQ
Common questions about 940 Warehouse Shipping Order on the NLS (National Logistics Services) channel.
What is X12 940 Warehouse Shipping Order?
X12 940 (Warehouse Shipping Order) is the EDI transaction set used to exchange warehouse shipping order data. NLS (National Logistics Services)'s NLS (National Logistics Services) channel requires it from trading partners.
Does NLS (National Logistics Services) NLS (National Logistics Services) require 940 for trading partners?
Yes, NLS (National Logistics Services) (NLS (National Logistics Services)) supports X12 940 Warehouse Shipping Order. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate NLS (National Logistics Services) 940 with Stacksync?
Most companies go live with NLS (National Logistics Services) 940 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 940 on NLS (National Logistics Services)?
On NLS (National Logistics Services), X12 940 is typically exchanged alongside 945 Warehouse Shipping Advice, 943 Warehouse Stock Transfer Shipment Advice, 856 Ship Notice Manifest, 944 Warehouse Stock Transfer Receipt Advice. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your NLS (National Logistics Services) EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
