Map ECLASS to UNSPSC when your entities report differently
Some groups run into a specific problem: one entity classifies its material data to ECLASS (formerly written eCl@ss), because that's what its manufacturing or engineering stakeholders require, while another entity or the head office reports spend in UNSPSC. Neither entity is wrong. The two standards answer different questions, one about technical attributes, one about spend category, and most groups in this position don't choose one over the other. They map between them so both views stay accurate.
What this means for your data
Some groups run into a specific problem: one entity classifies its material data to ECLASS (formerly written eCl@ss), because that's what its manufacturing or engineering stakeholders require, while another entity or the head office reports spend in UNSPSC. Neither entity is wrong. The two standards answer different questions, one about technical attributes, one about spend category, and most groups in this position don't choose one over the other. They map between them so both views stay accurate.
What it costs to leave it
Bad data doesn't stay behind when you migrate. It gets carried into the new system, where it causes extra test runs, a delayed go-live, and spend reports nobody trusts once the dust settles.
How classification to ECLASS works
Classify each entity to its own standard
Pearstop classifies each entity's data to whichever standard it already reports against, ECLASS or UNSPSC, rather than forcing a single standard across the group.
Map between the two
Where the group needs a combined view, we map ECLASS categories to their nearest UNSPSC equivalent, and flag where the mapping is approximate rather than exact.
Keep both views current
As new purchase and material data comes in, it's classified and mapped the same way, so the combined view doesn't drift out of date.
Where ECLASS classification matters
- Which entities report in which standard today, before anything is remapped.
- Where ECLASS technical attributes and UNSPSC spend categories genuinely correspond, and where the mapping can only be approximate.
- How new data keeps getting classified and mapped consistently after the initial project.
What good data looks like
- One record per supplier, with no duplicates across entities.
- Every spend line labelled to one standard (UNSPSC or your own).
- Item and material descriptions written the same way.
- Units of measure consistent.
- Inactive suppliers and items flagged, not migrated.
- Every field mapped to the new system and documented.
- Every entity's classification standard documented, not assumed.
- A maintained mapping table between ECLASS and UNSPSC categories, not a one-off spreadsheet.
How Pearstop handles it
The data doesn't need to be clean first. AI classification handles the clear cases, and a person reviews anything uncertain. ECLASS labels are mapped to ECLASS and UNSPSC's fields, in the format your migration needs. New invoices stay classified after go-live, so reporting doesn't slip back into the same mess.
Work with your partner
Most migrations run through an implementation partner. We work alongside them, or directly with you. Your partner sets up the new system; we give them clean, classified data in the format their import tools need. Nobody's scope changes, and your partner's team can spend their time on the new system instead of fixing records.
Why start early
Bring us in when you assess the data, not after the first test run fails. You find duplicates, free-text lines and missing categories while there is still time to fix them, nothing has to be cleaned twice, and the test runs go faster because the data goes in cleanly. Some problems only show up once you look closely at how the data behaves, which is why it pays to work with someone who handles this data every day.
Frequently asked questions
Can you map ECLASS codes to UNSPSC?
Yes. Pearstop maps ECLASS categories to their nearest UNSPSC equivalent, and flags where a mapping is approximate because the two standards were built to answer different questions.
How do we report spend when entities use different standards?
Keep each entity classifying against the standard it already uses, and map between ECLASS and UNSPSC for the combined view, rather than forcing every entity onto one standard it wasn't built to serve.
Related reading
Send us 200 lines
We'll classify a sample of your purchase data and send it back so you can see what good data looks like before you commit to cleaning the rest.
