Reg (EU) 2024/2847Generate dossier — €149
LIVE — Enforcement tracker · Deadline dashboard · Transposition status — Updated weekly from EUR-Lex, Safety Gate, OEIL & 12 official sourcesView regulatory intelligence →

You manufacture WiFi, Zigbee and Bluetooth modules in Shenzhen and sell them to OEM customers worldwide. Article 3(1) of Regulation (EU) 2024/2847 defines a product with digital elements as including "software or hardware components being placed on the market separately." If your module is sold as a standalone component on the EU market, it is a product with digital elements. It needs Annex VII documentation. CRACheck generates it.

The CRA draws a clear line: components placed on the market separately are products with digital elements and must comply independently. If your ESP32-based WiFi module is sold on Mouser, Farnell or directly to EU OEMs as a standalone part, Article 3(1) applies. The module needs its own technical documentation under Annex VII. Your OEM customers will also ask for documentation to fulfil their Art. 13.5 due diligence obligation on third-party components. CRACheck generates 8 PDF documents per module. 15-25 minutes. €149 per module model. Browser-side.

Generate CRA dossier — €149Free: check your product classification

€149 one-time · 8-document ZIP · 15-25 minutes · Browser-side

Regulation (EU) 2024/2847 · Art. 31 + Annex VII · 8 documents · 100% browser-side

Key numbers

Art. 3(1)
Components placed on the market separately are products with digital elements. CRA applies.
Annex III.13-15
Microprocessors, microcontrollers, ASICs and FPGAs with security-related functionalities = Class I.
€149
Per module model. Documentation for the module as a standalone product.

CRA documentation for a Chinese wireless module manufacturer

Your OEM customer's CRA compliance starts with your module's documentation. Provide it before they ask.

1
Determine if your module is placed on the market separately
Sold on Mouser, Farnell, LCSC, directly to OEMs as a standalone SKU? Then it is a product with digital elements under Art. 3(1).
2
Classify the module
WiFi/BLE/Zigbee module without security-related functionality: Default. Module with cryptographic functions, secure boot, secure element: may be Class I under Annex III points 13-15.
3
Generate CRA dossier
Enter your module's specifications: radio interface, firmware, SDK, protocol stack, security features, OTA capability. 15-25 minutes.
4
Provide to OEM customers
Your OEM customers need your module's CRA documentation to fulfil their Art. 13.5 due diligence. Delivering it proactively is a competitive advantage.
5
Maintain with firmware updates
When you release a new SDK version or firmware update, regenerate the documentation. Art. 31.2 requires continuous updates.

Your OEM customer's CRA compliance starts with your module's documentation. Provide it before they ask.

Wireless module CRA mistakes

ART. 3(1)

We sell a component, not a finished product — CRA does not apply

Article 3(1) of Regulation (EU) 2024/2847 explicitly includes "hardware components being placed on the market separately" in the definition of product with digital elements. If your WiFi module is sold as a standalone component, it is a product with digital elements. The CRA does not distinguish between finished products and components placed on the market separately.

ANNEX III.14

Our module is a simple radio transceiver — not a security device

Annex III points 13-15 list microprocessors, microcontrollers, ASICs and FPGAs "with security-related functionalities" as Class I. If your module integrates secure boot, hardware encryption, secure key storage or a trusted execution environment, it has security-related functionalities. A module with an ESP32's flash encryption or secure boot feature may fall under this classification.

ART. 13.5

Our OEM customers handle compliance — they integrate our module into their product

When your module is integrated into an end product and not sold separately, the end-product manufacturer has the CRA obligation. But Art. 13.5 requires them to exercise due diligence on third-party components — your module. They will request your module's cybersecurity documentation. If you also sell the module separately on the market, it needs its own Annex VII documentation.

What each CRACheck dossier contains: 8 documents

Wireless modules are the building blocks of IoT products. CRACheck generates 8 documents covering the module as a standalone product with digital elements.

1

Product Classifier

Determines product category per Annex III. Defines conformity assessment route under Art. 32.

2

Technical Documentation

Complete technical documentation structured per Art. 31 and Annex VII. All 8 mandatory sections.

3

Risk Assessment

Cybersecurity risk assessment per Art. 13.2 and Art. 13.3. Mapped against Annex I Part I requirements.

4

User Information

Information and instructions per Annex II. Security properties, support period, vulnerability reporting.

5

Declaration of Conformity

EU declaration of conformity per Art. 28 and Annex V.

6

CVD Policy

Coordinated Vulnerability Disclosure policy per Annex I Part II.

7

ENISA Notification Template

Pre-structured for 24h early warning, 72h notification, 14-day final report under Art. 14.

8

Obligations Calendar

Key dates: Art. 14 from 11 Sep 2026, full enforcement 11 Dec 2027, support period per Art. 13.8.

Mira antes de comprar — Descargar dossier de muestra (PDF, empresa ficticia) — Estructura real, artículos reales, formato real. Datos ficticios.

Generated in your browser. No product data is transmitted to any server.

What you pay for module CRA documentation

🧾 COMPONENT CERTIFICATION CONSULTANCY
€8,000–€20,000
Per module platform. 3-6 months. Includes radio + cybersecurity.
✓ CRACHECK
€149
8 CRA documents. 15 min. Radio certification (RED) handled separately.

