To start and identify an interchange of zero or more functional groups and interchange-related control segments
QRS/GXS Catalog X12 832 Price/Sales Catalog
X12 832 (Price/Sales Catalog) is the EDI transaction exchanged between QRS/GXS Catalog (QRS/GXS Catalog (via OpenText)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 36
- Loops
- 9
- X12 832
- All partners ↗
Transaction context
Where 832 Price/Sales Catalog fits on QRS/GXS Catalog (via OpenText)
- QRS/GXS Catalog channels
- 1 of 1
- Trading partners
- 10
- Channels
- 26
1 of QRS/GXS Catalog's 1 channel carries 832
partners across the Stacksync network trade 832
channels network-wide carry 832
Most common alongside 832
On OpenText, 832 runs on 1 channel.
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
| 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 — 36 segments 9 loops · X12 832 Price/Sales Catalog
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 Price/Sales Catalog Transaction Set and specify catalog purpose and number information
To specify pertinent dates and times
To specify restrictions/conditions (such as shipping, ordering)
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
N1 Loop
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To specify identifying information
To identify a person or office to whom administrative communications should be directed
LIN Loop Repeat: 100
To specify basic item identification data
To identify the specific type of item maintenance
To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To describe a product or process in coded or free-form format
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)
To describe marking, packaging, loading, and unloading requirements
To specify the carrier and sequence of routing and provide transit time information
To specify transportation special handling requirements, or hazardous materials information, or both
To specify lead time for availability of products and services
To identify a commodity or a group of commodities or a tariff page commodity
To specify tax information
To specify textual data
To provide physical characteristics relative to a consumer unit
CTP Loop Repeat: 100
To specify pricing information
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
G39 Loop Repeat: 20
To identify a vendor's selling unit or to provide physical characteristics relative to a vendor's selling unit
PKL Loop Repeat: 20
To identify the package level, quantity of stock-keeping units (SKUs), and other basic data related to the configuration of the package being defined
LM Loop
To transmit standard code list identification information
LQ Loop
Code to transmit standard industry codes
To provide basic information about the electronic format of the interchange data
SLN Loop
To specify product subline detail item data
PID Loop
QRS/GXS Catalog QRS/GXS Catalog (via OpenText) EDI 832 FAQ
Common questions about 832 Price/Sales Catalog on the QRS/GXS Catalog (via OpenText) 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. QRS/GXS Catalog's QRS/GXS Catalog (via OpenText) channel requires it from trading partners.
Does QRS/GXS Catalog QRS/GXS Catalog (via OpenText) require 832 for trading partners?
Yes, QRS/GXS Catalog (QRS/GXS Catalog (via OpenText)) supports X12 832 Price/Sales Catalog. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate QRS/GXS Catalog 832 with Stacksync?
Most companies go live with QRS/GXS Catalog 832 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Ready to automate your QRS/GXS Catalog EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
