Three standards, three different jobs. ETIM classifies what the product IS, with typed attributes. UNSPSC classifies what budget bucket the purchase goes in. eClass does both, but mainly for German manufacturing supply chains. Most electrical distributors need two of the three.
The same contactor, three ways
Forget the abstract definitions. Look at what happens when you classify a single product in all three systems.
Take a 3-pole 25A AC power contactor. The kind you'd find in any motor control panel. Here's how each standard handles it:
Code and hierarchy path
| Standard | Code | Hierarchy path |
|---|---|---|
| ETIM | EC000066 | Electrical engineering → Low-voltage switch & control gear → Power contactor, AC switching |
| UNSPSC | 39121500 | Electrical Systems → Electrical components → Electrical controls and accessories |
| eClass | 27-37-10-03 | Electrical engineering → Low-voltage switchgear → Contactor → Power contactor, AC switching |
Typed attributes at the leaf node
| Standard | Attribute count | Examples |
|---|---|---|
| ETIM EC000066 | ~15 | Rated current, number of poles, coil voltage, rated operational voltage, AC/DC switching |
| UNSPSC 39121500 | 0 | None. The standard defines no attributes. |
| eClass 27-37-10-03 | ~12 | Rated current, number of poles, coil voltage (ISO-compliant data types) |
That zero in the UNSPSC row isn't a mistake. It's the point. UNSPSC is a procurement taxonomy, not a product description standard. It tells SAP Ariba which spend category your PO belongs to, which budget line gets charged, which approval workflow kicks in. What it doesn't tell anyone is what the contactor actually does.
Who requires what
Your trading partners don't all want the same thing.
| Trading partner type | Standard required | Why |
|---|---|---|
| Electrical distributor (NA/EU) | ETIM | Sonepar's product data guidelines list full ETIM classification as mandatory |
| Procurement system (SAP Ariba, Coupa) | UNSPSC | SAP Business Network only validates UNSPSC codes |
| German manufacturer / Industry 4.0 | eClass | Siemens uses eClass across development, purchasing, and sales |
The Sonepar requirement isn't a soft preference. Their January 2025 product data guidelines put ETIM classification in the same mandatory column as GTIN and product descriptions.
And ETIM isn't just a European thing anymore. ABB, Schneider Electric, Siemens, and Sonepar North America all joined ETIM NA. If you sell to any of them in the US or Canada, ETIM is what they're asking for.
The attribute depth gap
This is where the standards actually diverge in practice. UNSPSC stops at "Electrical controls and accessories." That's it. A buyer filtering for "25A, 3-pole, 400V" in a UNSPSC-only catalog gets nothing back.
| Standard | Leaf node | Typed attributes | Supports filtering? |
|---|---|---|---|
| ETIM EC000066 | Power contactor, AC switching | ~15 | Yes |
| UNSPSC 39121500 | Electrical controls and accessories | 0 | No |
| eClass 27-37-10-03 | Power contactor, AC switching | ~12 | Yes |
UNSPSC-only catalog
- Buyer searches "25A 3-pole contactor"
- No typed attributes exist at commodity code level
- Filter returns zero results
ETIM-classified catalog
- Same search runs against typed features
- Rated current = 25 A, poles = 3, switching type = AC all filterable
- Filter returns matched products instantly
UNSPSC serves a real purpose. It routes purchase orders to the right budget in procurement systems. But it was never designed to help someone find the right product. That's ETIM's job for electrical, and eClass's job for German industrial.
Where the standards overlap
ETIM covers about 6,000 product classes, all in electrotechnical, HVAC, and building products. Deep but narrow.
eClass covers roughly 45,000 classes across every industry. It goes broader, but the electrical coverage overlaps heavily with ETIM. A Siemens 3RT2028 contactor carries both codes: ETIM EC000066 and eClass 27-37-10-03. Same product, both classifications valid.
There's an official cooperation agreement between ETIM and eClass. Products classified in one can often map to the other without starting from scratch. If you've done the ETIM work, getting to eClass is a mapping exercise, not a re-classification project.
UNSPSC sits in a different universe. Roughly 56,000 commodity codes spanning every industry, but almost all are high-level groupings with no attribute schema attached. You can't map ETIM to UNSPSC in any meaningful way because UNSPSC doesn't have a destination for the attributes.
Which one do you actually need?
Your main trading partners are electrical distributors: ETIM. It's mandatory for Sonepar suppliers and expected by the major buying groups.
Your catalog feeds SAP Ariba or a procurement portal: UNSPSC. It's the only commodity code domain SAP Business Network validates.
Your customers include German manufacturers or Industry 4.0 platforms: eClass. Siemens, Bosch supply chains, and Asset Administration Shell integrations all expect it.
You need both distributor and German manufacturing coverage: ETIM first, then use the ETIM-eClass mapping for eClass output.
You're not sure who will ask: Start with ETIM. It's the mandatory ask from the largest electrical buying groups in North America and Europe.
These aren't three competing options you pick between like PIM vendors. They're three different answers to three different questions. ETIM tells your trading partner what the product does. UNSPSC tells their procurement system where to route the spend. eClass tells German manufacturing platforms how to integrate the product data into their supply chain.
Most electrical distributors end up maintaining two: ETIM for the catalog, UNSPSC for procurement. Add eClass only when a German manufacturing customer actually asks for it.