EDIFACT WHINRP — Warehouse Inbound Receipt Report
WHINRP extends basic receipt with putaway location, quality status, and exception reasons.
✦ What It Does
Used when partners require richer operational telemetry than WHSREC alone.
Supports high-compliance verticals with lot and serial capture.
Message pairing varies by WMS vendor adapter—validate MIG.
⚡ When It's Used
- Detailed putaway bin after provisional WHSREC.
- Quality inspection fail or split quantities.
- Bonded warehouse reporting for customs.
- Temperature-controlled lane excursion notes.
- Serialized asset capture for warranty.
Who Uses EDIFACT WHINRP
European retail & brands
Common in EDIFACT-first programs where warehouse inbound receipt report flows between HQ, DCs, and suppliers across the EU and APAC.
Global manufacturers
Automotive, industrial, and CPG companies standardize on EDIFACT for plants and suppliers outside North America.
3PLs & carriers
Logistics service providers consume or produce the message when the contract mandates UN/EDIFACT syntax and directories.
Key Segments & Constructs
EDIFACT uses a hierarchical structure: UNH (message header) opens the transaction; BGM (beginning of message) carries the document name and reference; party data uses NAD; lines often use LIN with QTY, PRI, and MOA. Exact segment requirements depend on the message directory (D.96A, etc.) and your trading partner's implementation guide.
BGM
Inbound report function.
LOC
Putaway locations and zones.
LIN / QTY / STS
Quantities with disposition status.
FTX
Exception narratives.
Related Messages
Need Help with EDIFACT WHINRP?
Better EDI maps, tests, and operates EDIFACT alongside X12—same platform, translation when partners use different standards.
Talk to an EDI Expert