Skip to main content

X12 947 — Warehouse Inventory Adjustment Advice

The X12 947 warehouse inventory adjustment advice is sent by a warehouse or 3PL to the depositor to report inventory adjustments — damage, count corrections, or status changes — with reason codes.

EDI 947 facts

  • GS01 functional ID for 947 groups is AW — inventory adjustment advice is distinct from shipping and receiving warehouse sets.
  • 947 W19 reason codes explain why on-hand quantities changed, which is essential for accurate inventory reconciliation.
  • SignalEDI maps W15/W19 adjustment data into structured JSON so depositor systems can post inventory corrections.

Where EDI 947 fits

Direction
Warehouse / 3PL → depositor (seller)
GS functional ID
AW
Workflow position
947 keeps the depositor's inventory in sync with the warehouse: the warehouse reports adjustments so the depositor's system of record reflects true on-hand quantities.

Related sets: 944, 943, 997 · Document guide

Key segments in EDI 947

SegmentRole
STOpens transaction set 947.
W15Adjustment identification — adjustment date and number.
N1Warehouse and depositor party identification.
W19Adjustment detail — quantity, UOM, reason code, and item ID.
SETransaction set trailer.

Sample EDI 947

ST*947*0001~
W15*20260609*ADJ7781~
N1*DE*DEPOSITOR*92*DEP01~
W19*A*5*EA*IC*UP*012345678905~
SE*5*0001~

Validate samples with the free EDI validator.

Send EDI 947 with SignalEDI

// Webhook: document.received (inbound 947)
// Apply W19 adjustment quantities and reason codes to inventory of record

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

Common EDI 947 errors

  • W19 reason code missing or not mapped to an internal adjustment type
  • Adjustment quantity sign/direction misinterpreted (increase vs decrease)
  • Item ID in W19 not matching the depositor's SKU master
  • Adjustments applied without reconciliation to physical counts

Related reference

EDI 947 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.