EDI 867 – Product Transfer and Resale Report (X12)

What Is the EDI 867?

The EDI 867 Product Transfer and Resale Report is an ANSI X12 transaction used by distributors to report downstream product movement to manufacturers. The report communicates sales to end customers, inventory transfers between locations, customer returns, and other resale activity occurring after products enter the distribution channel.

The transaction provides manufacturers and suppliers with visibility into how products move through distributor networks, internal facilities, or retail channels.

The EDI 867 is most common in sectors where manufacturers do not sell directly to the end customer and need downstream reporting from distributors to understand real market demand. Distribution organizations use the EDI 867 to report inventory transfers, distributor sales, returns, and channel consumption information. The transaction enables manufacturers to monitor product demand, measure channel performance, reconcile inventory movement, and generate downstream financial or commission calculations.

What Does the EDI 867 Do?

The EDI 867 reports product activity occurring after distribution, including sales to end customers, transfers between warehouses, and customer returns. The transaction helps manufacturers measure channel demand, reconcile distributor activity, and analyze market consumption trends.

Manufacturers rely on the EDI 867 reporting events that occur within the downstream distribution channel typically to reconcile distribution channel inventory, calculate rebates or commissions, and understand consumption trends across the market.

The EDI 867 transaction enables suppliers to:

• Monitor inventory transfers between facilities
• Capture distributor sales to end customers
• Track customer returns to distributors
• Analyze market intelligence and channel demand signals

Who Uses the EDI 867?

The EDI 867 is commonly used by manufacturers, distributors, wholesalers, and retailers to report downstream product movement across distribution networks. The transaction is especially common in pharmaceutical distribution, consumer goods supply chains, industrial distribution, and government logistics programs across supply chains where downstream resale activity must be reported to product manufacturers or upstream suppliers. 

Common participants include:

When Is the EDI 867 Required?

The EDI 867 is typically required when manufacturers require visibility into downstream product activity after initial shipment. Organizations generally transmit EDI 867 reports on a regular basis (e.g., daily, weekly, or monthly), dependent on the reporting requirements of the supplier agreement.

Common contractual or operational scenarios include: 

• Manufacturer–distributor resale reporting agreements
• Vendor-managed inventory programs
• Government or military contract reporting
• Channel rebate or commission programs
• Healthcare distribution compliance reporting

Is the EDI 867 Mandated Under Regulation?

No, the EDI 867 itself is not mandated by regulation; however, regulatory programs may require product traceability or downstream visibility. Such programs can be supported by the EDI 867 and align with the GS1 Healthcare US initiative, which encourage standardized data exchange for pharmaceutical distribution tracking and supply chain transparency.

How Does the EDI 867 Work in the Business Workflow?

The EDI 867 works as a downstream reporting transaction that communicates product activity occurring after distribution. Distributors collect sales, transfer, and return data from operational systems and transmit periodic EDI 867 reports to manufacturers, allowing suppliers to analyze sell-through activity, inventory movement, and market demand across distribution networks.

Organizations generate data using sales, inventory, and shipment records collected across distributor or branch operations, then use the EDI 867 as a downstream reporting transaction that communicates events occurring after product distribution.

Upstream Transactions

Positioning the EDI 867 at the center of the lifecycle, upstream transactions are those transactions that organizations use to collect sales, inventory, and shipment records (e.g., data) and generate the EDI 867. The following upstream transactions typically precede the EDI 867, these transactions establish the initial commercial transaction and product shipment:

Downstream Transactions

Positioning the EDI 867 at the center of the lifecycle, downstream transactions respond to activity reported in the EDI 867 and may confirm remittance or adjustments.  The EDI 867 supports several downstream activities including transactions that support financial reconciliation and channel accounting processes:

End-to-End Workflow Example

A typical EDI 867 reporting cycle may follow the sequence below:

1. Manufacturer ships products to distributor (EDI 856 / 810).
2. Distributor sells products to downstream customers.
3. Distributor collects transaction data (e.g., order to cash transactions) from ERP or POS systems.
4. Distributor generates an EDI 867 resale report periodically and on a regular basis (e.g., daily, weekly, or monthly)
5. Manufacturer analyzes resale activity to measure demand and channel performance.
6. Manufacturer calculates rebates, commissions, or replenishment decisions based on the EDI 867 resale report responding with one or more downstream transactions (e.g., EDI 820 Remittance Advice, EDI 844 Product Transfer Account Adjustment, EDI 849 Response to Product Transfer Account Adjustment)

