To start and identify an interchange of zero or more functional groups and interchange-related control segments
EDI Cencora (ASD Health Care) (formerly AmerisourceBergen) Cencora (formerly AmerisourceBergen) (Supplier) 867
Cencora (ASD Health Care) (formerly AmerisourceBergen) X12 867 Product Transfer and Resale Report
X12 867 (Product Transfer and Resale Report) is the EDI transaction exchanged between Cencora (ASD Health Care) (formerly AmerisourceBergen) (Cencora (formerly AmerisourceBergen) (Supplier)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 15
- Loops
- 4
- X12 867
- All partners ↗
Transaction context
Where 867 Product Transfer and Resale Report fits on Cencora (formerly AmerisourceBergen) (Supplier)
- Cencora (ASD Health Care) (formerly AmerisourceBergen) channels
- 1 of 1
- Trading partners
- 10
- Channels
- 11
1 of Cencora (ASD Health Care) (formerly AmerisourceBergen)'s 1 channel carries 867
partners across the Stacksync network trade 867
channels network-wide carry 867
Most common alongside 867
The 867 reports what happened to product after the initial sale: resales to end customers (sell-through or point-of-sale data), transfers between company locations, and customer returns. Manufacturers and suppliers use it for visibility into channel sales and inventory movement, and report lines can carry purchase order and contract identifiers that tie reported activity back to specific agreements. A reseller, typically a distributor, wholesaler, or retailer, sends the 867 upstream to the manufacturer or supplier whose product it moved, although the standard allows either party to originate it.
When it fires: A distributor or retailer closes a reporting period and transmits an 867 detailing units sold, transferred between locations, or returned during that period.
Common 867 rejection causes
- Product identifiers on reported lines that do not match the manufacturer's item catalog, so resale lines cannot be matched and processed automatically.
- Missing or incomplete ship-from, ship-to, or end-customer identification, which prevents the manufacturer from attributing reported sales to the right locations or accounts.
- Quantity or unit-of-measure inconsistencies between reported resales and the distributor's purchases, producing reconciliation disputes.
- Transaction type codes that fail to distinguish sales, transfers, and returns, distorting downstream demand reporting.
Specification summary
X12 867 Product Transfer and Resale Report at the element level
The X12 867 specification defines 30 segments carrying 90 data elements, 50 of which are mandatory.
- Segments
- 30
- Data elements
- 90
- Mandatory elements
- 50
| Segment | Elements | Mandatory |
|---|---|---|
| BPT | 4 | 2 |
| DTM | 2 | 1 |
| REF | 2 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| PTD | 3 | 1 |
| N2 | 1 | 1 |
| QTY | 2 | 1 |
| LIN | 11 | 2 |
Key identifiers in 867
- Transaction Set Purpose Code
- Date
- Date/Time Qualifier
- Reference Identification Qualifier
- Entity Identifier Code
- Address Information
- Product Transfer Type Code
- Name
Full segment guideline — 15 segments 4 loops · X12 867 Product Transfer and Resale Report
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of the Product Transfer and Resale Report Transaction Set and transmit identifying data
To specify pertinent dates and times
N1 Loop Repeat: 5
To identify a party by type of organization, name, and code
To specify identifying information
PTD Loop Repeat: 5
To indicate the start of detail information relating to the transfer/resale of a product and provide identifying data
To specify the location of the named party
To specify the geographic place of the named party
CTT Loop Repeat: 1
To transmit a hash total for a specific element in the transaction set
To indicate the total monetary amount
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
SII Loop
To specify line item information related to a sale of an item
To transmit identifying information as specified by the Reference Identification Qualifier
Trading partners
5+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
PU Purchase Order PU Purchase Order Acknowledgment SH Ship Notice Manifest PR Product Activity Data IN Invoice
No trading partner matches your search.
Browse the full directory
Cencora (ASD Health Care) (formerly AmerisourceBergen) Cencora (formerly AmerisourceBergen) (Supplier) EDI 867 FAQ
Common questions about 867 Product Transfer and Resale Report on the Cencora (formerly AmerisourceBergen) (Supplier) channel.
What is X12 867 Product Transfer and Resale Report?
X12 867 (Product Transfer and Resale Report) is the EDI transaction set used to exchange product transfer and resale report data. Cencora (ASD Health Care) (formerly AmerisourceBergen)'s Cencora (formerly AmerisourceBergen) (Supplier) channel requires it from trading partners.
Does Cencora (ASD Health Care) (formerly AmerisourceBergen) Cencora (formerly AmerisourceBergen) (Supplier) require 867 for trading partners?
Yes, Cencora (ASD Health Care) (formerly AmerisourceBergen) (Cencora (formerly AmerisourceBergen) (Supplier)) supports X12 867 Product Transfer and Resale Report. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Cencora (ASD Health Care) (formerly AmerisourceBergen) 867 with Stacksync?
Most companies go live with Cencora (ASD Health Care) (formerly AmerisourceBergen) 867 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 867 on Cencora (formerly AmerisourceBergen) (Supplier)?
On Cencora (formerly AmerisourceBergen) (Supplier), X12 867 is typically exchanged alongside 850 Purchase Order, 855 Purchase Order Acknowledgment, 810 Invoice, 856 Ship Notice Manifest. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Cencora (ASD Health Care) (formerly AmerisourceBergen) EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