Cybersecurity documentation vs. radio certification

● LAYER 1

What CRACheck does

Generates Annex VII documentation for your wireless module as a standalone product. Covers firmware, SDK, protocol stack, security features and vulnerability handling.

∅ LAYER 2

What CRACheck does NOT do

CRACheck does not perform RED radio testing, measure RF emissions or certify your module for specific frequency bands. CRA covers cybersecurity. RED covers radio compliance. Both needed for wireless modules.

We document cybersecurity. Your RED lab handles radio.

CRA penalty regime — Article 64 of Regulation (EU) 2024/2847

Article 64 establishes three tiers of administrative fines. Penalties are calculated per undertaking — but non-compliance on a single product can trigger inspection of your entire portfolio.

🇪🇺
Non-compliance with essential cybersecurity requirements (Annex I) and Art. 13/14 obligations
€15M / 2.5%

Art. 64.2. Up to €15 million or 2.5% of total worldwide annual turnover, whichever is higher.

🇪🇺
Non-compliance with technical documentation (Art. 31), authorised representative (Art. 18), conformity assessment (Art. 32)
€10M / 2%

Art. 64.3. Up to €10 million or 2% of total worldwide annual turnover, whichever is higher. Includes failure to produce Annex VII documentation.

🇪🇺
Supply of incorrect, incomplete or misleading information to authorities
€5M / 1%

Art. 64.4. Up to €5 million or 1% of total worldwide annual turnover, whichever is higher.

Art. 64.5 accounts for the nature, gravity and duration of the infringement, and gives consideration to microenterprises, small and medium-sized enterprises, including start-ups.

Alternatives

AlternativeCostWhat you get
Component certification consultancy€8,000–€20,000RED + CRA. 3-6 months.
Provide only RED certification€0 additionalRED covers radio. CRA covers cybersecurity. Separate.
Let OEM customers handle CRA€0OEM customers will ask for your module's documentation. No docs = no design-in.
CRACheck€1498 CRA docs. 15 min. Per module model.

Your module portfolio spans multiple radio technologies and platforms?

WiFi module, Zigbee module, BLE module, combo WiFi+BLE — each module model needs its own CRA dossier. Volume pricing: €99/module (10-pack), €79/module (30-pack).

Request volume pricing
Response within one business day.

What CRACheck guarantees and what it does not

CRACheck generates a structured document according to Article 31 and Annex VII of Regulation (EU) 2024/2847 from the information you provide. The accuracy, completeness and truthfulness of that information is your responsibility as the manufacturer.

We guarantee that the document structure follows Article 31 and Annex VII of Regulation (EU) 2024/2847 and that the legal references cited are correct as of the last verification date. We do not guarantee that a specific document will be accepted by a market surveillance authority in a specific case or by a commercial buyer in a procurement process.

CRACheck is not legal advice. For specific situations, consult a lawyer or specialised regulatory consultancy.

Frequently asked questions

Does CRA apply to a module that is only sold to OEMs and never to end users?
If the module is placed on the EU market separately (sold as a standalone component), Art. 3(1) applies regardless of whether the buyer is an OEM or an end user. B2B placement is still market placement under Art. 2.1.
If our module is integrated into a product and never sold separately, do we need CRA documentation?
If the module is not placed on the market separately, it is not independently subject to CRA. The end-product manufacturer documents the complete product. However, under Art. 13.5, the end-product manufacturer will request documentation of your module's cybersecurity properties for their due diligence.
Is an ESP32-based module Class I because of its secure boot feature?
Annex III points 13-14 list microprocessors and microcontrollers "with security-related functionalities." If the ESP32's secure boot, flash encryption or cryptographic acceleration are exposed as features of your module, classification as Class I under Annex III point 14 is possible. If your module disables or does not expose these features, Default classification may apply. Use the CRACheck classifier.
Does CRA documentation for the module reduce the documentation burden for our OEM customers?
Yes. If you provide Annex VII documentation for your module, your OEM customer can reference it in their product's technical documentation to satisfy Art. 13.5 due diligence. Your documentation becomes an input to theirs. It reduces their effort and strengthens their compliance case.
Is this a subscription?
No. One-time payment. The licence includes 30 days of editing and 10 regenerations. The downloaded PDF is yours to keep.
Can I request a refund?
Pursuant to Art. 16(m) of Directive (EU) 2011/83 on consumer rights, by activating the licence you give express consent for the immediate generation of the digital content, waiving the 14-day withdrawal period. Refunds are accepted only for reproducible technical failures.
What if the regulation changes?
If the regulation changes during the validity of your licence, you can regenerate the document with the updated version of the generator at no additional cost.
⚠️ Important notice: CRACheck is a self-assessment documentation tool, not legal advice and not a third-party audit. The document under Article 31 and Annex VII of Regulation (EU) 2024/2847 is generated from your input data. You are responsible for the accuracy of the data you provide. CRACheck does not replace a qualified professional assessment.

Your wireless module is a product with digital elements. Annex VII documentation is required. Generate it — 15 minutes, €149.

€149 one-time payment
8 professional documents · 15-25 minutes · No subscription · 100% in your browser
Generate CRA dossier — €149
✓ Last regulatory check: 1 May 2026 · No substantive changes detected · View history