
What Is EDI Inventory?
EDI inventory refers to the standardized electronic documents that trading partners exchange to share stock levels and product movement. In North America these documents follow the ANSI X12 standard, maintained by X12. The standard defines each transaction set, the segments inside it (lines of data, such as LIN for item identification or QTY for quantity), and the data elements each segment carries.
Unlike a spreadsheet emailed every Monday morning, these documents move system to system on an agreed schedule through electronic data interchange. That speed is the whole point, and it is also the risk. If the source numbers are wrong, the error lands in the retailer's systems just as fast as a correct number would.
Why Inventory Accuracy Matters to Trading Partners
Retailers and marketplaces use your stock data to decide what to display online, what delivery dates to promise, and what to reorder. When a feed overstates availability, the partner oversells, cancels customer orders, and often issues compliance chargebacks. When it understates availability, products show as out of stock and sales disappear, a problem covered in more depth in our guide to understanding and managing stock-outs. Either way, the pattern shows up on vendor scorecards, and repeated misses wear down the trust that earns shelf space and favorable terms.
How EDI Inventory Differs From Order and Shipment EDI
Order and shipment transactions, such as the 850 purchase order and the 856 advance ship notice, record specific events tied to a specific order. Inventory transactions describe a state: what is available right now, or what sold over a period. That makes them continuous and cumulative. A bad ASN affects one shipment. A bad inventory number can affect every order a partner accepts until the next update corrects it, which might be hours or a full day later.

EDI 846 Explained: Inventory Inquiry/Advice
The 846 is the transaction a supplier, manufacturer, or 3PL sends to tell a trading partner how much product it can ship. It can also work as an inquiry, where a partner asks for a status, but in practice most 846 traffic is an advice pushed out on a schedule without being requested.
The critical point for warehouse teams: the quantity in an 846 is usually meant to represent sellable, available-to-promise (ATP) stock, not raw on-hand. The gap between those two numbers is everything your building has already committed or cannot ship. A pallet sitting in a damage cage is physically present, but no customer should be promised it.
Key Segments and Data Elements in the 846
A typical 846 opens with a BIA header that identifies the report type and date. Item identification sits in LIN segments, which can carry a UPC, GTIN, vendor SKU, or buyer item number. QTY segments hold the quantities themselves, each tagged with a qualifier code that tells the receiver whether the figure means on-hand, available, or on-order.
Many partners also require:
- A location identifier for each ship-from warehouse
- Unit of measure codes on every quantity
- Dates for future availability, such as an expected restock
Each retailer publishes its own implementation guide that spells out which segments and qualifiers are mandatory. Two partners can both ask for an 846 and still expect noticeably different files.
Common 846 Use Cases and Send Frequency
Drop ship programs depend heavily on this document because the retailer sells your inventory without ever holding it. Marketplace and ecommerce feeds use it to switch online availability on and off. Distributors use it to confirm supplier stock before placing orders. If you sell across several of these channels at once, the same physical units are being promised in multiple places, which is why multi-channel inventory management discipline matters here.
Frequency varies by partner. Daily is common for traditional store replenishment, while drop ship and marketplace programs often expect several updates per day, or near-real-time feeds during peak season.

EDI 852 Explained: Product Activity Data
The 852 flows in the opposite direction. A retailer or distributor sends it to suppliers to report how products performed over a period, usually broken out by week and by store or distribution center.
Where the 846 says "here is what I can ship," the 852 says "here is what happened to what you shipped." For suppliers, and for the 3PLs that serve them, it is one of the most direct views into real demand downstream of the warehouse. Without it, a supplier only sees purchase orders, which reflect the retailer's buying decisions rather than what shoppers actually took home.
What Data the 852 Contains
For each item and location, an 852 typically reports:
- Units sold
- On-hand quantity at the store or DC
- Quantity received
- Quantity on order
- Sometimes returns, adjustments, or lost sales
Items are identified in LIN segments, activity types are carried in ZA segments with activity codes, and the quantities themselves appear in SDQ segments broken out by location. The reporting period is defined in the header, so suppliers can line the data up with their own fiscal calendars.
How Suppliers Use 852 Data for Replenishment and VMI
With sell-through and on-hand by location in hand, suppliers can spot items trending toward stockouts, adjust production or purchasing, and sharpen forecasts. In vendor-managed inventory programs, the supplier goes a step further and generates replenishment orders on the retailer's behalf based on these reports.
For the warehouse, those trends should shape slotting, labor planning, and safety stock. Suppose a hypothetical outdoor goods brand sees a sunscreen SKU selling much faster than planned across its southern stores in April. Moving that item to a quicker pick location and raising its safety stock means the next 846 reflects inventory positioned where demand is heading, not where it was last month.

