From working prototype to CE-certified production

When your IoT prototype finally works, it's tempting to think the hard part is over. The sensors read correctly, the firmware behaves, 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 rules first, and carry the CE mark. CE means the device is safe, doesn't interfere with other electronics, and stays inside the environmental limits.

Plenty of startups find this out late, when changing the hardware is slow and expensive and the launch slips by months. That's why certification belongs in the plan during IoT product development, not after it.

If you're preparing a device for approval right now, our guide on CE certification for IoT devices goes deeper into the testing and the paperwork.

CE is a declaration, not a test you pass

People often picture CE as one exam at the end. It isn't. CE is your declaration that the product complies with several EU directives.

Which ones apply depends on the product. Most IoT devices land on three.

Radio Equipment Directive (RED)

Applies to anything with a radio in it: Wi-Fi, Bluetooth, LoRaWAN, cellular. It exists to keep devices using the spectrum properly and out of each other's way.

Electromagnetic Compatibility (EMC)

Your device has to keep working while surrounded by other electronics. EMC sets limits on how much interference it may emit, and how well it has to cope with the interference around it.

RoHS

The Restriction of Hazardous Substances directive limits what you can put in electronics: lead, mercury, cadmium, and certain flame retardants.

Between them, these three shape how a device is designed, tested and documented before it can go on sale.

Designing with compliance in mind

A prototype proves the idea works. 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 get into trouble.

A handful of design choices decide most of the outcome. Antenna and RF design, where poor placement or routing causes interference. PCB grounding and shielding, which is what gets you through EMC. Power supply filtering, because noisy rails turn into emissions. Component selection, since not everything meets RoHS. And the enclosure materials, which affect both safety and RF performance.

An antenna that measures beautifully on the bench can still fail radio certification once the layout around it starts radiating.

So when you're doing IoT product development, weigh compliance next to the hardware, firmware and mechanical design from the start. It's a lot cheaper than discovering a redesign late.

Why pre-compliance testing pays for itself

Before paying for official certification, most teams run pre-compliance testing to catch the obvious problems while they're still cheap.

You'd typically scan for unwanted radiated and conducted emissions, check the antenna and transmitter behaviour, and verify the electrical safety basics: isolation, grounding, 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 technical file

CE also needs a technical file, the paperwork that shows your product complies. It usually holds:

• Circuit schematics and PCB designs
• Product specifications
• Component lists
• Risk assessments
• Compliance test reports
• User guides and labelling details
• The Declaration of Conformity

You keep that file for ten years after the product goes on the market, because regulators can ask to see it. Build it up as you go instead of reconstructing it at the end and certification gets much less painful.

Certification is not the same as being ready to ship

Passing certification is a milestone, not a launch. Manufacturing brings its own problems.

Factories are tuned for throughput, and throughput and consistency pull against each other. To hold quality across a run you want an approved component list so nobody substitutes parts, a production test fixture for every device, and a pilot run before you scale manufacturing.

Skip those and a perfectly certified design can still turn into unreliable units in the field.

Planning for updates and scale

It's easy to pour everything into the hardware and forget the product has a life after launch.

Connected devices need firmware updates, security patches and new features. Build in over-the-air updates and you can deliver all of that remotely, without recalling anything.

The backend has to scale too. A system that's fine for a handful of prototypes can fall over at a few thousand devices. Planning for that during development costs far less than re-architecting it once the units are out there.

How we work

A connected device is more than working hardware. You're juggling hardware design, firmware development, compliance testing and manufacturing prep at the same time.

We work across that whole span: flagging the standards that apply early, designing the hardware with certification in mind, lining up pre-compliance testing, and assembling the technical file. Treating compliance, engineering and manufacturing as one job rather than three handovers is what keeps the path from prototype to production short.

The short version

Getting from prototype to certified production takes more than a device that works. You need to know which rules apply, prepare the documentation, run the right tests, and hold quality steady across a production run.

Bring certification in early and the whole thing becomes predictable. Leave it to the end and you're usually looking at several rounds of redesign.

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 needs it. It confirms the device meets EU rules on safety, electromagnetic compatibility and hazardous substances.

How long does CE certification take for an IoT product?

Usually 4 to 12 weeks, depending on how complex the device is and how much testing it needs across EMC, radio and electrical safety.

What testing is required?

For most IoT devices: EMC testing, radio testing, electrical safety checks and RoHS verification.

Can a startup get CE certification on its own?

Yes. You complete the required testing, prepare the technical documentation, and sign the Declaration of Conformity yourself. Nobody else issues it to you.

How much does CE certification cost for an IoT device?

It depends on the device, how many directives apply, and how much lab time the testing needs. A battery-powered BLE sensor and a mains-connected gateway are not in the same bracket. Ask us for a figure against your actual product.