The question almost always arrives at the same moment: the prototype works, there is real customer interest, and someone asks how much CE marking will cost before you can start selling. The honest answer is slightly uncomfortable, because the number that matters is not the one on the laboratory quote.
CE marking an electronic product has a direct cost — testing, documentation, sometimes a notified body — that can be estimated fairly realistically. It also has an indirect cost, far less visible, which is what happens when the product reaches the test lab without having been designed to pass. That second cost is what wrecks project budgets.
The core idea of this article: in electronics, most of the money spent on CE marking is not spent on certifying. It is spent on redesigning what should not have been designed that way in the first place.
Table of contents
What CE marking actually is (and what it is not)
CE marking is the manufacturer's declaration that a product meets the essential requirements of the European legislation that applies to it. It is not a quality seal, it is not granted by the European Union and, in most cases, nobody external issues it: the manufacturer applies it under their own responsibility.
That distinction is not bureaucratic hair-splitting. It changes who does the work, who carries the risk and where the real cost sits. The official definition is available in the European Commission's CE marking guidance.
It is not a certificate somebody issues to you
Many people go looking for "the CE certificate" expecting a document they can buy. What actually exists is different: a technical file that demonstrates conformity, and an EU declaration of conformity signed by the manufacturer. Only in specific product categories does a notified body get involved, and only then does it issue an examination certificate.
For a typical electronic product — a consumer device, a light industrial unit, a connected sensor — self-declaration is the norm. That makes the administrative side cheap and the technical side expensive: nobody is going to tell you your design is sound. You have to demonstrate it.
Which legislation applies to an electronic product
Before talking about money, you need to know what you are buying. The first real task in the process is defining the product, its intended use and the legislation that covers it. The same device can fall under one directive or four, and that is where budgets multiply.
The directives that usually apply
- Electromagnetic Compatibility (2014/30/EU). The equipment must not emit interference above the limits, and must tolerate the interference it receives. This applies to practically anything with electronics inside.
- Low Voltage (2014/35/EU). Electrical safety for equipment between 50 and 1,000 V AC. If your product plugs into mains, you are here.
- Radio Equipment Directive, RED (2014/53/EU). The moment there is Wi-Fi, Bluetooth, LoRa, NB-IoT or any radio module, this directive absorbs the previous two and adds spectrum requirements. It is the single biggest cost driver.
- RoHS (2011/65/EU). Restriction of hazardous substances. Cheap if your supply chain is documented; painful if it is not.
There are others depending on the case — WEEE, ecodesign and, if the product carries a lithium cell, everything we cover in CE marking for battery-powered products — but these four cover the bulk of what we handle in electronic product development.
What changed in 2025: cybersecurity under the RED
Since 1 August 2025, the cybersecurity requirements of Delegated Regulation 2022/30 are enforceable for any radio equipment connected to the internet, directly or indirectly. In practice: almost any IoT product.
The sensible route to compliance is the harmonised standards EN 18031-1, EN 18031-2 and EN 18031-3, published by CEN-CENELEC, covering respectively general security for connected equipment, handling of personal and location data, and handling of monetary value. Applying them keeps you on the self-declaration route, without a notified body.
This has design consequences, not just paperwork. Credential management, secure firmware update, verified boot and secret storage are architectural decisions. If the firmware is already frozen when they surface, it gets rewritten. And once the product is on the market the opposite question appears: whether a firmware update invalidates the CE marking.
What is coming: GPSR and the Cyber Resilience Act
Two further regulations worth keeping on the radar, even though they are not strictly part of CE marking:
- GPSR, Regulation (EU) 2023/988. Mandatory since 13 December 2024. It requires risk analysis, traceability and documentation for every consumer product, CE marked or not.
- Cyber Resilience Act, Regulation (EU) 2024/2847. Fully applicable on 11 December 2027, with vulnerability reporting obligations from 11 September 2026. It imposes cybersecurity requirements across the whole lifecycle of products with digital elements, with penalties reaching €15 million or 2.5% of worldwide turnover.
If you are designing a connected product today that will be on the market in 2028, the CRA is not a future concern. It is a present architectural requirement.
How much CE marking costs for an electronic product
There is no price list. There are reasonably stable market ranges, and it is worth looking at them line by line rather than as a single figure.
Breakdown by line item
- EMC testing at an accredited laboratory: roughly €1,500 – €10,000, depending on how many standards apply and how complex the equipment is. This is almost always the dominant item.
- Electrical safety testing: in the region of €800 – €3,000 if the product connects to mains.
- Radio and spectrum testing (if RED applies): a further €3,000 – €8,000. EN 18031 cybersecurity assessment sits on top of that.
- Technical file and documentation: close to nothing if an experienced in-house team handles it, or €2,000 – €6,000 if fully outsourced.
- Notified body, where mandatory: a separate line, normally several thousand euros and several weeks of lead time.
- Your own engineering time: the cost that never appears on any quote, and usually the largest of them all.
The overall range in the European market runs from about €1,500 for a simple product to €20,000 or more for a complex one with radio. Typical timelines are measured in weeks or months from the point the documentation is complete, not days.
A worked example: a connected device with radio
Picture a consumer product with a microcontroller, USB power, a Bluetooth module and a mobile app. It is a very common profile among the projects that reach our IoT development team. RED applies — absorbing EMC and Low Voltage — along with RoHS and the cybersecurity requirements.
Adding up EMC testing, radio testing, cybersecurity assessment and the technical file, the budget lands comfortably in the €8,000 to €15,000 band, assuming everything passes first time. That last condition is what decides whether the project resembles that number or twice it.
Why self-certification does not mean free
This is a common misunderstanding. Being allowed to self-declare means you do not pay a third party to sign. It does not mean the work goes away. You still have to run the tests, apply the correct harmonised standards, compile the technical file and answer for conformity if anyone challenges it.
Self-certification shifts the cost from the certifier to the manufacturer. If the manufacturer has solid engineering judgement, it works out cheaper. If not, it works out more expensive — just later.
The cost nobody budgets for: failing the test
Here is the real reason why two similar products end up with certification budgets that differ by a factor of three.
One PCB respin and everything it drags along
When equipment fails an emissions test, the fix is rarely a minor tweak. It is a new board: adding filtering, reworking the ground plane, adding shielding, rerouting clock traces. And a new board drags a full chain behind it:
- schematic and layout redesign and review,
- a new prototype run and its manufacturing lead time,
- assembly and functional validation all over again,
- a return trip to the laboratory and a second test session to pay for,
- and, if the enclosure depended on the board, new tooling or new prints too.
A single day in an accredited anechoic chamber runs somewhere around €2,000 – €4,000, and that excludes engineering hours, travel and the launch delay. Two or three iterations turn an €8,000 budget into a €25,000 one and push the market launch back by months. It is exactly the kind of overspend we describe in the most expensive mistakes when building a prototype.
Radiated emissions: the most common failure
If one failure mode dominates statistically, it is radiated emissions. And it almost always originates in decisions taken much earlier, when nobody was thinking about certification: a fragmented ground plane, a fast clock routed without return path control, an unfiltered connector, a cable acting as an antenna, a poorly decoupled switching supply.
The asymmetry is brutal. A well-placed decoupling capacitor in the initial design costs cents. Discovering it was missing after the test costs a new board, a lab session and six weeks.
Pre-compliance: walking into the chamber knowing the result
Pre-compliance testing means approximating the official measurements before paying for them. It is done in pre-compliance chambers or with bench instrumentation, and it has no legal standing: it does not replace the accredited test and it cannot serve as evidence in the technical file.
Its value lies elsewhere. It stops you walking in blind. Accredited laboratories across Europe offer exactly this service, and it exists because it works.
What gets measured in pre-compliance
A radiated and conducted emissions sweep with a spectrum analyser and near-field probes shows the equipment's profile and locates where each peak comes from. It will not give you the exact number the accredited chamber will produce, but it will tell you whether you are five decibels under the limit or fifteen over. That difference decides everything.
With tight margins, you fix things before you go. With comfortable margins, you go relaxed. What makes no sense is paying for an official test to find out something you could have known beforehand for a fraction of the price.
Design decisions that decide the test
Pre-compliance finds problems; design avoids them. The decisions that weigh most are taken during PCB design, and they are almost always the same ones:
- A continuous ground plane with short, predictable return paths.
- A stack-up planned from the start, not inherited from the previous board.
- Filtering on every input and output crossing the enclosure, especially connectors and long cables.
- Control of fast signals: clocks, memory clock lines, differential buses.
- Switching supplies with the smallest possible switching loop.
- Firmware architecture compatible with EN 18031 where radio is involved: secure update, credential management, secret storage.
None of these decisions makes the board meaningfully more expensive if taken in time. All of them make the project more expensive if taken after the first failure.
The technical file and the EU declaration of conformity
The documentation side is consistently underestimated, and it is what most often blocks a market launch once the testing is already done.
What the file contains
The technical file is the body of evidence demonstrating the product's conformity. At minimum it usually includes:
- a description of the product and its intended use,
- identification of the legislation and harmonised standards applied,
- a risk analysis,
- schematics, layout, bill of materials and design documentation,
- laboratory test reports,
- certificates for components and pre-approved modules,
- the instruction manual and labelling,
- and the signed EU declaration of conformity.
That file has to be retained and made available to market surveillance authorities on request. It is not a one-off formality: it is maintained for as long as the product is on the market, and updated with every relevant design or supplier change.
One legitimate shortcut: using pre-certified radio modules with their own documentation substantially reduces the testing required. It does not eliminate it — the finished product still has to comply — but it is one of the single biggest money-savers available, and the decision has to be made when selecting components, not at the end.
When you need a notified body
It depends on which conformity assessment module applies. For most consumer electronic products, Module A — internal production control — is enough, and requires no third party. A notified body comes into play when the product belongs to a higher-risk category, when harmonised standards are not applied, or when the directive itself requires it.
This question is worth settling at the start of the project. Discovering late that a notified body was needed does not just add cost: it adds months of calendar nobody had planned for.
How we help at RobotUNO (and what we don't do)
Let's be clear. RobotUNO is not an accredited laboratory or a notified body. We do not issue CE marking, we do not certify and we do not sign declarations of conformity: that is the manufacturer's responsibility and, where applicable, an accredited third party's.
What we do is the work that comes before, which is where the cost is actually decided:
- Identify from the outset which legislation will apply and what it means for the design.
- Design the electronics and firmware with EMC and cybersecurity criteria built in, not bolted on afterwards.
- Select modules and components that reduce the testing required.
- Run pre-compliance testing and fix what shows up before going to the accredited laboratory.
- Assemble and organise the technical documentation that makes up the file.
- Coordinate with the laboratory and support you through the test campaign.
It is the work we did, for example, on the anti-theft bag alarm, an ultracompact Bluetooth device we left ready for CE/FCC certification. And it is a natural part of the move to production described in industrialization and mass manufacturing.
If one rule helps: CE marking is not a phase at the end of the project. It is a design constraint from the first schematic. Treating it as the first thing costs little; treating it as the last thing costs a great deal.
Frequently asked questions
How much does CE marking cost for an electronic product?
There is no fixed price. Market ranges run from around €1,500 for a simple device to €20,000 or more for a complex one, and laboratory testing is almost always the heaviest line item. A product without a radio module sits at the low end; a connected device with radio and cybersecurity requirements sits at the top.
Do I need a notified body to apply the CE marking?
For most consumer electronic products, no. The EMC and Low Voltage directives let the manufacturer self-declare conformity. A notified body becomes necessary when the product falls into a higher-risk category or when harmonised standards are not applied.
Does self-certification mean CE marking is free?
No. Self-certification means no external party signs the certificate, not that the work disappears. The manufacturer still has to run the tests, compile the technical file and stand behind the declaration of conformity. The cost does not vanish; it changes hands.
What is EMC pre-compliance testing and why does it matter?
It is preliminary testing, usually in a non-accredited lab or a pre-compliance chamber, that approximates the official measurements. It carries no legal weight, but it lets you find and fix deviations before paying for the accredited test.
What changed in August 2025 for radio products?
Since 1 August 2025 the cybersecurity requirements of Delegated Regulation 2022/30 under the Radio Equipment Directive are enforceable. They apply to any radio equipment connected to the internet, directly or indirectly, and are met through harmonised standards EN 18031-1, -2 and -3.
Have a product that needs to reach the market?
Tell us where it stands. We'll give you a technical read on which legislation will apply and which design decisions are worth settling before you spend money on testing.
