EDI 846: Inventory inquiry, format, and how it works

Inventory accuracy is not just a reporting problem. It is a synchronization problem.

As businesses scale across suppliers, warehouses, and sales channels, the challenge is no longer tracking inventory in one system. It is keeping inventory availability, quantity, and replenishment data consistent across every system that depends on it.

That is where the EDI 846 transaction comes in.

The EDI 846 inventory inquiry/advice transaction is a core part of electronic data interchange workflows. It enables trading partners to exchange structured inventory data, providing buyers, suppliers, distributors, warehouses, and commerce platforms with visibility into item availability, stock levels, locations, and replenishment signals across systems.

At enterprise scale, the value of the EDI 846 document depends on more than the format itself. It depends on how that data moves between ERP systems, warehouse systems, ecommerce platforms, and trading partner networks — and how reliably those flows operate in production.

What is EDI 846?

The EDI 846 is a standardized X12 EDI transaction used to communicate inventory information between trading partners.

In simple terms, it is an electronic inventory report or inventory inquiry/advice document.

The EDI 846 transaction allows trading partners to exchange structured data about:

• Item availability
• Inventory quantity
• Warehouse or location-level stock
• Inventory status
• Replenishment or planning indicators

In many retail and distribution workflows, suppliers use the EDI 846 to send buyers inventory availability, quantity, and location details. But the transaction is not limited to supplier-to-buyer communication. It may also be used between sellers, marketplaces, distributors, warehouses, 3PLs, and other trading partners that need inventory visibility.

The 846 can be used in two common ways:

• Inventory inquiry response: A trading partner requests inventory data, and another trading partner responds.
• Inventory advice or update: A trading partner proactively sends inventory availability or stock-level updates.

This is why the transaction is often referred to as the EDI 846 inventory inquiry/advice transaction.

Unlike a static report, the 846 is part of an ongoing electronic data interchange workflow, where inventory data is exchanged and updated across systems according to business rules, trading partner requirements, and integration schedules.

EDI 846 format and specification

The EDI 846 specification follows the X12 standard, which defines how inventory data is structured into segments and elements.

Rather than focusing on every possible segment, it is more useful to understand how the EDI 846 format represents inventory data in a way downstream systems can process.

Key data elements in an EDI 846

A typical 846 EDI document may include:

Header information

• Sender and receiver identifiers
• Transaction date
• Inventory report or inquiry reference number
• Transaction purpose or report type
• Warehouse, supplier, buyer, or location identifiers

Item-level details

• Item or product identifier
• Buyer item number, vendor item number, UPC, GTIN, SKU, or other product code
• Available quantity
• On-hand quantity
• Unit of measure
• Inventory status (i.e. available, backordered, allocated, discontinued, or unavailable)

Location data

• Warehouse or distribution center
• Store, fulfillment location, or inventory node
• Location-specific inventory availability

Additional attributes

• Partner-specific replenishment or planning indicators
• Lead time or availability dates, when required by the trading partner
• Allocation, reserved, committed, in-transit, or on-hand stock indicators
• Product descriptions or item attributes, depending on the implementation guide

These elements allow systems to determine not just what inventory exists, but whether it is actually available for fulfillment.

Common EDI 846 segments

Common segments in an EDI 846 include:

• BIA — Beginning Segment for Inventory Inquiry/Advice: identifies the transaction purpose, report type, reference number, and date.
• N1 — Name or party identification: identifies trading partners, warehouses, buyers, suppliers, or other relevant parties.
• LIN — Item identification: identifies the product using partner-specific item numbers, vendor part numbers, UPCs, GTINs, SKUs, or other identifiers.
• QTY — Quantity information: communicates inventory quantities such as available, on-hand, allocated, reserved, or other quantity types.
• DTM — Date/time reference: communicates relevant dates, such as inventory effective date, availability date, or report date.
• CTT — Transaction totals: summarizes counts or totals for validation.

The exact segment usage depends on the trading partner’s implementation guide. One partner may require only item identification and available quantity. Another may require multiple inventory quantity types, warehouse-level detail, lead time, status codes, or location-specific availability.

EDI 846 example

A simplified EDI 846 transaction might look like this:

ST*846*0001~
BIA*00*SI*INV-1001*20260529~
N1*WH*Warehouse 1*92*WH1~
LIN*1*VP*ITEM123~
QTY*33*150*EA~
CTT*1~
SE*7*0001~

In this simplified example:

• ST starts the EDI 846 transaction.
• BIA identifies the inventory inquiry/advice transaction.
• N1 identifies the warehouse location.
• LIN identifies the item.
• QTY communicates the available quantity.
• CTT summarizes the transaction.
• SE closes the transaction set.

This example communicates that item ITEM123 has an available quantity of 150 EA at warehouse WH1.

Actual EDI 846 documents may include interchange and group envelopes, multiple items, multiple locations, multiple quantity types, product descriptions, date references, partner-specific qualifiers, and validation rules.

How the EDI 846 works in a real workflow

