Most EDI documents tell you to do something — ship this, change that, pay attention to a rejection. The 852 Product Activity Data is different: it hands you information and leaves the decisions to you. Retailers use it to share what actually happened to your product at their stores and DCs — what sold, what's on hand, what's on order — and the suppliers who read it well tend to be the ones whose fill rates stay off the buyer's problem list.
What arrives in the file
The structure is simple compared to an ASN. An XQ segment defines the reporting period. Then, per item (LIN), ZA loops carry activity quantities, each with a code identifying what the number means — quantity sold and quantity on hand are the two workhorses, with received, on order, and withdrawn appearing depending on the retailer. Location detail typically rides in SDQ segments, breaking each measure down by store, or arrives as one record per location.
Multiply items by stores by measures and the files get large. A national program reporting weekly on a full assortment produces some of the biggest documents in retail EDI — which is a parsing problem, not a pricing one, as we'll get to.
What the data is for
Retailers don't share sell-through out of generosity. Replenishment programs run on a shared-responsibility model: they send the demand signal, you keep the shelf stocked. Kohl's, for example, sends weekly location-level sell-through and expects replenishment vendors to plan from it. Mass retailers, club programs, and even military exchange stores run the same play — the 852 cadence is usually weekly, and the expectation is that it feeds your forecast rather than a folder.
Concretely, suppliers use 852 data to:
- Forecast demand at store or DC granularity instead of extrapolating from PO history, which lags real demand by the length of the retailer's ordering cycle.
- Protect fill rate by spotting velocity spikes on specific SKUs before the next 850 purchase order makes the shortage official.
- Catch dying inventory — stores showing stock on hand but no sales — early enough to act on it with the buyer.
- Reconcile the retailer's view of on-hand against shipments, which occasionally surfaces receiving discrepancies worth disputing.
The 852 and the 846: two halves of one picture
It's easy to confuse this document with the 846 Inventory Advice, but they point in opposite directions. The 846 is you telling the partner what you have available to sell; the 852 is the partner telling you what happened to it after it left. Drop-ship and distributor programs lean on the 846; replenishment retail leans on the 852; plenty of relationships trade both, and together they close the demand-and-inventory loop from your warehouse to the shelf.
A practical note on cadence: partners define both the reporting frequency and the measures they include, and neither is negotiable from your side. Build your planning process around what actually arrives — a weekly sold-and-on-hand feed used well beats a wishlist of daily metrics nobody sends.
Getting it out of the mailbox and into a forecast
The failure mode with 852s isn't rejection or chargebacks — it's neglect. The file lands weekly, nobody parses it, and a genuinely valuable demand signal rots in an archive directory. EDISQ lands the parsed data where you can use it: pushed into your ERP or planning system among 30+ supported integrations, or delivered as a clean analytical feed keyed by item and location.
On cost: pricing stays per document even when the document is enormous. After the 25 free documents every month, an 852 starts at $0.50 — the same as a two-line PO — and drops toward $0.10 as monthly volume climbs, tier by tier. No charge for the data volume inside the file, and the AS2/SFTP/VAN plumbing that delivers it is included. Retail data programs are, deliberately, some of the cheapest EDI you can run.
FAQ
What data is in an EDI 852?
Sales and stock movement by item and usually by location: units sold, on hand, on order, received, and similar activity measures for a reporting period the retailer defines.
Is the 852 the same as POS data?
It is the EDI vehicle for POS-derived data. Retailers aggregate register and inventory movement into the 852 on a weekly or daily cadence rather than streaming raw transactions.
Do I have to do anything when an 852 arrives?
No response document is expected. The obligation is commercial: replenishment retailers expect vendors to plan production and shipments from the data they share.
What does receiving 852s cost with EDISQ?
Per document, nothing else: 25 free monthly, then from $0.50 per document with volume discounts down to $0.10. A weekly all-store 852 is one document.