Industry-Specific Workflow Variations

The EDI 867 transaction can summarize deliveries, identify receiving locations, and report quantities delivered under contract or promotional programs in support of a number of industry-specific reporting scenarios including:

How does PartnerLinQ use the EDI 867?

PartnerLinQ implementations frequently support EDI 867 reporting for distributor resale reporting, military supply chain reporting, and channel inventory analytics, enabling organizations to track product movement across complex distribution networks. PartnerLinQ tracks and aggregates product movement data and transmits structured EDI 867 reports to manufacturers and suppliers to support inventory visibility and downstream demand monitoring. PartnerLinQ implementations also support several operational use cases including:

1. Intra-company product transfers between internal facilities.

2. Distributor sales reporting to downstream customers.

3. Customer returns reporting to distributors.

4. Market intelligence reporting for channel performance analysis.

Where Is the EDI 867 Used?

The EDI 867 – Product Transfer and Resale Report is used in industries where manufacturers require visibility into downstream product movement after initial shipments to distributors or resellers have taken place. The 867 transaction provides structured reporting of sales, transfers, returns, and channel consumption data so upstream suppliers can monitor demand and inventory across distribution networks, resale reporting that can be used to improve demand planning, pricing accuracy, and contract compliance. Industries where the EDI 867 is commonly deployed include:

Are there Industry-Specific Responses to the EDI 867?

Yes, and while the EDI 867 does not always require a direct response transaction, organizations may generate response documents under specific industry guidance such as the guidance provided by the Healthcare Distribution Alliance (HDA) in support of Distributor Service Agreements used by healthcare distributors 

• Inventory reconciliation adjustments (EDI 846, EDI 852)
• Financial settlements (EDI 810, EDI 812, EDI 820)
• Return transactions (EDI 180)
• Price Authorization Acknowledgement/Status (EDI 845)
• Product Transfer Account Adjustment (EDI 844)
• Response to Product Transfer Account Adjustment 

What Is the Purpose, Key Features, and Business Use Cases of the EDI 867?

The primary purpose of the EDI 867 is to provide post-distribution reporting of product activity occurring after the initial shipment from a manufacturer to a distributor. The transaction communicates customer returns and product exchanges. Many manufacturers compensate distributors through rebates, commissions, or incentive programs based on actual product resale. EDI 867 data provides the transaction-level information needed to calculate these payments accurately. Manufacturers use this information to generate invoices, track contract fulfillment, and credit distribution partners for deliveries made under government agreements. Manufacturers use this information to analyze product performance, warranty activity, and reverse logistics operations. Aggregated EDI 867 reports provides market intelligence data helping manufacturers analyze data like regional demand, distributor performance even promotional campaigns.

Operational Purpose

Manufacturers use the EDI 867 to understand real product consumption rather than shipment volume. The transaction reveals how inventory moves through distributor networks, enabling suppliers to monitor demand, reconcile inventory movement, and evaluate distributor performance across markets. 

The EDI 867 reports what happens after the distributor receives inventory, including sales, transfers, returns, and other channel activity providing structured visibility into downstream product activity, enabling manufacturers to monitor and understand actual product consumption across distributor networks, improving supply chain coordination, inventory management, and financial reconciliation.

Key Features

Key features include:

Business Use Cases

Common business use cases include distributor resale reporting, channel inventory visibility, reverse logistics tracking, government contract reporting, and market demand analytics. By transmitting structured downstream activity data, the EDI 867 enables manufacturers to measure real product consumption rather than just shipment volumes, improving supply planning and channel performance management.

EDI 867 Example Use Cases by Industry

The EDI 867 Product Transfer and Resale Report is used across distribution-driven industries to report downstream product movement such as distributor sales, inventory transfers, and customer returns. Manufacturers rely on the EDI 867 to measure channel demand, reconcile distributor activity, and analyze market consumption patterns across supply chain networks.

