EDI 944 Stock Transfer Receipt Advice: The Complete Guide (2026)

Inventory accuracy at a 3PL isn't lost in dramatic events; it leaks away one unverified receipt at a time. You shipped 24 pallets, the warehouse put away what it put away, and if nothing formally reports back, your ERP's number and the warehouse's number begin their slow divorce. The EDI 944 Warehouse Stock Transfer Receipt Advice is the report-back: the warehouse's structured confirmation of what it actually received from your transfer.

What comes back after the truck unloads

When a transfer you announced with a 943 arrives, the warehouse checks it in and answers with the 944. A W17 header identifies the receipt — dates, the warehouse's receipt number, and the reference back to your shipment identifier. W07 detail lines report each item's received quantity, with condition and disposition where relevant: good stock to putaway, damaged units quarantined, unexpected items received on exception. Where the operation tracks lots or dates, those ride at the line level, giving you traceability from the moment inventory enters the building.

The number that matters most is the simplest: received quantity, per item, as counted by people with no incentive to confirm your paperwork. That independence is what makes the 944 a control rather than an echo.

Frequency follows your replenishment pattern: a supplier feeding a 3PL weekly sees a handful of receipts a month, while a high-turn operation may see several a day. Either way the processing rule is identical — post on arrival, because allocations and customer promises are waiting on the stock.

Advice versus receipt: the shrink detector

Matching each 944 against its 943 turns transfers into auditable events:

• Shipped 200, received 200 — the match closes silently and on-hand at the 3PL updates. This should be almost every receipt.
• Shipped 200, received 192 — a specific, timestamped shortage with a lane, a carrier, and a trailer attached. Claimable while evidence exists, instead of surfacing months later as unexplained shrink.
• Received damaged or on exception — condition detail routes the units to inspection or claim, and your available-to-promise excludes them immediately rather than after a customer order fails to pick.

Without the match, all three outcomes look identical in your books until a cycle count disagrees with everything. And discrepancies discovered at count time are orphans: no shipment to blame, no claim window left, just a write-off. Adjustments the warehouse makes after receipt — damage found later, count corrections — arrive on the 947, which together with the 944 gives every unit at the 3PL a documented history.

The pair also disciplines the carrier conversation. Freight claims live or die on documentation windows, and a matched 943/944 with a dated shortfall is precisely the paperwork a claim needs — assembled automatically, before the window closes.

Closing the loop in the ERP

Operationally, the 944 should do its work without humans: post the receipt against the transfer order, update the remote warehouse's on-hand, release any waiting allocations, and open an exception only when quantities or conditions disagree with the advice. That last routing is where the value concentrates — the goal of the whole loop is that people look at the mismatches and only the mismatches. EDISQ automates exactly that pattern, matching 944s to 943s and posting results into your ERP alongside the outbound 940/945 traffic; the complete warehouse document set is laid out in our 3PL solution.

Cost, briefly

Receipt confirmations track your inbound replenishment cadence — a modest, steady trickle of documents. EDISQ prices them like everything else: the month's first 25 documents free, then from $0.50 apiece stepping down to $0.10 across the tiers, billed marginally, with AS2/SFTP/VAN transport included and nothing charged for mapping or setup. It's a small price for the difference between inventory records you trust and inventory records you audit.

FAQ