DEV Community

challan116-ux
challan116-ux

Posted on

The EDI 846, Decoded: Inventory Advice Is a Promise You Have to Keep

Short answer: the 846 · Inventory Inquiry/Advice is how a supplier tells a retailer or distributor what it can actually sell — quantities available, on order, and sometimes allocated — without taking an order. It looks like the simplest document in the set. It causes outsized damage when it is wrong, because every downstream decision — a retailer's replenishment, a marketplace listing, a drop-ship promise — is built on numbers you published.

What the 846 actually carries

An 846 is a snapshot, not a feed of record. Its core is the LIN loop identifying the item (usually by UPC/GTIN or buyer item number) and QTY segments stating quantities by type: quantity on hand, quantity available to sell, quantity on order, quantity committed. The qualifiers are the whole document. "Available" that includes stock already allocated to another channel is not available — it is double-promised.

Three fields decide whether an 846 helps or hurts:

  1. The quantity qualifier. On-hand, available-to-promise, and in-transit are different numbers with different meanings. Sending on-hand where the partner expects available is how oversells are manufactured.
  2. The timestamp. An 846 without a clear as-of time invites the receiver to treat a stale snapshot as live truth. Partners schedule their reads around your cadence — publish that cadence and keep it.
  3. The item identity. If your LIN uses a different identifier than the partner's item file, the inventory lands on the wrong SKU silently. No error, no rejection — just stock shown for an item you do not carry and zero for the one you do.

Where 846 programs break

Cadence drift. The agreement says hourly; the job quietly runs daily after an infrastructure change. Nothing errors. The retailer's system keeps ordering against yesterday's numbers.

Returns counted too early. Stock that is back in the building but not yet inspected is not sellable. Counting it at dock receipt inflates available quantity by exactly the units most likely to fail inspection.

Kit and case breaks. If you sell eaches but report cases (or the reverse), the partner's math is off by the pack factor on every line. Unit-of-measure mismatches are the single most common silent 846 defect I see.

Zero is a value, not an omission. Dropping an item from the file when it hits zero stock reads to many receivers as "no change," not "none left." Send the explicit zero.

A sane 846 checklist

  • Reconcile available = on hand − allocated − safety stock, in that order, every cycle.
  • Send explicit zeros; never silently drop SKUs.
  • Keep the identifier, unit of measure, and pack size identical to the partner's item file — and diff them weekly.
  • Timestamp every file and monitor your own publish cadence like an SLA.
  • Treat a sudden available-quantity jump as a bug until proven otherwise; real inventory rarely teleports.

The 846 will never get the attention the 850 · Purchase Order or 856 · Ship Notice/ASN gets. That is precisely why it rots. It is a promise published on a schedule — keep it accurate, keep it on time, and it quietly prevents the angriest class of partner conversations: the ones that start with "your feed said you had it."

— Chris, founder of SignalEDI, where we handle X12 inventory, order, and shipping documents for SMB suppliers.

Top comments (0)