UNSPSC vs eCl@ss: when your ERP and reporting disagree

Quick answer: UNSPSC and eCl@ss are not competing versions of the same idea. UNSPSC classifies what was bought for spend analysis and category management, common in US and UK reporting structures. eCl@ss classifies technical attributes at the material master level, the standard requested across DACH manufacturing and engineering supply chains. Most companies operating across both worlds do not choose one. They map between the two, because their ERP was built for one and their reporting is expected in the other.

On this page: Two standards answering two different questions · Where each one actually gets used · The conflict is in your ERP · How to pick when you cannot avoid both · FAQ

Two standards answering two different questions

If we plan an important business trip, we do not book the flight and the hotel from the same checklist. Both matter, both need to happen, but they answer different questions and fail in different ways if we mix them up. UNSPSC and eCl@ss have the same relationship. UNSPSC answers what category of spend a purchase falls into: segment, family, class, commodity, four levels deep, built for totaling and comparing spend across a business. eCl@ss answers what a specific item actually is, technically: its attributes, its properties, the specifications an engineer or a procurement system needs to match one part against another.

Neither standard is a weaker or incomplete version of the other. A company using UNSPSC alone can tell you, accurately, how much was spent on pumps last year. It cannot tell you, from the classification alone, the flow rate or the seal type of a specific pump. eCl@ss can tell you the seal type. It was not built to give you a clean, board level total across every category the business buys.

Where each one actually gets used

UNSPSC shows up wherever the requirement is spend visibility rather than engineering precision: US corporate procurement systems, UK public and private sector reporting, and the majority of category management structures we see in hard FM, cleaning, and construction. The reason is straightforward. Those sectors need to answer "how much did we spend on this category" more often than they need to answer "what are this item's technical properties," and UNSPSC is built for the first question.

eCl@ss is the usual ask in DACH region industrial, automation, and engineering supply chains, and it shows up specifically at the material master level, the record that describes a single part or component with enough technical detail that an engineer can specify it without ambiguity. A German manufacturing client or a DACH region industrial customer requesting eCl@ss classification is not asking for a different flavour of the same category system. They are asking for a level of technical attribute detail UNSPSC was never designed to carry.

The conflict is in your ERP

The practical problem is rarely a company deciding, from a blank page, which standard to adopt. It is a company whose ERP was implemented years ago against one standard, usually UNSPSC if the system originated in a US or UK deployment, discovering that a parent company, a client, or a new manufacturing site now expects eCl@ss level detail on the same material records. The taxonomy conflict is really an ERP conflict wearing a classification label.

This is definitely a solvable problem, and it is a common one. Most companies in this position are not choosing between the two standards. They are running UNSPSC as the category layer for spend reporting, and adding eCl@ss attributes at the material master level for the specific parts where a manufacturing or engineering stakeholder requires that detail. The two coexist on the same record without contradiction, because they are answering different questions about it, not competing to answer the same one.

How to pick when you cannot avoid both

The honest starting point is admitting it is impossible to predict, months or years ahead, exactly which classification requirement a future client, parent company, or acquisition will bring with it. Rather than guessing which single standard to standardise on forever, the more durable approach is picking the primary standard based on what the business reports against today, UNSPSC for spend and category reporting in most hard FM, cleaning, and construction contexts, and treating the other standard as an attribute layer applied only where a specific stakeholder actually requires it.

The first step is confirming what your own reporting structure is actually built around, not what sounds more rigorous. The second step is checking whether any current or likely client, parent company, or regulatory requirement specifically asks for eCl@ss attributes at the material level, since that requirement, if it exists, is usually narrower than the whole spend base. The third step is applying the second standard only to that narrower set of records rather than reclassifying everything, because reclassifying spend data that already answers its intended question correctly is work with no proportional benefit attached to it.

None of this requires predicting every future requirement in advance, which is not possible. It requires a classification approach that can carry a second standard as an addition to specific records rather than a wholesale replacement of the first, so the next unexpected request does not force a choice between two systems that were never actually competing with each other.

Frequently asked questions

What is the main difference between UNSPSC and eCl@ss?

UNSPSC classifies what category a purchase belongs to for spend analysis and category management, using a four level hierarchy from segment down to commodity. eCl@ss classifies the technical attributes of a specific item at the material master level, the properties an engineer needs to specify or match a part correctly. They answer different questions rather than competing to answer the same one.

Which industries typically use UNSPSC instead of eCl@ss?

UNSPSC is the common standard in US corporate procurement, and UK public and private sector reporting, and in category management across hard FM, cleaning, and construction, because those sectors usually optimise for spend visibility rather than deep engineering level technical detail on individual parts.

Which industries typically require eCl@ss instead of UNSPSC?

eCl@ss is the standard requested across DACH region industrial, automation, and engineering supply chains, particularly at the material master level, where a German or DACH based manufacturing customer needs precise technical attributes for a part rather than a broader spend category.

Do we have to choose only one classification standard for our ERP?

No. Most companies that encounter both requirements run one standard, usually UNSPSC, as the primary spend and category reporting layer, and apply the other standard as an additional attribute layer only on the specific material records where a client, parent company, or engineering stakeholder actually requires it.

How do we decide which standard to prioritise if our ERP and our reporting expect different ones?

Start from what your own reporting is actually built around today rather than which standard sounds more technically rigorous. Confirm whether any current or likely requirement specifically calls for eCl@ss level detail, apply it only to that narrower set of records, and keep the primary standard aligned with how the business already reports spend.

How does Pearstop help companies handle both UNSPSC and eCl@ss requirements?

Pearstop classifies spend against the taxonomy a client already reports against, UNSPSC in most hard FM, cleaning, and construction engagements, and applies additional technical attributes at the material level only where a specific client, parent company, or engineering requirement calls for it, so the two standards coexist on the same data without a full reclassification project.

Stephanie Wiechers

CEO & Co-founder, Pearstop

Stephanie leads Pearstop's go-to-market and strategic direction. She works directly with procurement and FM leaders across Europe to understand how data quality affects margins, contracts, and AI readiness.

LinkedIn →