XQ
Reporting date/action: the transaction purpose and the period the report covers.
EDI 852: Product Activity Data
A retailer’s report of sales and inventory movement by product and location, sent back to the supplier. Retailer to supplier. This page covers what the 852 is for, the segments you meet when you open one, the documents it travels with, where it tends to go wrong, and how it moves over AS2 into your systems on Files.com, which receives, parses, validates, and routes it as configuration.
No credit card required · 7-day free trial · Live in minutes
#1 MFT vendor in Gartner Peer Insights
Trusted by 4,000+ companies
Every protocol included
What The 852 Is For
The 852 flows the opposite way from most EDI: from the retailer back to the supplier. It reports what happened to the supplier’s products at the retailer’s locations over a period, units sold, units on hand, units on order, receipts, returns, and out-of-stocks, typically by store and by week.
Suppliers use it to forecast, replenish, and manage vendor-managed inventory programs, where the supplier decides what to ship based on the retailer’s sell-through. It is the document that turns a supplier from order-taker into planner, and large retailers send it in volume: one 852 can carry thousands of item-location rows.
The Segments You Meet First
In document order, the segments that carry the 852's meaning. A partner's implementation guide says which are required and which fields each must hold.
N1
The reporting location, such as a store or distribution center.
LIN
Item identification.
ZA
Product activity reporting: an activity code (sold, on hand, on order, received) with the quantity for that item and location.
CTT
Transaction totals.
Where It Goes Wrong
Volume and shape. An 852 from a national retailer is a large, wide document, and a parser that assumes one location per file or one activity code per item falls over on the first real feed. Period alignment is the other issue: a supplier who aggregates weekly reports across retailers with different week endings is comparing unlike periods.
The Documents It Travels With
The 852 rarely moves alone. These are the documents that precede, answer, or settle it.
846 · Inventory Inquiry / Advice
A supplier’s report of stock levels: on hand, available, committed, and on order.
See The 846850 · Purchase Order
A buyer’s order to a supplier: the items, quantities, prices, dates, and ship-to locations.
See The 850830 · Planning Schedule with Release Capability
A customer’s forecast of what it will need, by item and period, which suppliers plan against and may ship against.
See The 830997 · Functional Acknowledgment
The receipt that says an EDI transmission arrived and was parsed, with any syntax errors found.
See The 997How The 852 Moves On Files.com
A partner sends the 852 over AS2, SFTP, or FTPS, and it lands in that partner’s inbox folder on Files.com with the transport receipt recorded. From there it is a workflow, not a project: TransformScript parses the X12 natively into the JSON, CSV, or XML your ERP or WMS reads, content validation flags a document whose contents are wrong before anything ingests it, and an automation routes the result to the system and the people who act on it.
Outbound is the mirror image. Your system exports its record, TransformScript builds the 852 the partner’s guide specifies, and the file dropped in the partner’s outbox goes out over AS2 with automatic retries until the MDN confirms delivery. Every transmission in both directions is in the audit log, and delivery monitoring alerts when a 852 that was due never arrives. The full picture is on the EDI software page.
EDI 852 Questions
What teams ask about the 852 and how it moves on Files.com.
An EDI 852 is the X12 Product Activity Data document. A retailer sends it to a supplier to report sales, on-hand, on-order, and other movement for the supplier’s products by location and period, which suppliers use for forecasting and replenishment.
The retailer or distributor that holds and sells the product sends it to the supplier or manufacturer, the reverse of the usual buyer-to-supplier direction.
Demand forecasting, replenishment planning, and vendor-managed inventory, where the supplier decides shipments based on the retailer’s sell-through and stock position.
Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 852 sent by a trading partner lands in that partner’s inbox folder with a signed MDN receipt returned to the sender. Partners who exchange over SFTP or FTPS connect to the same platform and the document lands in the same place.
Yes. TransformScript parses the X12 852 natively and writes the JSON, CSV, or XML your systems ingest, as a step in the workflow that fires when the document arrives. Outbound, the same engine builds a 852 from your system’s export and drops it in the partner’s outbox for delivery.
Exchange The 852 Without The Legacy Stack
Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 852 lands in their folder, parses into the record your system reads, and every transmission carries a signed receipt.
No credit card required • Free for 7 days • Live in minutes