--- title: "QRS/GXS Catalog EDI Integration | Stacksync" description: "QRS/GXS Catalog EDI: 1 listed document types, channel comparison, record mapping and validation guidance for your integration." canonical: https://www.stacksync.com/edi/qrsgxs-catalog last_modified: 2026-09-15 --- # *QRS/GXS Catalog* EDI integration guide. > 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 Plan your QRS/GXS Catalog EDI integration using 1 listed document types across 1 channel. Compare channels, map business records and test the operational handoff. [Book an EDI demo](https://www.stacksync.com/book-a-demo) Explore EDI documents | | | | | --- | --- | --- | | Listed documents | 1 | Partner document references | | Listed channels | 1 | QRS/GXS Catalog (via OpenText) | | Implementation | Plan | Map, validate and reconcile | ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Implementation guide ## QRS/GXS Catalog: EDI implementation plan Build a reliable EDI workflow for QRS/GXS Catalog. Use 1 document type across 1 channel to plan record mapping, prevent duplicate processing and reconcile results in your business systems. The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | [X12 832 Price Sales Catalog](https://www.stacksync.com/edi/qrsgxs-catalog/qrs-gxs-catalog-via-opentext/x12-832-price-sales-catalog) Listed on 1 channel: QRS/GXS Catalog (via OpenText) | **product and price catalog** item identifier, catalog revision and price basis | 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. | ### Implementation steps 1. #### Choose the trading account and channel Choose among QRS/GXS Catalog (via OpenText). Confirm the business unit and account before copying a mapping from another channel. 2. #### Map records and assign owners Start with product and price catalog. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event. 3. #### Test a complete exchange Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the QRS/GXS Catalog production handoff and save the results of each approved test. 4. #### Check results after launch Match records between systems using item identifier, catalog revision and price basis. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries. ### Go-live checklist - The required X12 documents, versions and sample files are agreed. - Sender and receiver IDs, test connections and production connections are agreed with the channel owner. - Delivery receipts, document validation and business responses have monitoring and a named owner. - Tests cover duplicates, partial processing and reconciliation with realistic business records. ### Related documents and resources - [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) - [Evaluate your integration requirements](https://www.stacksync.com/blog/integration-evaluation-worksheet) **Sources.** Directory data as of 2026-05-07. 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/) - [QRS/GXS Catalog document reference](https://www.orderful.com/network/qrsgxs-catalog) Document catalog ## EDI documents listed for QRS/GXS Catalog 1 transactions across 1 channel. ### [QRS/GXS Catalog (via OpenText)](https://www.stacksync.com/edi/qrsgxs-catalog/qrs-gxs-catalog-via-opentext) 1 doc - [X12 832 Price Sales Catalog](https://www.stacksync.com/edi/qrsgxs-catalog/qrs-gxs-catalog-via-opentext/x12-832-price-sales-catalog) Document flow ## Example document relationships for QRS/GXS Catalog Where each document sits in its trading cycle, based on the 1 document type listed for QRS/GXS Catalog across 1 channel. These are example relationships; the trading agreement determines the required sequence. ### Catalog & inventory Some example steps listed 1. [832 Price Sales Catalog](https://www.stacksync.com/edi/qrsgxs-catalog/qrs-gxs-catalog-via-opentext/x12-832-price-sales-catalog) 2. 846 Inventory Inquiry / Advice not listed for QRS/GXS Catalog 3. 852 Product Activity Data not listed for QRS/GXS Catalog Network context ## QRS/GXS Catalog channel references for OpenText These network names are derived from the listed QRS/GXS Catalog channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method. ### OpenText 3 channels · 3 trading partners in the catalog QRS/GXS Catalog channel on this network: QRS/GXS Catalog (via OpenText) Most frequently listed documents - 810 2 ch - 850 2 ch - 856 2 ch - 860 2 ch - 204 1 ch Also listed with OpenText - [Ulta Beauty](https://www.stacksync.com/edi/ulta-beauty) - [Aldi](https://www.stacksync.com/edi/aldi) LEGACY EDI MIGRATION FUND ## Still with a legacy EDI vendor? Ask about a contract buyout. Stacksync can buy out your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. Eligibility and terms are confirmed on a call. [Check your eligibility for the EDI migration fund](https://www.stacksync.com/book-a-demo) | | | | --- | --- | | | [Migrate from SPS Commerce](https://www.stacksync.com/sps-commerce-alternative) | | | Migrate from Cleo | | | Migrate from TrueCommerce | | | Migrate from OpenText | SECURITY ## Security teams trust Stacksync As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### SSO & SCIM Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more. ### Alerts Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options. ### Secure connection options Securely connects to your systems with: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more Related references ## Partners with related document listings Compare document requirements for similar business processes. [Quebec Health Ministry 85 docs · 17 channels](https://www.stacksync.com/edi/quebec-health-ministry) [Boscov's Department Stores 13 docs · 2 channels](https://www.stacksync.com/edi/boscovs-department-stores) [Cardinal Health, Inc. 11 docs · 3 channels](https://www.stacksync.com/edi/cardinal-health-cardinal) [NLS (National Logistics Services) 8 docs · 1 channel](https://www.stacksync.com/edi/national-logistic-services) [ASUSTeK Computer Inc. (dba ASUS) 8 docs · 1 channel](https://www.stacksync.com/edi/asus) [MSC Industrial Supply Co. 8 docs · 1 channel](https://www.stacksync.com/edi/msc-industrial-supply) [Sportsman's Warehouse 8 docs · 1 channel](https://www.stacksync.com/edi/sportsmans-warehouse) [DSW Canada (Formerly Town Shoes Limited) 4 docs · 1 channel](https://www.stacksync.com/edi/town-shoes-limited) [American Greetings 1 doc · 1 channel](https://www.stacksync.com/edi/american-greetings-004180022) [Browse the full directory](https://www.stacksync.com/edi) FAQ ## QRS/GXS Catalog EDI questions ### Which EDI documents are listed for QRS/GXS Catalog? X12 832 Price Sales Catalog. Confirm which documents, directions and versions apply to your account. ### How should I choose the QRS/GXS Catalog EDI channel? The directory lists 1 channels for QRS/GXS Catalog, including QRS/GXS Catalog (via OpenText). Match the channel to your actual trading relationship and compare its document list before reusing a mapping. ### Which identifiers should the QRS/GXS Catalog mapping preserve? For X12 832 Price Sales Catalog, plan around item identifier, catalog revision and price basis. Use the partner guide to locate these values and check their allowed formats. ### Does a successful EDI receipt mean QRS/GXS Catalog accepted the business document? Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed. ### What should be tested before launching QRS/GXS Catalog EDI? 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 missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch. ## Your last integration took months. Your next one takes a prompt. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)