EDI 846 vs EDI 852: How They Compare and Work Together
The two transactions get confused because both carry quantities and item identifiers. The simplest distinction is direction and purpose. The 846 pushes supply information outward to a partner, and the 852 pushes demand information back to the supplier.
Side-by-Side Comparison
- Name: the 846 is called Inventory Inquiry/Advice, while its counterpart is called Product Activity Data.
- Typical sender: availability advice comes from a supplier, manufacturer, or 3PL; activity reports come from a retailer or distributor.
- Direction: the 846 travels outward from the stockholder to its partner, and the 852 returns from that partner to the vendor.
- Purpose: one communicates sellable stock, and the other reports sell-through plus inventory sitting in stores and DCs.
- Key data: available quantity, location, and future availability on one side; units sold, on-hand, receipts, and on-order on the other.
- Typical frequency: daily to several times per day for availability, usually weekly for activity.
- Source of truth: your WMS feeds the 846, while retailer POS and store inventory systems feed the 852.
The Closed Inventory Visibility Loop
Together, the two documents form a loop:
- Your WMS calculates available stock and sends an 846.
- The retailer sells, receives, and reorders, then reports that activity in an 852.
- You use the 852 to adjust replenishment and inventory positioning.
- Those adjustments change what your next 846 reports.
If either side of the loop is inaccurate, the partnership runs on guesses. A retailer working from inflated availability will oversell, and a supplier reading activity figures that do not match its own shipment records will replenish the wrong items. Accurate warehouse data is what keeps the loop honest, and it is the one part of the cycle the supplier fully controls. Tracking the right inventory KPIs, such as inventory accuracy rate and fill rate, gives you an early read on whether your side is holding up.
Where EDI Inventory Feeds Break Down and How Your WMS Fixes It
Most inaccurate inventory feeds are not translation failures. The EDI translator faithfully converts whatever number it receives into X12 format. The problem is that the number came from the wrong place, at the wrong time, or in the wrong unit. A warehouse management system acting as the inventory system of record is where a business can catch these issues upstream. The translator and its mapping still matter, but neither can correct a quantity that was wrong when it left the warehouse.
Five Common Failure Points
- On-hand instead of available. Sending physical quantity ignores allocations, picks in progress, and reserved stock.
- Holds left in the count. Damaged, quarantined, expired, or QA-held inventory gets reported as sellable.
- Multi-warehouse aggregation errors. Quantities are summed across sites the partner cannot ship from, or reported under the wrong location ID.
- Unmapped units of measure. The WMS tracks eaches while the partner expects cases, so availability is multiplied or shrunk by the pack size.
- Stale batch timing. A feed generated at 2 a.m. does not reflect morning receipts, cycle count adjustments, or a surge of overnight orders.
Many of these trace back to the same root causes behind everyday inventory discrepancies, which is why fixing the feed usually starts with fixing the count.
Accuracy Checklist for Reliable 846 Output
What to calculate
- Start from on-hand, then subtract allocated, picked-not-shipped, and reserved quantities.
- Apply partner-specific safety buffers where they have been agreed.
- Calculate by ship-from location when the partner requires site-level data.
What to exclude
- Inventory on quality, damage, recall, or customer-specific holds
- Stock in receiving that has not been put away and confirmed
- Lots near expiration that fall outside the partner's shelf-life rules
- Inventory owned by a different client in a multi-client 3PL building
When to send
- Match or exceed each partner's required frequency, and add event-triggered updates when stock crosses a low threshold.
- Schedule sends after major receiving and cycle counting windows, not before them.
What to validate
- Item cross-references (UPC, GTIN, buyer SKU) for every active item
- UOM conversions for each partner
- Zero-quantity records for out-of-stock items, so partners stop selling them
Checklist for Acting on 852 Data
- Map 852 locations and items to your own item master so incoming records land cleanly.
- Review weekly sell-through against current available stock to flag items at risk.
- Feed sales trends into replenishment, slotting, and labor planning.
- Compare retailer-reported receipts with your shipped quantities to catch ASN or receiving discrepancies early.
- Watch for rising retailer on-hand alongside falling sales, a signal to slow replenishment before overstock turns into returns.
When the warehouse system calculates availability correctly and activity reports flow back into planning, both documents start doing what partners expect of them. Request a Demo to see Sphere WMS in action.
Frequently Asked Questions
What is the difference between an 846 and an 852?
An 846 is sent by the party holding stock to tell a partner how many units it can ship, while an 852 is sent by a retailer back to the supplier to report sales and store inventory. The 846 often goes out daily or more often, and the 852 usually arrives once a week.
Should an 846 report on-hand or available quantity?
Most partners want available-to-promise quantity, not physical on-hand. That means subtracting allocated orders, picks in progress, reserved units, and anything sitting on a quality or damage hold. Check each retailer's implementation guide, because the QTY qualifier code tells the receiver exactly which figure you are sending.
How often should inventory advice files be sent to retailers?
It depends on what each partner requires. Traditional store replenishment programs commonly accept one file per day, while drop ship and marketplace partners often want several updates daily. Timing each send right after receiving and cycle counts finish keeps the file from missing that morning's adjustments.
Why does a retailer still show my item in stock after we sold out?
Usually the feed is stale or the zero was never sent. If an item drops to zero and your system leaves it out of the file instead of reporting a zero quantity, many retailers keep displaying the last positive number. Sending explicit zero-quantity records tells the partner to stop selling the item.
How is 852 data used in vendor-managed inventory?
In vendor-managed inventory, the supplier reads weekly sales and on-hand figures by store or DC and creates replenishment orders for the retailer. Suppliers typically compare sell-through against the retailer's remaining stock to decide which locations need product next, then adjust warehouse safety stock and slotting to match.




