Freeze intended use, user, environment, power, radio modules, interfaces, app and cloud dependencies.
Category route · electronics
Connected hardware needs one product story across circuitry, radio, software and cloud.
A test report for one layer does not prove the finished product route. Define the production configuration, intended use and connectivity architecture before turning standards into purchase orders.
Route map
What must connect before market entry
Map every applicable framework; several EU product rules can apply to the same finished device.
Use applicable standards and risk controls while the design can still change.
Test the production-representative configuration and connect results to the technical documentation.
Control declaration, labels, instructions, software versions, economic-operator details and production changes.
What it costs
Electronics & connected devices: indicative EU entry budget for 2026
- One-off budget
- €7k–19.8kdesign frozen · €8k–23.4k from concept
- Per year
- €1k–2.5kkeeping the product compliant
- Route duration
- 14–29 weeks22–40 weeks from concept
Applies to low-risk electronics on the LVD/EMC route. Radio, connected software and cybersecurity add scope that is priced separately. EUR excluding VAT, planning orientation, not a quote. Full tables, method and unpriced triggers: EU Regulatory Entry Cost Index 2026.
Resolve early
Questions that change the route
- Does the product intentionally transmit or receive radio?
- Which functions disappear if the app or cloud service is unavailable?
- Does it process personal, health, location or authentication data?
- Are batteries, chargers, external power supplies or accessories part of the placed-on-market product?
- Could claims or intended use move the product toward a medical-device route?
Budget drivers
What changes the cash case
Radio, EMC, electrical safety and environmental evidence may require different laboratories or combined test planning.
Pre-certified modules can reduce some work, but they do not transfer responsibility for the finished product.
Firmware changes, enclosure changes and alternative components can affect previous evidence.
Cybersecurity work is an engineering and lifecycle cost, not a final-week document.
Evidence room
What a defensible launch leaves behind
- 1Controlled hardware, firmware and software configuration
- 2Risk analysis and standards / requirement map
- 3Test plans, reports and component evidence
- 4Technical documentation and EU declaration where required
- 5Labels, instructions, update and vulnerability-handling records
Official starting points
Use the rule that fits the product—not the nearest label.
These links explain general obligations. Product classification, claims and market role determine the specific route.
Your configuration