What Is EDI 846? Inventory Inquiry / Advice Explained

The ANSI X12 inventory inquiry or inventory advice transaction used to communicate inventory availability.

EDI 846 The ANSI X12 inventory inquiry or inventory advice transaction used to communicate inventory availability. The EDI 846 lets trading partners exchange structured inventory details—on-hand quantities, available-to-promise, reserved stock, and basic location or lot information—so buyers, suppliers, carriers, and warehouses can make replenishment and fulfillment decisions without manual spreadsheets.

Used across retail, manufacturing, 3PL, and distribution networks, the 846 is a readout of inventory state rather than an order or shipment notice. It’s commonly produced by an ERP or warehouse management system (WMS) and consumed by suppliers, customers, or vendors that need up-to-date visibility for planning, vendor-managed inventory (VMI), or automated replenishment.

What The Transaction Typically Covers

• On-Hand Quantity: Current physical count available at the warehouse or location.
• Available Quantity: Quantity that can be promised after accounting for reservations and holds.
• On-Order/Incoming: Quantities expected from purchase orders or transfer receipts with estimated dates.
• Location Or Facility: Warehouse, aisle/bin, or site identifiers so recipients map figures to their systems.
• Lot/Serial And Expiry: When applicable—perishable or serialized inventory needs these fields.

Why It Matters

Accurate inventory visibility reduces stockouts, overstock, and manual reconciliation work. For a retailer receiving nightly 846s from multiple distribution centers, planners can adjust purchase orders before shortages affect sales. 3PLs use 846 feeds to report client holdings; suppliers use them to trigger production or shipments. The 846 supports operational cadence—daily, intraday, or event-driven updates—depending on velocity and agreement.

How The Format And Usage Varies

Although the 846 is an ANSI X12 standard, implementations differ by trading partner. Variations include segment usage for lot numbers, whether available quantity is net of allocations, and whether multiple locations are sent in one message. Transmission methods also vary—AS2, SFTP, or via a VAN—and modern integrations may wrap EDI content in APIs through middleware.

Who Sends And Who Receives

In a distributor-supplier relationship the party maintaining the physical stock (typically a warehouse operator or 3PL) is the sender. The receiver is usually a supplier, buyer, or inventory planner. In VMI arrangements the supplier often requests or subscribes to 846 feeds so they can replenish automatically; in replenishment-on-consumption models the retailer or buyer consumes 846 data to create POs or shipments.

Practical Example

A clothing retailer receives nightly 846 messages from three regional DCs. Each 846 lists SKU-level on-hand and available quantities per DC plus incoming purchase order receipts. The retailer’s replenishment engine consolidates the three feeds, calculates safety stock shortfalls, and issues replenishment POs to suppliers. Because the 846 includes incoming receipts, the engine avoids ordering stock already en route.

Implementation Tips For Reliability

• Agree On Definitions: Clarify whether "available" excludes allocated and reserved stock so both parties interpret numbers consistently.
• Define Frequency: Set update cadence (nightly, hourly, on-change) based on SKU velocity and system load.
• Map Carefully: Map ERP/WMS fields to X12 segments precisely; document lot/serial and date fields explicitly.
• Validate And Monitor: Use schema checks and reconciliation routines (e.g., totals vs. daily snapshots) to catch spikes or missing data.
• Use Middleware: Consider an integration layer for protocol translation (AS2/SFTP) and logging, especially when partners have different EDI capabilities.

In short, the EDI 846 is an operational inventory visibility message that, when standardized between partners, reduces manual reconciliation and improves replenishment decisions by communicating timely availability data.