EDI 852 and 867 are two X12 transaction sets that track product movement at different points in the supply chain. The 852, called the Product Activity Data report, carries point-of-sale and inventory figures from a retailer back to the manufacturer. The 867, the Product Transfer and Resale Report, documents business-to-business movement: distributors shipping to resellers, wholesalers selling to professional end-users, or warehouses transferring stock between locations. One looks at the retail shelf. The other looks at everything happening between the factory and that shelf.
Manufacturers that participate in both retail and wholesale channels typically receive both. Read together, they show how product is flowing through the network and whether it’s actually reaching consumers.
What the 852 Reports
Every line in an 852 starts with a product identifier carried in the LIN segment: a UPC, a GS1 Global Trade Item Number, or an internal SKU the trading partners have mapped in advance. Everything else on that line hangs off the identifier.
The core of the report is quantity data, and the 852 uses activity codes to distinguish types of movement. The two most common are quantity on hand (what’s sitting in the store or warehouse right now) and total sales quantity (units sold during the reporting window). A single line item can carry both, broken out by location using destination quantity segments that tie each figure to a specific store.
Locations are identified with the GS1 Global Location Number, a 13-digit code that pinpoints a specific warehouse, store, or dock.1EDICOM. GLN (Global Location Number): Definition and Uses in EDI Many retailers also use internal store numbers, mapped during trading partner setup.
A time-period header defines the scope of the data. Reporting frequency varies: some retailers send 852 data daily, others weekly or monthly, and some trigger transmissions when inventory shifts significantly rather than on a fixed schedule. The report can also include retail pricing through the CTP segment, so the manufacturer sees the selling price alongside movement.2X12. 852 – Product Activity Data
What the 852 Is Used For
The 852 is the engine behind vendor-managed inventory. In a VMI arrangement, the retailer hands replenishment responsibility to the manufacturer. Instead of the retailer cutting purchase orders based on its own counts, the manufacturer monitors the incoming 852 feed and decides when to ship. Walmart’s Retail Link is the best-known example: suppliers pull 852 data and either generate purchase orders automatically or recommend shipment quantities for the retailer to approve.
The logic is straightforward. If a store sold 200 units last week and only has 50 on hand, a replenishment shipment needs to move before the shelf goes empty. Multiplied across hundreds or thousands of locations, the system responds to actual demand rather than forecasts.
Manufacturers also use 852 data to adjust production. A sell-through spike during a promotion can trigger a ramp-up before backorders accumulate. Stagnant inventory across multiple locations can prompt a pricing review, a planogram change, or a marketing push. The 852 turns those calls into data-driven decisions.
What the 867 Reports
The 867 documents a different kind of movement. Rather than reporting what consumers bought off a shelf, it tracks transfers between businesses. The X12 standard describes three core uses: reporting product transferred from one location to another, reporting sales to an end customer, and reporting demand beyond actual sales, including lost orders.3Defense Logistics Agency. DLMS Implementation Convention 867D Demand Reporting
The transaction opens with a BPT segment that sets the report’s purpose (original versus correction), the preparation date, and the report type. Party identification matters here in a way it doesn’t for the 852. The 867 has to clearly identify who shipped the product, who received it, and sometimes who originally ordered it. Ship-from and ship-to parties are encoded in N1 segments with identification codes like a DoD Activity Address Code for military logistics or a DUNS number for commercial partners.
Each line item carries the product identifier, the quantity transferred or sold, and often the unit price or contract price that governed the transaction. When goods move under a specific purchasing agreement, the contract reference is included so the manufacturer can tie the movement back to negotiated pricing. If the transfer is a final sale to a professional end-user, that customer’s identifying information appears in the transaction as well.
What the 867 Is Used For
In wholesale distribution, a manufacturer often sells to a distributor at one price, and the distributor sells downstream at a lower contract price the manufacturer has pre-negotiated. The distributor then claims the difference back through a chargeback. The 867 is the data that makes the chargeback process work.
A distributor sells product to a hospital system at a contract price below what the distributor originally paid. The distributor files a chargeback using an EDI 844 transaction, asking the manufacturer to reimburse the pricing difference. Before paying, the manufacturer needs proof the sale happened at that price to that customer. That proof comes from the 867: who bought it, how much they paid, and what contract governed the transaction.4TraceLink. EDI ANSI X12 844 – Product Transfer Account Adjustment
Beyond chargebacks, manufacturers use the 867 to calculate territory-based sales commissions, manage rebate programs, and monitor where products actually end up geographically. A manufacturer that doesn’t sell directly to end-users would be flying blind without it. In industries like pharmaceuticals and medical devices, where contract pricing structures are especially complex, the 867 is often the only reliable record of what happened downstream.
Accuracy matters because real money changes hands. Wrong quantities, incorrect contract references, or misidentified end-users can cause chargebacks to be rejected, delay commissions, or create phantom revenue in a territory report. On the manufacturer’s side, inaccurate 867 data can lead to overpayment on chargebacks or incorrect commission calculations that compound across thousands of transactions.
The Practical Difference Between the Two
The 867 shows the push side of the network: how product flows from the manufacturer into distribution. The 852 shows the pull side: what consumers are actually buying. Neither tells the complete story alone, and read together they expose problems neither would reveal on its own.
The classic example is a product with strong 867 volume into distributors but weak 852 sell-through at retail. That pattern means product is piling up somewhere in the middle, sitting in a warehouse or a backroom instead of reaching consumers. Without the 852, the manufacturer would see healthy shipments to the distributor and assume everything was fine.
The reverse pattern is equally useful. Strong 852 sell-through with declining 867 transfers signals a thinning pipeline. If the manufacturer doesn’t ramp shipments to the distributor, retail stockouts are on the way.
Where the Data Tends to Go Wrong
Inaccurate on-hand quantities are the most common 852 problem. If the retailer’s inventory system is off, whether from theft, miscounts, or receiving errors, every 852 transmission carries that inaccuracy forward. Replenishment decisions built on wrong on-hand numbers produce either overstock or stockouts.
Format inconsistency is another persistent issue. Every retailer structures its 852 slightly differently within the same X12 standard. Field usage, code values, and reporting periods vary. A manufacturer receiving 852 data from a dozen retail partners often maintains a dozen mapping configurations, and each partner system update can break a mapping.
On the 867 side, the most damaging errors involve contract references and party identification. A wrong contract number can trigger a chargeback rejection or create incorrect commission entries. These errors often don’t surface until a financial reconciliation weeks or months later, when untangling them is far more expensive than getting the data right the first time. Trading partner agreements sometimes impose chargebacks for EDI errors, and those penalties can reach several hundred dollars per incorrect transaction.
How the Transactions Are Transmitted
Both 852 and 867 files move between trading partners through the same set of EDI transmission methods, chosen based on volume, cost, and security requirements.
A Value Added Network acts as a secure middleman. Both partners connect to the VAN, which handles routing, format translation, and delivery confirmation. Pricing is typically based on data volume measured per kilocharacter, which works for moderate volumes but scales up as traffic grows.
AS2 (Applicability Statement 2) creates a direct encrypted connection over the internet. It uses TLS/SSL to secure the channel and S/MIME to encrypt the payload, and it provides non-repudiation through a digitally signed Message Disposition Notification. Once the infrastructure is in place, there’s no per-transaction cost, which makes AS2 attractive for high-volume relationships. Both sides need to support it and exchange digital certificates before the first transmission.
SFTP uses SSH encryption and authenticates with public/private key pairs rather than the certificate exchange AS2 requires. It lacks AS2’s built-in non-repudiation, so trading partners sometimes layer on additional confirmation processes. For companies already running SFTP for other file transfers, adding EDI to the same channel is often the path of least resistance.
The X12 standard, maintained by the organization ANSI chartered more than 40 years ago, still handles the bulk of structured supply chain data exchange.5X12. About X12 For most manufacturers, the choice among VAN, AS2, and SFTP comes down to what their largest trading partners already require.