CE Certification for IoT Devices: A Complete Guide

Bringing a connected device to market in Europe comes down to one thing first: the CE mark. Without it you legally can't sell in the EU. For a lot of IoT startups, though, the path from prototype to certified product is murky, costly, and full of delays that didn't need to happen.

So here's the whole path: which directives apply, how to structure your technical file, what pre-compliance testing to run, and how to pick an accredited lab that won't hold you up.

What CE Marking Actually Means

CE stands for Conformité Européenne, European Conformity. It's a manufacturer's declaration that the product meets all the EU legislation that applies to it. It is not a quality mark handed out by a third party. It's your own declaration, and a technical file has to back it up.

For most IoT devices you will need to address at minimum:

• RED (Radio Equipment Directive 2014/53/EU) — applies to any device with a radio (BLE, Wi-Fi, LoRa, cellular)
• LVD (Low Voltage Directive 2014/35/EU) — applies to mains-powered devices (>50V AC or >75V DC)
• EMC Directive (2014/30/EU) — applies to anything that could emit or be susceptible to electromagnetic interference
• RoHS Directive (2011/65/EU) — restricts hazardous substances in electrical equipment

Battery-powered IoT sensors that communicate over BLE or Wi-Fi typically fall under RED + RoHS. Mains-connected gateways add LVD + EMC.

The Technical File

Before a single lab test, you need a Technical File. This is the document package that proves your product conforms. It must include:

1. Product description — what the device is, its intended use, markets
2. List of harmonised standards applied — e.g., EN 300 328 for 2.4 GHz Wi-Fi/BLE, EN 62368-1 for safety
3. Design documents — schematics, PCB layout files (at minimum layer stackup and copper pours)
4. Risk assessment — particularly for safety (LVD/RED Article 3.1a)
5. Test reports — from an accredited lab
6. Declaration of Conformity (DoC) — signed by the EU-based responsible person

The Technical File does not need to be submitted to any authority upfront. It must exist, be accurate, and be available on request from market surveillance authorities for ten years.

Pre-Compliance: Catch Problems Early

Pre-compliance testing is informal RF and EMC testing you do yourself or with a consultant before paying for accredited lab time. A one-day pre-compliance session can cost €500–1500 and potentially save you months of re-testing.

Key pre-compliance checks for an IoT BLE/Wi-Fi product:

• Radiated emissions scan — look for unintentional emitters above Part 15 / Class B limits
• BLE TX power and frequency accuracy — verify you're within ±20 kHz and at the correct power level
• Conducted emissions on power lines — check SMPS switcher spurs don't exceed EN 55032 limits
• ESD immunity — touch all exposed metal and connectors with a discharge gun; €2000 handheld units work for pre-compliance

Common issues found in pre-compliance:

• Clock harmonics from MCU oscillators radiating via the PCB ground plane
• USB D+/D- lines acting as antennas
• Switching regulator noise coupling into the RF front-end
• Plastic housing resonances amplifying emissions at specific frequencies

All of these are fixable with PCB layout tweaks or filtering. But only if you find them before the lab.

Choosing an Accredited Test Lab

For RED, you need a lab accredited by a Notified Body (not all accredited labs are Notified Bodies, this matters for some product classes). For most Class 1 radio devices (BLE, Wi-Fi < 100 mW), you can self-declare conformity after having tests done at an accredited (but not necessarily Notified Body) lab.

EU vs. Southeast Asia labs:

European labs (SGS Netherlands, TÜV Rheinland, Bureau Veritas) are excellent but have 4–8 week queues and charge €10.000–20.000 per submission.

Labs in Shenzhen, many of which are CNAS-accredited and ILAC-recognised. Can turn around a standard IoT BLE/Wi-Fi submission in 5–10 working days at 40–60% lower cost. Insyght works with two such labs and manages the submission logistics for clients.

What to give the lab:

• 3–5 production-representative samples (not developer boards)
• Antenna tuned for mass-production units
• Full description of operating modes for testing
• List of applicable standards you are testing to

Timeline and Cost

For a typical BLE + Wi-Fi IoT sensor:

If you start the Technical File early (during design) and run pre-compliance testing before final PCB spin, you can reliably hit the low end of this range.

FCC (USA) and UKCA (UK)

FCC covers the US market. For BLE and Wi-Fi products, the key authorisation is FCC Part 15 Subpart C (intentional radiators). You can use a Supplier's Declaration of Conformity (SDoC) for most BLE/Wi-Fi products, which means no mandatory third-party certification, but you still need test data. Timeline: similar to CE. Many SE Asia labs that do CE also do FCC in the same submission.

UKCA is now required for products placed on the UK market post-Brexit. The standards are largely the same as CE (UK adopted EN harmonised standards as "designated standards"). Plan for UKCA if you're selling in the UK.

How Insyght Helps

Insyght embeds compliance planning from the first PCB spin, not as an afterthought. Our process:

1. Standards identification at PCB design kickoff, we flag applicable directives and which standards we'll design to
2. DFT layout review — we check antenna clearance, ground plane integrity, and filtering before laying out the PCB
3. Pre-compliance coordination - we can arrange informal testing at our partner lab in Shenzhen
4. Lab submission management - we handle the logistics, sample shipping, and engineer liaison at the accredited lab
5. Technical File drafting - we prepare the full Technical File and Declaration of Conformity

Standard IoT BLE/Wi-Fi CE certification through our process: under 2 weeks from sample submission.

Get in touch if you're planning a new connected product and want to build certification into the roadmap from day one.