EDI 852 - Product Activity Data
The EDI 852 carries point-of-sale data, inventory levels, and product movement history from retailer to supplier - the lifeblood of Vendor Managed Inventory programs and collaborative demand planning.
✦ What It Does
The EDI 852 Product Activity Data transaction set flows downstream-to-upstream: the retailer or distributor sends it to the supplier on a scheduled basis (daily, weekly) to share what actually happened at store or DC level. It can carry point-of-sale (POS) sell-through quantities, on-hand inventory counts, on-order quantities, in-transit quantities, and returns - for each SKU, at each location (store, DC, or region).
The 852 structure centers on the ZA header segment (not to be confused with ST/SE envelope segments) - actually, the key opening segment is the BCT (Beginning Segment for Product Activity Data), which establishes the reporting period, date of report, and purpose. Below BCT, the 852 uses PA (Product Activity) segments that carry quantity and type codes, LIN segments for item identification, and N1/N9 loops for location identification. A single 852 can contain data for hundreds of SKUs across thousands of store locations, making it one of the largest and most complex transaction sets in retail EDI.
Suppliers who receive and act on 852 data can dramatically improve forecast accuracy, reduce stockouts, and time replenishment orders more precisely. Without the 852, suppliers are essentially forecasting blind - relying on lagging order data rather than actual sell-through. Retailers like Walmart, Kroger, and Costco use the 852 as the input to collaborative replenishment programs, where the supplier earns greater shelf space by demonstrating in-stock performance driven by 852-informed ordering.
⚡ When It's Triggered
- A retailer's VMI system generates a weekly 852 file containing prior-week POS sales and current on-hand inventory by store for all items in a supplier's assortment.
- A grocery DC sends a daily 852 to a CPG supplier showing case movements out of the warehouse to individual stores, allowing the supplier to spot velocity spikes before they become stockouts.
- A consumer electronics retailer transmits a 852 during a promotional event period so the supplier can monitor sell-through against promotional forecasts in near real time.
- A club-channel buyer shares 852 data after a new item setup, giving the supplier visibility into early adoption rates by warehouse location.
- A supplier's demand planning team subscribes to automated 852 ingestion, feeding the data into their forecasting engine to generate replenishment recommendations or automated 850s.
Who Uses EDI 852
Retail VMI Programs
Walmart's Retail Link and similar portals feed 852 data to suppliers participating in vendor-managed inventory. The supplier uses 852 sell-through and on-hand data to propose replenishment orders - either generating 850s automatically or providing order recommendations that the buyer approves. VMI programs require reliable 852 processing as a prerequisite for participation.
Grocery & CPG
Grocery is arguably the highest-volume 852 environment. Major chains send daily 852 files covering DC-to-store movements, store on-hand inventory, and POS scan data. CPG suppliers ingest this data into their S&OP process to manage promotional lifts, seasonal spikes, and everyday replenishment. Scan-based trading programs depend entirely on 852 POS data for payment triggering.
Consumer Electronics
Electronics retailers transmit 852 data to vendors to manage fast-moving, high-value SKUs. With short product lifecycles and significant price erosion risk, electronics suppliers use 852 sell-through data to make markdown decisions, plan end-of-life inventory, and time new product introductions to coincide with existing inventory depletion.
Home Goods & Seasonal
Home goods suppliers with seasonal velocity patterns rely on 852 data to manage inventory positioning ahead of peak demand. A housewares supplier at a major home improvement chain uses weekly 852 data to identify regional sell-through variance and rebalance inventory between DCs before stockouts occur in high-velocity markets.
Key Segments & Data Elements
BCT: Beginning Segment
Opens the 852 and identifies the report type (BCT01: PA = product activity), the report date (BCT02), and the period start/end dates (BCT03/04). BCT05 carries a reference number assigned by the sender. Getting the period dates right is critical - mismapped BCT dates cause report overlap or gaps in the supplier's demand history.
LIN: Item Identification
Identifies the product using one or more qualifier-value pairs: UP (UPC), VN (vendor part number), BP (buyer's part number), UK (UPC case code), or IN (buyer's item number). The 852 may carry multiple LIN qualifiers for the same item when the retailer cross-references their internal item number with the UPC.
PA: Product Activity
The workhorse segment of the 852. PA01 is the activity type code: 001 = beginning inventory, 002 = ending inventory, 003 = POS sales, 004 = returns to store, 006 = on order, 007 = in transit, 010 = transfers in, 011 = transfers out. PA02 is the quantity. PA03 is unit of measure. Multiple PA segments appear per item to report different activity types in a single transmission.
N1: Location Identification
Identifies the reporting location - individual store, distribution center, or geographic region. N101 qualifier SL = ship location (store), WH = warehouse (DC), SU = supplier's DC. N103/N104 provide the location identifier code (store number, DC number). When a 852 covers multiple locations, N1 loops nest within the item structure to report per-location activity.
PO4: Item Physical Details
Optionally carries pack configuration details: PO401 = pack quantity per case, PO402 = size (inner pack), PO404 = unit weight. Important when the 852 reports in cases but the supplier's system needs to convert to eaches for forecasting. Mismatched UOM assumptions are one of the most common 852 integration bugs.
PID: Product Description
Carries human-readable item descriptions. PID01 = F (free-form) or S (structured), PID05 = description text. While not required for automated processing, PID aids in exception handling and manual reconciliation when item cross-references fail. Some retailers populate PID with their internal item description for auditing.
Related Transaction Sets
Planning Schedule
The 830 sends forward-looking demand forecasts from buyer to supplier. While the 852 reports what already happened (actual sales/inventory), the 830 communicates what the buyer expects to order in upcoming periods. The two documents work together in a demand visibility loop.
Purchase Order
The replenishment PO triggered by 852 analysis. In VMI programs, the supplier generates 850s based on 852 sell-through and on-hand data. The 852 is the input; the 850 is the output. Tight latency between 852 receipt and 850 generation is key to VMI performance.
Inventory Inquiry / Advice
The 846 flows in the opposite direction - supplier to buyer - reporting the supplier's own warehouse inventory levels. Together, the 852 (retailer's inventory) and 846 (supplier's inventory) give both parties a complete view of the supply pipeline.
Grocery Products Invoice
In scan-based trading, the 852 POS data drives payment: the supplier is paid when items scan at the register, not when they are received at the DC. The 852 feeds the 880 invoice calculation in scan-based trading programs at major grocery chains.
Need Help with EDI 852?
Better EDI handles 852 mapping, testing, and trading partner certification so you don't have to.
Talk to an EDI Expert