UNSPSC Codes Explained: Structure, Examples and When Buyers Ask

UNSPSC codes are eight-digit numbers that say what kind of product or service something is. They form a four-level hierarchy owned by the United Nations Development Programme (UNDP). Procurement and finance systems ask for them so a buyer can see spend on, say, lithium batteries across four ERPs and eleven countries. A UNSPSC code carries a category and nothing else: no attributes, no units, no identifiers.

That narrow purpose explains almost everything that frustrates suppliers. UNSPSC was built for spend analysis, not merchandising. A code that is fine for reporting a purchase order can be useless for driving a filterable catalogue.

What UNSPSC stands for and who runs it

UNSPSC is the United Nations Standard Products and Services Code. According to the FAQ on unspsc.org, it was developed jointly by UNDP and Dun and Bradstreet in 1998. GS1's member organisation for the United States managed it from 2003. The same FAQ states that management would transition back to UNDP by the end of 2024. UNDP's own UNSPSC page now describes the code as owned by UNDP and offers the current version to browse and download at no cost.

Two practical points follow. The current code set comes as a spreadsheet download, not a versioned data service. And neither UNDP's page nor unspsc.org publishes a release calendar. Treat any date you are given for the next version as unconfirmed.

How UNSPSC codes are structured

Every code is eight digits read as four pairs. Each pair is one level of the hierarchy:

• Segment (digits 1 and 2): the broadest grouping.
• Family (digits 3 and 4): a recognised group within the segment.
• Class (digits 5 and 6): items sharing a common use or function.
• Commodity (digits 7 and 8): a single product or service type.

Zeros mark an unused level. A code ending 000000 is a segment, 0000 a family and 00 a class. There is also an optional fifth pair, the business function, which unspsc.org describes as rounding out a ten-digit code. Its own example is 4410210510, "(Lease or Rental of) Addressing Machines", built on the commodity 44102105. Few systems use it. If a trading partner asks for ten digits, confirm they really want the business function rather than a padded eight-digit code.

UNSPSC code examples, level by level

These three codes were checked against the UN Global Marketplace (UNGM). It is the UN system's procurement portal, and it publishes UNSPSC titles on its tender notices.

Docking stations

• 43000000 Information Technology Broadcasting and Telecommunications (segment)
• 43210000 Computer Equipment and Accessories (family)
• 43211600 Computer accessories (class)
• 43211602 Docking stations (commodity)

Lithium batteries

• 26000000 Power Generation and Distribution Machinery and Accessories (segment)
• 26110000 Batteries and generators and kinetic power transmission (family)
• 26111700 Batteries and cells and accessories (class)
• 26111711 Lithium batteries (commodity)

Circuit protection

• 39000000 Electrical Systems and Lighting and Components and Accessories and Supplies (segment)
• 39120000 Electrical equipment and components and supplies (family)
• 39121600 Circuit protection devices and accessories (class)

Look at what is missing. Nothing in 26111711 tells you the chemistry, voltage, capacity or cell format. A buyer can report spend on lithium batteries. A buyer cannot filter for an 18650 cell at 3.7 volts. The same goes for a 16 A type B miniature circuit breaker sitting in class 39121600: the code says circuit protection, not rating or curve. unspsc.org says it plainly: the schema does not normally consider specific product attributes such as size, colour or performance, or application.

What UNSPSC codes do not do

Suppliers asked for UNSPSC codes often assume they are being asked for product data. They are not.

• No attributes. No feature list, value list or units. ETIM and ECLASS attach typed features to a class; UNSPSC does not.
• No identifiers. The unspsc.org FAQ is explicit: GTINs identify trade items, UNSPSC classifies commodities, and UNSPSC is not marked on products. A code sits alongside a GTIN; it never replaces one.
• No file format. UNSPSC is a code list. It travels inside whatever you already send: a catalogue upload, a punchout catalogue, a spreadsheet column.
• No validation beyond existence. A code is in the published set or it is not. Nothing will tell you a docking station has been filed under batteries.

When buyers and procurement systems ask for UNSPSC codes

Requests usually come from one of three places:

• Procurement suites. SAP Ariba static catalogues are a common example. Buyer guides for Ariba catalogue uploads list the SPSC code as a required field and state that commodity codes must be assigned to every item.
• Business marketplaces. Amazon Business publishes a downloadable file of the UNSPSC codes it supports.
• Sector catalogues. GS1 New Zealand states that Australian and New Zealand healthcare data recipients require UNSPSC at commodity level in the National Product Catalogue.

Public sector frameworks and large corporate buyers ask for the same reason. They run spend analysis across many suppliers, and UNSPSC is the shared category key. If you supply a local authority and a German electrical wholesaler, expect UNSPSC from the first and ETIM from the second.

UNSPSC vs ETIM, ECLASS and GPC

These classifications were built for different jobs. A distributor selling into procurement and trade channels often carries more than one:

• UNSPSC. Procurement and spend analysis. Eight digits, four levels, no attributes. Free to download from UNDP.
• ETIM. Technical products in electrical, HVAC and plumbing, building materials, tools and shipbuilding. Each class carries typed features, values and units, which is what makes filterable catalogues possible. A 16 A MCB is ETIM class EC000042 with 47 features attached.
• ECLASS (often written eCl@ss). A reference data standard for classifying and describing products and services. ECLASS describes itself as a four-level hierarchy identified by an eight-digit code, with properties attached to each class.
• GPC. GS1's Global Product Classification. A four-tier hierarchy of segment, family, class and brick, where each brick carries attributes with set values.

