EDI 852 — Product Activity Data for demand planning
In short: EDI 852 is the ANSI X12 Product Activity Data transaction: retailers send suppliers weekly point-of-sale, on-hand and on-order data per SKU per store or DC. It is the raw material for vendor-managed inventory (VMI), demand forecasting and CPFR programs.
Key capabilities
- Per-SKU per-store POS: Weekly units sold and dollars per SKU per store or DC — the retailer's actual sell-through, not just orders received.
- On-hand & on-order: Current inventory at each location plus quantity already on order but not received — enables true demand signal.
- Weekly cadence: Most retailers send 852 files weekly on Sunday night or Monday morning; some send daily for high-velocity SKUs.
- Feeds VMI & forecasting: The 852 is the input to VMI where the supplier — not the retailer — decides replenishment quantities and timing.
From EDI 852 to a working VMI program
A VMI program without automated 852 processing is a spreadsheet exercise that breaks by week 3. The right architecture: the retailer drops 852 files daily/weekly → EDIconnect normalizes them into a canonical POS + inventory table → your demand-planning tool (SAP IBP, o9, Kinaxis, or a simple BI dashboard) generates replenishment proposals → confirmed replenishments flow back out as EDI 855/856.
EDIconnect ships pre-built 852 parsers for the top 40 US and EU retailer formats, plus a lightweight VMI dashboard for suppliers who don't yet have a dedicated planning tool.
Frequently asked questions
What is EDI 852 used for?
EDI 852 gives the supplier visibility into what actually sold and what's on hand at each retailer store or DC — the foundation for demand forecasting, VMI programs and CPFR (Collaborative Planning, Forecasting and Replenishment).
Which retailers send EDI 852?
Walmart (weekly Retail Link 852), Target, Kroger, Home Depot, Lowe's, CVS, Walgreens, Costco (limited SKUs), plus most grocery, DIY and drug chains for their strategic suppliers.
How often is EDI 852 sent?
Typically weekly. Some retailers send daily for fast-movers or specific programs. Historical replay is available in most retailer portals if you miss a file.
What is the difference between EDI 852 and EDI 867?
852 is per-store per-SKU activity. 867 is a Product Transfer and Resale Report — usually distributor→manufacturer sell-through, for markets like electronics and pharma.
How do I consume EDI 852 data?
EDIconnect loads 852 files into a structured warehouse table (or your BI tool via API) — no manual parsing. From there you drive forecasts, replenishment orders and out-of-stock alerts.