ETIM and ECLASS both classify products and describe them with standardized features, but they are built for different buyers. ETIM, run by ETIM International, is a classification for technical products used across the electrical, installation and building trades: a flat list of classes, each with its own technical features, free to use. ECLASS, run by the association ECLASS e.V., is a cross-industry standard with a four-level, eight-digit hierarchy and properties identified by IRDIs, used in industrial purchasing and engineering, and licensed for a fee.
UNSPSC, the third name in most of these comparisons, is a procurement code list with no product features at all. Which one you need is decided by who receives your product data, and plenty of manufacturers deliver two. The standard-by-standard background sits in the ETIM, ECLASS and UNSPSC guides; this post puts them side by side and follows one product through all three.
One miniature circuit breaker, three codes
The fastest way to see the difference is to classify the same product in each system. A miniature circuit breaker (MCB) for a distribution board lands in these places in ETIM 10.0, ECLASS 16.0 and the UNSPSC code set UNDP offers for download:
A miniature circuit breaker in ETIM 10.0, ECLASS 16.0 and UNSPSC
| ETIM 10.0 | EC000042 | Group EG000020 Circuit breakers and fuses > class Miniature circuit breaker (MCB) | 27 technical features, e.g. EF000227 Rated current, EF000889 Release characteristic |
|---|---|---|---|
| ECLASS 16.0 Basic | 27-14-19-01 (IRDI 0173-1#01-AAB905#022) | 27 Electric engineering, automation, process control engineering > 27-14 Electrical installation, device > 27-14-19 Miniature circuit breaker system (MCB) > 27-14-19-01 Miniature circuit breaker (MCB) | Technical properties plus identification and trade properties such as GTIN, manufacturer name, HS code and supplier article number |
| UNSPSC UNv260801 | 39121603 | 39000000 Electrical Systems and Lighting and Components and Accessories and Supplies > 39120000 Electrical equipment and components and supplies > 39121600 Circuit protection devices and accessories > 39121603 Miniature circuit breakers | Nothing: a code and a title |
The ECLASS row is taken from the free ECLASS content search for 27-14-19-01, the ETIM row from the official ETIM 10.0 release file and the UNSPSC row from the code set that UNDP publishes for free download. Note what each code is for. An installer filtering for a 16 A, C-characteristic breaker needs the ETIM or ECLASS features; a purchasing team adding up what it spent on circuit protection last year only needs 39121603.
ETIM vs ECLASS vs UNSPSC on twelve points
ETIM, ECLASS and UNSPSC compared
| Governed by | ETIM International with national ETIM organizations | ECLASS e.V., a membership association | UNDP (owner) |
|---|---|---|---|
| Scope | Technical products: electrical, HVAC and plumbing, and other technical sectors | Products and services across industries | Products and services, for procurement |
| Levels | 2 (group, class); groups only order the classes | 4 (segment, main group, group, commodity class) | Segment, family, class, commodity; UNDP describes the code set as five levels |
| Code format | EC000042 (class), EF, EV, EU, EG codes | 27-14-19-01 plus IRDI such as 0173-1#01-AAB905#022 | Eight digits, e.g. 39121603 |
| Product description | Features per class: alphanumeric, logical, numeric, range | Properties per class; Basic flat, Advanced with blocks and aspects | None |
| Size | 5,640 classes in 159 groups, counted in the official ETIM 10.0 all-sectors release file | About 48,000 product classes, 23,000+ properties | Not compared here |
| Licence | Free, Open Data Commons Attribution | Paid licence or membership; free search to browse | Free download |
| Release rhythm | Official release about every 3 years, plus dynamic releases | New release every year | Versioned code sets (e.g. UNv260801) |
| Release used in this post | ETIM 10.0 (December 2024), the current official release | ECLASS 16.0 (28 November 2025); 17.0 is scheduled for the end of November 2026 | UNv260801 in the UNDP download |
| Languages | ETIM English plus national translations, some member-only | All available languages included in the licence | English download on the UNDP page |
| Typical receivers | Technical wholesalers and their data pools | Industrial buyers, e-procurement, engineering tools | Procurement and spend analysis |
| Common carrier | ETIM BMEcat, ETIM xChange, national formats | BMEcat and other e-business formats | A field in a catalog or ERP |
Who decides what goes into each standard
ETIM is governed by ETIM International, seated in Margraten in the Netherlands, with national ETIM organizations from Austria to North America. New and changed classes come from expert groups of manufacturers and wholesalers, and a standardization committee votes them in. That origin shows in the content: the classes and features are the ones a wholesaler's customer filters on.
ECLASS e.V. works the same way at a larger scale. Its expert groups span industries from automation to office supplies, and the ECLASS 16.0 release incorporated over 155,000 change requests. UNSPSC is owned by the United Nations Development Programme, which publishes the code set.
Flat ETIM classes against the ECLASS four-level tree
ETIM is deliberately flat. Groups exist only to keep classes manageable; the work happens in the class and its features. Each class has an ordered list of features of four types (alphanumeric with a value list, logical, numeric, range), and the unit or value list of a feature is set per class. You classify a product by giving it one class, never a group.
ECLASS is a tree with four levels of two digits each, so the code itself tells you the segment, main group and group. Properties hang on the commodity class. ECLASS ships each release in two variants, as ECLASS describes them: Basic with a simple, flat property structure, often used in purchasing, sales and controlling, and Advanced with blocks, aspects, cardinality and polymorphism, mainly used in engineering and CAx tools. Both variants are included in a licence.
UNSPSC has the same kind of tree (segment, family, class, commodity, two digits each), but it stops at the code. There are no features to fill. If you are deciding between classification and ontology-style models more broadly, taxonomy vs ontology covers that distinction.
What ETIM, ECLASS and UNSPSC cost to use
ETIM's model and ETIM English are published under the Open Data Commons Attribution licence: free to use and redistribute with attribution, per ETIM's licence information. Some translations are open too (Belgian Dutch, Belgian French, Finnish, Italian, Norwegian). Others, including Netherlands Dutch and German, are maintained by national ETIM organizations and need a national membership.
ECLASS can be browsed for free, but using it requires a licence or membership in ECLASS e.V. Under its licence models, a Single License covers one release without time limit and a Concordance License works as a subscription to all past and future releases during its term. Fees depend on company size, and members use all licences without extra cost. UNSPSC is free: UNDP lets anyone browse and download the current code set.
Which customers ask for which standard
Start from the receiving side, because nobody gets to choose a classification in isolation:
- Electrical, installation and HVAC wholesale. ETIM is the working language of technical wholesalers and their data pools in the countries with an ETIM organization, including the Netherlands, Belgium and Germany. A manufacturer delivering there classifies in ETIM.
- Industrial buyers and e-procurement. ECLASS is common where purchasing departments and procurement platforms ask for classified electronic catalogs, and ECLASS says companies increasingly make it mandatory for their business partners.
- Engineering and automation. ECLASS Advanced feeds engineering and CAx tools and the Asset Administration Shell, which ETIM's basic model does not aim to cover.
- Spend analysis. Procurement teams that group spend across all suppliers ask for UNSPSC codes, often next to whatever technical standard the product data uses.
Mapping ETIM classes to ECLASS and carrying both
The two standards are not competitors on paper. ETIM and ECLASS started harmonizing in 2001, mapped all electro-technical ETIM classes to ECLASS, and widened that cooperation to an international scope in April 2019, according to ETIM's collaborations page. The effect is visible in the content: ECLASS 16.0 lists new classes "due to the ETIM Harmonisation", such as 27-21-07-17 Immersion thermostat.
In practice, a manufacturer that sells to both technical wholesale and industry keeps one set of technical values and publishes it twice. A working setup looks like this:
- Pick a lead standard per product family. For an installation product line that is usually ETIM, because that is where the wholesaler's checks run.
- Store the second code per family, not per product. One ECLASS commodity class per ETIM class covers most families; split where the mapping is not one to one.
- Map features to properties once per class. EF000227 Rated current and the ECLASS property rated current describe the same fact; the mapping is a table you maintain, not work you redo per article. The table below shows what that table looks like for one class.
- Translate value lists and units explicitly. ETIM uses EV and EU codes, ECLASS its own value and unit identifiers. A value that has no counterpart is a gap, not a guess.
- Keep identifiers outside both. GTIN, manufacturer and supplier article number belong in your item master. ECLASS has properties for them; ETIM leaves them to the exchange format.
Most of the mapping work hides in the details of single features. Here is the MCB class from the first table, feature by feature, against the properties ECLASS 16.0 Basic lists for 27-14-19-01. ETIM codes come from the ETIM 10.0 release file, ECLASS names and IRDIs from the ECLASS content search.
Seven EC000042 features mapped to ECLASS 16.0 Basic properties
| EF000227 Rated current | N, unit EU570459 (A) | rated current (A) | 0173-1#02-AAF726#006 | One to one |
|---|---|---|---|---|
| EF000889 Release characteristic | A, e.g. EV000084 (C) | release characteristic (value list) | 0173-1#02-AAG457#011 | One to one, values mapped per EV code |
| EF008618 Number of poles (total) | N, no unit | Pole number | 0173-1#02-AAT080#004 | One to one |
| EF005548 Number of protected poles | N, no unit | number of protected poles | 0173-1#02-AAG460#003 | One to one |
| EF007517 Flush-mounted installation | L | suitable for flush-mounted installation | 0173-1#02-AAL647#006 | One to one, yes/no |
| EF007515 Ambient temperature during operating | R, unit EU570073 (°C) | min. and max. ambient temperature during operation (°C) | 0173-1#02-AAC022#009 and 0173-1#02-AAB906#009 | One range to two properties |
| EF009555, EF009556, EF009557, EF009558 (Icn per EN 60898 and Icu per IEC 60947-2, at 230 V and 400 V) | N, unit EU570170 (kA) | rated short-circuit breaking capacity at 400 V (kA) | 0173-1#02-ABF012#004 | Four to one: decide which value feeds it |
The last two rows are where carried data goes wrong. The range has to be split into its lower and upper limit on the way out, and joined again on the way in. For breaking capacity, the ETIM class separates the EN 60898 and IEC 60947-2 values at two voltages, while this ECLASS Basic class lists a single property at 400 V. Read the property definition, decide once which ETIM feature feeds it, and write that rule into the mapping table, so nobody picks a different value per article.
How one product record carries both codes
Store the technical values once, in your own attributes: a number with its unit, a value from your own list, a lower and an upper limit. Next to them, per product family, keep the ETIM class with its release (EC000042, ETIM-10.0) and the ECLASS class with its IRDI and release (27-14-19-01, 0173-1#01-AAB905#022, ECLASS-16.0). Both exports are then generated from the same values through the mapping table, and a corrected value reaches both standards at once.
BMEcat 2005 can carry both in one file. The ECLASS BMEcat 2005 guideline states that an ARTICLE can have many ARTICLE_FEATURES elements, each referring to a different classification system. One block carries REFERENCE_FEATURE_SYSTEM_NAME ETIM-10.0 with group ID EC000042 and EF codes; a second carries ECLASS-16.0 with the eight-digit class 27141901, properties referenced by IRDI (FT_IDREF) and coded values by VALUE_IDREF. Ask the receiver whether it accepts both blocks in one file before you send one.
A UNSPSC code, if a customer asks for one, is a single extra field per family. Because it carries no features, it never changes how you describe the product. The same reasoning applies to any code list you add: treat it as maintained reference data with an owner and a version.
Three places where an ETIM to ECLASS mapping drifts
A mapping table that was right on the day you built it does not stay right. These are the three spots to recheck:
- Release rhythm. ECLASS publishes every year and ETIM roughly every three years, plus dynamic releases. Recheck the mapping at every new ECLASS release, not only at an ETIM one. ECLASS ships machine-readable update files (TUF and CUF) with each release for migrating classified data, which tell you which of your classes changed.
- Names and catch-all classes. Match on synonyms and definitions, not on names. ETIM calls EC000271 "Miniature circuit breaker (MCB) plug model" and lists "screw-in model" as a synonym; ECLASS 16.0 calls the matching class 27-14-19-04 "Miniature circuit breaker (MCB) screw-in model". ECLASS groups also carry catch-all classes such as 27-14-19-90 (unspecified), -91 (parts) and -92 (accessories); do not map a specific product there when a specific class exists.
- Values and units. A feature can match while its value list does not. If ETIM offers release characteristics that the ECLASS property lacks, or the other way round, those articles need a decision per value, documented once in the mapping table.
Key the mapping table on both releases, for example ETIM-10.0 to ECLASS-16.0, and keep the IRDI version in every row. When a new release changes the version suffix of a class or property IRDI, that row goes back to review instead of being carried forward silently. Rows with no counterpart get an explicit status such as "no ECLASS property", so an empty cell never hides an unfinished decision.
Five questions to ask a customer before you classify
Most rework in classified data starts with an assumption about what the receiver wants. Ask these five before the first file goes out, and write the answers into your delivery spec:
- Which standard and which release? ETIM-10.0 or a dynamic ETIM release; for ECLASS, the latest release or an older one the customer has not migrated from. ECLASS has scheduled 17.0 for the end of November 2026, and customers rarely migrate on day one.
- Basic or Advanced, if ECLASS? A purchasing system usually wants Basic; an engineering tool may want Advanced structures.
- Which language for labels? Codes are language-independent, but a customer may still expect labels, and some ETIM languages need a national membership.
- Which exchange format? ETIM BMEcat, ETIM xChange, a national format, or a spreadsheet template with code columns.
- Which features are mandatory for listing? Receivers often require a subset of a class's features before an article goes live. That subset, not the full class, is your minimum.
ETIM and GS1 GPC in WISEPIM, without ECLASS or UNSPSC
WISEPIM supports two classification standards, ETIM and GS1 GPC. It does not support ECLASS or UNSPSC. For ETIM, the optional Classification module loads ETIM 10.0: you adopt ETIM classes per product family, map your own attributes to ETIM features in Mapping review, check each product's ETIM Conformance and export a BMEcat 2005 (ETIM) file from Feed Hub. The step-by-step method for a supplier file is in ETIM classification, and the screens are on the product classification feature page. When a BMEcat file with ECLASS feature blocks is imported, those blocks are skipped, and WISEPIM does not export ECLASS or UNSPSC codes.
For food and consumer goods, which ETIM does not cover, the same module has a GS1 GPC tab that turns GPC bricks into categories; the GS1 GPC guide explains that standard.

