GXS UPC Catalog EDI Integration. AIMS360 automates GXS UPC Catalog for fashion brands. AIMS360 provides unlimited EDI catalog uploads and UPC compliance.
So what is GXS, and why does it matter to fashion companies? The GXS Catalog — originally built by GXS, Inc. and now operated by OpenText as part of their Trading Grid — is a cloud-based product information registry that stores over 220 million Global Trade Item Numbers (GTINs) from thousands of vendors worldwide. You may also see it referred to as the GXS Active Catalogue, OpenText Active Catalogue, or simply the GXS UPC Catalog — they all refer to the same platform. As the dominant UPC catalog provider, GXS (now under OpenText) is the system most major U.S. retailers rely on to look up and validate the UPC codes, product descriptions, dimensions, and compliance attributes of every item a vendor wants to ship or sell through their channels.
For apparel and fashion brands, the GXS Catalogue is not optional. Major department stores, sporting goods chains, and mass-market retailers require that every UPC is registered with GXS before they will accept an EDI 850 purchase order or generate an EDI 856 advance ship notice. If your UPC is not in the catalogue, your order does not process — it is that simple. The catalogue also stores fashion-specific attributes like NRF color codes, NRF size codes, fabric descriptions, country of origin, garment dimensions, and seasonal availability dates. These attributes drive everything from the retailer's planogram to their e-commerce product detail pages, so accuracy matters.
Brands that rely on a separate OpenText GXS login to manually update their catalogue data face a constant bottleneck: every new style, colorway, or size run requires someone to log into the GXS Catalogue portal, key in the data, and hope it matches what is in the ERP. AIMS360 apparel ERP systems remove that bottleneck entirely.
One of the most common frustrations for apparel vendors is managing a standalone GXS catalog login — whether through tradinggrid.gxs.com or the OpenText Catalogue browser portal — alongside their ERP, warehouse system, and B2B portal. Every separate login means another set of credentials, another interface to train staff on, and another opportunity for product data to fall out of sync. Many vendors searching for how to add UPC to GXS catalog are doing so because they have just been told by a retailer that they need GXS catalog access before their first order can process.
AIMS360's built-in OpenText GXS integration eliminates the standalone login entirely. When you create or update a style in AIMS360 fashion management software — including its UPC codes, NRF color code, NRF size code, description, pricing, dimensions, and pack configuration — that data is pushed directly to the OpenText GXS Catalogue through an automated EDI 832 Price/Sales Catalog transaction. There is no CSV export to format, no web form to fill out on tradinggrid.gxs.com, and no third-party middleware to configure. The question of how to add products to GXS catalog becomes a non-issue — AIMS360 apparel software handles it every time you save a style.
This means your team manages one source of truth for product data. When a buyer at Nordstrom or Macy's pulls up your UPC in their system, the catalogue information matches what is in your ERP exactly — same dimensions, same pricing, same attribute codes. The integration supports unlimited catalogue uploads, so whether you are pushing 50 UPCs for a capsule collection or 5,000 GTINs for a full seasonal line, the process is the same.
For brands that have been logging into catalogue.gxs.com to manually register each item, switching to AIMS360 apparel ERP's direct connection typically saves hours per week and eliminates the data entry errors that lead to retailer chargebacks and compliance violations.
Before a fashion brand can ship a single unit to a GXS-connected retailer, every UPC must be registered in the GXS Catalogue with a complete set of required attributes. At minimum, the OpenText Active Catalogue requires seven core fields: Product ID Number, Product ID Description, GTIN (UPC), NRF Color Code, NRF Size Code, NRF Color Description, and NRF Size Description. Without all seven, the item cannot be loaded into the catalogue.
Many retailers add their own required attributes on top of the GXS minimums. For example, a retailer may also require published cost, MSRP, country of origin, fabric content, garment weight, and pack size before they will grant catalogue access or accept an EDI order. Managing these extended attributes manually — especially when each retailer has different requirements — is where standalone GXS catalog portals become a bottleneck for brands that lack apparel ERP systems with built-in catalogue connectivity.
AIMS360 software for the apparel industry maps its internal product fields directly to the OpenText GXS attribute structure. When you set up a style in AIMS360 with its full color-size matrix, the apparel ERP automatically generates the correct UPC type (UCC-12, EAN-13, or GTIN-14) and populates the required NRF codes, descriptions, and dimensional data. The system then submits the complete record to the GXS Catalogue via EDI 832, including any retailer-specific attributes needed for compliance. If a retailer updates their requirements, AIMS360 apparel software can push revised attribute data without re-entering anything from scratch.
This workflow ensures that every UPC is registered with GXS correctly the first time, reducing catalogue rejections and accelerating the retailer onboarding timeline.
What is an 832 electronic catalog? The EDI 832 — also known as the 832 Price/Sales Catalog — is the standard electronic document used to transmit detailed product information between vendors and their retail trading partners. The GXS Catalog is not just a static UPC registry — it is an active node in the EDI supply chain that receives and distributes product data via the 832 electronic catalog transaction set. When a vendor pushes an EDI 832 to the OpenText GXS Catalogue, the data becomes available to every retailer who has been granted access to that vendor's catalogue, enabling seamless downstream processing of purchase orders (EDI 850), invoices (EDI 810), advance ship notices (EDI 856), and price changes.
For apparel brands, the 832 price sales catalog carries particular weight because fashion products have complex attribute structures. A single style may have 8 colors and 7 sizes, producing 56 individual UPCs — each of which needs its own GTIN, NRF color codes, NRF size codes, pricing tier, and dimensional data in the catalogue. Multiply that across a seasonal line of 100+ styles, and manual catalogue management becomes impractical without dedicated apparel ERP software.
AIMS360 fashion management software generates EDI 832 documents directly from your product database using its in-house EDI engine — no third-party VAN or middleware is involved. The integration maps every style-color-size combination to the correct catalogue format automatically and handles both initial catalogue loads for new items and ongoing updates when you change a price, discontinue a colorway, or modify packaging dimensions. Because the 832 originates from the same apparel ERP that manages your orders, inventory, and shipping, the data in the GXS Catalogue is always in sync with what you are actually producing and fulfilling.
This end-to-end EDI automation is what separates an ERP-integrated catalogue workflow from the manual login-and-upload approach that many smaller brands still rely on.
Apparel companies evaluating GXS Catalog solutions typically have three options: use the standalone OpenText GXS web portal and manually key in data, connect a third-party EDI translator between their ERP and the catalogue, or choose apparel ERP systems that include the GXS Catalogue connection natively. AIMS360 apparel ERP is built for the third option.
One of the first questions brands ask is about GXS catalog pricing — does it cost to use GXS catalog, and what are the ongoing fees? The answer depends on your approach. Standalone GXS catalog access through OpenText typically involves account setup fees, per-user licensing, and in some cases per-transaction charges for EDI 832 submissions. Brands that use a third-party EDI translator add VAN (Value-Added Network) fees, kilocharacter fees, per-line fees, and per-document charges on top of that. With AIMS360 software for the apparel industry, the GXS Catalogue connection is part of the platform's in-house EDI engine — not routed through a third-party VAN or middleware. AIMS360 apparel ERP uses 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. The catalogue connection ships alongside the rest of your in-house EDI infrastructure: 850 purchase orders, 810 invoices, 856 ship notices, and all the other transaction sets your retail partners require.
This matters for growing fashion brands because the cost of standalone EDI solutions and separate OpenText GXS catalogue accounts adds up quickly, especially when you are onboarding multiple retailers with different compliance requirements. AIMS360 fashion management software consolidates everything — product information management (PIM), apparel PLM, UPC catalogue registration, EDI transaction processing, inventory, order management, and shipping — into a single apparel ERP. Your team logs into one system, manages one set of product data, and lets the platform handle the rest.
If you are currently using the GXS catalog login portal to register UPCs manually, or if a retailer has just told you that your UPC needs to be in the GXS Catalogue before they can process your first order, AIMS360 apparel software can get your product data into the catalogue faster and keep it accurate going forward.
The GXS Catalog — now called 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 other attributes for over 220 million items worldwide. Major retailers use the GXS Catalogue to validate vendor product data before processing EDI purchase orders, advance ship notices, and invoices. It is the industry-standard UPC catalog provider for apparel, footwear, accessories, 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. In 2014, OpenText Corporation acquired GXS and integrated its products — including the GXS Active Catalogue and Trading Grid — into the OpenText Business Network. Today, the platform is still commonly referred to as "GXS" in the apparel industry even though it officially operates under the OpenText brand.
There are several ways to add UPC codes to the GXS Catalog: manually through the OpenText Catalogue web browser interface at catalogue.gxs.com, via CSV template upload, through EDI 832 Price/Sales Catalog transactions, or through web services. With AIMS360 apparel ERP software, the process is automated — when you create a style with its full color-size-UPC matrix in the fashion management software, the system pushes the complete record to the GXS Catalogue via EDI 832 without any manual data entry or file formatting.
Adding products to the GXS Catalog requires at minimum seven attributes: Product ID Number, Product ID Description, GTIN (UPC), NRF Color Code, NRF Size Code, NRF Color Description, and NRF Size Description. Many retailers require additional attributes like published cost, MSRP, country of origin, and fabric content. Products can be loaded through the web interface, CSV upload, EDI 832, or direct API integration. AIMS360 apparel software handles this automatically by mapping its internal product fields to the GXS attribute structure and submitting everything via EDI 832.
The 832 electronic catalog — formally known as the EDI 832 Price/Sales Catalog — is a standardized electronic document used to transmit detailed product information from a vendor to their 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 — no third-party VAN or middleware required.
GXS Catalog pricing depends on your access method. Standalone access through OpenText typically involves account setup fees, per-user licensing, and may include per-transaction charges. Brands that use third-party EDI translators add VAN (Value-Added Network) fees, kilocharacter fees, per-line fees, and per-document charges. AIMS360 apparel ERP takes a different approach — EDI is built in-house, not routed through a third-party VAN. The GXS Catalogue connection is included in the platform 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 the number of users, transaction volume, and whether you are using the web portal, EDI, or API access. 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's 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 — eliminating the need to negotiate a separate OpenText catalogue contract or budget for variable EDI costs.
To get GXS Catalog access, you typically need to register for an OpenText Active Catalogue account, which involves contacting OpenText or your retailer's EDI onboarding team. Retailers who require GXS compliance will often 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 your onboarding team handles the account setup as part of your apparel ERP implementation.
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. 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 full official name for the product data registry commonly called the "GXS Catalog." It is a cloud-based platform operated by OpenText that supports over 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.
Both names refer to the same platform. GXS, Inc. originally built the Active Catalogue, and OpenText acquired GXS in 2014. Today, 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 the retailer's requirements, so brands selling to both domestic and EU-based retail partners can manage all their catalogue data from a single apparel ERP.
AIMS360's 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 your AIMS360 fashion management software.
