CPV to UNSPSC Mapping
Crosswalk CPV-coded tender, contract, and supplier data into UNSPSC so procurement, finance, ERP, and master-data systems can report against one internal taxonomy.
Version
CPV 2008 -> UNSPSC UNv260801.1
Last Updated
March 16, 2026
Coverage
Each CPV 2008 code is mapped into the most relevant UNSPSC category for downstream normalization workflows. CPV code coverage is 100%.
Typical use cases
- Normalize TED or tender exports into UNSPSC for spend cube and category reporting.
- Align CPV coded supplier and contract data with UNSPSC-led ERP and P2P systems.
- Support taxonomy harmonization across procurement, finance and master data teams.
FAQ
Why would I map CPV into UNSPSC?
UNSPSC is commonly the internal classification used in ERP, supplier master, P2P, and spend analytics environments, while CPV is the coding system attached to EU procurement notices.
Is the mapping one-to-one?
Not always. Some CPV concepts are broader or narrower than the closest UNSPSC category, so review rules are still recommended for sensitive classification and reporting workflows.
Operational note
Use as a mapping accelerator, not as a substitute for domain review in regulated procurement, financial reporting, or compliance workflows.