In many distribution networks manufacturers ship products to distributors rather than directly to customers. The EDI 867 allows distributors to report downstream sales, transfers, and returns so manufacturers can understand real product consumption across the market.

Operational Visibility Enabled by the EDI 867

Unlike point-of-sale reporting systems that capture retail checkout activity, the EDI 867 reports distributor-level product movement across warehouses, branches, and reseller networks. The transaction therefore provides manufacturers with channel-level visibility into inventory consumption and product demand across distribution ecosystems.

The 867 transaction communicates structured data about product movement, allowing manufacturers to observe how inventory is consumed across the distribution channel rather than relying solely on shipment activity.

Organizations use the EDI 867 to transform downstream operational data into actionable intelligence. The transaction aggregates product transfers, sales activity, returns, and related financial values into a standardized report that can be analyzed by enterprise resource planning (ERP), analytics, and demand planning systems. This visibility allows supply chain operators to align production, inventory, and replenishment decisions with actual market consumption.

EDI 867 vs EDI 852 – What Is the Difference?

The EDI 867 reports downstream product movement such as distributor sales, transfers, and returns, while the EDI 852 Product Activity Data transaction typically reports inventory levels and retail sales activity. Manufacturers use the EDI 867 to analyze channel sell-through, while the EDI 852 focuses more on inventory visibility and point-of-sale activity within retail environments.

EDI 867 vs Point-of-Sale (POS) Reporting

The EDI 867 reports product activity across distributor networks, including transfers, reseller sales, and returns. Point-of-sale (POS) reporting captures retail checkout transactions directly from store systems. Manufacturers use EDI 867 reporting to monitor distributor channel performance, while POS data provides detailed visibility into consumer purchasing behavior at the retail level.

EDI 867 vs Inventory Reporting

The EDI 867 focuses on product movement and resale activity after distribution, including distributor sales, transfers, and returns. Inventory reporting transactions such as EDI 846 or EDI 852 communicate current stock levels. Together these transactions help manufacturers understand both inventory availability and downstream consumption across supply chain networks.

EDI 867 vs Other Related EDI Transactions

The EDI 867 Product Transfer and Resale Report communicates downstream product activity such as distributor sales, transfers, and returns. Other EDI transactions focus on different supply chain functions including order management, shipment visibility, inventory reporting, and financial settlement. Together these transactions provide end-to-end visibility across the order-to-cash lifecycle.

EDI 867 vs EDI 852

The EDI 867 reports distributor sales, transfers, and returns to manufacturers, providing downstream resale visibility. The EDI 852 Product Activity Data transaction primarily reports inventory levels and point-of-sale activity. Organizations often use the two transactions together to provide both inventory visibility and resale reporting.

EDI 867 vs POS Reporting

The EDI 867 provides standardized resale reporting between distributors and manufacturers using ANSI X12 EDI formats. POS reporting typically originates directly from retail systems and captures real-time consumer purchase activity. The 867 aggregates channel activity and communicates it upstream to suppliers for demand planning and analytics.

EDI 867 vs Inventory Reporting

Inventory reporting describes stock levels at a given point in time. The EDI 867 reports product movement events such as sales, transfers, and returns. Manufacturers use EDI 867 reports to analyze consumption trends and channel performance rather than static inventory levels.

While transactions such as EDI 850, 855, 856, and 810 manage ordering, shipment, and billing activities, the EDI 867 provides visibility into what happens after distribution. The transaction reveals how products move through distributor networks and are ultimately sold to downstream customers.

Visibility into Downstream Sales Activity

Manufacturers often ship products to distributors without direct insight into how those products are subsequently sold. The EDI 867 closes this visibility gap by reporting sell-through activity, showing when and where distributors sell products to downstream customers.

This visibility allows manufacturers to:

• Measure actual market demand
• Evaluate distributor performance
• Detect regional sales trends.

Visibility into Channel Inventory Movement

Inventory frequently moves between distribution centers, warehouses, or branch locations after initial delivery. The EDI 867 communicates product transfers and redistribution activity, providing manufacturers with insight into how inventory flows through the channel.

Operational benefits that include:

• Improved demand forecasting
• Optimized inventory allocation
• Reduced stock-outs across distribution regions.

