CE Self-Declaration or Notified Body?Choose Wrong and the Money Is Wasted

The short answer first: the majority of ordinary electrical and electronic products can take the self-declaration route (Module A, internal production control). You carry out the assessment, sign the Declaration of Conformity (DoC) and affix the CE mark yourself, with no third-party involvement. Wireless products are where the exceptions cluster: under the RED (2014/53/EU), wireless products that no harmonized standard covers, or that are assessed against non-harmonized standards, usually need a notified body (NB) to issue an EU-type examination certificate.

Choose the wrong route and the cost is not just "an extra test fee". Take the route you should not have taken and the DoC will not hold up legally: marketplace reviews and customs may both reject it. The reverse hurts too — go to an NB for a product you could have self-declared, and the extra type-examination fee and time are simply wasted.

This article answers four things only: which route your product takes, who signs the documents, how long it takes, and where the money goes.

1. Three routes to CE: self-declaration, NB type examination, and the de facto third option

Under the current CE system, conformity assessment is divided into modules. In consumer-goods exports there are in practice only three ways to go.

Module A: internal production control (self-declaration)

The manufacturer completes all testing and assessment, signs the DoC and affixes the CE mark itself. No NB involvement. It covers the majority of low-risk electronic products — an ordinary Bluetooth speaker on the RED + EMC route, for example. The precondition is that the manufacturer can complete a full compliance assessment, either in an in-house laboratory or by commissioning a third-party testing body to issue reports.

Module B+C / Module H: NB involvement

The notified body issues an EU-type examination certificate. This is the route the regulation itself reserves for cases where a third party is required, and it covers high-risk products and cases that standards do not reach.

The third one: third-party test reports (not mandatory by law, close to essential commercially)

Strictly speaking this is not a "conformity assessment route" at all: the regulation does not require ordinary electrical and electronic products to be tested by a third party. In practice, though, customers, e-commerce marketplaces and market-surveillance spot checks all ask for the "report". So the usual industry approach is to self-declare under the regulation and, at the same time, commission a qualified laboratory to issue test reports, then use those reports to support the DoC. You stay inside the route rules and still have documents you can hand over.

2. When an NB is mandatory

There is really only one criterion: does your product have a usable harmonized standard, and does the directive place this type of product directly into the "third party required" category?

• Products under RED that use non-harmonized standards, or that fall in non-harmonized frequency bands. The majority of Bluetooth and WiFi devices use standard bands and modulation schemes and can self-declare on the basis of harmonized-standard testing. If a non-standard modulation scheme or a non-harmonized band is involved, an NB must issue the EU-type examination certificate.
• Devices in the specific wireless bands covered by Article 3.3 of the RED. In these cases the directive itself requires third-party involvement, and a self-signed DoC is not enough.
• Medical devices (MDR), personal protective equipment (PPE), some construction products (CPR). These three are the categories generally recognised in the CE system as requiring an NB, and the logic is different from electronics — do not assume "I make earphones and never needed an NB" applies to them.

If you are unsure whether your modulation scheme, band and power count as "covered by a harmonized standard", do not guess. The applicable directive and harmonized standards govern, so have a body assess your actual RF parameters and make a determination. That step takes far less time than reworking the project afterwards.

3. Where RED and LVD / EMC divide: why wireless products trip up so easily

The same Bluetooth speaker can fall under three directives at once. The threshold for third-party involvement differs sharply across the three, which is where misjudgments usually start:

Keep three points in mind and the picture stays clear:

• Of the three, RED is the one where "route" and "standard coverage" are tightly linked. For ordinary EMC and LVD products it is internal production control all the way; for RED it depends on whether the band and modulation scheme you use fall within a harmonized standard.
• LVD has an explicit voltage threshold. The directive states 50-1000V AC or 75-1500V DC. Low-voltage products below that range fall outside the scope of the LVD. Note, though, that this is a question of regulatory applicability, not of whether the customer wants a report — many customers will still ask for a safety report.
• EMC covers a lot of ground. If there is a circuit, it nearly always applies. It is rarely the subject of a "do I need an NB?" dispute, but it is often what trips you up when a report is missing an item.

