--- title: "EDI 940 Warehouse Shipping Order: X12 940 Guide | Stacksync" description: "EDI 940 is the X12 Warehouse Shipping Order, used when stock is released to a warehouse for shipping. See key segments (W05, LX, W01) and mapping checks." canonical: https://www.stacksync.com/edi/x12/940-warehouse-shipping-order last_modified: 2026-09-29 --- X12 transaction code # EDI 940 Warehouse Shipping Order (X12 940) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 940 is the X12 Warehouse Shipping Order transaction set, used when stock is released to a warehouse for shipping. The supplier or manufacturer that owns the inventory (the depositor) sends the 940 to the 3PL warehouse or fulfillment center holding the stock. Standard X12 Code 940 Partner references 18 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 940 at a glance What the 940 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 940 Warehouse Shipping Order summary** | | | | --- | --- | | Document | X12 940 Warehouse Shipping Order | | Business record | Warehouse fulfillment order | | Who sends it to whom | The supplier or manufacturer that owns the inventory (the depositor) sends the 940 to the 3PL warehouse or fulfillment center holding the stock. | | When it is sent | 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. | | Match on | Warehouse order, owner, ship-to and item | | Partner references | 18 trading partners in this directory | | Related documents | [X12 945 Warehouse Shipping Advice](https://www.stacksync.com/edi/x12/945-warehouse-shipping-advice), [X12 943 Warehouse Stock Transfer Shipment Advice](https://www.stacksync.com/edi/x12/943-warehouse-stock-transfer-shipment-advice), [X12 944 Warehouse Stock Transfer Receipt Advice](https://www.stacksync.com/edi/x12/944-warehouse-stock-transfer-receipt-advice) | ### Key segments in an EDI 940 The business segments that appear in at least half of the 20 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send. | Segment | Name | Purpose | Partner references | | --- | --- | --- | --- | | W05 | Shipping Order Identification | To transmit identifying numbers and other basic data for this transaction set. | 20 of 20 | | LX | Assigned Number | To reference a line number in a transaction set. | 20 of 20 | | W01 | Line Item Detail - Warehouse | To transmit basic and most frequent shipment-related line-item data elements. | 20 of 20 | | N1 | Name | To identify a party by type of organization, name, and code. | 19 of 20 | | N3 | Address Information | To specify the location of the named party. | 19 of 20 | | N4 | Geographic Location | To specify the geographic place of the named party. | 19 of 20 | | N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 19 of 20 | | G62 | Date/Time | To specify pertinent dates and times. | 19 of 20 | | W66 | Warehouse Carrier Information | To specify transportation instructions relating to shipment. | 19 of 20 | | NTE | Note/Special Instruction | To transmit information in a free-form format, if necessary, for comment or special instruction. | 16 of 20 | Stacksync connects EDI documents such as the X12 940 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. Implementation guide ## X12 940 mapping and validation X12 940 Warehouse Shipping Order is used when stock is released to a warehouse for shipping. Preserve warehouse order, owner, ship-to and item so the warehouse fulfillment order in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **warehouse fulfillment order** warehouse order, owner, ship-to and item | Define which combination of warehouse order, owner, ship-to and item identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the warehouse fulfillment order** ID assigned by the receiving system and processing result | Test a cancellation after picking and define who approves any warehouse reversal. Validate owner-specific SKU and unit mappings before allocating stock. | | Check the processing result | **Processing status for the warehouse fulfillment order** Original document reference and matching response | Reconcile the warehouse fulfillment order with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### How the related documents differ Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately. - [X12 945 Warehouse Shipping Advice](https://www.stacksync.com/edi/x12/945-warehouse-shipping-advice) **warehouse shipment confirmation:** a warehouse reports what it shipped. - [X12 943 Warehouse Stock Transfer Shipment Advice](https://www.stacksync.com/edi/x12/943-warehouse-stock-transfer-shipment-advice) **warehouse transfer shipment:** stock has been shipped toward another warehouse. - [X12 944 Warehouse Stock Transfer Receipt Advice](https://www.stacksync.com/edi/x12/944-warehouse-stock-transfer-receipt-advice) **warehouse transfer receipt:** a warehouse reports received transfer stock. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when stock is released to a warehouse for shipping. Name the operational owner of the warehouse fulfillment order and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map warehouse order, owner, ship-to and item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier. 3. #### Test failures before launch Run the failure cases in the mapping table against realistic warehouse fulfillment order data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate. 4. #### Track every document to completion Record transport delivery and document validation separately from successful warehouse fulfillment order processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 940 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic warehouse fulfillment order data. - Each submitted document can be traced through delivery, validation and processing in the receiving system. - Your team knows how to investigate and recover a rejected or timed-out warehouse fulfillment order without processing it twice. ### Related documents and resources - [X12 945 Warehouse Shipping Advice](https://www.stacksync.com/edi/x12/945-warehouse-shipping-advice) - [X12 943 Warehouse Stock Transfer Shipment Advice](https://www.stacksync.com/edi/x12/943-warehouse-stock-transfer-shipment-advice) - [X12 944 Warehouse Stock Transfer Receipt Advice](https://www.stacksync.com/edi/x12/944-warehouse-stock-transfer-receipt-advice) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) Document structure ## X12 940 Warehouse Shipping Order at the element level The X12 940 reference contains 33 segment entries and 106 data elements; 53 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 33 Data elements 106 Mandatory elements 53 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 940 18 partners, 20 channels. Choose a channel to inspect its listed document reference and implementation context. - [Americold Logistics, LLC.](https://www.stacksync.com/edi/americold-oracle) [Americold](https://www.stacksync.com/edi/americold-oracle/americold/x12-940-warehouse-shipping-order) - [ASUSTeK Computer Inc. (dba ASUS)](https://www.stacksync.com/edi/asus) [ASUS](https://www.stacksync.com/edi/asus/asus/x12-940-warehouse-shipping-order) - [AT&T Inc.](https://www.stacksync.com/edi/att) [AT&T (Legacy ISA ID: 108024050NHP)](https://www.stacksync.com/edi/att/at-t-legacy-isa-id-108024050nhp/x12-940-warehouse-shipping-order) [AT&T (New ISA ID: 108024050B2B)](https://www.stacksync.com/edi/att/at-t-new-isa-id-108024050b2b/x12-940-warehouse-shipping-order) - [Atlanta Bonded Warehouse](https://www.stacksync.com/edi/atlanta-bonded-warehouse) [Atlanta Bonded Warehouse](https://www.stacksync.com/edi/atlanta-bonded-warehouse/atlanta-bonded-warehouse/x12-940-warehouse-shipping-order) - [Dot Foods, Inc.](https://www.stacksync.com/edi/dot-foods-inc) [Dot Foods, Inc (Distribution)](https://www.stacksync.com/edi/dot-foods-inc/dot-foods-inc-distribution/x12-940-warehouse-shipping-order) [Dot Foods, Inc (E-commerce)](https://www.stacksync.com/edi/dot-foods-inc/dot-foods-inc-e-commerce/x12-940-warehouse-shipping-order) - [Dow Inc.](https://www.stacksync.com/edi/dow-inc) [Dow](https://www.stacksync.com/edi/dow-inc/dow/x12-940-warehouse-shipping-order) - [Expeditors](https://www.stacksync.com/edi/expeditors) [Expeditors](https://www.stacksync.com/edi/expeditors/expeditors/x12-940-warehouse-shipping-order) - [Fraser Direct](https://www.stacksync.com/edi/fraser-direct) [Fraser Direct](https://www.stacksync.com/edi/fraser-direct/fraser-direct/x12-940-warehouse-shipping-order) - [Google](https://www.stacksync.com/edi/google) [Google](https://www.stacksync.com/edi/google/google/x12-940-warehouse-shipping-order) - [Hub Group \\ Unyson](https://www.stacksync.com/edi/hub-group--unyson) [CASESTACK RETAIL SUPPLIER SOLUTIONS](https://www.stacksync.com/edi/hub-group--unyson/casestack-retail-supplier-solutions/x12-940-warehouse-shipping-order) - [Lineage, Inc.](https://www.stacksync.com/edi/lineage-logistics) [Lineage](https://www.stacksync.com/edi/lineage-logistics/lineage/x12-940-warehouse-shipping-order) - [Niagara Bottling](https://www.stacksync.com/edi/niagara-bottling) [Niagara Bottling](https://www.stacksync.com/edi/niagara-bottling/niagara-bottling/x12-940-warehouse-shipping-order) - [NLS (National Logistics Services)](https://www.stacksync.com/edi/national-logistic-services) [NLS (National Logistics Services)](https://www.stacksync.com/edi/national-logistic-services/nls-national-logistics-services/x12-940-warehouse-shipping-order) - [Quaker Oats Company (A Pepsico Company)](https://www.stacksync.com/edi/quaker-a-pepsico-company) [Quaker Oats](https://www.stacksync.com/edi/quaker-a-pepsico-company/quaker-oats/x12-940-warehouse-shipping-order) - [RJW Logistics, LLC](https://www.stacksync.com/edi/rjw-logistics-llc) [RJW Logistics, LLC](https://www.stacksync.com/edi/rjw-logistics-llc/rjw-logistics-llc/x12-940-warehouse-shipping-order) - [Stord](https://www.stacksync.com/edi/stord) [SPS Stord](https://www.stacksync.com/edi/stord/sps-stord/x12-940-warehouse-shipping-order) - [Ventura Foods](https://www.stacksync.com/edi/ventura-foods) [Ventura Foods, LLC](https://www.stacksync.com/edi/ventura-foods/ventura-foods-llc/x12-940-warehouse-shipping-order) - [Warehouse Leader](https://www.stacksync.com/edi/warehouse-leader) [Warehouse Leader](https://www.stacksync.com/edi/warehouse-leader/warehouse-leader/x12-940-warehouse-shipping-order) Catalog breakdown ## Where X12 940 Warehouse Shipping Order appears in this catalog The largest groups of classified 940 catalog entries are in logistics & transport, grocery & food and electronics & technology. ### By industry - logistics & transport 10 channels - grocery & food 5 channels - electronics & technology 4 channels - manufacturing & industrial 1 channel Partner entries with the most listed channels - [AT&T Inc.](https://www.stacksync.com/edi/att) - [Dot Foods, Inc.](https://www.stacksync.com/edi/dot-foods-inc) - [Americold Logistics, LLC.](https://www.stacksync.com/edi/americold-oracle) - [ASUSTeK Computer Inc. (dba ASUS)](https://www.stacksync.com/edi/asus) - [Atlanta Bonded Warehouse](https://www.stacksync.com/edi/atlanta-bonded-warehouse) - [Dow Inc.](https://www.stacksync.com/edi/dow-inc) - [Expeditors](https://www.stacksync.com/edi/expeditors) - [Fraser Direct](https://www.stacksync.com/edi/fraser-direct) FAQ ## EDI 940 questions ### What is an EDI 940? EDI 940 is the X12 Warehouse Shipping Order transaction set. Trading partners use it when stock is released to a warehouse for shipping. It carries the data for the warehouse fulfillment order, and your system matches it on warehouse order, owner, ship-to and item. ### Who sends an EDI 940 and who receives it? The supplier or manufacturer that owns the inventory (the depositor) sends the 940 to the 3PL warehouse or fulfillment center holding the stock. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 940 sent? 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. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 940? Across 20 partner document references listed here, the business segments that appear most often include W05 (Shipping Order Identification), LX (Assigned Number), W01 (Line Item Detail - Warehouse), N1 (Name), N3 (Address Information), N4 (Geographic Location). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 940 and EDI 945? The 940 tells the warehouse what to ship. The 945 is the warehouse's reply once the order leaves, with the quantities and carrier details that actually shipped. ### What should I map for X12 940? Start with warehouse order, owner, ship-to and item and the target warehouse fulfillment order. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats. ### How should I test 940 error handling? Test a cancellation after picking and define who approves any warehouse reversal. Validate owner-specific SKU and unit mappings before allocating stock. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 940? The directory on this page links 18 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ## Connect EDI to your business systems See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)