Where to log in to the GXS Catalog, and how AIMS360 sends UPCs with NRF codes to the OpenText catalogue by EDI 832, with unlimited uploads per retailer.

AIMS360 apparel ERP sends your UPCs, NRF color codes and NRF size codes to the OpenText GXS Catalogue with an EDI 832 upload, from the same system that runs your orders, ASNs and invoices. No VAN fees and no per-document charges, just unlimited 832 uploads for one flat monthly fee per retailer. Built for fashion, beauty and cosmetic brands selling to Nordstrom, Macy's, Bloomingdale's, Saks, Dillard's, Kohl's, JCPenney, Burlington and other retailers that ask for catalogue registration.
GXS is now part of OpenText. Sign in to the catalogue at catalogue.gxs.com with your Network ID, User ID and password. OpenText Trading Grid Online is at tradinggrid.gxs.com. OpenText runs these accounts, so password resets and new catalogue accounts go through OpenText. Already on AIMS360? You keep that account for setup and retailer access, and send new UPCs from AIMS360.
Logged in and stuck? See how to grant a retailer access, add UPCs and prepacks, and fix rejected uploads.
The GXS Catalog is OpenText's product catalogue for retail suppliers, also called the OpenText Active Catalogue or Trading Grid Catalogue. Brands host their UPCs there, with NRF color and size codes, so retailers like Nordstrom, Macy's and Saks can look up the items on their EDI 850 purchase orders. You buy your catalogue account from OpenText and register your GS1 company prefix with them. After that, AIMS360 uploads your UPCs with an EDI 832 Price Sales Catalog, with no VAN fees and unlimited transactions for one flat monthly fee per retailer.
AIMS360 is the apparel ERP software with the OpenText GXS Catalogue upload built into the same platform that runs your purchase orders, advance ship notices, invoices, and inventory. Your team manages product data, UPCs, NRF codes and EDI in one system, instead of keying items into the catalogue's web screens and keeping a separate EDI translator in sync.
Your UPCs go from AIMS360 to the OpenText catalogue by EDI 832. You keep your OpenText account for setup and retailer access, and day-to-day item uploads run from AIMS360.
Set NRF size codes on the size scale and NRF color codes in AIMS360, and every UPC carries them into the 832. A UPC missing either code fails the upload, so review the export before you send it.
The GXS Catalogue upload is part of AIMS360's built-in EDI for apparel, built in house with no third-party VAN.
Every product attribute a retailer needs already lives inside your AIMS360 PIM. When you're ready to publish, you pick the catalogue, the UPC catalog group and the UPCs, and AIMS360 builds the EDI 832 and sends it. No CSV exports, no manual portal entry, no third-party VAN translator in the middle. Here's the path your product data takes from AIMS360 to the OpenText catalogue and back to the retailer's purchase order.
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 UPCs from your GS1 company prefix by style, color and size, and each UPC carries the NRF color and size codes set in AIMS360.
Pick the UPC catalog group, such as men's or women's, so retailers can find your items by group. Each 832 upload covers one group.
AIMS360's in-house EDI builds the 832 electronic catalog and sends it to the OpenText GXS Catalogue. No VAN, no middleware, no third-party translator.
The catalogue checks each GTIN and makes the product data available to the retailers you've given access to in your catalogue account.
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.
Add a new style or color, assign its UPCs, and send them in the next 832 upload from AIMS360. No one keys them into the catalogue's web screens.
There are three common ways to load the GXS Catalog: key items in by hand, add a third-party EDI translator to your current system, or use an apparel ERP with the catalogue upload built in. Here's how they compare on cost and day-to-day work.
| 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 | ✓ Set up during implementation |
| VAN fees | N/A, manual only | ✗ Per-transaction VAN fees | ✓ No VAN, in-house EDI |
| 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 needed | ✗ Yes, for every item | ✗ Yes, for setup and troubleshooting | ✓ Only for account setup and retailer access |
| Data sync with ERP | ✗ Manual, data drifts | ✗ Middleware mapping required | ✓ Built in, one source of truth |
| NRF code mapping | ✗ Manual lookup per item | Partial, depends on translator | ✓ Set once in AIMS360 |
| Catalogue rejection support | OpenText queue, open a ticket | Translator vendor + OpenText (two queues) | ✓ AIMS360 EDI support for upload errors |
| Connects to EDI 850 / 856 / 810 | ✗ Catalogue only | Yes, separate setup and cost | ✓ Same engine, same flat rate |
| Onboarding new retailers | Weeks per retailer | Days to weeks plus per-retailer fees | ✓ Flat monthly fee per retailer, unlimited transactions |
| All cost descriptions reflect typical industry pricing models as of 2026. Your catalogue account is with OpenText either way, and OpenText doesn't publish standard GXS Catalog pricing. Request an AIMS360 demo for a quote covering your retailers. | |||
The GXS Catalog is now OpenText Trading Grid Catalogue, and the screens you sign in to are called OpenText Active Catalogue. These are the tasks brands log in for most, taken from OpenText's own vendor guide and retailer instructions. OpenText updates its screens, so a label in your account can differ slightly.
Your account's administrator (OpenText calls this a super user) can add users and reset passwords. If nobody at your company has that role, contact OpenText Cloud Support Services.
Many retailer programs ask for Unrestricted access. Dick's Sporting Goods' catalogue FAQ, for example, asks vendors to grant it.
Active Catalogue calls a prepack a container GTIN, and the units inside it components. OpenText's rules:
To assign components, find the container GTIN, click the Component link in its Components column, click Add, and enter the component GTIN, GTIN type, quantity and unit of measure. New to prepacks? See case pack vs prepack vs bundle.
From AIMS360, the most common cause is a UPC missing its NRF color or size code, which fails the upload. Set the codes on the style and send it again.
Sources: OpenText Active Catalogue CE 21.2 Browser Interface User Guide for Vendors (OpenText, 2021), How to grant trading partner access (OpenText) and DSG GXS Active Catalogue Program FAQ (OpenText). Checked November 7, 2026.
The OpenText Active Catalogue sits at the center of the apparel EDI supply chain. The more you understand how it works, the more you get from connecting it to your apparel software. The four areas below, onboarding, support, PIM and the EDI flow after the catalogue, are where brands either save staff hours or lose them to manual catalogue work, retailer chargebacks and data drift. (For how the GXS Catalogue fits 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 access means contacting OpenText, registering for a catalogue account, registering your GS1 company prefix, setting up the catalogue login at catalogue.gxs.com, and granting your retailers permission to view your product data through their Account ID. The retailer may then check a test 832 load before approving you for live EDI orders.
With AIMS360, you still buy your catalogue from OpenText, register your GS1 company prefix with them and grant your retailers access in your catalogue account. AIMS360's team helps you set up your UPC catalog groups and send the first 832 upload. After that, your team sends new UPCs from AIMS360 instead of keying them into the catalogue.
When a GXS catalog upload fails, because of a rejected GTIN, a missing NRF code or a group mix-up, finding the right OpenText contact and waiting on a ticket can take a while. Meanwhile your retailer may be holding the purchase order, and late or wrong data can turn into retailer chargebacks.
Because the 832 upload runs from AIMS360's own EDI, an upload error is an AIMS360 support ticket. Support is free on every plan, and regular support averages under 2 hours to respond. The EDI team knows the retailer's map and the path your data takes from the style record to the catalogue. Questions about your OpenText account, billing or password still go to OpenText.
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, since 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 sends the right data to the GXS UPC Catalog, to B2B sales platforms, to Shopify and Shopify Plus, and to whichever other channels your brand runs. It also makes a GXS catalog transfer, moving your catalogue data from one company name or account to another during an acquisition or rebrand, 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 in the catalogue, a retailer can issue an EDI 850 purchase order against any GTIN in it. 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, using the same UPCs you sent in the 832. The EDI 810 invoice follows, drawing pricing and product data from the same record. The same workflow applies to retailers like Belk and Dick's Sporting Goods and to newer e-commerce-first partners.
This is why the GXS Catalog isn't a one-time setup. If your catalogue drifts from your ERP, say a new colorway that never got uploaded, the UPCs on a retailer's purchase order won't match what it can look up. Send a new 832 whenever you add styles or colors, so the catalogue stays matched to your style records. 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 fills the core fields from your style record, as long as each UPC has its NRF color and size codes.
| 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 |
These retailers commonly ask vendors to register UPCs in a catalogue before EDI orders start. Check your retailer's vendor guide for the catalogue it uses: AIMS360 can upload to the OpenText catalogue or to InterTrade's.
Beyond Yoga ran its operations on AIMS360 through its growth phase and was acquired by Levi Strauss & Co. for about $400 million in 2021. 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.
The questions fashion, beauty and cosmetic brands ask most about the OpenText GXS Catalogue and AIMS360.
The GXS Catalog, now run by OpenText as the Active Catalogue (also called Trading Grid Catalogue), is a hosted catalogue where suppliers keep their UPC codes, product descriptions, NRF color and size codes and other item data. Retailers use it to look up vendor items for EDI 850 purchase orders, EDI 856 advance ship notices and EDI 810 invoices. Apparel, footwear, accessories, beauty and general merchandise suppliers use it widely.
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.
You can add UPC codes to the GXS Catalog by hand in the catalogue's web screens at catalogue.gxs.com, by file upload, or with an EDI 832 Price Sales Catalog. With AIMS360, you assign UPCs on the style, pick the catalogue and UPC catalog group, tag the UPCs and export an EDI 832, which AIMS360 sends to the catalogue. No CSV formatting and no keying items into the web screens.
Each item needs at least 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 ask for more, like published cost, MSRP, country of origin, fabric content and pack size. You can load products through the web screens, a file upload or an EDI 832. AIMS360 sends the core fields from your style record in an EDI 832, as long as each UPC has its NRF color and size codes.
The 832 electronic catalog, formally the EDI 832 Price Sales Catalog, is a standard EDI document that sends product data from a vendor to its trading partners: UPC codes, descriptions, pricing, NRF color and size codes and other attributes. For the GXS Catalog, the 832 is the main way to load product data in bulk instead of typing it into the web screens. AIMS360 builds the 832 from your style records with its own in-house EDI, with no third-party VAN or middleware.
Yes. Your catalogue account is with OpenText, and OpenText sets that price. What changes is how you load it. A third-party EDI translator can add VAN, kilocharacter, per-line or per-document fees on each 832. With AIMS360, EDI is built in house and billed as a flat monthly fee per retailer with unlimited transactions, so the 832 uploads carry no VAN, kilocharacter, per-line or per-document fees.
OpenText doesn't publish standard GXS Catalog pricing. It depends on your account and how you connect, so ask OpenText for a quote on the catalogue itself. On the AIMS360 side, the catalogue upload is part of built-in EDI: a flat monthly fee per retailer with unlimited transactions and no VAN, kilocharacter, per-line or per-document fees.
Contact OpenText to set up a catalogue account and register your GS1 company prefix with them. Retailers that use the catalogue give you their Account ID so you can grant them access to your product data, and some run a test load before live EDI orders start. If you run AIMS360, its team helps you set up your UPC catalog groups and send the first 832 upload.
The GXS Catalog login is at catalogue.gxs.com, where you sign in with your Network ID, User ID and password. OpenText Trading Grid Online is at tradinggrid.gxs.com. OpenText runs both, so password resets and new accounts go through OpenText. On AIMS360 you still keep this login for account settings and retailer access, but new UPCs go up from AIMS360 by EDI 832 instead of being keyed in.
NRF (National Retail Federation) color and size codes are standard numeric codes for garment colors and sizes. The GXS Catalog requires them for every GTIN: NRF Color Code, NRF Color Description, NRF Size Code and NRF Size Description. In AIMS360 you set them once, with NRF size codes on the size scale, and every UPC carries them into the 832. A UPC missing either code fails the upload.
The GXS Active Catalogue is the full name of what most people call the GXS Catalog. OpenText runs it today and also calls it Trading Grid Catalogue. Suppliers update it by EDI 832, the web screens or file upload, and retailers read from it, so it works as a live exchange rather than a static list.
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.
The OpenText catalogue takes GTIN-12 UPCs used in the U.S. and EAN-13 codes used in Europe. AIMS360 assigns GTIN-12 UPCs by default, so talk to our team about EAN-13 setup if your European retailers need it.
Yes, for the uploads. AIMS360's support team helps with upload errors on data sent from AIMS360, like a UPC missing an NRF code or a catalog group mix-up, and support is free on every plan. Questions about your OpenText account, billing or password go to OpenText.
Retailers that commonly ask vendors to register UPCs in a catalogue 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, Academy Sports, REI, Bass Pro Shops and Dick's Sporting Goods. Each retailer's vendor guide names the catalogue it uses and any extra fields it wants.
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 better setup 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.
Log in at catalogue.gxs.com and click Administration, then Trading Partner Access. Filter by the retailer's name, choose an access type (Unrestricted for your whole catalogue, or Selection Code or Product for part of it) and click Apply. Many retailer programs, such as Dick's Sporting Goods, ask for Unrestricted access.
In OpenText Active Catalogue a prepack is a container GTIN and its units are components. Add the prepack UPC as a container and save it, then open its Components link, click Add and enter each component GTIN with its type, quantity and unit of measure. A container can hold up to 100 components.
There are three kinds of errors. An EDI validation error means the 832 broke EDI standards; fix it and resend it with a new control number. A translation error sends that group to Error Processing to fix and resend. A data validation error means an item failed a business rule; correct it in Data Management, Error Processing and resubmit. From AIMS360, the usual cause is a UPC missing its NRF color or size code.
See how AIMS360 sends UPCs to the OpenText catalogue by EDI 832, next to the orders, ASNs and invoices for Nordstrom, Macy's, Bloomingdale's, Saks and 350+ more retailers.
AIMS360 · apparel ERP & EDI · 10,000+ brands · 40+ years · $45B+ processed