For sales and bid teams, CPV codes are a way to find likely purchases. They do not establish that a tender fits your offer, that you are eligible, or that every relevant buyer used the code you expected.
The useful output is a small, tested code map with inclusion reasons and examples.
Understand the hierarchy
CPV describes the subject of a public procurement. Its main vocabulary uses eight digits plus a check digit. The first two digits identify a division; further digits refine the subject. The supplementary vocabulary adds qualitative detail. This is different from additional main-vocabulary codes attached to a notice. Official CPV guide.
Keep the code, scheme and official label together. Labels can be translated; the code does not change with the page language. A broad code signals a broader subject, not a broader legal right to bid.
Start with the work you deliver
Write five phrases a buyer might use for your services or products, including local terminology. Find official code definitions that describe the work, then inspect previous relevant notices and their lots.
Use a map with these columns:
| Field | What to record |
|---|---|
| Offer | A deliverable you actually sell |
| Candidate code | Official code and label |
| Role | Core, adjacent or discovery-only |
| Positive example | A notice where the scope fits |
| False positive | Similar code but unsuitable work |
| Keywords | Buyer phrases and language variants |
| Review date | When the mapping was last tested |
Do not copy a long supplier-directory list without examining what its codes mean.
Decide how broad to search
Keep a core search for specific services, a broader discovery search and a separate buyer watch. A very narrow code can miss mixed procurements; a division-level filter can generate substantial unrelated work.
Test whether your portal expands parent codes into children. Test main and additional codes if the portal distinguishes them. Combine a code search with a keyword search using OR when either signal should be sufficient, then apply delivery constraints. Check TED's search documentation for the behavior of its fields.
Example: architectural and engineering services
CPV 71000000-8 is the broad division for architectural, construction, engineering and inspection services. It can help discover the field, but is too broad to stand in for one specialist offer. Consult the official vocabulary for suitable child codes, then read the actual scope.
Illustrative practice: an inspection consultancy retains the broad division in a discovery sample, selects appropriate inspection service codes for daily review and watches named infrastructure buyers. It excludes unrelated design work only after examining whether a suitable inspection lot is included.
The code is an official reference; the consultancy scenario is illustrative.
What language is CPV 71000000-8?
The number is language-independent. In English, its official label is Architectural, construction, engineering and inspection services. In Dutch, it is Dienstverlening op het gebied van architectuur, bouwkunde, civiele techniek en inspectie. These are labels for the same code, not separate national classifications. Check the language editions of Regulation 213/2008 and the Dutch vocabulary.
Choose a more specific branch for your daily search: 71200000-0 covers architectural and related services; 71320000-7 covers engineering design services; 71600000-4 covers technical testing, analysis and consultancy services. These are starting points, not interchangeable descriptions of every engineering assignment. The Commission classification reference supplies the labels.
For a reproducible search, record the code, whether children are included, whether main and additional codes are searched, language-specific keywords and the date range. Some interfaces show eight digits without the check digit; verify the field's accepted format. Save your settings and rejected examples in the tender monitoring log.
For a real example of relevant work under an unexpected classification, read the Dutch AI and knowledge-management buyer watchlist.
Prevent silent misses
Review a small set of known relevant notices after each filter change. Retain notices with missing classification for separate keyword review. Keep an explanation for each exclusion, and revisit exclusions when the offer changes.
Do not translate CPV into NAICS or UNSPSC by matching digits or assuming equivalent labels. These schemes classify different things. Use the CPV, NAICS and UNSPSC comparison to build separate market-specific searches.
Your next action
Use the three-record search case study to test classification, stage and geography mistakes against public evidence.
Create the code map for one offer and use it in the CPV, region and buyer monitoring workflow. Before pursuing a result, complete the notice review. For market context, return to the procurement playbooks.
Reviewed 13 September 2026 against the official CPV and TED search references. Classification selection and testing steps are editorial practice, not a guarantee of complete retrieval.