When your IoT prototype finally works, it's tempting to think the hard part is behind you. The sensors read correctly, the firmware does what it should, data lands on your dashboard. That's a real milestone. It's also nowhere near the finish line.
To sell that product in Europe, it has to clear a set of regulatory requirements first, and it has to carry the CE mark. CE means the device meets EU safety rules, doesn't interfere with other electronics, and stays within environmental limits.
Plenty of startups don't find this out until late, when changing the hardware is slow and expensive and the launch slips by months. That's the reason to plan certification early, during IoT product development rather than after it.
If you're getting a device ready for approval specifically, our guide on CE certification for IoT devices goes deeper into the testing process and the documentation you'll need.
CE Certification Is More Than a Label
A common misconception is that CE certification is one test you pass at the end. It isn't. CE is a declaration that your product complies with several EU directives.
Which directives apply depends on the product. Most IoT devices fall under three.
Radio Equipment Directive (RED)
This one applies to any device with a radio: Wi-Fi, Bluetooth, LoRaWAN, or cellular. It exists to keep devices using the spectrum correctly and out of each other's way.
Electromagnetic Compatibility (EMC) Directive
A device has to keep working when it's surrounded by other electronics. The EMC directive sets limits on how much electromagnetic interference your device can emit, and how well it has to cope with interference from everything around it.
RoHS Directive
The Restriction of Hazardous Substances (RoHS) directive limits hazardous materials in electronics, including lead, mercury, cadmium, and certain flame retardants.
Between them, these three cover how a device is designed, tested, and documented before it can go on sale in Europe.
Designing With Compliance in Mind
A prototype proves the idea is feasible. A production device has to prove it works reliably and safely, batch after batch. That's a higher bar, and it's where a lot of IoT projects hit trouble.
A handful of design choices have an outsized effect on whether you pass:
- Antenna and RF design - improper placement or routing can cause interference
- PCB grounding and shielding - critical for passing EMC tests
- Power supply filtering - noisy power rails create emissions
- Component selection - not all components meet RoHS requirements
- Materials used in the enclosure - affects both safety and RF performance
An antenna that tests fine on the bench can still fail radio certification once the PCB layout around it starts radiating.
This is why, during IoT product development, it pays to weigh compliance alongside the hardware, firmware, and mechanical design from the start, rather than discovering a redesign late.
Why Pre-Compliance Testing Is Important
Before they pay for official certification, most teams run pre-compliance testing first, to catch the obvious problems while they're still cheap to fix.
Typical checks include:
- Electromagnetic emission scans to detect unwanted radiated or conducted emissions
- Radio frequency performance testing to verify antenna and transmitter behavior
- Electrical safety checks to validate isolation, grounding, and voltage limits
Fixing something during development is far easier than fixing it after a failed certification test. On a tight timeline, that gap is often the difference between shipping and slipping a quarter.
The CE Technical File
CE certification also needs a technical file: the paperwork that shows your product complies. It usually includes:
- Circuit schematics and PCB designs
- Product specifications
- Component lists
- Risk assessments
- Compliance test reports
- User guides and labeling details
- Declaration of Conformity
You have to keep this file for ten years after the product goes on the market, since regulators can ask to see it during an inspection. Building it up as you go, instead of reconstructing it at the end, makes certification far less painful.
Certification Is Only Part of Production
Passing certification is a milestone, not a launch. Manufacturing brings its own problems.
Factories are tuned for throughput, and throughput and consistency pull in different directions. To hold quality across a run, you want things like:
- Approved component lists to prevent substitutions
- Production test fixtures for each device
- Pilot production runs before scaling manufacturing
Skip these and a perfectly certified design can still turn into unreliable units once they're out in the field.
Planning for Updates and Scalability
It's easy to pour everything into the hardware and forget that the product still has a life after launch.
Connected devices need firmware updates, security patches, and new features over time. Build in over-the-air (OTA) updates and you can do all of that remotely, without recalling anything.
The backend has to scale too. A system that's fine for a handful of prototype units can fall over at a few thousand. It's much cheaper to plan for that during development than to re-architect it once devices are in the field.
How Insyght Helps Bring IoT Products to Market
A connected device is more than working hardware. You're juggling hardware design, firmware development, compliance testing, and manufacturing prep all at once.
We work with companies across that whole span. We flag the standards that apply early, design the hardware with certification in mind, line up pre-compliance testing, and put together the technical file CE needs. Handling compliance, engineering, and manufacturing as one job, rather than three handoffs, is what keeps the path from prototype to production short and predictable.
From Prototype to CE-Certified Production
Getting from prototype to CE-certified production is a lot more than building a device that works. You need to understand which rules apply, prepare the documentation, run the right tests, and keep quality steady across a production run.
Bring certification into the picture early and the whole thing gets more predictable. Leave it to the end and you're often looking at several rounds of redesign. For most IoT teams, that early planning is what separates a clean European launch from a slow, expensive one.
Frequently Asked Questions
Do IoT devices need CE certification before they can be sold in Europe?
Yes. Any IoT device sold in the European Economic Area must have CE certification. This confirms the device meets EU safety, electromagnetic compatibility, and environmental standards.
How long does CE certification take for an IoT product?
CE certification usually takes 4-12 weeks, depending on the device complexity and testing requirements such as EMC, radio frequency, and electrical safety compliance.
What testing is required for CE certification of IoT devices?
Most IoT devices must pass EMC testing, radio frequency testing, electrical safety checks, and RoHS compliance verification before receiving CE certification.
Can startups obtain CE certification for their IoT products?
Yes. Startups can obtain CE certification by completing required testing, preparing technical documentation, and issuing a Declaration of Conformity for the product.
How much does CE certification cost for an IoT device?
The cost of CE certification varies depending on device complexity and required testing. For most IoT devices, certification testing typically ranges from EUR 5,000 to EUR 20,000.