DEV Community

challan116-ux
challan116-ux

Posted on

The EDI 867, Decoded: A Product Transfer and Resale Report Is How a Distributor Proves What Actually Sold

Short answer: The EDI 867 · Product Transfer and Resale Report is the message a distributor, reseller, or sales agent sends back up the chain to report what happened to product after it left the manufacturer or supplier: what was transferred, what was resold, to whom, in what quantity, and at what price. It is not an order, not an invoice, and not inventory advice. It is the sell-through evidence that rebates, commissions, chargebacks, and replenishment decisions get graded against.

If the 846 · Inventory Inquiry/Advice says "here is what we have," the 867 says "here is what we moved — and here is the proof."

What is the 867 actually for?

Manufacturers sell through distributors. Distributors hold stock at multiple locations, transfer it between branches, and resell it to end customers. The manufacturer cannot see any of that in its own ERP. The 867 closes that blind spot.

A typical 867 reports, per product and per location:

  • Transfers between distributor locations (product moved, not sold)
  • Resales to end customers (product sold, with ship-to identity)
  • Quantities, dates, and the distributor's internal reference numbers
  • Pricing where the agreement requires resale price reporting

That feed drives three things manufacturers care about: special-pricing and rebate claims (a distributor claiming a rebate must prove the resale qualified), commission and sales-credit assignment, and demand signal — real end-customer demand, not just distributor reorders.

How is the 867 different from the 846 and the 852?

These three get confused constantly, and the confusion causes real mapping errors:

  • 846 · Inventory Inquiry/Advice — a snapshot: quantities on hand and on order at a location, at a moment in time. No movement, no customer.
  • 852 · Product Activity Data — sales and inventory activity, usually retail point-of-sale driven: what sold at store level, what remains.
  • 867 · Product Transfer and Resale Report — movement and resale in distribution: transfers between locations plus resales to identified end customers, with the transaction detail rebate programs need.

Rule of thumb: stock level = 846, store sell-through = 852, distributor transfer + resale = 867.

What breaks in an 867 feed?

1. Resales reported without the end-customer identity. A rebate claim lives or dies on who the product was resold to. An 867 line that reports quantity and price but omits or mangles the ship-to identification is ungradeable — the manufacturer cannot verify eligibility, so the claim stalls or gets denied.

2. Transfers double-counted as sales. A transfer between two distributor branches is movement, not demand. If the sending location reports it as a resale and the receiving location later reports the real sale, the manufacturer sees two sales for one unit. Transfer and resale activity must carry distinct activity codes, and the receiving location's later resale is the only one that counts as demand.

3. Negative and correction lines that do not reference the original. Returns, cancellations, and corrections arrive as negative quantities or reversal lines. When they do not reference the original report line, the manufacturer's system cannot net them — gross sales stay inflated and every downstream rebate calculation is wrong by that amount.

4. Product identification drift. The distributor's item number, the manufacturer's part number, and the GTIN/UPC are three different keys. An 867 mapped on the distributor's internal number alone forces the manufacturer to maintain a cross-reference that goes stale silently. Report the manufacturer's number or the GTIN where the agreement calls for it — and flag unmapped items as exceptions instead of dropping them.

5. Reporting-period gaps. The 867 is usually periodic — weekly or monthly. A missing period is worse than a late one if nobody notices: rebate accruals, commission statements, and demand forecasts all quietly assume zero activity instead of unknown activity. The feed needs a completeness check: every location, every period, accounted for — even if the report is legitimately empty.

What does a clean 867 process look like?

Generate the report from the distributor's transaction records — transfers and invoices — never from a spreadsheet assembled at period end. Key each line to the original transaction so corrections can reference it. Separate transfer activity from resale activity with the correct activity codes. Validate product identification against the manufacturer's catalog before sending, not after a denial. And track acknowledgment: the 997 · Functional Acknowledgment confirms the file was received and parsed, which is the minimum evidence the report actually landed.

Frequently asked questions

Is the 867 an order? No. Nothing in an 867 asks for product or commits to buy. It reports activity that already happened.

Who sends the 867? Usually the distributor, reseller, warehouse, or sales agent holding or moving the product. The manufacturer or supplier receives it.

Does every distributor relationship need 867s? No — mainly where rebates, special pricing, commissions, or consignment/visibility programs depend on verified resale data. Plain buy-sell relationships often run fine on orders and invoices alone.

What happens when an 867 disagrees with a rebate claim? The 867 wins, or the claim waits. That is the point of the feed: it is the shared evidence both sides grade against, which is why accuracy at the line level matters more than speed.


The 867 is unglamorous and decisive: it is how money that depends on "trust us, we sold it" becomes money that depends on a record both sides can check. We handle 867 mapping and validation the same way at SignalEDI — generated from transaction records, keyed to originals, checked before it goes out: https://signaledi.com?utm_source=devto&utm_medium=article&utm_campaign=2026-11-12

— Chris, founder of SignalEDI

Top comments (1)

Collapse
 
hiredov profile image
Dov at HireDov •

Good breakdown. One practical point on the correction lines: in my experience the netting problem is easiest to prevent at the sender, by making the original transaction reference mandatory on any negative or reversal line and rejecting the file at intake if it's missing or doesn't match a line already received. Cleaning it up afterwards is much slower.

It also helps to keep a stable key per resale line (distributor ID, their invoice number, line number, and product ID) so a resend replaces the earlier line instead of duplicating it. Late-arriving corrections for a closed rebate period are worth a separate rule too, since otherwise they silently change numbers someone has already paid on.