Visibility into Returns and Reverse Logistics

Customer returns and product exchanges create adjustments within the distribution channel that manufacturers must reconcile. The EDI 867 can report returns from customers to distributors, enabling manufacturers to analyze return rates and reconcile inventory corrections.

Operational teams use returns information to:

• Monitor product quality issues
• Manage warranty programs
• Improve reverse logistics processes.

Visibility into Contract and Incentive Programs

Many manufacturers operate distributor incentive programs tied to resale performance. The EDI 867 provides the transaction-level reporting needed to support rebate programs, commission calculations, and promotional allowances.

With automated EDI reporting, organizations can:

• Validate distributor claims
• Reconcile incentive payments
• Audit channel performance against contractual obligations.

Visibility into Market Intelligence and Demand Signals

Aggregated EDI 867 reports generate valuable market intelligence about how products perform across regions and distribution channels. Manufacturers analyze this information to identify demand trends, evaluate promotional effectiveness, and plan future production.

Insights commonly derived from EDI 867 data include:

• Geographic demand patterns
• Distributor performance benchmarks
• Product adoption and lifecycle trends.

Operational Impact Across the Supply Chain

When integrated with ERP and supply chain systems, the EDI 867 becomes a critical data source supporting end-to-end operational visibility. Manufacturers can monitor product movement across the distribution network, reconcile inventory levels, and adjust production plans based on real consumption data.

Organizations that automate EDI 867 reporting gain:

• Improved demand forecasting accuracy
• Stronger channel inventory visibility
• Better coordination between manufacturers and distributors
• Faster financial reconciliation across the supply chain.

By capturing downstream activity and transmitting it in a standardized electronic format, the EDI 867 enables manufacturers to operate with real-time awareness of product movement throughout the distribution ecosystem.

Industry Applications

• Pharmaceutical distribution reporting
• Retail sell-through analytics
• Government logistics reporting

Operational Visibility

Manufacturers gain insight into:

• Product movement
• Inventory consumption
• Distributor performance

Financial Reconciliation

Manufacturers reconcile:

• Distributor commissions
• Rebates
• Contract pricing adjustments

Compliance Reporting

Organizations use EDI 867 reporting to support contractual reporting requirements and traceability initiatives. 

Supply Chain Coordination

Resale reporting improves:

• Demand forecasting
• Inventory planning
• distribution network visibility.

Exception Management

The EDI 867 helps identify:

• Unreported inventory movement
• Distributor reporting discrepancies
• Unexpected sales patterns.

What Information Is Required in the EDI 867?

An EDI 867 includes reporting period information, trading partner identification, product identifiers, activity classification codes, quantities, and monetary values describing downstream product movement. These elements allow manufacturers to analyze distributor sales, inventory transfers, and returns across distribution networks.

The EDI 867 communicates structured information describing downstream product movement, data that represents sales, transfers, returns, and inventory adjustments, (e.g., resale-related activity). To support this level of reporting, the transaction includes a combination of identification data, reporting period information, product-level activity details that enables manufacturers and suppliers to understand what product moved, where it moved, when the activity occurred, and the quantity or monetary value associated with that activity, and of course, summary totals.

Core Information Categories in an EDI 867

Required Segments in the EDI 867

An EDI 867 transaction typically includes segments such as ST (Transaction Header), BPT (Report Header), DTM (Dates), N1 loops (Trading Partner Identification), PTD (Activity Classification), LIN (Item Identification), QTY (Quantity), AMT (Monetary Values), CTT (Transaction Totals), and SE (Transaction Trailer).

Several commonly used to communicate the required level of detail (e.g., information/data) in the transaction include:

Key Data Elements Typically Required

Reporting Period Information

The report defines the period of activity being summarized, typically using elements in the BPT segment including the report creation date.

Required Identifiers

Product Identification

Each product reported in the transaction must be uniquely identified. Product identifiers typically appear in the LIN segment. Common identifiers include:

Optional Segments

Optional segments may include:

• REF – Reference identifiers
• SII – Sales item information
• SAC – Allowances or charges

Required Reference Numbers

Common references include:

• Invoice numbers
• Contract numbers
• Shipment identifiers

Summary Table of Key Segments

