Explore Cenitia’s compliance workflow and availability.Cenitia compliance workflow

How it works →
Cenitia
How it worksLibraryGlossaryRegulationsToolsAbout
Reserve your spot
How it worksLibraryGlossaryRegulationsToolsAbout

On this page

  • Start with the product, before opening the certificate
  • Classify the documents you received
  • Check the declaration as a controlled document
  • A model review: the antenna mismatch
  • Verify the issuer and close the gaps
  • Before relying on the result
← Library
tutorial·CEMark, RED, EMC, RoHS·5 min read

How to Verify CE Documents from an Electronics Supplier

Check product identity, declarations, test reports and supplier gaps before accepting CE evidence for an electronics order.

By Cenitia · 5 October 2026

Verify CE documents by matching the declared product to what you are buying, checking the applicable legislation and assessment route, and tracing the declaration to supporting evidence. A PDF headed “CE certificate” is not, by itself, proof that your finished product is compliant.

This workflow is for an electronics buyer receiving an unfamiliar supplier evidence pack. It helps identify gaps before an order or release decision. It does not establish conformity through a document check alone.

Start with the product, before opening the certificate

Write down the manufacturer, purchase SKU, supplier model, hardware revision, firmware version, power supply, radio options and intended use. Request the same identifiers for the tested sample. Keep a photograph of the label and the commercial specification alongside the documents.

A commercial SKU can differ from a laboratory model. That is not automatically a problem, but you need an explicit mapping. “Same series” is too vague when the series includes different antennas, mains adapters or enclosures. Ask which differences were assessed, by whom and where the assessment is recorded.

Use the supplier review worksheet to record each question and its answer. Keep “received”, “checked” and “accepted for this product” as separate states.

Classify the documents you received

DocumentWhat it can establishWhat it cannot establish alone
EU Declaration of ConformityThe manufacturer's declaration for an identified product and listed legislationThat every supplied unit matches the assessed design
Test reportResults for described samples, configurations and methodsCompliance outside its tested scope
EU type examination certificateA notified body's assessment within a particular legislative procedure and scopeThat all production units or all applicable laws are covered
Voluntary certificateThe issuing organisation's stated assessmentThat a legally required conformity procedure was completed
Supplier material declarationA stated material compliance position for an identified itemThe identity or chemical composition of unrelated parts

The Commission explains that the required procedure depends on the legislation; some procedures permit manufacturer assessment and others involve a notified body. A third party certificate is therefore neither universally mandatory nor universally sufficient. See its conformity assessment guidance.

Check the declaration as a controlled document

For radio equipment, use RED Article 18 and Annex VI as the declaration checklist. Check the product identification, manufacturer details, responsibility statement, declared legislation, standards or other specifications, any relevant notified body information and the authorised signature. The exact declaration structure must follow the applicable legislation. See the Radio Equipment Directive.

Do not paste an identical list of directives into every purchase. A radio product and a non-radio accessory may have different legal bases. A power adapter supplied with the product may have its own evidence. Ask the reviewer to explain the legal scope rather than accepting a long list as a quality signal.

Check the editions of the listed standards and the relevant Official Journal references. An old edition is a question to investigate, not enough information for an automatic rejection. You need to understand the assessment date, applicable transition and whether the underlying evidence still addresses the product's requirements.

A model review: the antenna mismatch

This example is fictional. A buyer orders sensor SKU S-42 with an external antenna. The declaration identifies model S-40; the radio report describes S-40 with a PCB antenna. The supplier says the electronics are identical.

The initial finding is “configuration mapping missing”, not “counterfeit certificate”. The buyer requests a model mapping, antenna specifications, the integration assessment and evidence addressing the external antenna configuration. The purchasing decision remains open until a competent reviewer decides what evidence or additional testing is needed.

This wording matters. It describes the observable gap without asserting fraud or inventing a laboratory result.

Verify the issuer and close the gaps

Where a notified body is part of the chosen procedure, verify its identity and relevant designation in the official NANDO system. A four digit number printed on a PDF is not a substitute for checking the scope. A testing laboratory and a notified body are different roles.

If authenticity is uncertain, contact the issuer using independently obtained contact details. Preserve the original file and correspondence; do not edit the supplier PDF to make it look complete. Record whether your concern is authenticity, product identity, missing scope or insufficient technical evidence.

For each gap, specify the requested evidence, owner, deadline and acceptance decision. Do not close a gap because a new PDF arrived: check whether it answers the original question. Your final record should explain which configuration was accepted and which variants remain outside the decision.

Before relying on the result

A purchasing review is one input to the manufacturer's or importer's obligations. It does not transfer responsibility to the supplier or certify the product. Obtain specialist advice where the assessment route or product scope is uncertain.

For context, see our declaration introduction and notified body overview.

Continue reading

Related guides

  • reference

    ETSI EN 303 645 — the 13 consumer IoT controls explained

    The 13 high-level provisions of ETSI EN 303 645 v2.1.1 (June 2020) and v3.1.3 (September 2024) explained, with the TS 103 701 conformance assessment mapping.

    13 min read

  • reference

    RED Annex IV path: when radio equipment needs a Notified Body

    RED Annex IV path — when radio equipment requires Notified Body full quality assurance (Module H), versus Module A self-assessment under Article 17(2).

    10 min read

  • comparison

    RED and CRA overlap for connected radio products: 2025-2027 transition

    RED cybersecurity and CRA scope for connected radio products: OJ coverage, assessment conditions, legacy transitions and the 2027 delegated-act repeal.

    4 min read

  • reference

    EN 18031-1 vs -2 vs -3: which parts apply to your radio product

    EN 18031-1, -2 and -3 compared: product scope, mechanism families, OJEU restrictions, notified body routes and the transition to CRA on 11 December 2027.

    14 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.

Explore Cenitia’s compliance workflow

Review the supported scope and workflow

← Back to Library

Cenitia

The EU compliance engine for hardware manufacturers. Cited drafts, electronic signing, regulation watching — all in one place.

A product of Inovasense s.r.o., Bratislava, Slovakia · Data hosted in Stockholm, EU

Site

  • How it works
  • Library
  • Glossary
  • Regulations
  • By product type
  • Tools
  • About

Legal

  • Imprint
  • Privacy
  • Terms

© 2026 Inovasense s.r.o. · cenitia.com

EU sovereign · EU data residency by design · Customer data never trains models