CE Marking Isn't Just RoHS: The Other Directives Hiding in Your Technical File

Teams sometimes treat CE marking as a RoHS checkbox with extra paperwork. It isn't. The CE mark is the EU's general declaration that a product meets every legislative regime that applies to it — RoHS is frequently just one of several.

A wireless charging pad, for example

Take a fairly ordinary consumer electronics product: a wireless charger. Depending on its features, it may need to satisfy:

• RoHS — substance restrictions in the electronics and cabling
• The Low Voltage Directive — electrical safety for the voltage range it operates in
• The EMC Directive — electromagnetic compatibility, so it doesn't interfere with (or get disrupted by) other devices
• The Radio Equipment Directive — if it includes any wireless charging protocol or radio functionality

CE marking is unlawful if any one of these fails, regardless of how well the product performs against the others. A product with excellent RoHS documentation and a missing EMC test report is not CE compliant — it's non-compliant with a strong first chapter.

Where this breaks down in practice

The most common failure isn't a missing test. It's a technical file assembled by whoever handled the most recent directive, with earlier work from a different team, a different year, or a different contract manufacturer left un-integrated. Nobody owns the full bundle, so nobody notices the gap until an authority asks for it.

What holds up under scrutiny

• One technical file per product, indexed by directive, not scattered across whichever team happened to handle each regime.
• A single named owner who can answer "is this product still fully CE compliant" without convening three departments.
• Explicit sign-off against the full applicable set — determined at the design stage, not assumed from the product category.

CE marking rewards teams that treat it as a bundle from day one. It punishes teams that treat it as a sequence of separate, disconnected approvals.