A manufacturer that sells through distributors goes blind at the loading dock: product ships into the channel, and what happens next — who bought it, at what price, in which territory — disappears into someone else's system. The EDI 867 Product Transfer and Resale Report is the document that restores sight. Distributors use it to report sell-through and product movement back to the manufacturer, and in several industries it's not a courtesy — it's the data on which real money settles.
What a resale report contains
The 867's core is the PTD loop — product transfer detail — each occurrence reporting a movement: a sale to an end customer, a transfer between distributor locations, a return to stock. Within it, LIN identifies the product, QTY the amount, and pricing detail rides where the reporting supports settlement. N1 loops carry the parties, including — where the trading agreement requires it — the end customer's identity and location. A BPT header frames the report and its period.
That end-customer detail is what separates the 867 from mere summary statistics: it turns the channel from a black box into a ledger of who is actually consuming your product, at what velocity, where.
Where the money hangs on it
Two settlement mechanisms make the 867 load-bearing rather than informational:
- Contract chargebacks. In channels where manufacturers negotiate end-customer pricing below distributor acquisition cost — pharmaceutical distribution being the canonical case — the distributor sells at the contract price and bills the manufacturer back for the difference. That rebill is computed from resale reporting: no accurate 867 detail, no clean chargeback settlement, and disputes bloom in the gap.
- Rebates and ship-and-debit programs. Electronics and industrial channels run similar logic — distributor margins adjusted after the fact based on what was sold to whom, with the 867 as the evidentiary record.
Even outside settlement, the visibility compounds: territory analytics, demand sensing ahead of distributor reorders, and inventory-in-channel estimates all fall out of consistent resale reporting. Paired with the retailer-side 852, a manufacturer can see demand across both halves of its go-to-market; paired with distributor 846 inventory feeds, sell-through and stock-on-hand reconcile into a full channel picture. Some agreements also lean on the 867 for serialized or regulated product, where knowing which units went where is a tracing requirement rather than an analytical preference.
Making the data usable
Resale files are dense — many movements, many parties, long periods — and their failure mode is arriving faithfully and never being analyzed. The processing pattern that works: validate identifiers on arrival (products against your item master and the 832 catalog you publish, customers against your account records), post settlement-relevant detail into the rebate or chargeback workflow, and land the rest in an analytical store keyed by product, customer, and territory. Identifier hygiene is most of the game; a resale line reporting an unrecognized part number or an unmatchable end customer is a settlement dispute in embryo. Period alignment is the other recurring snag: distributors report on their calendars, rebate agreements settle on yours, and movements that straddle a boundary get claimed twice or not at all unless the processing layer prorates deliberately. It's dull work, which is exactly why software should do it.
EDISQ parses inbound 867s, runs the cross-reference validation automatically, and delivers clean, keyed data to your ERP or analytics stack — among 30+ integrations — so channel reporting feeds decisions instead of a folder.
And the meter
Reporting documents bill at EDISQ's standard rates: your first 25 documents each month are free, then per-document pricing starts at $0.50 and declines through the volume tiers to $0.10, applied marginally — no mapping or setup fees, AS2/SFTP/VAN transport included. However many thousand resale lines a distributor packs into one 867, it meters as a single document; the visibility inside it is the closest thing to free intelligence a channel manufacturer gets.
FAQ
What does an EDI 867 report?
Product movement after the first sale: what a distributor sold or transferred, in what quantities, and often to which end customers. It gives a manufacturer visibility past the distributor's loading dock.
How does the 867 differ from the 852?
The 852 is retail activity data — store-level sales and stock from a retailer. The 867 is the distribution-channel equivalent: sell-through and transfers reported by a distributor, frequently with end-customer identification.
Why do contracts depend on the 867?
Because channel pricing does. Distributor rebates and contract chargebacks hinge on who the end customer was and what price applied — the 867 supplies the transaction detail those settlements are calculated from.
What does receiving 867s cost through EDISQ?
The usual ladder: nothing for the first 25 documents monthly, then from $0.50 per document with rates falling to $0.10 at volume. Even dense reporting stays cheap.