The semantic role of the 945
Think of the 945 as warehouse closure: pallets staged, carriers assigned, shorts captured. It complements—not replaces—ASN obligations when retailers demand carrier-level visibility separate from DC receipts. Confusion spikes when the same TMS prints labels while two teams trigger different EDI events from overlapping timestamps.
When partners mandate the 945
Mandates cluster in 3PL-heavy supply chains and drop-ship models where the retailer never sees your DC scan directly. If your packet references “warehouse confirmation prior to ASN finalize,” treat 945 as part of critical path testing—not optional QA.
Duplicate narrative risk
If both 945 and 856 carry quantities, establish precedence rules: which document drives inventory commits in your ERP, and which drives retailer-facing promise dates. Document the rule in runbooks—future-you will not remember the tribal consensus from go-live week.
Build a testing matrix, not a single script
Certification scripts often happy-path single-SKU pallets. Production hits mixed pallets, substitutions, and partial waves. Capture three messy scenarios—split wave, cancel/repick, multi-stop truck—and prove your 945 quantities reconcile to SSCC lists attached to ASNs.
Learn more inside SignalEDI
Browse EDI vs API for hybrid stacks and comparison hub if you evaluate platforms during document remediation.
Related Reading
Frequently Asked Questions
Q: Is the 945 a replacement for the 856?
No—they solve different visibility layers. The 856 tells the retailer what left your sphere toward theirs; the 945 often reflects warehouse-level disposition inside a 3PL network. Programs specify which document carries legal receipt triggers—never assume interchangeability.
Q: Who generates the 945 when a 3PL ships for me?
Typically the warehouse operator whose WMS owns the physical pick/pack/ship truth—unless your contract centralizes EDI on your tenant. Clarify EDI responsibility in the 3PL agreement; ambiguous ownership causes silent omissions.
Q: Can one shipment produce both 945 and 856?
Yes in multi-leg models—internal consolidation hubs, then outbound retailer-directed legs. The risk is contradictory quantities or times; orchestrate a single source of carton counts feeding both narratives.
Q: Where does SignalEDI help Document 945 mapping?
SignalEDI validates cross-document consistency and surfaces human-readable exceptions before trading partners see rejects—pair with /resources/edi-transactions for code references and /pricing for SMB tiers.