Here is the conclusion up front: EDI 852 is not just another document your warehouse has to send. It is the data retailers use to decide how much to order from you next time, where to place your products, and whether to keep working with you at all. If the warehouse gets three things right, nothing goes wrong: agree on the definitions before you send a single number, write the sending frequency into the agreement, and reconcile every transmission. Miss one of the three and you will be dealing with chargebacks, stockouts, and arguments that drag on for weeks.

I have seen this exact failure three times. The first was in the summer of 2023, with a home-goods supplier whose warehouse management system recorded every outbound shipment correctly — yet the EDI 852 data the retailer received was consistently about 12% lower than actual sales. It took two weeks to find the cause: during a buy-two-get-one-free promotion, the free items left the warehouse as outbound shipments, but the 852 mapping automatically excluded them as "free gifts, not sales." The retailer's replenishment model read the numbers as "this SKU sells moderately," cut orders by 15% for two straight months, and the supplier only noticed when shelves went empty. The data was not wrong. The definition was wrong, and the loss was real money.

EDI 852 is formally called Product Activity Data. Retailers want it for a very practical reason: they need to know how many units of each SKU sold in each store over each period, how many were returned, and how much inventory remains. That data feeds their replenishment systems and category management teams, and it directly shapes purchase quantities and shelf space.

What EDI 852 actually carries, and what retailers do with it

The core content of an 852 falls into four buckets: sales quantities, inventory quantities, return quantities, and adjustments. The three most common sending frequencies are weekly, daily, and more frequent during promotions, as the retailer's EDI specification requires. The frequency is not your choice to make unilaterally — it is written into the trading-partner agreement, and changing it requires a formal change process.

The most common misunderstanding I see is treating 852 as an inventory snapshot. Sending only the ending inventory, with no sales or returns for the period, gives the retailer no way to calculate turnover. The correct approach is to report sales by actual sales date, list returns separately, and treat inventory as a snapshot at a defined point in time, with the three sets of numbers each standing on their own and reconciling with each other. Before you send, ask yourself one question: can the other side read this file and know exactly how much sold last week without calling you? If not, do not send it.

One detail many teams overlook: the product codes, store codes, and warehouse codes in your 852 must be exactly the same codes used in the 850 purchase order and the 856 advance ship notice. Change a code and the retailer's system cannot match the records, no matter how accurate the numbers are. The first item on the go-live night checklist should be the code cross-reference table, not something you scramble to find after the first transmission is rejected.

Five steps to produce 852 numbers from the warehouse

Step one, define the rules. Write a one-page definitions table and get the retailer's EDI contact to sign it: do sales include promotional free goods, are returns deducted, is data split by store; are returns recorded on the return date or the refund date; at what time is the inventory snapshot taken? Keep that table in the project documentation, not in a chat thread.

Step two, choose the data source. Should sales come from point-of-sale data or the retailer's sales feed, or from warehouse outbound data? The two often differ by the in-transit quantity. Use the sales source the retailer recognizes, and warehouse outbound data only as a cross-check. Until the source is settled, every reconciliation that follows is meaningless.

Step three, build the mapping. Map SKUs, locations, and order types from the WMS into the 852 fields. Promotional gifts, samples, damaged goods, and internal use must each have a defined destination in the mapping table — none of them can be vaguely lumped together as "sales." Keep a version history of the mapping table, and re-run a test transmission every time it changes.

Step four, run tests. Before going live, send at least two rounds of test 852s and ask the retailer to parse them in their real system and return feedback. Deliberately include one or two returns and one promotional gift in the test data, and check whether the other side recognizes them correctly. I have seen this pitfall three times — teams test only clean, normal sales, and the first real return on go-live day breaks everything.

Step five, reconcile after go-live. For the first four weeks, reconcile weekly: compare the total sales in your 852 against the retailer's POS totals, and investigate whenever the difference exceeds the agreed threshold, for example 2%, instead of waiting for a quarterly review. Keep records of every reconciliation — when a chargeback dispute arises, those records are your evidence.

Four failure points to clear in advance

The first is promotion definitions. Buy-one-get-one-free, spend thresholds, and second-item-half-price deals are each treated differently in sales statistics. In early 2024, a small-appliance supplier sent its 852 during a Black Friday week and reported sales nearly 20% below POS, because buy-one-get-one-free items had been excluded while the replenishment model ordered against the understated figure — and the product stocked out for two weeks after the promotion. The only fix is to write the current promotion's definitions into the mapping table before the promotion starts, and to re-check them once it ends.

The second is the timing of returns. A store return may take one to two weeks to come back to the warehouse, pass inspection, and return to stock. Record it on the warehouse return date and the retailer's net sales will be overstated; record it on the store refund date and the warehouse has no real-time data. There is no universal right answer, only the answer both sides agree on in writing.

The third is mixing channels. The same SKU may sell through online orders shipped from stores, buy-online-pickup-in-store, and third-party marketplaces. If the 852 lumps all channels together, the retailer cannot see which channel is growing and which is shrinking. Before splitting by channel, confirm that the retailer's system can accept channel-split 852s — some legacy systems only accept totals, and forcing a split will cause rejections.

The fourth is a missed transmission. System upgrades, holidays, and staff leave can all delay or skip one period's 852, and a missing week reads as zero sales in the replenishment model. My practice is to set up a scheduled job in the WMS or EDI system that raises an alert automatically on a failed send, and to name a backup contact. The last item on the go-live night checklist is always the same: if tonight's transmission fails, who is responsible, and what is their phone number?

How 852 fits with 850, 856, and 810

The chain in one sentence: the 850 is the retailer's purchase order, the 856 tells them the goods have shipped, the 852 regularly tells them how the goods are selling and how much is left, and the 810 is the invoice you raise on that basis. The 852 is not a standalone report; it is the only link in this chain that continuously feeds sales performance back. When the earlier documents go wrong, the 852 definitions tend to drift with them; when the 852 is inaccurate, the next round of 850 orders is distorted.

The counterintuitive judgment is this: most teams pour all their energy into the 850 and the 856, treating the 852 as a routine report that can wait. In practice the opposite is true. An error in an 850 or an 856 costs one order; an error in the 852 causes weeks of systematic misjudgment.

Here is a final self-check list to run before you send: has the definitions table been signed by both sides? Does the code cross-reference match the 850 and 856? Did the test transmissions include returns and gifts? Are the reconciliation threshold and the responsible person defined? Is there a backup if the send fails? Only press send when all five answers are yes. If any answer is no, fix it first — the cost of sending a day late is far smaller than the cost of sending wrong data for a month.

By Lin Xiao, WMS Implementation Consultant