EUProduct ReadyMARKET-ACCESS PREFLIGHT
EN

ELECTRONICS IN THE EU

Sell electronics in the EU — compliance preflight

Bring the common electronics layers into one evidence map, then add wireless, battery or digital-product checks when the product features trigger them.

Interactive preflightSource-backedNo signupNot a certification
Decision boundaryThis is a preflight. “Likely applies” still requires the official source and product facts to confirm legal scope.

QUICK ANSWER

What matters before you rely on a listing or supplier file

Electronics rarely have one single “EU compliance” rule. CE-route legislation, RoHS, WEEE, EMC and product-safety duties can overlap, with RED, batteries and CRA added by specific features.

WHO THIS IS FOR

Use this workflow when this is your decision

Brands and importers launching electrical or electronic equipment and needing one roadmap across CE-route legislation, RoHS, WEEE, batteries, GPSR and connected-product rules.

DECISION MAP

Resolve the questions in this order

This route is not a keyword shell: each step changes what evidence or market action should come next.

01

Build the technical product map

Voltage, radio, connectivity, battery and intended use determine which technical legislation and evidence layers are relevant.

02

Separate conformity from producer responsibility

CE, EMC, RED or LVD questions and WEEE, battery or packaging registrations are different workstreams with different evidence.

03

Plan cyber and lifecycle obligations for connected products

Connected functionality can add current or future security obligations beyond the electrical launch file.

EVIDENCE PACK

What a useful working file should contain

Names and formats vary by product regime. Keep evidence tied to the exact product, role and market rather than collecting disconnected PDFs.

Technical specification and BOM

Electrical ratings, radio modules, battery, software or firmware and component identity.

Conformity file

Applicable tests, standards rationale, risk or technical file and declarations for the exact marketed version.

Material and EPR file

RoHS evidence plus WEEE, battery and packaging producer-role or registration records.

Market presentation

Final labels, warnings, instructions, operator information and online listing fields by target market.

WORKED EXAMPLE

Wi-Fi rechargeable home device sold D2C

Facts

The team has EMC testing and a CE draft but has not mapped RED, RoHS, WEEE, battery, GPSR or CRA layers.

Practical review plan

Start from the technical feature map, build the applicable CE and RED evidence, then run the materials or EPR, battery, safety or listing and cyber timing workstreams separately so one successful test is not mistaken for complete EU readiness.

READY TO SEQUENCE THE WORK?

Turn this check into a launch roadmap

Use the launch planner to organise scope, supplier evidence, operator, labels, registrations, listing and post-market work by phase.

Open launch planner →

WHAT TO VERIFY

The scanner focuses on these evidence questions

  • CE route, EMC and technical documentation
  • RoHS material evidence
  • WEEE producer-responsibility layer
  • Add RED, batteries or CRA when product features trigger them

INTERACTIVE PREFLIGHT

Build an evidence-gap map for your product

Answer what you know. The engine maps product features, role and sales channel to rule cards and compares them with evidence you say you already have. It does not inspect or authenticate a document.

Rules 2026.10.01-1Verified 2026-10-01
Product features
Evidence you already have optional

Tick only evidence you actually hold. The scanner does not inspect or authenticate it.

COMMON QUESTIONS

Questions this preflight should help you frame

Does every electronic product need the same CE tests?

No. The applicable legislation and conformity route depend on the exact product and features.

Does WEEE registration replace CE compliance?

No. WEEE is a producer-responsibility layer separate from technical product conformity.

What changes if the product has Bluetooth or Wi-Fi?

Radio functionality adds a RED scope check and can change the conformity route.