Skip to content
EDI X12 867

X12 transaction code

X12 867 Product Transfer And Resale Report

Stop Mapping. Start Trading.

Standard
X12
Code
867
Trading partners
10

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
Segments with mandatory elements
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

Usage breakdown

Who trades X12 867 Product Transfer And Resale Report

867 is used most heavily in healthcare & pharma, building & hardware and electronics & technology.

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. A distributor or retailer closes a reporting period and transmits an 867 detailing units sold, transferred between locations, or returned during that period.

By industry

  • healthcare & pharma 4 channels
  • building & hardware 3 channels
  • electronics & technology 2 channels
  • grocery & food 2 channels

By network

  • Epicor Eclipse 2 channels
  • iTradeNetwork 1 channel

FAQ

X12 867 questions

What is X12 867 Product Transfer And Resale Report?

X12 867 (Product Transfer And Resale Report) is an EDI transaction set defined by ANSI ASC X12 for exchanging product transfer and resale report between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 10 Stacksync trading partners support this code across 11 channels.

Which trading partners use X12 867?

10 Stacksync partners accept X12 867: BioCare, Inc., Border States, Cardinal Health, Inc., Cencora (ASD Health Care) (formerly AmerisourceBergen), Central Supply Company, CuraScript SD, Dot Foods, Inc., Granite City Electric, and more. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.

How do I integrate X12 867 with my ERP?

Stacksync handles the full X12 867 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.

Ready to automate your EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.