Home
/
Use cases
/
UNSPSC codes for every product in your catalogue
Use case

UNSPSC codes for every product in your catalogue

UNSPSC classification at scale gives every product a commodity code from data you already hold. Codes sit alongside your own taxonomy and export in your customers' templates.

Try it on your own data
UNSPSC codes for every product in your catalogue

UNSPSC classification means giving every product in your catalogue an eight-digit commodity code that procurement systems can read. Corporate buyers, public sector frameworks and eProcurement platforms use those codes to report spend, route approvals and find what they need, which is why so many procurement customers now ask for a UNSPSC code on every line. Depending on how your account is set up, SKULaunch can assign UNSPSC codes across your catalogue from the data you already hold and keep them on each product record.

The problem

A procurement customer sends a catalogue template with a UNSPSC column, and your data has no codes. Finding the right commodity for each product means searching a code set of tens of thousands of entries, and the obvious match is often one level too broad. Doing it by hand for a few thousand lines takes weeks. The person who does it rarely documents why each code was chosen, so the next customer request or the next code set update starts from scratch.

The cost of getting it wrong lands on the buyer. A code at the wrong level puts your products in the wrong spend bucket, and some eProcurement platforms reject lines that are not at commodity level. That turns into back and forth with the customer, and a catalogue that goes live late.

Before and after

An illustrative example from an MRO and office supplies catalogue.

Before: the line in your catalogue

NB-15-I5, 15.6 inch laptop, Core i5, 16GB RAM, 512GB SSD. UNSPSC: blank.

After: classified in SKULaunch

  • UNSPSC: 43211503, Notebook computers
  • Segment 43: Information technology, broadcasting and telecommunications
  • Family 4321: Computer equipment and accessories
  • Class 432115: Computers
  • Commodity 43211503: Notebook computers

How it works in SKULaunch

  1. Link your categories to UNSPSC. Where an end node in your taxonomy maps cleanly to one commodity, the mapping is set once and applied to every product in it.
  2. Classify product by product where needed. Where a node spans several commodities, products are classified individually using their title, description and attributes.
  3. Review before you send. Codes are written to a UNSPSC attribute on each product and reviewed in the grid alongside the rest of the record.
  4. Export in the customer's template. Send the catalogue with UNSPSC codes in the columns your procurement customers ask for.

How UNSPSC codes are structured

A UNSPSC code is eight digits in four pairs. The first two digits are the segment, the broadest grouping. The next two add the family, then the class, then the commodity, the most specific level and the one procurement teams usually want. So 43211503 reads as segment 43, family 21, class 15, commodity 03. The code set is maintained centrally and updated periodically, so a code that was right a few years ago may now have a more specific alternative. For the full background, see our explainer on what UNSPSC is.

UNSPSC classification at scale: the rules that keep codes defensible

Most catalogues split into two groups. The majority of products sit in categories that map to a single commodity, so one decision covers hundreds of lines. The rest sit in mixed categories and need classifying one by one. Working category first, then exceptions, is what turns weeks of searching into a few days of review. Whichever way the code is set, these rules keep it consistent:

  • Go to commodity level where one exists. Fall back to class only when no commodity fits. Never stop at segment or family.
  • Classify what the product is, not who buys it. A notebook bought by a hospital is still a notebook computer, not medical equipment.
  • Watch accessories and consumables. A laptop bag, a toner cartridge and a replacement blade each have their own commodities. Keyword matching on "laptop" or "printer" puts them in the wrong place.
  • Set one rule for kits and multipacks. Decide how bundles are classified, write it down and apply it everywhere.
  • Record the code set version. When a customer queries a code, you need to know which version it came from.
  • Check supplier codes before you trust them. Codes in supplier files are often old, too broad or copied across a whole range.

UNSPSC, ETIM and GS1 are not interchangeable

Each solves a different problem. UNSPSC answers "what kind of spend is this?" for procurement. ETIM describes technical products in detail with defined features and values. GS1 identifies items and, through GPC, classifies them for retail supply chains. Many distributors need all three on the same product for different customers. Holding them as separate attributes on one record, rather than choosing one, is what keeps every customer's template answerable. See ETIM classification and GS1 GPC mapping for the other two.

What changes

A UNSPSC column in a customer template stops being a project. Codes are set once, held on the product, reviewed like any other attribute and exported whenever a procurement customer asks.

Common questions

How do I find the right UNSPSC code for a product?

Start from the segment that matches what the product is, work down through family and class, and stop at the most specific commodity that fits. At scale, map whole categories first and classify only the mixed ones product by product.

Which UNSPSC version do you use?

The version your customers specify. If different customers want different versions, the code can be held per version.

Can we classify to UNSPSC without changing our own categories?

Yes. UNSPSC is held as an attribute on each product, alongside your own taxonomy.

What if a product does not fit any commodity well?

Classify to the most specific class that fits and note it for review. Forcing a wrong commodity causes more problems for the buyer than a correct class.

What is the difference between UNSPSC and a product taxonomy?

Your taxonomy is built for browsing and attributes. UNSPSC is built for spend reporting. Products that sit together on your website can carry different UNSPSC codes, and that is fine.

Is UNSPSC classification available on every plan?

Standards classification depends on your set-up. Confirm with us for your catalogue and the code set version your customers need.

More on product classification standards, automatic product categorisation, and data for industrial and MRO distributors.

See it working on your own product data

Upload a supplier file and watch SKULaunch turn it into complete, structured, sales-ready records. Two weeks free, no card, no consultants.

© 2026 SKULaunch Ltd. All rights reserved.
Built for e-commerce teams who are done doing it by hand.