Usually inbound to you
EDI 867: the product transfer and resale report
The 867 reports product activity after goods have moved through a channel. Depending on the programme, it can describe transfers, resales, returns or balances by item and location for a stated period.
For a supplier, that makes it a downstream signal. It can show where products moved after the original order was fulfilled, provided the item and location references can be matched back to records you trust.
What the document carries
An 867 identifies the reporting parties, the period covered and the product activity being reported. The exact measures and reporting levels come from the partner's implementation guide, so one programme's 867 should never be assumed to match another's.
The rows may arrive at a much finer grain than a sales order: one item across many customer locations and reporting dates. That grain is useful for analysis and demanding for identity management.
How to use it with Odoo
The first job is resolution. The partner's product identifiers need to reach the corresponding Odoo product, and its location references need a stable customer or site record. Unresolved rows belong in an exception queue rather than an anonymous catch-all.
Once resolved, the report can support channel analysis, replenishment conversations and account review. It should remain distinguishable from Odoo's own stock ledger because it describes activity reported by another party, often after ownership or custody has changed.
Where it goes wrong
Item aliases drift, customer locations merge, and a report keeps loading without anyone checking what failed to match. The totals look complete while a quiet portion of the rows has no usable identity.
The basic controls are a reconciliation total, an unresolved-item count and an unresolved-location count for every file. Those three numbers show whether the report is ready for analysis before anyone builds a dashboard on it.
Official definition
X12 publishes the formal transaction-set definition linked below. Your trading partner's implementation guide still governs the fields, codes and timing used in your relationship.
The rest of the set
One document never travels alone. The mandate that asks for this one names its siblings, and the questions repeat: direction, mapping, and what happens when it is late or wrong.
Every code in plain language: the X12 catalog. What a late or wrong document costs: chargebacks and deductions. Who mandates and how it is enforced: the US programmes and the Canadian ones. How the documents fit into purchasing, fulfilment and accounting: EDI across the supply chain.
Start with the letter
The Requirement Check takes two answers: who mandated you and where you stand today. You get back a plain readout of which documents that customer asks for and what has to change inside your Odoo. It is free and it commits you to nothing.
Book a 30-minute call