The EDI 852 Product Activity Data is how a retailer tells a supplier what is actually selling, store by store, so the supplier can replenish before the shelf goes empty. Unlike a purchase order, the 852 is not a request to ship anything. It is a data feed: sales, on-hand inventory, and on-order quantities per item per location. Read it well and you replenish on real demand instead of guesswork.
This guide covers what the 852 reports, the segments you will work with, how it powers vendor-managed inventory, and how a supplier consumes one without a heavy ERP project.
What Is an EDI 852?
An EDI 852 is the Product Activity Data transaction defined by the ASC X12 standards body, used by a buyer (usually a retailer or distributor) to report product movement and inventory back to the supplier on a regular cadence. It turns the retailer's point-of-sale and warehouse data into a structured feed the supplier can act on.
Authoritative references for 852 implementation:
- The X12.org Transaction Sets reference defines the XQ and activity-reporting segment structure used across 852 implementations
- GS1 US governs the UPC and GTIN identifiers used to key each product line back to the supplier's catalog
Who sends it? The buyer, typically a retailer or wholesale distributor reporting to the brands that supply it.
When is it sent? On a schedule, commonly weekly or daily. Each 852 covers a reporting period.
Why does it matter? The 852 is the demand signal behind replenishment and vendor-managed inventory. It lets a supplier see sell-through and stock position without waiting for the buyer to cut the next 850 Purchase Order.
What the 852 Reports
A single 852 carries several activity types per item, each a different quantity:
- Quantity sold for the reporting period: the actual sell-through.
- Quantity on hand: current inventory at the store or distribution center.
- Quantity on order: units already on a purchase order and inbound.
- Out-of-stock and committed quantities, where the retailer tracks them.
Each quantity is reported per item and, in store-level feeds, per location. The supplier compares sold against on-hand to decide what to push next, which is the heart of replenishment.
Key Segments Explained
Here are the segments you will work with in an 852 transaction set:
| Segment | Name | Purpose |
|---|---|---|
| ST | Transaction Set Header | Identifies the start of the 852 and assigns a control number |
| XQ | Reporting Date/Action | The period the activity covers and the reporting action |
| XPO | Product Activity Reference | Ties the activity to a purchase order or reporting context where used |
| LIN | Item Identification | The product being reported, by UPC, GTIN, and supplier item number |
| ZA | Product Activity Reporting | The activity lines: a code (sold, on hand, on order) plus the quantity |
| G69 | Line Item Detail | Free-form product description for the item |
| CTT | Transaction Totals | Number of line items reported |
The ZA segment is the workhorse. Each ZA carries an activity code and a quantity, so one item can report several ZAs in a single 852: one for units sold, one for units on hand, one for units on order.
How the 852 Drives Replenishment and VMI
In a vendor-managed inventory (VMI) relationship, the supplier owns the replenishment decision, and the 852 is the data that decision runs on:
- The retailer sends a daily or weekly 852 with sales and on-hand per item per location.
- The supplier compares sell-through against on-hand and the agreed reorder points and safety stock.
- The supplier generates replenishment, often as an 850 Purchase Order it creates on the buyer's behalf, or feeds the numbers into demand forecasting.
- The shipment flows as an 856 Ship Notice / ASN and is billed with an 810 Invoice.
The 852 sits alongside the 846 Inventory Inquiry/Advice: the 846 communicates available stock, while the 852 reports what actually sold and moved.
How Suppliers Consume 852 Feeds Without a Big Integration
The common advice is to pipe 852 feeds into a planning system through a custom integration. For a supplier that does not run demand-planning software, that is a heavy lift for a weekly data file.
OrderSync reads inbound 852s (and arbitrary-format activity data like spreadsheets and portal exports), normalizes them into a clean per-item, per-location view of sold, on-hand, and on-order, and flags items that are selling through faster than they are being replenished. It produces valid X12 where you need to send replenishment back, without requiring an ERP read or write to start. Upload one of your own files to the free EDI inspector to see an 852 parsed, or book a 15-minute walkthrough to see a replenishment cycle on real data.
Frequently Asked Questions
What is an EDI 852 used for?
The 852 reports product activity, sales, on-hand inventory, and on-order quantities, from a retailer back to a supplier. Suppliers use it to see real sell-through and drive replenishment or vendor-managed inventory instead of waiting for the next purchase order.
What is the difference between an EDI 852 and an EDI 846?
The 846 Inventory Inquiry/Advice communicates inventory levels, often the quantity a supplier has available to sell. The 852 reports what actually sold and what is on hand at the buyer. The 846 is about supply; the 852 is about demand and movement.
Does an EDI 852 authorize a shipment?
No. The 852 is a data feed, not an order. It carries no instruction to ship. The supplier reads it and, in a replenishment or VMI program, generates a separate purchase order or shipment in response.
How often is an EDI 852 sent?
On a regular cadence set by the trading partner, commonly daily or weekly. Each 852 covers a reporting period, and store-level feeds can be large because they report per item per location.