CPV Codes for EV Charging Infrastructure Tenders, Explained

What a CPV code is and why it matters for EV charging bids

The Common Procurement Vocabulary (CPV) is the European Union's standardised classification system for public procurement. Every notice published on TED or on a national eProcurement portal is tagged with one or more CPV codes — eight-digit numbers, plus a check digit, arranged in a hierarchy that runs from broad divisions down to specific items — describing exactly what's being bought. For a buyer, tagging a notice correctly determines who sees it show up in a filtered search. For a supplier, filtering by CPV code is the standard way to separate genuine EV charging opportunities from the much larger volume of adjacent notices — general electrical installation work, plain vehicle fleet purchases, or unrelated construction — that would otherwise bury them in a keyword search across a general procurement portal.

This matters more for EV charging specifically than for many other categories, because the sector sits at the intersection of several established classification groups — electrical equipment, vehicles, construction and civil works, and ongoing services — rather than having always had one clean code of its own. A supplier who only searches under a single narrow code will reliably miss notices that a buyer has filed under an adjacent one.

The core CPV codes for EV charging infrastructure

The codes bidders should track for EV charging infrastructure work centre on the Common Procurement Vocabulary's charger and vehicle groupings. 31158000 (Chargers) and its narrower sibling 31158100 (Battery chargers) are the codes most consistently applied to notices for the supply of EV charge point hardware itself, and are the ones to start any CPV-based search with. 34144900 (Electric vehicles) is closely related but covers the vehicles rather than the charging infrastructure — it turns up on notices for fleet electrification programmes that bundle vehicle purchase and charger installation into a single contract, which is common enough among transport authorities and public sector fleet operators that it's worth tracking alongside the charger-specific codes rather than instead of them.

Because a full charging infrastructure contract rarely stops at hardware supply, real notices commonly pair those codes with ones from the construction and installation groupings — codes under the 45000000 (Construction work) division cover the civil and electrical installation work needed to actually put a charger in the ground and connect it to power — and with service codes for the ongoing maintenance contract that typically accompanies a hardware install. A UK council tender for on-street charge points, for example, will often carry 31158000 for the units themselves alongside a construction-division code for the groundworks and cabling, and sometimes a separate maintenance service code if support is being procured as a distinct multi-year contract rather than bundled into the same lot.

Why bundled contracts use multiple CPV codes at once

A large share of public EV charging tenders aren't pure hardware-supply contracts at all — they bundle charger supply, civil and electrical installation works, and a five-to-ten-year maintenance and network-management commitment into a single notice, because most public buyers would rather run one procurement and hold one supplier accountable for the whole lifecycle than manage separate contracts for installation and upkeep. A notice like that will typically carry three or four CPV codes at once — one for the hardware, one from the construction division for the works, and one or more service codes for maintenance — rather than a single tidy classification.

This is exactly where a bidder searching only under the "pure" 31158000 charger code under-performs: they'll find the notice, since it carries that code too, but a search strategy built around a single code and nothing else will just as often surface irrelevant hardware-only notices while missing the fact that a bundled contract needs installation and maintenance capability to bid competitively at all. Reading the full set of codes on a notice, not just the first one listed, is part of correctly scoping whether a contract fits what a given supplier can actually deliver.

Common misclassification pitfalls

CPV classification is applied by whoever drafts the notice at the buying authority, and it isn't always applied consistently. A reasonably common pattern is a smaller municipal authority filing an EV charging notice under a generic electrical installation works code, or occasionally under a general vehicle-related code, without ever adding one of the charger-specific codes at all — sometimes because the person drafting the notice is following an internal procurement template built for general electrical works and simply didn't think to add a more specific tag, sometimes because the contract genuinely spans categories and the drafter defaulted to the broadest one. A search tool that filters purely on CPV code will never surface that notice, because the code it's actually looking for was never applied.

This is the practical reason a classification system built on keywords in the notice text, not CPV codes alone, catches opportunities that a pure-CPV search tool misses. ChargeTenders' classifier reads notice titles and descriptions across every country and language it tracks and flags EV charging relevance from the text itself, so a misfiled notice under a generic electrical works code still gets picked up if the description mentions charge points, EVSE, or equivalent terms in the local language — which is the gap a bidder relying solely on official CPV filtering, whether searching TED directly or another classified feed, is otherwise exposed to.

How to set up a CPV-based watch across multiple countries

A practical manual watch combines CPV filtering with country and language filtering: start with 31158000 and 31158100 as the core charger codes, add 34144900 where fleet-bundled contracts are relevant, and layer in the relevant construction-division and maintenance service codes for the specific contract types being tracked. Because CPV codes are consistent across every member state regardless of language, this is one of the few search parameters that doesn't need to be re-translated country by country — the code itself does that work. The remaining manual effort is running that search across each national portal in turn, in whichever language it publishes in, since no single national portal aggregates every other country's notices.

That aggregation is what a classified, multilingual feed is built to remove. ChargeTenders combines CPV-code filtering with the text-based classifier described above across every tracked country — see the current UK, Germany and Italy tender pages for a sense of the range — so a bidder gets one list instead of running the same search a dozen times over. The free tier covers this archive with a short delay; Pro adds same-day alerts and CSV export, turning the watchlist described above from a recurring manual task into a done-for-you feed.

Reading the codes together, not in isolation

The single most useful habit for a bidder new to CPV-based searching is to treat the full list of codes on a notice as one description, not several unrelated tags. A notice carrying 31158000 alongside a construction-division works code and a services code for multi-year maintenance is describing one contract that needs hardware supply, installation capability and an ongoing support commitment all at once — not three separate opportunities a supplier can pick and choose between. Bidding on only the hardware-supply portion of a bundled contract generally isn't an option unless the notice explicitly splits it into separate lots; Section II of the notice will state whether lots exist and, if so, which CPV codes apply to each one. Checking that before investing time in a bid saves a supplier from preparing a response to only part of what's actually being procured, or from missing a lot they were fully capable of winning because the notice's primary code didn't obviously read as relevant at first glance.