---
title: "EDI 945 Warehouse Shipping Advice: X12 945 Guide | Stacksync"
description: "EDI 945 is the X12 Warehouse Shipping Advice, used when a warehouse reports what it shipped. See key segments (W06, N1, LX) and mapping checks."
canonical: https://www.stacksync.com/edi/x12/945-warehouse-shipping-advice
last_modified: 2026-09-29
---

X12 transaction code

# EDI 945 Warehouse Shipping Advice (X12 945)

> 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 945 is the X12 Warehouse Shipping Advice transaction set, used when a warehouse reports what it shipped. The 3PL or warehouse sends the 945 back to the supplier, manufacturer, or seller whose goods it ships.

Standard

X12

Code

945

Partner references

13

[Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi)

At a glance

## EDI 945 at a glance

What the 945 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.

**X12 945 Warehouse Shipping Advice summary**

|  |  |
| --- | --- |
| Document | X12 945 Warehouse Shipping Advice |
| Business record | Warehouse shipment confirmation |
| Who sends it to whom | The 3PL or warehouse sends the 945 back to the supplier, manufacturer, or seller whose goods it ships. |
| When it is sent | The warehouse completes picking, packing, and carrier handoff for a 940-directed order and the freight leaves the dock. |
| Match on | Warehouse order, shipment and shipped line |
| Partner references | 13 trading partners in this directory |
| Related documents | [X12 940 Warehouse Shipping Order](https://www.stacksync.com/edi/x12/940-warehouse-shipping-order), [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest), [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice) |

### Key segments in an EDI 945

The business segments that appear in at least half of the 14 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 |
| --- | --- | --- | --- |
| W06 | Warehouse Shipment Identification | To provide identifying numbers, dates, and other basic data for this transaction set. | 14 of 14 |
| N1 | Name | To identify a party by type of organization, name, and code. | 14 of 14 |
| LX | Assigned Number | To reference a line number in a transaction set. | 14 of 14 |
| W27 | Carrier Detail | To specify details of the transportation equipment and carrier routing details. | 13 of 14 |
| W12 | Warehouse Item Detail | To designate those line items that were shipped. | 13 of 14 |
| W03 | Total Shipment Information | To provide totals relating to the shipment. | 12 of 14 |
| N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 11 of 14 |
| G62 | Date/Time | To specify pertinent dates and times. | 11 of 14 |
| N3 | Address Information | To specify the location of the named party. | 10 of 14 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 10 of 14 |

Stacksync connects EDI documents such as the X12 945 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 945 mapping and validation

X12 945 Warehouse Shipping Advice is used when a warehouse reports what it shipped. Preserve warehouse order, shipment and shipped line so the warehouse shipment confirmation 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 shipment confirmation** warehouse order, shipment and shipped line | Define which combination of warehouse order, shipment and shipped line identifies one business record, its lines and any later revision. |
| Update the receiving system | **Processing the warehouse shipment confirmation** ID assigned by the receiving system and processing result | Test partial fulfillment and leave the unshipped order quantity open. Reconcile shipped units and tracking references before preparing a customer-facing shipment notice. |
| Check the processing result | **Processing status for the warehouse shipment confirmation** Original document reference and matching response | Reconcile the warehouse shipment confirmation 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 940 Warehouse Shipping Order](https://www.stacksync.com/edi/x12/940-warehouse-shipping-order)

  **warehouse fulfillment order:** stock is released to a warehouse for shipping.
- [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest)

  **shipment notice (ASN):** an order ships, before the goods arrive.
- [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice)

  **accounts-receivable or accounts-payable invoice:** a bill is ready for the buyer to process.

### Implementation steps

1. #### Choose the starting event and owner

   Decide which application acts when a warehouse reports what it shipped. Name the operational owner of the warehouse shipment confirmation and the team that resolves rejected or ambiguous messages.
2. #### Keep record IDs connected

   Map warehouse order, shipment and shipped line. 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 shipment confirmation 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 shipment confirmation processing. Give unresolved errors an owner and check the receiving system before approving retries.

### Go-live checklist

- An approved 945 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic warehouse shipment confirmation 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 shipment confirmation without processing it twice.

### Related documents and resources

- [X12 940 Warehouse Shipping Order](https://www.stacksync.com/edi/x12/940-warehouse-shipping-order)
- [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest)
- [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice)
- [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 945 Warehouse Shipping Advice at the element level

The X12 945 reference contains 58 segment entries and 279 data elements; 68 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments

58

Data elements

279

Mandatory elements

68

**Segments with elements marked mandatory in this reference**

| Segment | Elements | Mandatory |
| --- | --- | --- |
| W06 | 12 | 1 |
| N1 | 6 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| PER | 9 | 1 |
| N9 | 6 | 1 |
| G61 | 5 | 2 |
| NTE | 2 | 1 |
| W27 | 10 | 1 |
| W6 | 4 | 1 |
| W28 | 8 | 1 |
| G72 | 11 | 2 |

Key identifiers in 945

- Reporting Code
- Entity Identifier Code
- Name
- Address Information
- Contact Function Code
- Reference Identification Qualifier
- Description
- Transportation Method/Type Code

## Find your trading partner for X12 945

13 partners, 14 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-945-warehouse-shipping-advice)
- [ASUSTeK Computer Inc. (dba ASUS)](https://www.stacksync.com/edi/asus)

  [ASUS](https://www.stacksync.com/edi/asus/asus/x12-945-warehouse-shipping-advice)
- [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-945-warehouse-shipping-advice) [Dot Foods, Inc (E-commerce)](https://www.stacksync.com/edi/dot-foods-inc/dot-foods-inc-e-commerce/x12-945-warehouse-shipping-advice)
- [Dow Inc.](https://www.stacksync.com/edi/dow-inc)

  [Dow](https://www.stacksync.com/edi/dow-inc/dow/x12-945-warehouse-shipping-advice)
- [Google](https://www.stacksync.com/edi/google)

  [Google](https://www.stacksync.com/edi/google/google/x12-945-warehouse-shipping-advice)
- [Lineage, Inc.](https://www.stacksync.com/edi/lineage-logistics)

  [Lineage](https://www.stacksync.com/edi/lineage-logistics/lineage/x12-945-warehouse-shipping-advice)
- [Niagara Bottling](https://www.stacksync.com/edi/niagara-bottling)

  [Niagara Bottling](https://www.stacksync.com/edi/niagara-bottling/niagara-bottling/x12-945-warehouse-shipping-advice)
- [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-945-warehouse-shipping-advice)
- [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-945-warehouse-shipping-advice)
- [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-945-warehouse-shipping-advice)
- [Stord](https://www.stacksync.com/edi/stord)

  [SPS Stord](https://www.stacksync.com/edi/stord/sps-stord/x12-945-warehouse-shipping-advice)
- [Ventura Foods](https://www.stacksync.com/edi/ventura-foods)

  [Ventura Foods, LLC](https://www.stacksync.com/edi/ventura-foods/ventura-foods-llc/x12-945-warehouse-shipping-advice)
- [Warehouse Leader](https://www.stacksync.com/edi/warehouse-leader)

  [Warehouse Leader](https://www.stacksync.com/edi/warehouse-leader/warehouse-leader/x12-945-warehouse-shipping-advice)

Catalog breakdown

## Where X12 945 Warehouse Shipping Advice appears in this catalog

The largest groups of classified 945 catalog entries are in logistics & transport, grocery & food and electronics & technology.

### By industry

- logistics & transport 6 channels
- grocery & food 5 channels
- electronics & technology 2 channels
- manufacturing & industrial 1 channel

Partner entries with the most listed channels

- [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)
- [Dow Inc.](https://www.stacksync.com/edi/dow-inc)
- [Google](https://www.stacksync.com/edi/google)
- [Lineage, Inc.](https://www.stacksync.com/edi/lineage-logistics)
- [Niagara Bottling](https://www.stacksync.com/edi/niagara-bottling)
- [NLS (National Logistics Services)](https://www.stacksync.com/edi/national-logistic-services)

FAQ

## EDI 945 questions

### What is an EDI 945?

EDI 945 is the X12 Warehouse Shipping Advice transaction set. Trading partners use it when a warehouse reports what it shipped. It carries the data for the warehouse shipment confirmation, and your system matches it on warehouse order, shipment and shipped line.

### Who sends an EDI 945 and who receives it?

The 3PL or warehouse sends the 945 back to the supplier, manufacturer, or seller whose goods it ships. Your trading partner agreement confirms the direction and version for your account.

### When is an EDI 945 sent?

The warehouse completes picking, packing, and carrier handoff for a 940-directed order and the freight leaves the dock. Your partner guide sets any deadline or schedule for the document.

### What are the key segments in an EDI 945?

Across 14 partner document references listed here, the business segments that appear most often include W06 (Warehouse Shipment Identification), N1 (Name), LX (Assigned Number), W27 (Carrier Detail), W12 (Warehouse Item Detail), W03 (Total Shipment Information). Each partner guide sets which segments and elements your account must send.

### What is the difference between EDI 945 and EDI 940?

The 940 is the shipping order the owner of the goods sends to the warehouse. The 945 confirms what the warehouse shipped against it, including any lines it shipped short.

### What should I map for X12 945?

Start with warehouse order, shipment and shipped line and the target warehouse shipment confirmation. 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 945 error handling?

Test partial fulfillment and leave the unshipped order quantity open. Reconcile shipped units and tracking references before preparing a customer-facing shipment notice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

### Which partners list X12 945?

The directory on this page links 13 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)
