What is an 852 EDI Product Activity Data Document?

An EDI 852 is the Product Activity Data transaction set, the document a retailer sends to report what your product did in their stores. It runs from the retailer to you and carries no order and no obligation. Growers on replenishment and pay-by-scan programs read it to see what sold and to decide what ships next.

What is an EDI 852 Product Activity Data document?

An 852 is the paperless version of a store activity report. Two kinds of numbers travel in it. Point-of-sale data covers units sold, by SKU, at retail or at wholesale. Inventory data covers units on hand. Both arrive summarized by physical store or by distribution center, depending on how the program is set up.

Which of the two you actually receive is a program decision rather than a standard one. Some partners send sold quantities only. Others add on-hand, and a few include received and in-transit quantities. The annotated example below shows where in the file that choice lives.

An EDI 852 example, annotated

The 852 is exchanged in X12 format. Here is one addressed from Walmart to a grower:

ISA*00*          *00*          *08*925485US00     *12*5551234567     *211218*2308*:*00501*852100583*0*P*>
GS*PD*925485US00*5551234567*20211218*2308*852100583*X*005010
ST*852*100583
XQ*H*20211214
N9*IA*740012560
N9*FI*01ST
N1*FR*WALMART*UL*0078742000008
N1*TO*GROWER FARMS LLC
DTM*097*20211218
LIN*000001*UP*783975629553*IN*577321454*VN*63033
PO4*1
ZA*QS*13*EA
LIN*000002*UP*783975611474*IN*577472754*VN*611463
PO4*1
ZA*QS*2*EA
LIN*000003*UP*783975656942*IN*586246840*VN*656952
PO4*1
ZA*QS*6*EA
CTT*3
SE*18*100583
GE*1*852100583
IEA*1*852100583

Segment by segment:

• ISA and GS are the envelope. GS*PD is the functional group code for product activity data, so the receiving system knows what is inside before it reads the transaction. 005010 is the X12 version.
• ST*852*100583 opens the transaction set, and the closing SE segment repeats that control number.
• XQ is the reporting date and action segment. Its first element is a transaction handling code, and H means notification only, which is the posture of the whole document. The date after it is the activity date the file covers.
• N9*IA carries the internal vendor number the retailer assigned you. N9*FI is a file identifier, which lets a partner keep one feed separate from another.
• N1*FR and N1*TO name the sender and the receiver. The UL qualifier is a UCC location code, Walmart’s identifier for itself.
• DTM*097 is the transaction creation date, which is not the activity date in the XQ segment. This file was built on the 18th and reports activity as of the 14th.
• LIN identifies one item and opens a loop that repeats for every item. UP is the UPC, IN is the retailer’s SKU, VN is your item number. Three identifiers for one plant is normal, and keeping them matched is most of the ongoing work in an 852 program. The PO4 line under each carries the pack configuration.
• ZA is where the activity lives. ZA*QS*13*EA says thirteen each sold. QS is the activity code for quantity sold, and it is one of many: QB and QE are beginning and ending balance, QR is quantity received, QI is in transit, Q2 is returned.
• CTT is the line count, checked against the number of LIN segments. SE, GE and IEA close the transaction set, the group, and the interchange.

Every ZA line in this file is a QS. It reports what sold and says nothing about what is sitting on the shelf. If you need on-hand out of an 852, ask your trading partner which activity codes their file carries, because a file that only reports sales cannot answer an inventory question no matter how you process it.

How growers use 852 data

The numbers in an 852 are raw counts, and what makes them worth reading is what you calculate from them.

Sell-through is the first one. Units sold divided by units shipped, expressed as a percentage, tells you how well a store moved what you sent. Unit sell-through and dollar sell-through can come apart badly when a retailer runs markdowns, and the arithmetic behind that gap is worked through in our earlier sell-through piece.

Weeks of supply comes next. On-hand divided by an average weekly sales rate answers how long a store lasts before the shelf is empty at the current pace, which is the number a replenishment decision turns on.

The same data supports sales forecasting and the year-over-year comparisons buyers ask about. In a pay-by-scan program the stakes rise, because the retailer pays when your product scans at the register, which makes the 852 the record your revenue comes from.

An 852 gives you units and never the reason behind them. A store that sold 40% of what you sent looks identical in the file whether the product sat in the wrong spot or the weather kept shoppers home for three weeks. Know that before you build a plan on the numbers.

EDI 852 vs EDI 846

These two get confused because both carry item numbers and quantities. They run in opposite directions and answer different questions.

The 846 is yours. You send it to the retailer to declare what you have available to sell, as of a stated date and time. The 846 guide covers what goes in it.

The 852 is theirs. The retailer sends it to report what sold in their stores and, where the program includes it, what is on hand there.

Growers in a replenishment program usually run both, one going out with your availability and one coming back with what the shelf is doing.

Retailer programs, and where the 852 fits

Every program publishes an implementation guide, and that guide is the specification: which activity codes the file carries, whether it summarizes by store or by distribution center, and how often it arrives. One partner’s setup tells you nothing reliable about the next one.

Programs also change. In January 2020 we reported that Home Depot was phasing out certain data artifacts, including the EDI 852 documents some purchase-order suppliers were receiving, as part of a move to its own supplier analytics platform. We wrote that from what our customers were being told at the time. Where any given program stands now is a question for your trading-partner contact.

Where the sales data goes when an 852 goes away is not always obvious either. Home Depot has used 850 purchase order documents to notify pay-by-scan vendors of in-store sales, which means the document carrying your sales numbers is not always the one the standard would point you at.

Summary

An 852 is the retailer’s report of what your product did in their stores, sent as data on the program’s schedule. Read at the store level, it drives sell-through, weeks of supply, and the replenishment decision behind them. What any particular 852 can tell you comes down to which activity codes your trading partner puts in the file, so that is the first thing to ask them.