EDI 846 is the electronic data interchange transaction set used to communicate inventory levels between trading partners. Also known as the Inventory Inquiry/Advice, EDI 846 enables real-time visibility into stock quantities, locations, and availability—helping suppliers, distributors, and retailers coordinate replenishment and prevent stockouts.
This guide covers the EDI 846 definition, format, segments, and real-world examples.
EDI 846 at a Glance
| Attribute | Details |
|---|---|
| Transaction Set | 846 |
| Name | Inventory Inquiry/Advice |
| Standard | ANSI X12 |
| Direction | Bidirectional (inquiry or advice) |
| Purpose | Communicate inventory levels between partners |
| Common Use | Retail, distribution, manufacturing, 3PL |
| Acknowledgment | 997 Functional Acknowledgment |
Seamless EDI & ERP Integration
Connect your ERP, WMS, and business systems with automated EDI processing that eliminates manual data entry and reduces errors.
Request a Demo
What is EDI 846?
EDI 846 (Inventory Inquiry/Advice) is a standardized electronic document used to share inventory information between business partners. It can function in two ways:
- Inventory Inquiry – A request for current stock levels (“How much do you have?”)
- Inventory Advice – A notification of current stock levels (“Here’s what we have”)
The 846 transaction set follows ANSI X12 standards, ensuring compatibility across different ERP systems, warehouse management systems, and EDI platforms.
When is EDI 846 Used?
- Suppliers notifying retailers of available inventory
- Retailers requesting stock levels before placing orders
- 3PLs reporting warehouse inventory to clients
- Distributors sharing multi-location stock data
- Manufacturers advising on production availability
EDI 846 Specification: Key Segments
The EDI 846 document structure includes several required and optional segments. Here’s the specification breakdown:
| Segment | Name | Purpose | Required |
|---|---|---|---|
| ST | Transaction Set Header | Identifies the start of the 846 transaction | Yes |
| BIA | Beginning Segment | Specifies inquiry or advice, date, and reference | Yes |
| DTM | Date/Time Reference | Provides relevant dates (as-of date, ship date) | Situational |
| N1 | Party Identification | Identifies sender, receiver, ship-to locations | Situational |
| LIN | Item Identification | Product identifiers (UPC, SKU, vendor part #) | Yes |
| PID | Product Description | Item description text | Situational |
| QTY | Quantity Information | Stock quantities by type (on-hand, available, committed) | Yes |
| SE | Transaction Set Trailer | Marks the end of the transaction | Yes |
BIA Segment Details
The BIA (Beginning Segment for Inventory Inquiry/Advice) is critical—it defines whether the document is an inquiry or advice:
- BIA01 – Transaction Set Purpose Code (00=Original, 01=Cancellation, 05=Replace)
- BIA02 – Report Type Code (IB=Inquiry, IA=Advice)
- BIA03 – Reference Identification (document reference number)
- BIA04 – Date (CCYYMMDD format)
QTY Segment Details
The QTY segment communicates different quantity types:
- QTY01 – Quantity Qualifier (33=On Hand, 39=Available, 78=Committed)
- QTY02 – Quantity value
- QTY03 – Unit of Measure (optional)
EDI 846 Example
Here’s a simplified EDI 846 Inventory Advice message example:
ISA*00* *00* *ZZ*SUPPLIER *ZZ*RETAILER *260128*1200*U*00401*000000001*0*P*>~
GS*IB*SUPPLIER*RETAILER*20260128*1200*1*X*004010~
ST*846*0001~
BIA*00*IA*INV-2026-001*20260128~
N1*SU*Acme Distribution*92*ACME001~
N1*ST*Retailer Warehouse*92*RET-WH-01~
LIN**UP*012345678901*VP*WIDGET-100~
PID*F****Industrial Widget - Blue~
QTY*33*500*EA~
QTY*39*450*EA~
QTY*78*50*EA~
LIN**UP*012345678902*VP*WIDGET-200~
PID*F****Industrial Widget - Red~
QTY*33*250*EA~
QTY*39*250*EA~
SE*14*0001~
GE*1*1~
IEA*1*000000001~Example Breakdown
This EDI 846 example communicates:
- From: Acme Distribution (supplier)
- To: Retailer Warehouse
- Document Type: Inventory Advice (IA)
- Item 1 (WIDGET-100): 500 on-hand, 450 available, 50 committed
- Item 2 (WIDGET-200): 250 on-hand, 250 available, 0 committed
The difference between on-hand (33) and available (39) quantities reflects inventory that’s committed to other orders or otherwise reserved.
How EDI 846 Works in Practice
EDI 846 operates bidirectionally, supporting both push and pull inventory communication:
Inventory Advice (Push)
- Supplier’s system generates daily/hourly inventory snapshot
- EDI 846 document transmitted to trading partners
- Retailer’s system updates available-to-promise quantities
- 997 Functional Acknowledgment confirms receipt
Inventory Inquiry (Pull)
- Retailer sends EDI 846 inquiry requesting current levels
- Supplier’s system queries warehouse management system
- EDI 846 advice returned with current quantities
- Retailer uses data for purchasing decisions
EDI 846 Use Cases by Industry
Retail and E-commerce
Retailers use EDI 846 to maintain accurate available-to-promise quantities across channels. Real-time inventory visibility from suppliers enables:
- Accurate website stock displays
- Drop-ship fulfillment coordination
- Automatic reorder point triggers
- Stockout prevention
Warehouse and Distribution
3PLs and distribution centers use EDI 846 to report inventory positions to clients:
- Multi-location inventory visibility
- Lot and serial number tracking
- Expiration date reporting
- Cross-dock availability updates
Manufacturing
Manufacturers use EDI 846 to communicate raw material and finished goods availability:
- Component availability for production planning
- Finished goods ready for shipment
- Work-in-progress inventory status
Benefits of EDI 846
- Real-time visibility – Current inventory data across the supply chain
- Reduced stockouts – Proactive replenishment based on actual levels
- Eliminated manual processes – No phone calls or spreadsheet exchanges
- Improved forecasting – Historical inventory data supports demand planning
- Better customer service – Accurate availability promises
- Faster order processing – Automatic validation against available inventory
Related EDI Transactions
EDI 846 often works alongside other inventory and order transactions:
| Transaction | Name | Relationship to 846 |
|---|---|---|
| EDI 850 | Purchase Order | Orders placed based on 846 availability |
| EDI 855 | PO Acknowledgment | Confirms order against available inventory |
| EDI 856 | Advance Ship Notice | Shipment updates that adjust inventory |
| EDI 852 | Product Activity Data | Point-of-sale data that drives replenishment |
| EDI 940 | Warehouse Shipping Order | Fulfillment instructions based on 846 data |
Implementing EDI 846
Requirements
- EDI-capable system or integration platform
- Trading partner EDI agreements
- Item master synchronization (UPCs, SKUs)
- Inventory data source (WMS, ERP)
Best Practices
- Frequency – Daily updates minimum; hourly for fast-moving inventory
- Accuracy – Sync EDI 846 with real-time WMS data
- Consistency – Use standard product identifiers (UPC, GTIN)
- Testing – Validate with trading partners before go-live
How Comparatio Simplifies EDI 846
Comparatio’s integration platform handles EDI 846 complexity:
- Pre-built mappings – Connect to major retailers and suppliers without custom development
- Real-time sync – Automatic inventory updates from your WMS or ERP
- Multi-format support – Translate between EDI, API, and flat-file formats
- Error handling – Automatic validation and alerting for transmission issues
See how Comparatio streamlines EDI 846 →
EDI 846 Data Elements and Field Mapping
Successful EDI 846 implementation requires precise mapping between your internal systems and the standardized transaction format. Understanding critical data elements ensures accurate inventory communication and prevents transmission errors.
Essential Data Element Requirements
- Item Identification: Product SKUs, UPCs, or vendor part numbers must match exactly between trading partners
- Location Codes: Warehouse or distribution center identifiers using standardized location qualifiers
- Unit of Measure: Consistent measurement units (EA for each, CS for case, PL for pallet)
- Quantity Qualifiers: Specific codes defining inventory types (on-hand, available-to-promise, committed stock)
- Date/Time Stamps: Accurate as-of dates ensuring inventory freshness and preventing stale data issues
Common Field Mapping Challenges
Many organizations encounter difficulties when translating internal inventory data into EDI 846 format. Product identifiers often require cross-reference tables to map internal SKUs to trading partner item numbers. Location hierarchies must align with partner expectations—a single warehouse might need subdivision into picking zones or storage areas depending on the recipient’s requirements.
Quantity calculations present another complexity. While your WMS might track inventory across multiple statuses (received, put-away, picked, shipped), the EDI 846 typically consolidates these into standard quantity qualifiers that trading partners can universally interpret.
EDI 846 Integration with Warehouse Management Systems
Modern warehouse operations rely on seamless integration between EDI 846 transactions and warehouse management systems to maintain real-time inventory accuracy. This integration eliminates manual data entry while ensuring trading partners receive timely stock updates.
Real-Time vs. Batch Processing
Warehouse management systems can generate EDI 846 messages through two primary methods:
- Real-time triggers: Automatic transmission when inventory levels reach predetermined thresholds or after specific transactions (receipts, picks, adjustments)
- Scheduled batch processing: Regular intervals (hourly, daily) where the system compiles inventory changes and transmits consolidated updates
Real-time processing provides maximum visibility but can generate high transaction volumes. Batch processing reduces transmission frequency while still maintaining acceptable inventory freshness for most trading relationships.
System Integration Considerations
Effective EDI 846 integration requires your warehouse management system to maintain accurate lot tracking, location management, and inventory reservations. The system must distinguish between physically available inventory and stock allocated to existing orders—a critical distinction for accurate available-to-promise calculations.
Integration also demands robust error handling procedures. When EDI 846 transmissions fail or receive rejection notices, the warehouse system should flag affected inventory records and provide mechanisms for manual review and retransmission. This ensures no inventory updates are lost during communication disruptions.
Summary
EDI 846 (Inventory Inquiry/Advice) is essential for supply chain visibility. It enables trading partners to share real-time inventory data, preventing stockouts and optimizing replenishment.
Key points:
- EDI 846 can be an inquiry (request) or advice (notification)
- The BIA segment defines the document type and date
- QTY segments communicate on-hand, available, and committed quantities
- Works alongside EDI 850, 855, 856, and 852 for complete order-to-fulfillment visibility
Frequently Asked Questions
What is EDI 846?
EDI 846 is the Inventory Inquiry/Advice transaction set in the ANSI X12 standard. It’s used to communicate inventory levels between trading partners—either as an inquiry (request for stock levels) or advice (notification of stock levels).
What is the difference between EDI 846 and EDI 852?
EDI 846 communicates current inventory levels (what’s in stock). EDI 852 (Product Activity Data) reports sales and inventory movement data (what sold, what’s moving). The 852 is often used to share point-of-sale data for demand planning.
How often should EDI 846 be sent?
Frequency depends on inventory velocity. Daily updates are typical for most products. Fast-moving inventory may require hourly updates. Some trading partners specify their requirements in EDI implementation guides.
What acknowledgment is used for EDI 846?
The 997 Functional Acknowledgment confirms receipt of an EDI 846 document. It indicates whether the document was accepted or rejected due to syntax errors.
Can EDI 846 include multiple warehouse locations?
Yes. The N1 segment with qualifier “ST” (Ship To) can repeat to show inventory at different locations. Each location section includes its own LIN/QTY segments for item-level quantities.
