Skip to content
X12 EDI

Cardinal Health, Inc. X12 832 Price/Sales Catalog

X12 832 (Price/Sales Catalog) is the EDI transaction exchanged between Cardinal Health, Inc. (Cardinal Health (Specialty Pharmaceutical Distribution)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
15
Loops
3
X12 832
All partners ↗

Transaction context

Where 832 Price/Sales Catalog fits on Cardinal Health (Specialty Pharmaceutical Distribution)

Cardinal Health, Inc. channels
1 of 3

1 of Cardinal Health, Inc.'s 3 channels carries 832

Trading partners
10

partners across the Stacksync network trade 832

Channels
26

channels network-wide carry 832

The 832 transmits a supplier's electronic product catalog: item identifiers such as UPC codes and vendor part numbers, descriptions, packaging, availability, and prices including promotions and effective dates. Trading partners require it because buyers load this data into their item and pricing masters, and every downstream order and invoice depends on both sides agreeing on the same identifiers and prices. Sent by the supplier or manufacturer to the retailers, distributors, or buyers that need current item and price data.

When it fires: The supplier introduces new products, changes prices, or starts or ends a promotion and must publish the updated catalog to its trading partners.

Common 832 rejection causes
  • Missing mandatory segments or invalid pricing qualifiers that fail the partner's structural validation.
  • Price values or formats that do not match the receiving partner's requirements, creating billing discrepancies on later invoices.
  • Effective or expiration dates outside acceptable windows, so prices load for the wrong period.
  • Product identifiers the receiving partner does not recognize, leaving items unorderable until cross-references are corrected.

Specification summary

X12 832 Price/Sales Catalog at the element level

The X12 832 specification defines 60 segments carrying 256 data elements, 70 of which are mandatory.

Segments
60
Data elements
256
Mandatory elements
70
Segments with mandatory elements
Segment Elements Mandatory
BCT 6 1
DTM 2 1
CTB 3 1
CUR 2 2
SAC 3 1
N1 4 1
N3 2 1
REF 3 1
PER 8 1
LIN 29 2
G53 1 1
Key identifiers in 832
  • Catalog Purpose Code
  • Date/Time Qualifier
  • Restrictions/Conditions Qualifier
  • Entity Identifier Code
  • Currency Code
  • Allowance or Charge Indicator
  • Address Information
  • Reference Identification Qualifier
Full segment guideline — 15 segments 3 loops · X12 832 Price/Sales Catalog
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

BCT Beginning Segment for Price/Sales Catalog 2 elements

To indicate the beginning of the Price/Sales Catalog Transaction Set and specify catalog purpose and number information

DTM Date/Time Reference 2 elements

To specify pertinent dates and times

N1 Loop
N1 Name 3 elements

To identify a party by type of organization, name, and code

N3 Address Information 1 element

To specify the location of the named party

N4 Geographic Location 3 elements

To specify the geographic place of the named party

LIN Loop Repeat: 100
LIN Item Identification 7 elements

To specify basic item identification data

G53 Maintenance Type 1 element

To identify the specific type of item maintenance

REF Reference Identification 3 elements

To specify identifying information

PID Product/Item Description 5 elements

To describe a product or process in coded or free-form format

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

PO4 Item Physical Details 3 elements

To specify the physical qualities, packaging, weights, and dimensions relating to the item

CTP Loop Repeat: 100
CTP Pricing Information 2 elements

To specify pricing information

Trading partners

4+ 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.

Cardinal Health, Inc. Cardinal Health (Specialty Pharmaceutical Distribution) EDI 832 FAQ

Common questions about 832 Price/Sales Catalog on the Cardinal Health (Specialty Pharmaceutical Distribution) channel.

What is X12 832 Price/Sales Catalog?
X12 832 (Price/Sales Catalog) is the EDI transaction set used to exchange price/sales catalog data. Cardinal Health, Inc.'s Cardinal Health (Specialty Pharmaceutical Distribution) channel requires it from trading partners.
Does Cardinal Health, Inc. Cardinal Health (Specialty Pharmaceutical Distribution) require 832 for trading partners?
Yes, Cardinal Health, Inc. (Cardinal Health (Specialty Pharmaceutical Distribution)) supports X12 832 Price/Sales Catalog. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Cardinal Health, Inc. 832 with Stacksync?
Most companies go live with Cardinal Health, Inc. 832 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 832 on Cardinal Health (Specialty Pharmaceutical Distribution)?
On Cardinal Health (Specialty Pharmaceutical Distribution), X12 832 is typically exchanged alongside 856 Ship Notice Manifest, 850 Purchase Order, 855 Purchase Order Acknowledgment, 810 Invoice. 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 Cardinal Health, Inc. EDI?

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