A commercial team expanding across markets should describe its offer once, then build and test a separate classification map for each source. CPV, NAICS and UNSPSC are not interchangeable code systems.
This reference helps you avoid false matches and silent exclusions when moving a tender search between portals.
What each scheme describes
| Scheme | Primary purpose | Structure and source |
|---|---|---|
| CPV | Subject of public procurement: works, supplies and services | Eight main digits plus a check digit; Publications Office guide |
| NAICS | Economic activity of business establishments | Hierarchy from sectors to six-digit industries; US Census Bureau manual, page 18 |
| UNSPSC | Products and services | Eight-digit segment, family, class and commodity hierarchy; UN Global Marketplace guide |
A procurement system can use an industry classification in a notice, but that does not turn the classification into a product catalogue. Check the field's purpose on the source portal as well as the dictionary definition.
Why a simple conversion fails
One industry can supply multiple products and services; the same product can be supplied by establishments in different industries. Even two product-oriented vocabularies can split the market differently. Similar wording is a candidate relationship to investigate, not proof of equivalence.
Keep scheme, code, label and version. Preserve leading zeros where applicable and treat codes as identifiers, not quantities. Do not strip the scheme and compare numeric strings from different sources.
For a crosswalk, require its publisher, version, scope and mapping relationship. A broad-to-narrow association is useful for exploration, but should not automatically become an exact-match rule.
Build a map around an actual offer
Illustrative offer: installation and maintenance of campus communications equipment. Separate equipment supply, installation and ongoing service before choosing codes.
For each target portal:
- Read its classification guidance and identify the scheme used.
- Search official definitions using buyer terminology.
- Inspect several relevant notices and record their native codes.
- Keep the classification search alongside keywords and named buyers.
- Test known relevant notices, including one with a broad or missing code.
- Record unmatched cases for review.
The example intentionally does not provide a universal code conversion: the contract's scope determines which native entries are appropriate.
Copy this cross-market map
| Offer component | Portal and scheme | Native code and version | Reason it fits | Known notice | Mapping confidence |
|---|---|---|---|---|---|
| Equipment supply | Fill from the source | Verify in its dictionary | Actual deliverable | Official URL | Confirmed for this example |
| Installation | Fill separately | Do not reuse automatically | Service scope | Official URL | Candidate or confirmed |
| Maintenance | Fill separately | Include broader search if needed | Support scope | Official URL | Candidate or confirmed |
Keep “unmapped” visible. It is more useful than a guessed code that makes the search look complete.
Continue with a tested search
Use the practical CPV guide for European code selection and the monitoring workflow for buyer and geography logic. Consult a country playbook before assuming that its sources use the same classification.
Reviewed 13 September 2026 against the official scheme references linked above. No automatic crosswalk or current Duke cross-market matching capability is asserted.