These three are not a "pick one and stop there" list but cumulative: a Bluetooth speaker with a power adapter needs RED + EMC + LVD + RoHS documentation all in place together. If any single directive requires an NB, the conformity assessment of the whole unit follows the NB route.

4. Technical file and DoC: who signs, what is signed, how long it is kept

Self-declaration does not mean nothing has to be kept on file. Quite the opposite: the core obligation is to keep the evidence complete. The technical documentation (TCF) must be retained for at least 10 years, and market-surveillance authorities may request it at any time.

The DoC (EU Declaration of Conformity) is the front page of the whole file. Under ISO/IEC 17050-1, a valid DoC needs at least these seven items:

Who signs? The manufacturer, or its EU authorised representative — one responsible party. It cannot be "signed on your behalf by the laboratory". And a hard requirement applies here: non-EU manufacturers must appoint an authorised representative within the EU, and the representative's details must appear on the product or its packaging. A CE mark without an EU representative is non-compliant, and marketplace reviews check for this more and more often.

What goes in the NB field? If an NB is involved, state its name, number and certificate number accurately; if there is none, leave the field empty, and certainly do not borrow someone else's number. Get this wrong and the problem is no longer "incomplete information" but a false document.

While we are on the subject, a few more hard requirements that are easily missed: the CE mark must be at least 5 mm high and its proportions must not be scaled at will; it must appear on the product itself, on the packaging and in the instructions; the instructions must include the official language of the country of sale and at least English.

5. Four frequent misjudgments: finished products, modules, wireless charging, stacked directives

① Bluetooth / WiFi finished products: you can go wrong either way

Two opposite mistakes are common. One is "wireless products always need an NB", so even a 2.4GHz Bluetooth earphone goes to an NB for type examination — an extra fee and several extra weeks of waiting. The other is "anything with CE can be self-declared", so a product built on a non-standard modulation scheme still ships with a self-signed DoC, and the file does not survive scrutiny. The right approach is to check first whether a harmonized standard covers your RF parameters, and only then decide the route.

② Wireless modules: a module passing does not mean the finished product passes

The module maker supplies a report, and the finished-product maker often treats it as proof that the finished product complies. That does not hold up. The finished product still has to assess its own main board, antenna layout, enclosure, power supply, interfaces and the EMC behaviour of the whole unit. Whether the module report can be reused, and how much of it, depends on whether the finished-product configuration matches the state in which the module was tested — and that has to be confirmed with the laboratory before the project starts, not left to be discovered just before shipment.

③ Products with wireless charging: an entire block gets missed

Many teams treat wireless charging as part of "the power supply", test only safety and EMC, and forget that it is itself a wireless transmitting / inductive device within the scope of the RED, which must be assessed against the relevant harmonized standards for short-range devices; products used close to the body also need SAR considered. For phone accessories, earphone charging cases and wearables, skipping it leaves a whole block of the file missing.

④ Stacked directives: if one needs an NB, the whole unit takes the NB route

The more functions a product packs in, the more directives apply. A Bluetooth speaker with an adapter is RED + EMC + LVD + RoHS; a doorbell with a camera adds data and privacy compliance considerations. Judge at the level of the "finished product"; do not let each module clear its own package and call it done.

6. What marketplaces and customs actually look at

The regulatory route is one thing; who actually checks you, and what they check, is another. Three checkpoints, each with different criteria:

Falling short costs more than "supplying another document": delisting, goods detained by customs, fines — and fines can reach 4-6% of global annual turnover. For brand-owning companies this is a real commercial risk; for contract factories it shows up directly as lost orders.

In practice, then, the industry settles it the same way: even when the regulation allows self-declaration, a qualified laboratory is still commissioned to issue reports. Not because it is mandatory, but because customers, marketplaces and customs want to see something verifiable. That is also why "do I need an NB?" and "should I run tests?" have to be discussed separately — the first is the legal route, the second is the commercial deliverable.