What Status and Reason Codes Are Used with the EDI 867?

The EDI 867 – Product Transfer and Resale Report does not rely on a single universal “status code list” in the same way some transactional messages (such as the 214 or 277) do. Instead, status and reason context is communicated through a combination of transaction purpose codes, activity classification codes, quantity qualifiers, monetary qualifiers, and reference identifiers that describe the type of activity being reported.

Status Codes

Status indicators are commonly carried in the BPT segment purpose code may include:

• Original report
• Replacement report
• Cancellation report

Reason Codes

Reason codes may identify:

• Returns
• Inventory adjustments
• Promotional activity

Industry-Specific Code Sets

Healthcare implementations frequently use GS1 and NDC identifiers for product tracking.

What are the Benefits of the 867?

The EDI 867 provides manufacturers with visibility into downstream product consumption. By reporting distributor sales, transfers, and returns, the transaction improves demand forecasting, channel inventory visibility, and financial reconciliation across distribution networks.

Operational Benefits

• Improved channel inventory visibility
• Enhanced demand forecasting
• Better distributor performance tracking

Financial Benefits

• Accurate rebate calculations
• Improved commission tracking
• Better contract compliance monitoring

Compliance Benefits

• Traceability across distribution channels
• Regulatory reporting support

What are the Benefits of Automating the EDI 867?

Automation reduces manual reporting and improves reporting accuracy by:

• Automatically collecting sales data
• Generating standardized reports
• Reducing reconciliation errors
• Accelerating demand analytics.

Are there Regulatory and Compliance Requirements for the EDI 867?

No, the EDI 867 itself is not mandated by regulation but it does support Healthcare and government supply chains which may require structured reporting of product movement, The EDI 867 also aligns with the GS1 Healthcare US initiative, which while not mandated, does encourage standardized data exchange for pharmaceutical distribution tracking and supply chain transparency

EDI 867 Technical Structure, Format, and Versions

The EDI 867 transaction uses standard ANSI X12 segments to communicate product transfer and resale activity. The structure typically includes a transaction header, reporting context segments, party identification loops, item-level activity reporting, and summary totals.

The 867 communicates reporting context that includes trading partner identification, product activity classification, item identification, quantities, and financial values. Using standardized segments and delimiters, the transaction enables trading partners to exchange detailed resale and product transfer data used for inventory visibility, demand analysis, and supply chain reporting.

Hierarchical Loop Structure

Typical loop structure includes: 

File Format and Delimiters

Using the following Production Delimiters on all EDI transmissions sent to Vendors, Carriers, Trading and Solution partners will enable consistent EDI parsing across trading partners:

• Segment Separator – hex 15 (NAK) or hex 7E (~)
• Element separator – hex 7C (|) or hex 2A (*)
• Sub-element Separator – hex 3E (>)

Version Differences

Companion guides often define implementation-specific requirements, common X12 EDI versions include:

• X12 4010
• X12 5010

What are the Limitations of the 867?

The EDI 867 is subject to several limitations that arise from X12 version dependencies and trading partner implementation guides (companion specifications). These constraints affect how the transaction can be structured (required segments), transmitted, and interpreted across supply chain partners.

Version or Companion Guide Constraints

The EDI 867 exists across multiple ANSI X12 releases, and each version defines the available or required segments, qualifiers and element definitions, and code lists and validation rules used. Trading partner guidelines often restrict allowable segments, data structures, and identifier formats.

Jurisdiction-Specific Requirements

Healthcare and government supply chains may impose additional reporting standards.

Timing and Frequency Limitations

Organizations typically transmit EDI 867 reports on a regular basis (e.g., daily, weekly, or monthly), with the timing functionally dependent on the reporting requirements of the supplier agreement.

Are Implementation Guidelines and Sample Files Available for the EDI 867?

Yes. PartnerLinQ provides sample transactions and implementation guides. EDI 867 implementation guides illustrate both inbound and outbound flows, segment layouts, and valid data examples and support testing and partner onboarding. 

Companion Guides

Trading partners frequently publish EDI 867 implementation guidelines defining segment usage and validation rules.  Customized specification documents for use in on boarding and technical development are available through PartnerLinQ Support and Guideline Management.

Trading Partner Requirements

