Product Taxonomy Comparison: ETIM vs UNSPSC vs Google Product Category

When a supplier feed lands with 4 000 line items and no shared taxonomy between your PIM, your buyer’s ERP, and the Google Shopping template, every team downstream pays the cost: buyers get mis-categorized listings, procurement reports roll up incorrectly, and the catalog team spends weeks manually patching codes that drift back out of alignment the next time the feed updates.

ETIM, UNSPSC, and Google Product Category are three of the most common ways to classify products, and they were designed for very different jobs. This product taxonomy comparison looks at each standard on its own terms: what it covers, how granular it is, who governs it, and where it fits in a real catalog operation. Most retail and marketplace teams end up needing more than one, because the taxonomy that wins a Google Shopping placement is rarely the same structure that procurement or a B2B buyer expects to filter on.

Claro keeps product and supplier data trusted as catalogs change. It resolves product identity across sources, enriches missing attributes, validates taxonomy assignments on each record update, and writes clean ETIM classes, UNSPSC codes, and Google Product Category values back into your existing PIM or ERP — so you do not have to re-classify from scratch every quarter.

At a glance

Before and after: unmanaged vs trusted taxonomy

When to use each standard

ETIM

Reach for ETIM when the product is defined by its specifications and buyers filter on them. A miniature circuit breaker, a contactor, a pump, or an HVAC unit is chosen on rated current, IP rating, physical dimensions, and connection type — not on a marketing label. ETIM pairs each class with a structured set of features and allowed values, which makes it the strongest fit for industrial distribution, electrical, and technical MRO catalogs where two products can look identical until you compare attributes side by side.

Because ETIM is attribute-first, it also feeds product comparison engines, configurators, and faceted search more cleanly than any spend-side taxonomy. The ETIM classification workflow describes how to assign classes at scale without losing the attribute linkage.

UNSPSC

UNSPSC shines on the buy side. Its four-level Segment to Commodity hierarchy lets procurement and finance roll spend up across categories as different as office supplies, lab equipment, and facilities goods. It has broad horizontal coverage but no attribute model, so it answers “what kind of thing is this, for purchasing” rather than “what are its specifications.” If your catalog feeds enterprise procurement systems or you report on category spend, UNSPSC is usually mandatory.

UNSPSC codes are also a common requirement in EDI integrations and supplier scorecards. For more background on the broader spend-management context, see what is GDSN.

Google Product Category

Google Product Category is the taxonomy of commerce discovery. It maps cleanly to consumer shopping intent and is required to surface many products correctly in Google Merchant Center and Shopping. For retail and marketplace sellers — including furniture, apparel, and consumer goods — the correct value directly affects whether a listing appears against the right query. It is intentionally shallow on technical detail, because shoppers browse by category and use case rather than by feature tables.

For feeds with a mix of consumer and industrial products, the validate Merchant Center feed playbook walks through how to catch mis-categorized entries before they cause feed rejection or impression loss.

How classification drift happens — and how to stop it

Every taxonomy releases updates. ETIM publishes major revisions that rename, merge, or retire classes. Google Product Category paths change as categories are split or reorganised. UNSPSC codes are updated quarterly. When those releases land, records that carried valid codes last month may now carry stale ones.

The damage compounds across systems: the PIM holds one code, the ERP holds another, and the feed template still references a path from two years ago. By the time a mis-categorized product surfaces in a procurement audit or a feed rejection report, the root cause is usually scattered across three spreadsheets and two onboarding imports.

Claro addresses this by treating taxonomy codes as attributes that must be validated on every record touch — not just on initial classification. When a supplier updates a spec or a new taxonomy release ships, Claro compares the current code against the updated standard, flags the drift, and writes the corrected value back into whichever system of record your team already uses. The classification drift guide covers the detection and remediation pattern in detail.

Related

FAQ

Can one product have an ETIM class, a UNSPSC code, and a Google category at the same time? +

Yes, and many do. Each code answers a different question for a different audience, so the same SKU can carry all three. The challenge is keeping them aligned as the product record changes, which is why teams attach them to one canonical record rather than maintaining separate spreadsheets or mapping files.

Is UNSPSC a replacement for ETIM? +

No. UNSPSC classifies for procurement and spend reporting and has no attribute model, while ETIM adds structured technical features per class. A distributor often needs UNSPSC for the buyer’s ERP and ETIM for on-site filtering and product comparison. They answer different questions for different audiences.

Which taxonomy do I need for Google Shopping? +

Google Product Category. It is the taxonomy Google Merchant Center expects, and using the correct value helps your products appear against the right shopping queries. ETIM and UNSPSC do not feed Shopping placement.

Does Google Product Category work for B2B or industrial products? +

Partially. It can categorize many industrial and MRO items, but it is shallow on technical attributes and not built for procurement. For B2B catalogs you will usually pair it with ETIM or UNSPSC rather than rely on it alone.

How do I map a product between these taxonomies? +

Start from a clean, attribute-complete product record, then map to each standard’s structure. Crosswalks are imperfect because the standards model products differently, so attribute-level data and a review step matter. A taxonomy mapping tool combined with human checks on low-confidence matches is the reliable path. Claro automates the initial mapping and flags records that need manual review.

What happens when taxonomy codes fall out of sync across systems? +

Classification drift. When a product is updated in one system but the taxonomy codes are not refreshed across PIM, ERP, and feed templates, buyers see mis-categorized products, procurement reports roll up incorrectly, and feed rejections increase. Claro detects drift as supplier records change and writes corrected codes back into your existing systems.