7. Process, lead times and cost structure

Lead time per item, assuming normal scheduling and no major rework:

Note that these are per-item lead times. In practice the items run in parallel across a project, but any rework and retest restarts the clock. If NB type examination is involved, add the body's scheduling and technical-file review time — that part is subject to the assessment of the body; do not commit to delivery dates on a laboratory's turnaround.

Cost structure breaks down roughly into these blocks:

• Testing fees: calculated by directive, number of items and number of bands; the more complex the functions, the higher the fee.
• Technical file and DoC preparation: some bodies include it in the testing, others list it separately.
• NB type-examination fee: arises only when an NB is needed, and is an order of magnitude higher than routine testing.
• EU authorised representative: an annual service fee, and a mandatory item.
• WEEE registration by country: registered country by country; Germany is relatively expensive and requires ongoing reporting.
• Rework and retesting: leave headroom in the budget — this is the item that tends to overrun.

For reference, the order of magnitude: a simple Bluetooth speaker (RED + RoHS + EMC) runs roughly RMB 8,000–15,000; adding a power adapter brings in LVD and about another 2,000–4,000. If NB involvement is genuinely required, the cost multiplies several times over. Specifics are subject to the assessment of the body — product configuration, bands and the number of target countries all affect the quotation.

8. Common traps, and a decision checklist

After many years of projects, rework and wasted money cluster in the five places below:

• Presenting a "report" to a customer as a "certificate". The two terms are not interchangeable, so you spend the rest of the project explaining; in serious cases it is treated as a false document.
• Defaulting every wireless product to an NB. Products covered by harmonized standards could have been self-declared, and the extra type-examination fee and time never come back.
• Missing DoC elements. No directives listed, no standards listed, no signatory position or date — such a DoC counts for nothing in a spot check.
• No EU representative, or the EU representative's details not printed on the packaging. Non-EU manufacturers must appoint one; it is a hard requirement, not an option.
• Technical documentation not systematic, and retention too short. The requirement is at least 10 years; if you cannot produce it during a spot check you are in a weak position.

Two more that are easily overlooked: after Brexit the UK runs its own UKCA system and currently still accepts the CE mark (for the majority of product categories), but new projects go straight to UKCA to save conversion cost later; WEEE must be registered country by country in the country of sale, and selling in Germany without registration carries a risk of fines.

Decision checklist: a 5-minute self-check

Run through these questions in order and the route is basically clear:

1. Does the product have wireless transmitting / receiving functions? Bluetooth, WiFi, NFC/RFID and wireless charging all count. Yes → within RED scope.
2. Are the bands and modulation scheme used covered by a harmonized standard? Covered → self-declaration is available; not covered or uncertain → assess the NB route.
3. Is it an MDR / PPE / CPR product, or a specific device of the RED Article 3.3 kind? Yes → NB required.
4. Is it mains-powered, with voltage within 50-1000V AC / 75-1500V DC? Yes → do LVD as well; No → decide whether to add a safety report based on what the customer requires.
5. Does it contain circuits? Yes → EMC + RoHS are basically unavoidable.
6. Are all seven DoC elements present, who signs it, is there an EU representative? Fill any gap first.
7. Can the technical documentation support 10 years of retention? No → build the archive now.
8. Do the target marketplaces and customers require CNAS reports or a specific standard version? Yes → confirm in advance; do not wait until the report is out to change it.

Pick the right route and the money goes where it should; pick the wrong one and both the money and the lead time are wasted. There is no trick to it: line up the directive, the standard and the module, then keep the documents complete and in order.

▍If you have questions about this article, leave a comment or message me, with the note "CE"

▍One-line value proposition: We help you get export certification done and clear customs smoothly.

Further reading: EU CE/RED knowledge base, complete guide to the CE mark, EU CE certification services, how to do EU CE for Bluetooth earphones, UK UKCA/PSTI.