--- title: "EDI 832 Price/Sales Catalog: X12 832 Guide | Stacksync" description: "EDI 832 is the X12 Price/Sales Catalog, used when catalog entries or commercial details are published. See key segments (BCT, LIN, DTM) and mapping checks." canonical: https://www.stacksync.com/edi/x12/832-price-sales-catalog last_modified: 2026-09-29 --- X12 transaction code # EDI 832 Price/Sales Catalog (X12 832) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 832 is the X12 Price/Sales Catalog transaction set, used when catalog entries or commercial details are published. The supplier or manufacturer sends the 832 to the retailers, distributors, or buyers that need current item and price data. Standard X12 Code 832 Partner references 10 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 832 at a glance What the 832 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 832 Price/Sales Catalog summary** | | | | --- | --- | | Document | X12 832 Price/Sales Catalog | | Business record | Product and price catalog | | Who sends it to whom | The supplier or manufacturer sends the 832 to the retailers, distributors, or buyers that need current item and price data. | | When it is sent | The supplier introduces new products, changes prices, or starts or ends a promotion and must publish the updated catalog to its trading partners. | | Match on | Item identifier, catalog revision and price basis | | Partner references | 10 trading partners in this directory | | Related documents | [X12 846 Inventory Inquiry/Advice](https://www.stacksync.com/edi/x12/846-inventory-inquiry-advice), [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) | ### Key segments in an EDI 832 The business segments that appear in at least half of the 26 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send. | Segment | Name | Purpose | Partner references | | --- | --- | --- | --- | | BCT | Beginning Segment for Price/Sales Catalog | To indicate the beginning of the Price/Sales Catalog Transaction Set and specify catalog purpose and number information. | 26 of 26 | | LIN | Item Identification | To specify basic item identification data. | 26 of 26 | | DTM | Date/Time Reference | To specify pertinent dates and times. | 26 of 26 | | PID | Product/Item Description | To describe a product or process in coded or free-form format. | 26 of 26 | | CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 25 of 26 | | CTP | Pricing Information | To specify pricing information. | 24 of 26 | | N1 | Name | To identify a party by type of organization, name, and code. | 23 of 26 | | PO4 | Item Physical Details | To specify the physical qualities, packaging, weights, and dimensions relating to the item. | 19 of 26 | | TXI | Tax Information | To specify tax information. | 18 of 26 | Stacksync connects EDI documents such as the X12 832 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. Implementation guide ## X12 832 mapping and validation X12 832 Price/Sales Catalog is used when catalog entries or commercial details are published. Preserve item identifier, catalog revision and price basis so the product and price catalog in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **product and price catalog** item identifier, catalog revision and price basis | Define which combination of item identifier, catalog revision and price basis identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the product and price catalog** ID assigned by the receiving system and processing result | Test a pack-size change without treating case and each prices as equivalent. Apply a future price at its effective date while preserving the current price. | | Check the processing result | **Processing status for the product and price catalog** Original document reference and matching response | Reconcile the product and price catalog with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### How the related documents differ Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately. - [X12 846 Inventory Inquiry/Advice](https://www.stacksync.com/edi/x12/846-inventory-inquiry-advice) **inventory availability record:** stock availability is reported or requested. - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) **purchase order or sales order:** a buyer places an order. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when catalog entries or commercial details are published. Name the operational owner of the product and price catalog and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map item identifier, catalog revision and price basis. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier. 3. #### Test failures before launch Run the failure cases in the mapping table against realistic product and price catalog data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate. 4. #### Track every document to completion Record transport delivery and document validation separately from successful product and price catalog processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 832 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic product and price catalog data. - Each submitted document can be traced through delivery, validation and processing in the receiving system. - Your team knows how to investigate and recover a rejected or timed-out product and price catalog without processing it twice. ### Related documents and resources - [X12 846 Inventory Inquiry/Advice](https://www.stacksync.com/edi/x12/846-inventory-inquiry-advice) - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) Document structure ## X12 832 Price/Sales Catalog at the element level The X12 832 reference contains 60 segment entries and 256 data elements; 70 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 60 Data elements 256 Mandatory elements 70 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 832 10 partners, 26 channels. Choose a channel to inspect its listed document reference and implementation context. - [American Greetings](https://www.stacksync.com/edi/american-greetings-004180022) [American Greetings - 004180022](https://www.stacksync.com/edi/american-greetings-004180022/american-greetings-004180022/x12-832-price-sales-catalog) - [ASUSTeK Computer Inc. (dba ASUS)](https://www.stacksync.com/edi/asus) [ASUS](https://www.stacksync.com/edi/asus/asus/x12-832-price-sales-catalog) - [Boscov's Department Stores](https://www.stacksync.com/edi/boscovs-department-stores) [Boscov's Department Stores](https://www.stacksync.com/edi/boscovs-department-stores/boscov-s-department-stores/x12-832-price-sales-catalog) - [Cardinal Health, Inc.](https://www.stacksync.com/edi/cardinal-health-cardinal) [Cardinal Health (Specialty Pharmaceutical Distribution)](https://www.stacksync.com/edi/cardinal-health-cardinal/cardinal-health-specialty-pharmaceutical-distribution/x12-832-price-sales-catalog) - [DSW Canada (Formerly Town Shoes Limited)](https://www.stacksync.com/edi/town-shoes-limited) [Designer Brands Canada](https://www.stacksync.com/edi/town-shoes-limited/designer-brands-canada/x12-832-price-sales-catalog) - [MSC Industrial Supply Co.](https://www.stacksync.com/edi/msc-industrial-supply) [MSC Industrial Supply (via SPS Commerce)](https://www.stacksync.com/edi/msc-industrial-supply/msc-industrial-supply-via-sps-commerce/x12-832-price-sales-catalog) - [NLS (National Logistics Services)](https://www.stacksync.com/edi/national-logistic-services) [NLS (National Logistics Services)](https://www.stacksync.com/edi/national-logistic-services/nls-national-logistics-services/x12-832-price-sales-catalog) - [QRS/GXS Catalog](https://www.stacksync.com/edi/qrsgxs-catalog) [QRS/GXS Catalog (via OpenText)](https://www.stacksync.com/edi/qrsgxs-catalog/qrs-gxs-catalog-via-opentext/x12-832-price-sales-catalog) - [Quebec Health Ministry](https://www.stacksync.com/edi/quebec-health-ministry) [QHM (Chaudière-Appalaches) (via SPS Commerce formerly Intertrade) (ISA ID: CISSSCA)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-chaudi-re-appalaches-via-sps-commerce-formerly-intertrade-isa-id-cisssca/x12-832-price-sales-catalog) [QHM (Estrie CHUS) (via SPS Commerce formerly Intertrade) (ISA ID: CIUSSSESTRIE)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-estrie-chus-via-sps-commerce-formerly-intertrade-isa-id-ciusssestrie/x12-832-price-sales-catalog) [QHM (Laval) (via SPS Commerce formerly Intertrade) (ISA ID: CISSSLAVAL)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-laval-via-sps-commerce-formerly-intertrade-isa-id-cissslaval/x12-832-price-sales-catalog) [QHM (IUCPQ) (via SPS Commerce formerly Intertrade) (ISA ID: MSSSIUCPQ)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-iucpq-via-sps-commerce-formerly-intertrade-isa-id-msssiucpq/x12-832-price-sales-catalog) [QHM (Ouest-de-l'Île-de-Montréal) (via SPS Commerce formerly Intertrade) (ISA ID: CIUSSSWESTILE)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-ouest-de-l-le-de-montr-al-via-sps-commerce-formerly-intertrade-isa-id-ciussswestile/x12-832-price-sales-catalog) [QHM (Gaspésie) (via SPS Commerce formerly Intertrade) (ISA ID: CISSSGASPESIE)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-gasp-sie-via-sps-commerce-formerly-intertrade-isa-id-cisssgaspesie/x12-832-price-sales-catalog) [QHM (COMTL) (via SPS Commerce formerly Intertrade) (ISA ID: CIUSSSCOMTL)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-comtl-via-sps-commerce-formerly-intertrade-isa-id-ciussscomtl/x12-832-price-sales-catalog) [QHM (CHU Sainte-Justine) (via SPS Commerce formerly Intertrade) (ISA ID: 5143454931)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-chu-sainte-justine-via-sps-commerce-formerly-intertrade-isa-id-5143454931/x12-832-price-sales-catalog) [QHM (Capitale-Nationale) (via SPS Commerce formerly Intertrade) (ISA ID: CIUSSSCN)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-capitale-nationale-via-sps-commerce-formerly-intertrade-isa-id-ciussscn/x12-832-price-sales-catalog) [QHM (Montérégie-Est) (via SPS Commerce formerly Intertrade) (ISA ID: CISSSME)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-mont-r-gie-est-via-sps-commerce-formerly-intertrade-isa-id-cisssme/x12-832-price-sales-catalog) [QHM (via SPS Commerce formerly Intertrade) (ISA ID: CSINUULITSIVIK)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-via-sps-commerce-formerly-intertrade-isa-id-csinuulitsivik/x12-832-price-sales-catalog) [QHM (Montérégie-Centre) (via SPS Commerce formerly Intertrade) (ISA ID: CISSSMC)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-mont-r-gie-centre-via-sps-commerce-formerly-intertrade-isa-id-cisssmc/x12-832-price-sales-catalog) [QHM (via SPS Commerce formerly Intertrade) (ISA ID: 306012015)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-via-sps-commerce-formerly-intertrade-isa-id-306012015/x12-832-price-sales-catalog) [QHM (Mauricie-et-du-Centre-du-Québec) (via SPS Commerce formerly Intertrade) (ISA ID: CIUSSSMCQ-TR)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-mauricie-et-du-centre-du-qu-bec-via-sps-commerce-formerly-intertrade-isa-id-ciusssmcq-tr/x12-832-price-sales-catalog) [QHM (Côte-Nord) (via SPS Commerce formerly Intertrade) (ISA ID: CISSSCOTENORD)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-c-te-nord-via-sps-commerce-formerly-intertrade-isa-id-cissscotenord/x12-832-price-sales-catalog) [QHM (via SPS Commerce formerly Intertrade) (ISA ID: 306011188)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-via-sps-commerce-formerly-intertrade-isa-id-306011188/x12-832-price-sales-catalog) [QHM (Institut Phillippe-Pinel) (via SPS Commerce formerly Intertrade) (ISA ID: 5146488461)](https://www.stacksync.com/edi/quebec-health-ministry/qhm-institut-phillippe-pinel-via-sps-commerce-formerly-intertrade-isa-id-5146488461/x12-832-price-sales-catalog) - [Sportsman's Warehouse](https://www.stacksync.com/edi/sportsmans-warehouse) [Sportsman's Warehouse (via SPS Commerce)](https://www.stacksync.com/edi/sportsmans-warehouse/sportsman-s-warehouse-via-sps-commerce/x12-832-price-sales-catalog) Catalog breakdown ## Where X12 832 Price/Sales Catalog appears in this catalog The largest groups of classified 832 catalog entries are in healthcare & pharma, retail and logistics & transport. ### By industry - healthcare & pharma 18 channels - retail 2 channels - logistics & transport 1 channel - electronics & technology 1 channel - manufacturing & industrial 1 channel - consumer goods 1 channel ### By network - SPS Commerce 19 channels - OpenText 1 channel Partner entries with the most listed channels - [Quebec Health Ministry](https://www.stacksync.com/edi/quebec-health-ministry) - [American Greetings](https://www.stacksync.com/edi/american-greetings-004180022) - [ASUSTeK Computer Inc. (dba ASUS)](https://www.stacksync.com/edi/asus) - [Boscov's Department Stores](https://www.stacksync.com/edi/boscovs-department-stores) - [Cardinal Health, Inc.](https://www.stacksync.com/edi/cardinal-health-cardinal) - [DSW Canada (Formerly Town Shoes Limited)](https://www.stacksync.com/edi/town-shoes-limited) - [MSC Industrial Supply Co.](https://www.stacksync.com/edi/msc-industrial-supply) - [NLS (National Logistics Services)](https://www.stacksync.com/edi/national-logistic-services) FAQ ## EDI 832 questions ### What is an EDI 832? EDI 832 is the X12 Price/Sales Catalog transaction set. Trading partners use it when catalog entries or commercial details are published. It carries the data for the product and price catalog, and your system matches it on item identifier, catalog revision and price basis. ### Who sends an EDI 832 and who receives it? The supplier or manufacturer sends the 832 to the retailers, distributors, or buyers that need current item and price data. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 832 sent? The supplier introduces new products, changes prices, or starts or ends a promotion and must publish the updated catalog to its trading partners. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 832? Across 26 partner document references listed here, the business segments that appear most often include BCT (Beginning Segment for Price/Sales Catalog), LIN (Item Identification), DTM (Date/Time Reference), PID (Product/Item Description), CTT (Transaction Totals), CTP (Pricing Information). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 832 and EDI 846? The 832 carries the product and price catalog and is used when catalog entries or commercial details are published. The 846 carries the inventory availability record and is used when stock availability is reported or requested. ### What should I map for X12 832? Start with item identifier, catalog revision and price basis and the target product and price catalog. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats. ### How should I test 832 error handling? Test a pack-size change without treating case and each prices as equivalent. Apply a future price at its effective date while preserving the current price. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 832? The directory on this page links 10 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ## Connect EDI to your business systems See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)