The EDI 846 does not operate in isolation. It is part of a broader EDI and inventory synchronization lifecycle.

A typical flow may look like this:

Supplier or inventory owner sends an EDI 846 inventory update
       ↓
Buyer, marketplace, or trading partner receives and processes the transaction
       ↓
Inventory availability is updated across connected systems
       ↓
Buyer or downstream system uses that data to make ordering decisions
       ↓
Buyer sends an EDI 850 purchase order
       ↓
Supplier responds with an EDI 855 purchase order acknowledgment
       ↓
Shipment is communicated with an EDI 856 advance ship notice
       ↓
Invoice is sent with an EDI 810

The key role of the EDI 846 transaction is upstream: it influences what can be ordered, not how an order is confirmed.

Trading partners may also exchange a functional acknowledgment, such as an EDI 997 or EDI 999, to confirm whether the 846 transaction was received and accepted or rejected at the EDI validation level.

Without accurate 846 data:

• Buyers may over-order.
• Suppliers may overcommit.
• Commerce systems may oversell.
• Warehouses may receive inaccurate replenishment signals.
• Systems may drift out of sync.

Benefits of EDI 846 inventory integration

Accurate inventory availability across systems

When EDI inventory data is synchronized across systems, businesses can reduce overselling, backorders, and stock discrepancies. Inventory quantity becomes more consistent across ERP, warehouse, commerce, supplier, and marketplace systems.

Faster replenishment decisions

Timely or near-real-time inventory visibility, depending on the integration design, allows buyers and planners to react quickly to low stock levels and trigger replenishment before stockouts occur.

Reduced overstock and excess inventory

When demand signals and supplier inventory are aligned, businesses can avoid overstocking and reduce carrying costs. The EDI 846 helps teams make purchasing decisions based on current inventory availability rather than stale reports.

Better supplier coordination

Suppliers and buyers can operate from a more consistent inventory view, improving order accuracy and reducing backorders, substitutions, and manual follow-up.

Common challenges with EDI 846 processing

Most EDI 846 failures are caused by integration gaps, partner-specific requirements, or data quality problems across systems.

Inventory data not synchronized across systems

If warehouse, ERP, ecommerce, marketplace, and supplier systems are not connected, inventory availability becomes inconsistent. That can lead to overselling, stockouts, order delays, or unnecessary replenishment.

Data lag in high-volume environments

Batch processing delays can cause inventory quantity to drift from reality, especially in high-transaction environments. A quantity that was accurate when exported may no longer reflect current availability by the time it reaches the receiving system.

Partner-specific mapping requirements

The base X12 transaction set is standardized, but each trading partner may require different item identifiers, quantity qualifiers, location codes, status values, or reporting frequencies. A generic EDI map may not be enough to support reliable 846 processing across multiple partners.

Disconnected warehouse and supplier systems

If warehouse systems and supplier systems do not share inventory data reliably, replenishment decisions may be based on outdated or incomplete information.

Limited visibility into transaction flows

Without monitoring and observability, teams may not detect when an EDI 846 transaction fails, arrives late, or delivers data that cannot be processed by downstream systems.

EDI 846 vs. EDI 855 and EDI 856

It is common to confuse these transactions, but they serve different roles:

• EDI 846 communicates inventory availability, inventory quantities, and replenishment-related information.
• EDI 855 confirms whether a purchase order is accepted, rejected, or accepted with changes.
• EDI 856 communicates shipment details, packaging structure, carrier information, and tracking details.

In simple terms:

• The EDI 846 informs what can be ordered.
• The EDI 855 confirms what was accepted.
• The EDI 856 shows what was shipped.

Together, these documents help support a complete order and fulfillment lifecycle.

How Celigo automates EDI 846 workflows

The challenge with EDI 846 inventory management is making sure inventory data flows reliably across the systems that depend on it.

Celigo helps solve this by acting as an integration and orchestration layer for EDI workflows.

Celigo can connect ERP systems, warehouse management systems, supplier systems, commerce platforms, and other applications involved in inventory workflows. It can help automate the movement of EDI 846 transactions across those systems while supporting partner-specific mapping, validation, monitoring, and error handling.

This includes:

• Mapping and transforming EDI data into system-specific formats
• Synchronizing inventory availability across systems
• Coordinating downstream workflows like ordering and fulfillment
• Monitoring transaction flows and handling errors in production
• Managing partner-specific requirements through EDI profiles and validation rules

Celigo B2B Manager supports EDI and B2B integrations with capabilities such as EDI connectors, trading partner connectors, EDI profiles with validation rules, EDI parser and file generator capabilities, acknowledgment generation and reconciliation, and an EDI activity dashboard.

Celigo also provides operational visibility through monitoring and error management, helping teams detect and resolve failed transactions or data issues before they impact the business.

Instead of treating the 846 EDI document type as a static file, Celigo helps manage it as part of a governed, observable workflow that connects suppliers, inventory systems, and downstream operations.

→ Request a demo to see how Celigo operationalizes EDI 846 inventory workflows at scale.