Common CE marking errors — scope, assessment and evidence
Common pitfalls in CE marking, representative mandates, assessment routes and regulatory penalties, with primary references and product-evidence checks.
By CenitiaUpdated
Ten checks before issuing a declaration: confirm scope; confirm placing date; verify product identity/version; identify the actual assessment route; verify applied dated specifications; check test/report scope; record required NB/certificate details; apply the act-specific CE/NB-number rule; establish the appropriate responsible EU economic operator; and retain the issued record and supporting evidence. These are review checks, not ten automatic fines.
CE and notified-body number
Article 20(3) requires the NB identification number following CE when the Annex IV full-quality-assurance procedure is used. NB participation in type examination does not alone trigger that CE-adjacent number. Manufacturer documentation retention is Article 10(4); authorised-representative retention is Article 11(2)(a).
Penalty categories
Article 64(2) covers specified Annex I and Articles 13/14 non-compliance, with a maximum of EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher. Other categories have different limits. Article 64(10)(a) contains a micro/small enterprise exception concerning failure to meet the early-warning deadline, not exemption from reporting duties. Maximum penalties are not automatic fines or proof of personal liability for every signer.
Authorised representative
A manufacturer may appoint an authorised representative by written mandate. Article 18 restricts transfer of specified manufacturer obligations including design/manufacture and preparation of technical documentation. Annex VIII Part I point 5 permits specified marking/declaration tasks within the mandate. Do not confuse an authorised representative with the alternative responsible economic operators allowed under applicable market-surveillance law.
Conformity assessment
For Article 3(1) requirements, Article 17(2) permits A, B+C or H. For Article 3(2)/(3), Article 17(3) permits A, B+C or H where applicable OJ-listed harmonised standards are fully applied; absent/partially applied standards, Article 17(4) requires B+C or H. Check exact editions, scope and OJ restrictions. EN 18031 citations under 2025/138 carry limitations; neither EN 18031 nor ETSI EN 303 645 automatically gives CRA presumption of conformity.
Conformity assessment A, B+C and H
Annex VIII offers internal control (A), EU-type examination plus conformity to type (B+C), and full quality assurance (H). Standard products may use A. Important Class I A depends on Article 32(2) full coverage through applicable harmonised standards, common specifications or qualifying certification; otherwise B+C or H. Class II uses B+C or H under Article 32(3). Article 32(5) allows qualifying important free/open-source software with public technical documentation to use A. Critical products require assessment of Article 8 certification conditions; absent the mandated suitable scheme conditions, Article 32(4) provides B+C or H. Classify the main product function against Annexes III/IV and implementing technical descriptions 2025/2392, not a component name alone.
Evidence to keep with the product
Record the intended purpose, responsible economic operator, target market, first placing date and exact hardware/firmware configuration. For each applicable requirement, link the actual test or assessment record, dated standard/specification, scope and reviewer decision. Proposed controls and supplier marketing statements are not evidence that the final configuration has passed an assessment.
Separate an open question from a completed assessment. A report outside the laboratory's relevant scope, a different firmware build or an unverified exemption needs a reasoned decision before it supports a declaration. Keep original evidence and the issued declaration alongside any AI-assisted working draft.
Using Cenitia for this work
Cenitia assists with a limited regulatory catalogue and draft documents. The manufacturer must confirm applicability, actual applied specifications and completed assessment procedures. AI scores are quality signals, not a probability of conformity. Source monitoring raises a review prompt when validated source text changes; it does not automatically verify amendments, update the corpus or monitor every national rule and OJ standard edition. Public QR verification records issuance, not product certification.
Review status
This guide was substantively corrected by Cenitia on 2 October 2026 using the primary references below. It is an editorial summary, not an authoritative legal quotation or an independently signed expert opinion. Product-specific and licensed-standard questions remain subject to a real technical review.
Primary references
FAQ
Frequently asked questions
Does an AI draft or QR verification prove conformity?
No. The manufacturer must establish scope and satisfy applicable requirements using actual evidence. QR verification records issuance, not product certification.
What information must be checked for this product?
Confirm intended use, role, market/date, final configuration, dated specifications, assessment route and evidence scope. Record unresolved questions and a real reviewer decision.
Continue reading
Related guides
reference
Conformity assessment — selected routes under CRA, RED, machinery and MDR
Selected conformity-assessment routes and category checks under CRA, RED, machinery and MDR, with the evidence needed to justify the route for a product.
4 min read
guide
When you need a Notified Body — the EU CE marking decision guide
Selected RED, CRA, machinery and MDR route conditions that can require a notified body, with classification and evidence checks for the actual product.
4 min read
guide
CE Marking 101 — essential requirements and conformity evidence
A concise overview of RED marking and declaration rules, CRA declaration requirements, and the product evidence needed to support a manufacturer’s CE claim.
3 min read
tutorial
Coordinated Vulnerability Disclosure Policy for Hardware Manufacturers
Build a usable hardware vulnerability disclosure policy with intake owners, safe testing boundaries and a security.txt example.
4 min read
Put this into practice
Free tools & references
- Do I need a Notified Body?Find out, per regulation, whether a Notified Body is required.Open tool →
- EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.