Skip to main content

X12 945 — Warehouse Shipping Advice

The X12 945 warehouse shipping advice is sent by a warehouse or 3PL to the depositor (seller) to confirm what was actually shipped against a 940 warehouse shipping order.

EDI 945 facts

  • GS01 functional ID for 945 groups is SW — warehouse shipping advice is grouped separately from ASN (SH) traffic.
  • 945 W12 lines confirm actual shipped quantities a depositor reconciles against the 940 order and downstream 856.
  • SignalEDI correlates inbound 945 shipment confirmations to the originating warehouse order in structured JSON.

Where EDI 945 fits

Direction
Warehouse / 3PL → depositor (seller)
GS functional ID
SW
Workflow position
945 closes the outbound warehouse loop: the depositor sends a 940 shipping order, the warehouse ships and returns a 945 confirming items, quantities, and carrier.

Related sets: 940, 856, 997 · Document guide

Key segments in EDI 945

SegmentRole
STOpens transaction set 945.
W06Warehouse shipment header — depositor order number, ship date, and references.
N1Ship-to and warehouse/depositor party identification.
W12Item detail — shipped vs ordered quantity and product ID.
W27Carrier detail — routing and SCAC.
SETransaction set trailer.

Sample EDI 945

ST*945*0001~
W06*N*DOC8842*20260609*PO1001~
N1*ST*RETAIL DC*92*DC001~
W27*M*FXFE~
W12*CC*100*100*EA**UP*012345678905~
W03*100~
SE*7*0001~

Validate samples with the free EDI validator.

Send EDI 945 with SignalEDI

// Webhook: document.received (inbound 945)
// Reconcile W12 shipped quantities against the originating 940 order

Your side can reach partner-ready setup in days, not weeks — partner certification calendars may still take longer. See the API quickstart.

Common EDI 945 errors

  • W12 shipped quantity not matching the 940 ordered quantity without a reason
  • Missing W06 depositor order number for correlation
  • Carrier (W27 SCAC) not matching the routing instruction
  • 945 sent without a corresponding 940 warehouse shipping order

Related reference

EDI 945 FAQ

Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.

SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees on core plans, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.

Supports HIPAA complianceBAA path documentedSecure API + webhooksNo per-document fees on core plans

Operations teams

A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.

Healthcare billing

837, 835, and 270/271 workflows are explained in plain English, with handling that supports HIPAA compliance and a documented BAA review path for diligence.

Developer teams

JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.

Preview case studies

© 2026 SignalEDI Inc. All rights reserved.