GS1 GPC, the Global Product Classification, is how many retailers and data pools classify products in the retail supply chain. If a retail partner asks for a GPC brick code on every item, you need one assigned, checked and held on each product record. Depending on your set-up, SKULaunch can hold GPC codes alongside your own taxonomy, assign them across your catalogue and export them where retail partners require them.
The problem
A retailer or data pool asks for a GPC brick code on every product, and your catalogue uses your own categories. Finding the right brick means navigating segments, families and classes for each product type, and the closest match is not always obvious. Doing it by hand for thousands of SKUs is slow, and inconsistent choices cause rejections.
It gets worse with ranges that cross categories. A household supplier might list cleaning products, food storage and small electricals in one file. Each needs a different brick, and a junior team member working from a spreadsheet will often pick the first plausible match and copy it down the column.
Before and after
An illustrative example from a household and grocery catalogue.
Before: your record
"Washing-up liquid, lemon, 500 ml", category Household > Cleaning. GPC: blank.
After: in SKULaunch
- GPC brick assigned for dishwashing detergents
- Held as a separate attribute alongside your own category
- GTIN, brand and net content confirmed on the record
- Exported in the retailer's template
How it works in SKULaunch
- Map categories to bricks. Where an end node maps to one GPC brick, set it once for every product in it.
- Classify the rest. Where a node spans several bricks, classify products individually using their title, description and attributes.
- Review. Check assignments in the grid, filtered by category or brick, before anything is sent.
- Export. Send GPC codes in the format your partners request.
How GS1 GPC is structured
GPC has four levels. The segment is the broadest, such as food and beverage or cleaning and hygiene products. Each segment splits into families, each family into classes, and each class into bricks. The brick is the level partners ask for. It groups products that serve the same purpose and are the same kind of thing, so all dishwashing detergents share a brick regardless of brand, scent or pack size.
Each level has its own numeric code, and the brick code is the one that goes in the template. Many bricks also carry brick attributes, which describe the product further with a fixed list of values, for example a form or a claim. Not every partner asks for them, but when they do, they follow the same logic as the brick itself: choose from the list, never type free text. GS1 publishes updated releases periodically, so bricks are added, retired and occasionally moved.
GS1 GPC mapping rules that hold up
- Classify what the product is. GPC groups by the nature of the product, not by where it sits in store or who buys it.
- Map at category level first. Most end nodes map to one brick. Do those once and save individual classification for mixed nodes.
- Separate the product from its accessories. A mop and a replacement mop head usually belong in different bricks.
- Do not use a generic brick to clear the backlog. Catch-all bricks exist, and partners notice when hundreds of items land in one.
- Keep the release on record. When a partner queries a code, you need to know which GPC release it came from.
- Fix identifiers at the same time. A brick on an item with an invalid GTIN still gets rejected.
GPC is not your website taxonomy
GPC is designed for supply chain consistency, not shopper navigation. Bricks group products by what they are, not how customers browse. Keep your own taxonomy for the website and hold GPC as a second classification on each product. That keeps retail partners happy without forcing your navigation into a structure built for data exchange. The same principle applies to UNSPSC codes for procurement customers and ETIM classification for technical ranges.
Common mistakes
- Copying one brick down a whole supplier file because the first product fitted.
- Matching on keywords, so a "lemon" cleaner lands near citrus fruit.
- Trusting supplier brick codes without checking them against the current release.
- Treating GPC as a replacement for your own categories and losing useful website navigation.
What changes
Retail partner requirements stop blocking listings, and GPC is maintained as part of normal product set-up rather than a scramble before each submission.
Common questions
What is a GPC brick?
The most specific level of GS1 GPC. A brick groups products of the same kind that serve the same purpose, and it is the code retailers and data pools usually ask for.
What is the difference between GS1 GPC and UNSPSC?
GPC classifies products for the retail supply chain. UNSPSC classifies spend for procurement. Some suppliers need both on the same product, held as separate attributes.
Do we need to change our categories?
No. GPC sits alongside your own taxonomy.
What about GTINs?
GTINs are held as identifiers on each product and can be checked for format and check digit. See how to validate GTINs and barcodes.
Which GPC release do you classify to?
The release your partners specify. Agree it up front, because bricks change between releases.
Is this available on every plan?
Standards mapping depends on your set-up. Confirm with us for your catalogue.
More on ETIM, BMEcat and GS1 data mapping, GTINs and other product identifiers, and classification standards.

.avif)