EDIFACT message guide · Planning and inventory
INVRPT Inventory report
The UN/EDIFACT message trading partners use to share information about held inventories, in either direction.
- Sent by
- Party holding the inventory (supplier, retailer or warehouse)
- Received by
- Trading partner that plans against it
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- 846 Inventory Inquiry/Advice
What is the EDIFACT INVRPT message?
INVRPT is the UN/EDIFACT inventory report message. The directory defines it as a message specifying information relating to held inventories, intended for use in either direction between trading partners. It reports stock levels by product and location, with qualifiers for available, reserved, damaged or in-transit quantities and the dates they apply to.
Suppliers use it to give retailers and marketplaces available-to-sell stock, and retailers or warehouses use it to report stock so that suppliers can manage replenishment, as in vendor-managed inventory.
How to read this diagram: the top row shows who sends INVRPT, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around INVRPT and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.
When it is used
- Sharing available stock with retailers or marketplaces
- Reporting store or warehouse stock for vendor-managed inventory
- Reporting stock held by a third-party warehouse
Where it fits in the message flow
Structure
Mandatory segments in INVRPT (directory D.21A)
In UN/EDIFACT directory D.21A, the INVRPT message has 58 segment positions arranged in 19 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.
- UNH
- BGM
- DTM
- UNT
Practical example
INVRPT in practice
A consumer electronics brand manages inventory at a retailer's distribution centers. Each night the retailer sends an INVRPT with stock on hand and in transit for each item at each DC. The brand's planning system calculates replenishment needs and creates orders for the retailer to confirm.
Implementation
Implementation considerations for INVRPT
- Agree what each quantity qualifier means, such as available versus on hand.
- Report as of a clear date and time, so stale data is recognized.
- Use consistent product and location identifiers.
- Decide between full snapshots and changes only.
How ECOM helps
Automate INVRPT with ECOM
Solution
Supply Chain Visibility
Track orders, shipments and invoices across partners and catch exceptions early.
Industry
Retail
Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.
Industry
Consumer Goods
Retail, distributor, marketplace and direct-channel integration for consumer brands.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related planning and inventory messages
Need help with INVRPT?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.