Customized mapping, testing, and validation documentation are also available.  Partners may specify:

• Reporting frequency
• Identifier standards
• Validation rules.

EDI 867 Example File (X12 Sample)

An EDI 867 example shows how distributors report downstream product activity to manufacturers. The transaction includes reporting period information, trading partner identification, product identifiers, quantities, and monetary values describing sales, transfers, or returns within the distribution channel. 

* for illustrative purposes only (Not from a specific companion guide publication)

What are the more common EDI errors and rejection scenarios for the 867?

Structural Errors (997 / 999)

• Missing required segments
• Improper loop structure

Data Validation Errors

• Invalid product identifiers
• Incorrect quantity formats

Identifier Mismatch Errors

• Unknown distributor IDs
• Invalid GLN numbers

Version Compliance Errors

• Incorrect X12 version formatting
• Non-compliant segment usage

Industry-Specific Rejections

Healthcare or government implementations may reject reports due to:

• Incorrect NDC codes
• Invalid contract references.

What are the Basic Questions for EDI Integration with the 867?

Typical integration planning questions include:

1. What is the general direction of the transaction?

2. Are inbound or outbound orders required?

3. Are AS2, VAN, or SFTP connections used?

4. Are more than one trading partner exchanging the EDI 867?

5. Are there other interested parties?

6. What trading partner requirements apply?

7. What version is supported?

8. What other transactions might these interested parties be a party to?

9. What response to the EDI 867 is expected or sent?

10. Is a response to EDI 867 a timed event?  Are notifications involved/needed?

11. Are there samples and specs of the response transaction available?

12. Are change orders supported?

13. What validation rules apply?

14. How are changes to the EDI 867 business message managed today?

15. Is there automation? (an internal systems trigger) or are EDI 867 business message transactions triggered manually?

16. Are responses and changes automatically triggered? (an internal systems trigger) Or do transactions require human intervention?

17. What systems generate or receive the transaction?

18. How are one-time addresses handled in ERP?

19. Are SKU or UPC identifiers used? 

20. What identifiers are required (SKU, UPC, GTIN)?

21. What testing process is required?

22. What validation rules apply?

Common EDI 867 Implementation Challenges

Implementing the EDI 867 Product Transfer and Resale Report can introduce operational and technical challenges because distributors must collect, normalize, and transmit detailed downstream sales activity from multiple systems. Differences in partner requirements, product identifiers, reporting intervals, and data accuracy often require careful mapping, validation, and governance across the trading partner network.

Most EDI 867 implementation challenges occur because resale reporting requires data from multiple operational systems such as ERP, warehouse management systems, and distributor sales platforms. Successful implementations typically focus on data standardization, partner governance, and automated validation processes to ensure consistent downstream reporting.

What are the Best Practices for using the 867?

The EDI 867 transaction aggregates operational and financial data from multiple sources.  Successful implementations require clear reporting rules, consistent identifiers, and reliable validation processes. The following best practices help organizations ensure accurate reporting, effective analytics, and smooth trading partner interoperability, best practices that include:

What Transactions are associated with the 867?

Footnotes

1. PartnerLinQ EDI 867 Product Transfer and Resale Report Specification Notes and Implementation Guidance.

2. Basic EDI Integration Planning Questions Reference Document. 

FAQs

What is EDI 867 used for?

The EDI 867 is used to report downstream product movement such as distributor sales, inventory transfers, and customer returns to manufacturers or suppliers.

Who sends an EDI 867?

Distributors, wholesalers, and resellers typically generate EDI 867 reports and transmit them to manufacturers or suppliers.

Is the EDI 867 required by law?

No. The EDI 867 is not mandated by regulation but is widely used in distributor agreements, vendor-managed inventory programs, and healthcare distribution reporting.

What industries use EDI 867?

Industries using EDI 867 include pharmaceutical distribution, consumer goods, retail distribution, industrial supply chains, and government logistics programs.

How often is the EDI 867 transmitted?

Most organizations transmit EDI 867 reports daily, weekly, or monthly depending on the reporting requirements specified in supplier agreements.

What transactions work with EDI 867?

The EDI 867 often works with transactions such as EDI 850, 855, 856, 810, 820, 844, and 849.