GXS UPC Catalog EDI Integration. AIMS360 automates GXS UPC Catalog for fashion brands. AIMS360 provides unlimited EDI catalog uploads and UPC compliance.
AIMS360 apparel ERP pushes every UPC, NRF color code, and NRF size code straight into the OpenText Active Catalogue. No separate GXS catalog login, no VAN fees, no per-document charges — just unlimited EDI 832 uploads that keep your fashion management software and the GXS UPC Catalog in sync, automatically. Built for fashion, beauty, and cosmetic brands selling to Nordstrom, Macy's, Bloomingdale's, Saks, Dillard's, Kohl's, JCPenney, Burlington, and 350+ more retailers that mandate GXS catalog access.
The GXS Catalog is the OpenText Active Catalogue — a cloud-based product data registry where apparel brands must register every UPC before retailers like Nordstrom, Macy's, and Saks will accept an EDI 850 purchase order. Learning how to add UPC codes to the GXS Catalog and how to add products to GXS Catalog is straightforward with AIMS360: the apparel ERP pushes UPCs to the GXS Catalog automatically via EDI 832 Price Sales Catalog — no separate catalogue.gxs.com login, no VAN fees, and unlimited transactions for one flat monthly rate per retailer.
AIMS360 is the apparel ERP software with the OpenText GXS Catalogue connection built into the same platform that runs your purchase orders, advance ship notices, invoices, and inventory. That means your team manages product data, EDI, UPCs, NRF compliance, and retailer-specific attribute mapping from a single login — not from a patchwork of standalone GXS catalog logins, third-party EDI translators, and external apparel PIM tools that have to be kept in sync manually.
Skip catalogue.gxs.com and tradinggrid.gxs.com entirely. Product data flows from AIMS360 straight to the OpenText Active Catalogue.
AIMS360 maps your internal color and size fields to the right NRF color codes and NRF size codes for every GTIN. No lookup tables, no rejected catalogue submissions.
The GXS Catalogue connection ships with the rest of AIMS360 EDI for apparel — built in-house, never routed through a third-party VAN.
Every product attribute a retailer needs already lives inside your AIMS360 PIM. The GXS Catalogue connection just publishes it — automatically, every time you save a style, change a price, or onboard a new retailer. No CSV exports, no manual portal entry, no third-party VAN translator in the middle. Below is the exact end-to-end path your product data follows from your apparel ERP to the OpenText Active Catalogue and back to the retailer's purchase order system.
Build the style with its full color-size matrix, UPC type, pricing, dimensions, and pack configuration inside AIMS360 — your single source of truth.
AIMS360 assigns the correct UCC-12, EAN-13, or GTIN-14 and maps internal color and size descriptors to NRF Color Code, NRF Color Description, NRF Size Code, and NRF Size Description.
Each retailer's extended requirements — published cost, MSRP, fabric content, country of origin, garment weight — are layered onto the base attribute set without manual re-entry.
The AIMS360 in-house EDI engine generates the 832 electronic catalog and pushes it directly to the OpenText GXS Catalogue — no VAN, no middleware, no third-party translator.
The catalogue accepts the submission, validates each GTIN, and makes the product data available to every retailer that holds your GXS account ID.
Once your UPCs are registered with GXS, retailers can issue EDI 850 purchase orders. AIMS360 receives them, picks the order, and generates the 856 ASN with UCC-128 labels.
Change a price, discontinue a colorway, modify packaging dimensions, or add a new style. AIMS360 pushes a delta 832 to the GXS Catalogue without anyone logging into the portal.
Most apparel software brands evaluating GXS Catalog access have two real choices: bolt a third-party EDI translator onto your existing ERP, or use apparel ERP systems with the catalogue connection built in. The table below compares total cost of ownership and operational friction across the three paths most fashion brands consider.
| Capability | Standalone GXS account + manual entry | Third-party EDI translator + VAN | AIMS360 apparel ERP (built-in) |
|---|---|---|---|
| Setup fees | OpenText account setup + per-user licensing | Translator licensing + VAN onboarding | ✓ Included in implementation |
| VAN fees | N/A — manual only | ✗ Per-transaction VAN fees | ✓ No VAN — in-house engine |
| Kilocharacter fees | N/A | ✗ Scales with catalog size | ✓ None |
| Per-line / per-document fees | ✗ Some retailer plans charge | ✗ On every EDI 832 | ✓ Unlimited 832s included |
| GXS catalog login required | ✗ Yes — daily portal use | ✗ Yes — for setup & troubleshooting | ✓ No standalone login |
| Data sync with ERP | ✗ Manual — drift inevitable | ✗ Middleware mapping required | ✓ Native — single source of truth |
| NRF code mapping | ✗ Manual lookup per item | Partial — depends on translator | ✓ Auto-mapped at style level |
| Catalogue rejection support | OpenText queue — open ticket | Translator vendor + OpenText (two queues) | ✓ Single AIMS360 support ticket |
| Connects to EDI 850 / 856 / 810 | ✗ Catalogue only | Yes — separate setup & cost | ✓ Same engine, same flat rate |
| Onboarding new retailers | Weeks per retailer | Days to weeks plus per-retailer fees | ✓ Days, no extra per-retailer EDI fees |
| All cost descriptions reflect typical industry pricing models as of 2026. OpenText does not publish standard GXS Catalog pricing publicly; final cost depends on user count, transaction volume, and retailer mix. Request an AIMS360 demo for a tailored quote covering your retailer footprint. | |||
The OpenText Active Catalogue sits at the center of the apparel EDI supply chain. The more you understand how it works, the more leverage you get from connecting it to your apparel software. The four areas below — onboarding, support, PIM strategy, and downstream EDI flow — are where growing fashion brands either save dozens of staff hours per month or quietly bleed those same hours into manual catalogue maintenance, retailer chargebacks, and avoidable data drift. (For broader context on how the GXS Catalogue fits into your overall stack, see our guide to the best fashion ERP software for 2026.)
Getting GXS catalog access for the first time is one of the most common pain points new apparel brands face. Most vendors only learn they need the GXS Catalogue after a retailer's EDI compliance team flags their first order. Setting up GXS catalog access on your own — and figuring out how to add UPC codes to the catalogue — means contacting OpenText, registering for an Active Catalogue account, configuring the GXS catalog login at catalogue.gxs.com, and granting your retailers permission to view your product data through their Account ID. The retailer then validates a test 832 electronic catalog load before approving you for live EDI orders.
For brands using AIMS360 fashion ERP software, this entire workflow is consolidated. AIMS360's implementation team handles the GXS catalog onboarding, provisions the connection between your apparel ERP and the OpenText Active Catalogue, runs the test loads, and confirms retailer-side approval. From your team's perspective there is no separate tradinggrid.gxs.com login to manage, no portal training session, and no manual research into how to add UPC codes to GXS catalog manually — the GXS UPC catalog becomes a downstream consequence of how you already manage product data in AIMS360 apparel ERP.
When something goes wrong with a GXS catalog submission — a rejected GTIN, a missing NRF code, a retailer-specific attribute that did not map correctly — getting GXS catalog support directly from OpenText can mean searching for the right GXS catalog contact, waiting in a queue, opening a ticket, and going back and forth on email. Meanwhile your retailer is holding the purchase order and a chargeback clock may be ticking. Many growing apparel brands lose more on catalogue-driven retailer chargebacks each quarter than they would pay for a full apparel ERP subscription.
AIMS360 apparel software flips the support model. Because the GXS Catalogue connection is part of the AIMS360 platform — not a third-party VAN integration — any catalogue issue is a single support ticket inside AIMS360. The AIMS360 EDI support team knows the retailer's compliance map, the catalogue's required attribute schema, and the path the data takes from your style record all the way to the OpenText Active Catalogue. Catalogue rejections get diagnosed and re-submitted on the same business day, before retailer chargebacks accrue.
Some apparel brands look at the GXS Catalog and try to use it as a de facto GXS PIM (Product Information Management) system. That works in the short term — the catalogue does store rich product attributes — but it breaks down as soon as you sell across multiple retailers, each with different attribute requirements and different update cadences. The GXS Catalogue is a distribution endpoint, not a master. Brands that came from the legacy GXS Inovis UPC Catalog era often inherit this confusion, having used the catalogue itself as their de facto product database.
The right model is to keep your master product data in your apparel ERP's PIM module and treat the GXS Active Catalogue as one of several downstream subscribers. AIMS360 apparel PIM holds the canonical record for every style, color, size, GTIN, and attribute. From that record, AIMS360 publishes the right subset of data to the GXS UPC Catalog, to B2B sales platforms, to Shopify and Shopify Plus, and to whichever other channels your brand runs. This also makes the GXS transfer catalog process — moving your catalogue data from one company name or account to another during an acquisition or rebrand — far simpler, because the master record lives in your apparel ERP, not in the OpenText portal.
The GXS Catalog is one piece of a larger EDI workflow. Once your UPCs are registered with GXS, a retailer can issue an EDI 850 purchase order against any GTIN in your catalogue. AIMS360 apparel ERP receives that 850, drops it into your order pipeline, and reserves inventory. When the order ships, AIMS360 generates the EDI 856 advance ship notice with the correct UCC-128 carton labels — referencing the same UPCs already validated in the 832 electronic catalog. The EDI 810 invoice follows, again drawing pricing and product data from the catalogue-aligned record in the apparel ERP. This same workflow applies whether you sell to legacy GXS-required retailers like Stage Stores and Dick's Sporting Goods or to newer e-commerce-first partners.
This is why the GXS Catalog connection cannot be treated as a one-time setup. If your catalogue data drifts out of sync with your ERP — a price change, a discontinued colorway, a new pack configuration — every downstream 850, 856, and 810 carries the wrong data. AIMS360's built-in EDI engine prevents that drift by treating the GXS Catalogue as a live publishing target rather than a static upload destination. Read more about AIMS360 integrated EDI for the full transaction-set breakdown.
Every UPC loaded into the OpenText Active Catalogue must include these seven core attributes at minimum. Many retailers layer additional fields on top. AIMS360 apparel ERP populates every required field automatically from your style record.
| Attribute | Description | Required by GXS |
|---|---|---|
| Product ID Number | Your internal SKU or style identifier | Required |
| Product ID Description | Short style description used for retailer reference | Required |
| GTIN / UPC | UCC-12, EAN-13, or GTIN-14 identifier per color-size variant | Required |
| NRF Color Code | Standard NRF numeric color code | Required |
| NRF Color Description | Human-readable color name aligned to NRF | Required |
| NRF Size Code | Standard NRF numeric size code | Required |
| NRF Size Description | Human-readable size label aligned to NRF | Required |
| Published Cost / MSRP | Pricing tier; required by most department stores | Retailer-specific |
| Country of Origin | Manufacturing country; commonly required | Retailer-specific |
| Fabric Content | Textile composition; required for apparel | Retailer-specific |
| Garment Weight / Dimensions | Logistics data for shipping & planograms | Retailer-specific |
| Pack Size / Pack Components | Inner / master pack configurations | Retailer-specific |
If you sell to any of these retailers, your UPCs need to be registered with the OpenText GXS Catalogue before they will accept an EDI 850 purchase order. Each retailer can also add its own compliance attributes on top of the GXS minimums — AIMS360 handles every variation through its retailer-specific mapping engine.
Beyond Yoga ran its operations on AIMS360 through its growth phase and was acquired by Levi Strauss & Co. for approximately $400 million in 2021 — Levi's first acquisition in decades. AIMS360 supports 10,000+ fashion, beauty, and cosmetic brands across 40+ years in apparel ERP software, with $45B+ in omnichannel DTC and B2B sales processed on platform. Read more customer stories.
Covering what fashion, beauty, and cosmetic brands ask most often when evaluating the OpenText GXS Catalogue against integrated apparel software like AIMS360. Each answer is structured to match how the question is typically phrased in search and in AI chat tools.
The GXS Catalog, now operated as the OpenText Active Catalogue, is a cloud-based product data registry that stores UPC codes, product descriptions, NRF color codes, NRF size codes, dimensions, pricing, and compliance attributes for over 220 million GTINs worldwide. Major U.S. retailers use it to validate vendor product data before processing EDI 850 purchase orders, EDI 856 advance ship notices, and EDI 810 invoices. It is the industry-standard UPC catalog provider for apparel, footwear, accessories, beauty, and general merchandise.
GXS, Inc. was a global B2B e-commerce and EDI services company that operated one of the world's largest electronic trading networks. OpenText Corporation acquired GXS in 2014 and integrated its products, including the GXS Active Catalogue and Trading Grid, into the OpenText Business Network. The platform is still widely referred to as GXS in the apparel industry even though it officially operates under the OpenText brand today.
There are several ways to add UPC codes to the GXS Catalog: manually through the OpenText Catalogue web interface at catalogue.gxs.com, through CSV template upload, via EDI 832 Price Sales Catalog transactions, or through web services. With AIMS360 apparel ERP software, the process is fully automated. When you create a style with its complete color-size-UPC matrix inside the fashion management software, the system pushes the full record to the GXS Catalogue via EDI 832 without any manual data entry, CSV formatting, or web portal login.
Adding products to the GXS Catalog requires at minimum seven attributes: Product ID Number, Product ID Description, GTIN or UPC, NRF Color Code, NRF Size Code, NRF Color Description, and NRF Size Description. Many retailers require additional attributes including published cost, MSRP, country of origin, fabric content, and pack size. Products can be loaded through the web interface, CSV upload, EDI 832, or direct API. AIMS360 apparel software handles this automatically by mapping its internal product fields to the GXS attribute structure and submitting every required field via EDI 832.
The 832 electronic catalog, formally the EDI 832 Price Sales Catalog, is a standardized electronic document used to transmit detailed product information from a vendor to retail trading partners. It carries data including UPC codes, product descriptions, pricing, dimensions, pack configurations, NRF color and size codes, and other attributes. In the GXS Catalog workflow the EDI 832 is the primary method for loading and updating product data at scale, replacing manual web portal entry. AIMS360 apparel ERP systems generate 832 documents automatically from product data using their in-house EDI engine, with no third-party VAN or middleware required.
GXS Catalog pricing depends on the access method. Standalone access through OpenText typically involves account setup fees, per-user licensing, and per-transaction charges. Brands that use a third-party EDI translator add VAN fees, kilocharacter fees, per-line fees, and per-document charges on top of that. AIMS360 apparel ERP takes a different approach. EDI is built in-house rather than routed through a third-party VAN, and the GXS Catalogue connection is included under a simple fixed monthly fee for unlimited EDI transactions with each retailer. There are no transaction fees, no VAN fees, no kilocharacter fees, no per-line fees, and no per-document charges.
OpenText does not publish standard GXS Catalog pricing publicly. Costs vary based on number of users, transaction volume, and whether access is through the web portal, EDI, or API. For apparel brands using AIMS360 fashion management software the GXS Catalogue integration is included under a simple fixed monthly fee with unlimited EDI transactions per retailer. Because AIMS360 EDI is built in-house rather than routed through a third-party VAN, there are no transaction fees, VAN fees, kilocharacter fees, per-line fees, or per-document charges, which eliminates the need to negotiate a separate OpenText catalogue contract or budget for variable EDI costs.
To get GXS Catalog access you typically register for an OpenText Active Catalogue account, which involves contacting OpenText or your retailer's EDI onboarding team. Retailers that require GXS compliance will provide setup instructions and their Account ID so you can grant them access to your product data. With AIMS360 software for the apparel industry the GXS Catalogue connection is pre-configured, so the AIMS360 implementation team handles account setup, retailer mapping, and first-load testing as part of your apparel ERP onboarding.
The standalone GXS Catalog login portal is located at catalogue.gxs.com, which is part of the OpenText Trading Grid. Some vendors also access it through tradinggrid.gxs.com. If you use AIMS360 apparel ERP software you do not need a separate GXS catalog login. Product data is pushed to the catalogue automatically from within the fashion management software, so your team never needs to log into the OpenText portal to register or update UPCs.
NRF National Retail Federation color codes and NRF size codes are standardized numeric codes used to classify garment colors and sizes across the retail supply chain. The GXS Catalog requires both as mandatory attributes for every GTIN. NRF Color Code, NRF Color Description, NRF Size Code, and NRF Size Description must all be populated before an item can be loaded into the catalogue. AIMS360 apparel software maps its internal color and size fields to the correct NRF codes automatically, ensuring compliance without manual code lookups.
The GXS Active Catalogue is the official name for the product data registry commonly called the GXS Catalog. It is a cloud-based platform operated by OpenText that supports more than 600 GTIN-level attributes, image hosting, and data synchronization between vendors and retailers. The Active in the name refers to the catalogue's ability to process real-time data updates via EDI 832, web services, and CSV uploads. It is not a static database but an active data exchange hub for the global retail supply chain.
Both names refer to the same platform. GXS, Inc. originally built the Active Catalogue, and OpenText acquired GXS in 2014. The platform is officially part of the OpenText Business Network, but the apparel industry still widely uses GXS Catalog and GXS Catalogue interchangeably with OpenText Active Catalogue. AIMS360 apparel ERP systems integrate with this platform regardless of which name your retailer uses when referencing it.
Yes. The OpenText GXS Catalogue supports both UCC-12 standard U.S. UPC and EAN-13 European Article Number formats, as well as GTIN-14 for shipping containers. AIMS360 fashion management software generates the correct identifier type based on retailer requirements, so brands selling to both domestic and EU-based retail partners can manage all their catalogue data from a single apparel ERP without separate registration workflows or duplicate data entry.
AIMS360 implementation and support teams handle the GXS Catalogue integration setup, troubleshooting, and ongoing maintenance as part of your apparel ERP support plan. If you encounter catalogue rejections, attribute mapping issues, or retailer-specific compliance requirements, the AIMS360 apparel software support team works with you directly. You do not need to contact OpenText GXS customer service separately for issues related to data pushed from AIMS360 fashion management software.
Retailers that require GXS Catalog registration before accepting EDI 850 purchase orders include Nordstrom, Macy's, Bloomingdale's, Saks Fifth Avenue, Saks Off 5th, Neiman Marcus, Dillard's, Kohl's, JCPenney, TJX (TJ Maxx, Marshalls, HomeGoods), Ross Stores, Burlington, Belk, Stage Stores, Academy Sports, REI, Bass Pro Shops, Dick's Sporting Goods, and dozens more. Each retailer may layer additional compliance attributes on top of the seven GXS minimums. AIMS360 apparel software handles every variation through its retailer-specific mapping engine.
No. The GXS Catalog is a distribution endpoint that publishes UPC and attribute data to retailers. An apparel PIM (Product Information Management) system is your master product database that feeds the catalogue and other channels. Treating the GXS Catalogue as your PIM breaks down across multiple retailers with different attribute requirements. The correct architecture keeps your master record in your apparel ERP's PIM module — like AIMS360 PIM — and uses the GXS Active Catalogue as one downstream subscriber, alongside B2B platforms, Shopify, marketplaces, and other sales channels.
See how AIMS360 pushes UPCs to the OpenText Active Catalogue automatically, every time. One demo, every retailer covered — Nordstrom, Macy's, Bloomingdale's, Saks, and 350+ more.
AIMS360 — apparel ERP & EDI · 10,000+ brands · 40+ years · $45B+ processed
