- Service Definition
- Full CE certification management: directive identification, Technical File compilation, lab testing coordination, and post-market SBOM surveillance.
EU CE Marking & Compliance — Full Lifecycle Management
CE marking is not a single stamp. It is a legal declaration covering multiple directives — and getting any one wrong makes the entire mark invalid.
Inovasense manages the complete CE compliance path for B2B hardware products — from Conformity Assessment Planning and architecture reviews, to laboratory testing coordination, Technical File compilation, and post-market SBOM surveillance. We work with both new product development (compliance built in from day one) and existing product redesigns (gap analysis and remediation). Book a Conformity Assessment Session →
What CE Marking Actually Means
CE marking is not a quality label or a single certification. It is a self-declaration (or Notified Body-attested declaration) that your product complies with all EU directives and regulations that apply to it. The manufacturer draws up a Declaration of Conformity and affixes the CE mark — taking full legal responsibility for the claim.
The complexity lies in the word all. Depending on what your product does, it may need to comply with two, five, or more different European directives simultaneously. Each directive has its own harmonised standards, test requirements, and conformity assessment routes.
Getting one directive wrong does not just fail that directive — it invalidates your entire CE mark and makes your product illegal to sell in the EU.
Which EU Directives Apply to Your Product?
The first mandatory step in any compliance project is Conformity Assessment Planning — identifying exactly which directives govern your product. The table below covers the directives most commonly applicable to B2B hardware, IoT, and embedded products:
| Directive / Regulation | EU Number | Applies When | Key Standards | Assessment Route |
|---|---|---|---|---|
| EMC Directive | 2014/30/EU | Any electronic device — virtually always | EN 55032, EN 55035, EN 61000-3-2/-3-3 | Self-declaration with harmonised standards |
| Low Voltage Directive (LVD) | 2014/35/EU | Equipment operating at 50–1000V AC or 75–1500V DC | EN 62368-1, EN 60335-1 | Self-declaration with harmonised standards |
| Radio Equipment Directive (RED) | 2014/53/EU | Any product with a radio transmitter or receiver (Wi-Fi, Bluetooth, LoRa, cellular, GNSS…) | EN 300 328, EN 301 893, EN 300 220, EN 303 413 | Self-declaration or Notified Body |
| RED Delegated Act | EU 2022/30 | Internet-connected radio equipment, plus childcare, toy and wearable radio equipment processing personal data — cybersecurity baseline | EN 18031-1/-2/-3:2024 (OJ-cited with restrictions) | Applies since 1 August 2025; repealed from 11 December 2027 (Reg. (EU) 2026/339) |
| Cyber Resilience Act (CRA) | EU 2024/2847 | Products with digital elements that have a direct or indirect data connection to a device or network | Harmonised standards being developed under request M/606; ETSI EN 303 645 and IEC 62443 as supporting references | Self-assessment (default; important Class I only where harmonised standards, common specifications or certification are applied); Notified Body or certification for important Class II and critical products |
| RoHS Directive | 2011/65/EU | Most electrical and electronic equipment | Material declarations, supply chain documentation | Self-declaration |
| Machinery Regulation | EU 2023/1230 (applies from 20 January 2027; Directive 2006/42/EC until then) | Machinery, safety components, interchangeable equipment | EN ISO 13849-1, IEC 62061, EN ISO 12100 | Self-declaration, or Notified Body for Annex I Part A categories |
| AI Act | EU 2024/1689 (as amended by EU 2026/1744) | Products with embedded AI classified as high-risk; obligations apply from 2 December 2027 (Annex III) and 2 August 2028 (Annex I products) | Harmonised standards in preparation; ISO/IEC 42001 as supporting reference | Internal control for most Annex III systems; Notified Body for certain biometric systems and under the sectoral procedure for Annex I products |
| ATEX Directive | 2014/34/EU | Equipment for explosive atmospheres (mining, chemical, oil & gas) | EN 60079 series | Notified Body for categories M1/1 and for electrical equipment and internal combustion engines in M2/2; internal production control for category 3 |
| Medical Device Regulation (MDR) | EU 2017/745 | Medical devices (in vitro diagnostics: IVDR, EU 2017/746) | EN ISO 13485, IEC 62304 | Notified Body for Class IIa and above, and for sterile, measuring or reusable surgical Class I devices |
Key principle: If your product is radio equipment (Wi-Fi, BT, LoRa, cellular), the RED applies instead of the EMC Directive and LVD for the whole product: their safety and EMC objectives are applied through RED Article 3(1)(a) and (b), with no voltage limit for safety. In practice, the same safety and EMC standards are used and all tests are often conducted in a single laboratory visit.
Two Paths to CE Compliance
Path A: New Product — Compliance By Design
If your product is in the concept or early design phase, compliance is an architecture input, not an afterthought. This is the most cost-efficient path:
- We conduct a Conformity Assessment Planning session during requirements definition — identifying all applicable directives, selecting harmonised standards, and deciding the self-declaration vs. Notified Body route.
- Compliance requirements are entered as formal system requirements in the V-model, traced through design to test cases.
- Component selection considers compliance from the start: the right MCU with hardware security (for CRA/RED Delegated Act), components with RoHS material declarations, EMC-conscious PCB layout rules baked into design reviews.
- Pre-compliance EMC screening is conducted at prototype stage — catching issues before the formal laboratory visit costs €3,000–8,000+.
- The Technical File is built iteratively throughout the project, not scrambled together at launch.
Result: Pre-compliance screening at prototype stage significantly reduces the risk of failure at formal certification — catching issues before a formal laboratory test campaign, not after. Technical File compiled in parallel with development, ready at product launch rather than scrambled together after it.
Path B: Existing Product — Gap Analysis & Remediation
If your product is already on the market or in final design, we assess the gap between your current state and full compliance:
- CRA & RED Delegated Act Gap Analysis — the most urgent review for connected products: the RED cybersecurity requirements have applied since 1 August 2025, CRA reporting since 11 September 2026, and the main CRA obligations apply from 11 December 2027.
- Full-Directive Gap Analysis — we review your existing Technical File (if any), test reports, BOM, and architecture against all applicable directives.
- For each gap, we provide a RAG (Red/Amber/Green) assessment: what passes, what needs remediation, and the exact engineering effort required.
- We then execute the remediation — whether that means a partial board revision, a new hardware revision, or only process/documentation changes.
Two regulations are creating compliance pressure for products already on the EU market — but they impose different levels of hardware obligation:
RED Delegated Act (Article 3(3)(d); EN 18031-1) — applies since 1 August 2025, repealed from 11 December 2027
EN 18031-1 — the harmonised standard cited for RED Article 3(3)(d) — requires software update integrity and authenticity verification [SUM-2] for internet-connected radio equipment. EN 18031-1 is technology-neutral: a properly implemented software-based signing chain can satisfy SUM-2. The standard explicitly accepts digital signatures, secure-channel delivery, or access-control combined with hash as valid implementation paths.
The practical caveat: the mechanism is only as strong as its keys. The private signing key stays with the manufacturer, ideally in a hardware security module, and never goes onto the device. The device holds only the verification key (its trust anchor), which has to be protected against replacement. If the signing key leaks, every device that trusts it will accept forged updates.
| EN 18031-1 Requirement | Can Firmware Satisfy It? |
|---|---|
| Unique or forced-change default credentials [AUM] | ✅ Yes — provisioning process change |
| Software integrity & authenticity [SUM-2] | ✅ Yes — software signing chain with documented key management |
| Secure storage [SSM] | ✅ Yes — the standard accepts encryption, access control or hardware protection; the method chosen has to be described and justified |
| Access control [ACM]; limited exposure of interfaces and services [GEC] | ✅ Yes — firmware and architecture changes |
| Authenticated communications [SCM] | ✅ Yes — TLS with documented cipher suites |
CRA (EU 2024/2847) — reporting since 11 September 2026, main obligations from 11 December 2027
The CRA raises the bar significantly, but its Annex I requirements are outcome-based and risk-based: it names no technology. An SBOM is required (Annex I, Part II(1)); secure boot and a hardware root of trust are common engineering controls that the risk assessment can call for. Where it does, firmware alone cannot provide them: they depend on hardware features, an immutable boot stage and protected key storage, that are fixed when the microcontroller and the board are chosen.
| Control (where the risk assessment calls for it) or CRA obligation | Can Firmware Fix It? |
|---|---|
| Hardware Root of Trust | ❌ Not by firmware alone. It needs hardware chosen at design time: a microcontroller with an immutable boot stage and protected key storage (boot ROM, OTP or eFuse, TrustZone, an integrated secure enclave), or a discrete Secure Element or TPM. A separate security chip is one option, not a requirement |
| Tamper-resistant key storage | ❌ Keys in ordinary flash can be read through the debug port or directly from an external flash chip, and the readout protection of several common microcontrollers has been bypassed by fault injection. Tamper resistance comes from hardware: protected key slots, a secure enclave or a Secure Element |
| Authenticated OTA updates | ⚠️ Signature verification runs in firmware and the device stores only the public key; the private signing key stays with the manufacturer. Hardware is needed so that this public key and the boot code cannot be replaced (immutable or write-protected storage) |
| Secure device identity (attestation) | ❌ An identity key kept in ordinary flash can be copied to another device; a key generated and held in protected hardware is designed never to leave it |
| SBOM + 24h early warning for actively exploited vulnerabilities (Art. 14) | ⚠️ Achievable in software, but requires dedicated tooling and process |
| Security updates for the support period (normally at least 5 years) | ⚠️ Achievable, but only if OTA infrastructure is genuinely secure |
Timeline: The main CRA obligations apply to products placed on the market from 11 December 2027. If the risk assessment shows that your hardware lacks an immutable boot stage or protected key storage, a board revision, re-testing and updated technical documentation have to be finished before that date. That is why the assessment should come first.
For a first self-check, the CRA readiness checker in Cenitia, our compliance software, walks through the questions that shape a cybersecurity preparation plan.
Our 4-Step CE Compliance Process
Step 1 — Conformity Assessment Planning
What it is: A structured session (2–4 hours, remote or on-site) where our engineers determine the complete compliance scope for your product.
What we establish:
- Definitive list of applicable EU directives and regulations
- Applicable harmonised standards for each directive
- Self-declaration vs. Notified Body route for each directive
- Pre-compliance testing strategy and laboratory partner selection
- Technical File structure and division of responsibilities
- Compliance milestone plan integrated with your product development schedule
Output: A Compliance Scope Document — the binding technical and regulatory specification that governs every subsequent compliance decision on the project.
Pricing: Fixed price from €1,400 for a single product. Credited toward the full project if you proceed.
Step 2 — Architecture Design or Gap Analysis
For new products: Compliance requirements from Step 1 are integrated into the hardware architecture. Component selection, PCB layout rules, security silicon selection (Secure Elements, TPMs), EMC shielding strategy, and software security architecture are all defined with compliance as a first-class input.
For existing products: We conduct a full architecture review against all identified directives. Our engineers analyse your BOM, schematics, block diagram, and firmware update mechanism. You receive a RAG Compliance Report — Red/Amber/Green assessment of every requirement — with exact remediation specifications: which components to replace, which architectural changes to make, and what the cost and timeline will be.
Specific capabilities:
- Common Criteria-certified Secure Element integration (STSAFE-A110, OPTIGA Trust M, SE050) as a hardware root of trust where the CRA risk assessment calls for one
- FPGA-based security functions for products requiring hardware-level crypto acceleration
- EMC-compliant PCB layout and grounding strategy
- Dual-source BOM with full RoHS material declarations
- Machinery functional safety (EN ISO 13849-1, IEC 62061) where applicable
- Edge AI compliance against EU AI Act risk classification
Pricing (Gap Analysis): Fixed price from €2,900 depending on architecture complexity. Turnaround: 5–10 business days for standard architectures; complex multi-directive or large-BOM products may require additional time. Fee credited toward full redesign project.
Step 3 — Testing Coordination & Technical File
We manage the laboratory testing process end-to-end:
- Pre-compliance EMC/EMI screening — conducted at prototype stage at our EU partner laboratories to identify failures before the formal test campaign; catching issues at this stage is substantially less expensive than re-tests at an accredited laboratory
- Formal laboratory coordination — we select the accredited laboratory, prepare test samples, write test plans, attend tests where feasible, and review test reports
- Technical File compilation — we build and maintain the full Technical File: product description, list of directives and standards, design documentation, risk assessment (EN ISO 12100 or IEC 62368-1 as applicable), test reports, and Declaration of Conformity
- Notified Body liaison — where third-party assessment is required (e.g. machinery listed in Annex I Part A, RED or CRA where harmonised standards are not fully applied, certain high-risk AI systems), we manage the complete Notified Body engagement
Standards we routinely handle:
| Standard | Directive | Covers |
|---|---|---|
| EN 55032 / EN 55035 | EMC | Multimedia emissions and immunity |
| EN 61000-3-2 / -3-3 | EMC | Power line harmonics and flicker |
| EN 62368-1 | LVD / RED | Audio/video and IT equipment safety |
| EN 300 328 | RED | 2.4 GHz (Wi-Fi, Bluetooth) |
| EN 301 893 | RED | 5 GHz (Wi-Fi 5/6) |
| EN 300 220 | RED | Sub-GHz (LoRa, Sigfox, 868 MHz) |
| ETSI EN 303 645 | RED Del. Act / CRA (supporting reference, not an OJ-cited harmonised standard) | Cybersecurity for consumer IoT |
| EN 18031 series | RED Del. Act | Network/privacy/anti-fraud baseline |
| IEC 62443-4-2 | CRA (supporting reference, not an OJ-cited harmonised standard) | Technical security requirements for components of industrial automation and control systems |
| EN ISO 13849-1 | Machinery | Safety-related control systems (PLr) |
| IEC 62304 | MDR¹ | Medical device software lifecycle |
¹ MDR projects are assessed individually — engagement subject to project scope and applicable quality system requirements.
Step 4 — Post-Market Surveillance & SBOM Monitoring
Compliance does not end at product launch. EU regulations impose ongoing obligations throughout your product’s market lifetime:
- SBOM monitoring — we help you set up continuous checking of your Software Bill of Materials against CVE databases (NVD, OSV, GitHub Advisory Database)
- CRA Article 14 reporting — we prepare and submit notifications of actively exploited vulnerabilities and severe incidents (24-hour early warning, 72-hour notification, final report) on your behalf via the single reporting platform to the coordinating CSIRT and ENISA; legal responsibility for the notification remains with you as the manufacturer (CRA requirement since 11 September 2026)
- Security advisory triage — our team assesses severity and impact for your specific bill of materials and deployment context
- OTA patch preparation — for products developed or co-developed with Inovasense, we prepare and test security patches ready for deployment
- Post-market surveillance file maintenance — tracking field incidents, complaints, and corrective actions as required by CE directives
- Quarterly compliance reports — formal documentation of ongoing compliance for auditors, customers, and regulatory enquiries
- Directive change monitoring — we track amendments to applicable harmonised standards and notify you when your Technical File needs updating
Pricing: Monthly subscription per product line, priced according to scope.
Who This Is For
This service is designed for:
- Hardware startups building their first connected product for the EU market — compliance planning before any silicon is committed costs far less than fixing it at prototype stage
- B2B electronics manufacturers with existing products subject to the RED Delegated Act (since 1 August 2025) and the CRA (reporting since 11 September 2026; main obligations from 11 December 2027)
- OEMs and system integrators whose end-customers (NIS2 entities) are now requiring documented proof of hardware compliance
- CTOs and engineering directors who need a data-driven compliance report to justify board redesign budget to leadership
- Companies with radio equipment (Wi-Fi, Bluetooth, LoRa, cellular) — subject to the RED Delegated Act cybersecurity requirements since 1 August 2025
- Industrial equipment manufacturers needing Machinery Regulation compliance for safety-critical control systems
- Edge AI product companies navigating EU AI Act conformity assessment alongside CRA
Why Inovasense
We are not compliance consultants who hand you a checklist. We are the engineers who design, build, and test the compliant hardware:
- Full hardware security stack — Common Criteria-certified Secure Element integration, secure boot implementation, post-quantum cryptography readiness
- FPGA design capability — custom security and signal-processing implementations in programmable logic when standard MCUs cannot meet requirements
- EU-based development and manufacturing — your product is developed and tested in the EU, with PCB fabrication and assembly at EU facilities and EU/EFTA components prioritised for critical subsystems, under EU IP and trade secret law
- Edge AI compliance — EU AI Act risk classification and conformity assessment for products with on-device inference
- Product lifecycle management — compliance is woven into V-model gate reviews from CR through DV/PV; not bolted on at the end
- Defense-grade methodology — a V-model process with requirements traceability, applied to commercial product compliance programmes
The Conformity Assessment Planning session is an engineering deliverable — not a sales call. And when you need the design and certification executed, the same team that planned the compliance path builds and certifies the product.
Start with a Conformity Assessment Planning Session
Fixed price from €1,400. NDA-first. Remote or on-site. We determine exactly which directives apply, which standards to use, and your full compliance roadmap — before you commit to any design decision or laboratory booking.
Existing product with urgent CRA/RED gaps? Our Gap Analysis starts from €2,900 with results in 5–10 business days. Gap Analysis fee credited toward the full project.
Book a Compliance SessionSources & Official References
- Cyber Resilience Act — Regulation (EU) 2024/2847 — EUR-Lex (Official Journal of the EU)
- NIS2 Directive — Directive (EU) 2022/2555 — EUR-Lex (Official Journal of the EU)
- RED Delegated Act — Regulation (EU) 2022/30 — EUR-Lex (Official Journal of the EU)
- Radio Equipment Directive — 2014/53/EU — EUR-Lex (Official Journal of the EU)
- EU AI Act — Regulation (EU) 2024/1689 — EUR-Lex (Official Journal of the EU)
- Machinery Regulation — Regulation (EU) 2023/1230 — EUR-Lex (Official Journal of the EU)
- EMC Directive — 2014/30/EU — EUR-Lex (Official Journal of the EU)
- Low Voltage Directive — 2014/35/EU — EUR-Lex (Official Journal of the EU)
- RoHS Directive — 2011/65/EU — EUR-Lex (Official Journal of the EU)
- Medical Device Regulation — Regulation (EU) 2017/745 — EUR-Lex (Official Journal of the EU)
- ATEX Directive — 2014/34/EU — EUR-Lex (Official Journal of the EU)
Guides in this area
EU Electronics Compliance: CE, CRA & RED
A product-specific CE roadmap for electronics: applicable legislation, evidence, assessment routes, RED cybersecurity and CRA responsibilities.
EU CRA Hardware Compliance Checklist
A risk-based CRA checklist for hardware: scope, product category, security requirements, SBOM, support period, reporting and conformity evidence.
CRA Vulnerability Reporting: Step-by-Step Guide
CRA Article 14 reporting has applied since 11 September 2026: scope, 24/72-hour awareness deadlines, final reports, SRP and operational preparation.
EN 18031 Compliance: What "Self-Assessment" Actually Means for Connected Hardware
What EN 18031 self-assessment actually requires under Module A — and where the documented compliance gaps most often appear for connected hardware.
RED Delegated Act & EN 18031: Hardware Requirements
RED Delegated Act and EN 18031: cybersecurity for radio equipment since August 2025, repeal from December 2027, and the gaps firmware cannot fix.
EU Hardware Legislation 2026: Complete Guide
Which EU rules apply to your hardware? Distinguish CRA, RED, AI Act, ESPR and NIS2 scope, application dates and product-specific obligations.
Frequently Asked Questions
What does CE marking actually require?
CE marking is not a single standard — it is a declaration that your product complies with all applicable EU directives and regulations. Depending on your product, this may include the EMC Directive, Low Voltage Directive, Radio Equipment Directive (RED), Cyber Resilience Act (CRA), RoHS, Machinery Regulation, and others. The first step is always identifying which directives apply before any testing or documentation begins.
Do I need a Notified Body for CE marking?
It depends on the directive. For EMC, LVD, and RoHS, you can self-declare conformity using harmonised standards (no Notified Body required). For RED, self-declaration is allowed if you use harmonised standards from the OJEU list. For machinery, a Notified Body is mandatory for the categories listed in Annex I, Part A of the Machinery Regulation (EU) 2023/1230, which applies from 20 January 2027; for medical devices, for all classes above Class I and for sterile, measuring or reusable surgical Class I devices. For CRA, the conformity assessment route (self vs. Notified Body) depends on the product risk category.
What is the difference between a Gap Analysis and a Requirements Workshop?
A Gap Analysis is for existing products — we analyse your current hardware architecture against applicable EU directives and identify what must change. A Requirements Workshop is for new products — we define compliance requirements from the start, so they are designed into the architecture rather than retrofitted. Both result in a binding Technical Specification that guides design and certification.
When does the CRA become mandatory?
Reporting of actively exploited vulnerabilities and severe incidents has applied since 11 September 2026. From 11 December 2027, products placed on the EU market must meet the CRA's risk-based requirements (vulnerability handling, SBOM, security updates for normally at least 5 years); otherwise they may not be CE-marked or sold.
What is included in a Technical File?
A Technical File (required for CE marking) includes: product description and intended use, list of applicable directives and harmonised standards, design documentation (schematics, BOM, software description), risk assessment, test reports, Declaration of Conformity, and for CRA: the SBOM and vulnerability management plan. We compile and maintain this documentation as a living deliverable throughout the project.
How much does CE compliance management cost?
It depends on which directives apply and your product complexity. A Conformity Assessment Planning session starts from €1,400. A full Gap Analysis for existing products starts from €2,900. New product compliance design is included in the V-model project scope. Post-launch SBOM and post-market surveillance is priced according to scope. Contact us for a tailored quote.
Regulatory References (Authority Source)
- EU Cyber Resilience Act (2024/2847) (opens in new tab)
- Radio Equipment Directive (2014/53/EU) (opens in new tab)
- RED Delegated Act (EU 2022/30) (opens in new tab)
- EMC Directive (2014/30/EU) (opens in new tab)
- Low Voltage Directive (2014/35/EU) (opens in new tab)
- RoHS Directive (2011/65/EU) (opens in new tab)
- Machinery Regulation (EU 2023/1230) (opens in new tab)