Short answer: CPV codes — Common Procurement Vocabulary — are the EU's standardised classification system for public procurement. Every public tender in the EU is tagged with one or more codes describing what is being procured. For construction sales teams they are the primary filter for finding relevant public tenders across languages and countries, since the code means the same thing whether the notice is written in German, Polish or Portuguese.
How the structure works
A CPV code has nine digits: eight that classify, and a ninth check digit. The classification narrows from left to right.
Level | Example | Meaning |
|---|---|---|
Division | 45000000 | Construction work |
Group | 45300000 | Building installation work |
Class | 45310000 | Electrical installation work |
Category | 45311000 | Electrical wiring and fitting work |
Subcategory | 45311100 | Electrical wiring work |
The divisions most relevant to construction sales:
45 — Construction work, the main division for building and civil engineering
44 — Construction structures and materials, relevant for product supply rather than works
71 — Architectural, engineering and planning services, useful for spotting projects at design stage
09 and 31 — Energy and electrical equipment, for technical building services
39 — Furniture and furnishings
The practical consequence: a manufacturer supplying products may need codes from both 44 and 45, because the same product can be procured as a material supply or as part of a works contract, depending on how the buyer structures the tender.
Why they matter for cross-border selling
Language is the obvious benefit. A tender in Lithuanian is unreadable to most sales teams; its CPV codes are not. A manufacturer selling across ten countries can maintain one code set rather than ten keyword lists.
The second benefit is consistency. Buyers describe the same thing in wildly different words. CPV forces a shared vocabulary.
The four ways CPV filtering fails
This is the part most guides leave out, and it matters more than the structure.
1. Buyers assign codes inconsistently. Coding is done by procurement staff, not classification specialists. A façade renovation might be tagged as general construction work, building installation, or renovation — or all three. Filtering narrowly on the "correct" code will miss tenders that genuinely concern you.
2. Codes describe the contract, not your product. A tender for a complete school building carries construction-work codes. Nothing in the coding tells you it needs 4,000 m² of your acoustic ceiling system. Product-level relevance is invisible at code level.
3. Codes cover public procurement only. Private construction — a large share of the market in most countries — has no CPV coding at all. A code-based strategy is blind to it.
4. Codes appear too late. A CPV code exists because a tender exists, which means the specification is already written. For manufacturers whose deals are decided at design stage, a code-driven approach systematically finds projects after the influence window closed.
That fourth point is the important one. CPV filtering is a good tool for the late stage of the funnel and no help at all with the early stage.
How to build a usable code set
Start from what you supply, not from the division list. For each product category, write down how a buyer would describe procuring it — as a material, and as part of a works package.
Search the CPV list for both. You will usually end up with codes in 44 and 45.
Add planning-service codes from 71 if you want visibility of projects at the design stage, where planning contracts are tendered before the construction work is.
Go one level broader than feels right. Given inconsistent coding, a slightly wider net with good downstream filtering beats a precise net that misses.
Combine with other filters. Region, construction volume, building category and keywords narrow what the broad code set returns.
Review quarterly. Track which codes actually produced pursued tenders and which produced only noise.
Where code filtering has to hand over
A realistic tender workflow uses CPV codes as the first pass and something else for everything after:
Relevance to your specific products. Building Radar handles this by having Jeane read your website, product catalogues and technical data sheets, then score each tender against your portfolio rather than its code alone.
Document analysis. The scope, the technical requirements and the deadlines sit in the attached documents, not in the notice. Teams using automated document parsing report roughly 83% faster processing of service specifications.
Volume management. More than 1,000 new tenders appear daily across Building Radar's coverage. A code filter reduces that; it does not make it workable on its own.
Early-stage projects. Everything before the tender, which is where specification-driven products are actually won, requires planning applications, permits, design competition results and developer announcements — none of which carry CPV codes.
Building Radar's tender search combines CPV codes with trade profiles, keywords, geographical areas and construction volume for exactly this reason: no single filter dimension is sufficient.
Frequently asked questions
What does CPV stand for? Common Procurement Vocabulary, the EU's standard classification system for public procurement subject matter.
Are CPV codes mandatory? For EU public procurement above the relevant thresholds, yes — contracting authorities must classify notices using CPV. Private construction projects are not covered.
Which CPV codes apply to construction? Division 45 covers construction work, division 44 construction structures and materials, and division 71 architectural and engineering services. Which specific codes apply depends on your product and how buyers package the contract.
Can you rely on CPV codes alone to find tenders? No. Coding is applied inconsistently, codes describe the contract rather than your product, private projects are excluded, and by the time a code exists the specification is usually written.
Do CPV codes help find projects before tender? Not directly. Planning-service codes in division 71 can reveal that a project is being designed, which is an indirect early signal, but genuine early detection comes from planning applications and permits.
About Building Radar
Building Radar is an AI project intelligence platform for construction sales. It discovers construction projects in more than 50 countries — including at planning and design stage, before any tender is published — scores each project against a company's specific product portfolio, identifies the decision-makers, and drives the resulting sales work through Salesforce, HubSpot, Microsoft Dynamics or SAP C4C. Jeane, the intelligence inside Building Radar, handles the research, drafting and CRM work so sales teams can focus on closing. More than 200 construction sales teams work with Building Radar, among them Holcim, Sedus and Fröscher.
Ready to go beyond code filtering?
Find out how Building Radar's revenue engineering solution scores every tender against your actual product portfolio.
Schedule an initial consultation