The common mistake is picking one and hoping it serves every audience. UNSPSC and ETIM do not derive cleanly from each other: UNSPSC groups by what procurement reports on, ETIM by technical characteristics. Holding both against the same product record is the practical answer, and it is why standards mapping software exists.

Four problems practitioners hit with UNSPSC codes

It classifies by what a thing is, not how it is used

UNSPSC does not normally consider application. A stainless steel bolt is a bolt whether it ends up in a food line or a wind turbine. Spend analysts often want the opposite, because budgets are organised by use. So a category manager asks for a use-case code, the supplier sends an object code, and both think the other has made a mistake. Agree which reading applies before you map 50,000 SKUs.

Depth is uneven across segments

IT and electrical segments go deep, with dozens of commodities per class. Other areas are thin. Depth reflects what procurement historically needed to report on, not what a merchandiser needs to filter on. Check the depth in your own segments before adopting UNSPSC as a browsing taxonomy.

The published set contains duplicates

Codes 43221734 and 43221740 both carry the title "Satellite Communications Equipment" in the list UNGM publishes. Two suppliers can classify the same item correctly and differently, and the buyer's spend report splits in two. Buyers should publish their preferred code; suppliers should ask which one the customer uses.

Version drift breaks spend history

Codes are added, retitled and deprecated between versions, and nothing in the code tells you which version it came from. Store the version alongside the code on every product record, the same way you would store an ETIM release alongside a class. When you upgrade, keep the old code in a second field for at least one reporting cycle.

Class level or commodity level?

Many implementations classify to class level and pad with zeros, so 43211602 becomes 43211600. It is a reasonable trade-off. Commodity-level classification of a large catalogue costs more, and class level is often enough for spend reporting. Some recipients insist on commodity level, as the healthcare catalogues above do, so check before you decide.

Whatever you choose, be consistent. A field that mixes class-level and commodity-level codes produces a report where the same category appears twice, and the totals stop adding up.

How to add UNSPSC codes to a catalogue

1. Settle the version. Download the current code set, record its version, and store that version next to every code. Decide class or commodity level and write it down.

2. Classify categories, not products. If you have an internal product taxonomy, map each category to UNSPSC once and inherit the code down. Mapping 400 categories is a week of work. Mapping 50,000 products one at a time is not.

3. Handle exceptions individually. Mixed categories, kits, assortments and private label will not inherit cleanly and need a product-level decision.

4. Validate on every export. The only automatic check is whether the code exists in the version you claim. A deprecated code passes a format check and fails at the buyer's end.

Steps two and three are where software helps. Choosing from a fixed code list, using a category name, product descriptions and sample specifications, is a task a classification model handles well. SKULaunch suggests UNSPSC codes for every product from the same source data it uses for ETIM and a customer's own taxonomy. Each suggestion carries a confidence score for review rather than a silent overwrite. The results go out through standards-based feeds alongside the attributes each receiving system needs.

UNSPSC FAQs

What are UNSPSC codes?

UNSPSC codes are eight-digit classification codes from the United Nations Standard Products and Services Code, owned by UNDP. Each code has four two-digit levels: segment, family, class and commodity. Procurement and finance systems use them to group purchases for spend analysis. A code says what type of product or service an item is, but carries no attributes, units or product identifiers.

How do I find the UNSPSC code for a product?

Download or browse the current code set from UNDP's UNSPSC page, which offers it at no cost. Start at the segment that fits and drill down through family and class. Choose the commodity that describes what the item is, not what it is used for. If several commodities overlap, ask your customer which code their system expects.

Is UNSPSC free to use?

Yes. UNDP's UNSPSC page states that the current version can be browsed and downloaded at no cost. The unspsc.org FAQ adds that use of the codes is free. That makes UNSPSC unusual among classification standards, with no membership or per-user licence between you and the codes. Change requests and older versions may involve a subscription, so check the current terms with UNDP.

What is the difference between UNSPSC and ETIM?

UNSPSC is a procurement classification: one eight-digit code per item, used to report spend, with no attributes. ETIM is a technical classification for products such as electrical and plumbing goods. Each ETIM class carries a defined list of features, values and units, so products can be compared and filtered. Many distributors need both on the same record.

How many digits is a UNSPSC code?

A standard UNSPSC code is eight digits, made of four two-digit pairs for segment, family, class and commodity. Higher levels are written with trailing zeros, so 43210000 is a family code. An optional fifth pair, the business function, extends the code to ten digits to show whether an item is, for example, leased or rented. Most systems use eight digits.

Who asks suppliers for UNSPSC codes?

Mostly procurement teams. Buyers using catalogue tools such as SAP Ariba often require a commodity code on every item. Public sector and large corporate buyers use UNSPSC for spend reporting, and some sector catalogues, such as Australian and New Zealand healthcare, require commodity-level codes. Technical wholesalers are more likely to ask for ETIM.

Key takeaways

• UNSPSC codes are eight-digit, four-level procurement classifications owned by UNDP and free to download.
• A code carries a category and nothing else. No attributes, units, identifiers or file format.
• Classify by what the item is, not what it is used for, and agree that reading with the buyer first.
• Store the version beside every code and never mix class-level and commodity-level codes in one field.
• Map your own categories to UNSPSC once, then handle kits, assortments and mixed categories by hand.
• If you also sell into technical channels you need ETIM classification as well, held in parallel on the same product record.

See it in practice: UNSPSC codes for every product in your catalogue, ETIM classification alongside UNSPSC and reclassify a catalogue into a new taxonomy.