CE Compliance Testing Services In The Eu

Scope and evidence must be confirmed before any paid tests or filings.

CE compliance testing is not a single universal “CE test” or an EU-issued certificate. The evidence path starts with the EU legislation that applies to the product, the essential requirements to be demonstrated, the technical specifications or harmonised standards used to show conformity, and the conformity-assessment procedure. A laboratory should be booked only after those points are mapped.

For testing procurement, the practical objective is narrower: define the correct test scope, choose a competent laboratory, send representative samples, obtain reports that can actually support the technical documentation, and control whether later product changes require review or retesting.

CE testing matrix: six decisions before a laboratory quote

Question	What must be decided	Evidence to prepare	Main risk if missed
1. Which EU rules apply?	Identify every CE-marking directive or regulation relevant to the product and its intended use.	Product description, intended use, users, environment, technical characteristics.	Testing the wrong requirement set or omitting a parallel regime.
2. Which requirements need technical evidence?	Map the applicable essential requirements to calculations, inspections, tests or other evidence.	Requirements matrix and risk analysis.	A “pass” report that does not cover all applicable legal requirements.
3. Which standards or methods will be used?	Confirm the exact standard, edition, amendment and test method. Check whether a harmonised standard reference is current for the applicable legislation.	Standards list with edition/status.	Using an obsolete or irrelevant method, or assuming a standard covers requirements that it does not cover.
4. Is third-party conformity assessment mandatory?	Determine the conformity-assessment procedure under the applicable legislation and whether a notified body must be involved.	Conformity-route note.	Buying a private “CE certificate” that has no required legal role, or using a body outside its notified scope.
5. What exactly is the test specimen?	Freeze the tested configuration: model, hardware, software/firmware, critical components, power options, accessories and operating modes.	Sample configuration sheet and photos.	The report cannot be tied reliably to the marketed product.
6. What will trigger a retest?	Predefine which changes require engineering review, partial retest, full retest or notified-body approval where applicable.	Change-control matrix.	Continuing to rely on evidence for a materially different product.

Build the test scope before sending samples

Start from the product and applicable legislation, not from a laboratory’s generic package. Harmonised standards are generally voluntary tools: when their references are published for the relevant EU legislation, applying them can provide a presumption of conformity for the requirements they cover. A manufacturer may use another technical solution, but then the technical documentation must explain how the mandatory legal requirements are met.

A useful test plan therefore links each requirement to a method and an output. Separate requirements that can be demonstrated by laboratory testing from those that depend on design review, risk assessment, calculations, instructions, software behaviour, production controls or another form of evidence.

Record the exact product model and intended use, including reasonably foreseeable operating conditions relevant to the test.
List all potentially applicable CE legislation before selecting standards; one product can fall under more than one EU act.
For each chosen standard, record the edition and amendments and verify the current EU harmonisation status where that status matters.
Define pass/fail criteria, modes of operation, accessories, loads and worst-case configurations before the sample arrives at the laboratory.
Identify evidence that must come from a notified body, where the applicable conformity-assessment route requires one.

For product-specific EMC scope, use the dedicated CE EMC testing requirements guide rather than expanding this page into a full EMC standard-selection article.

Laboratory selection: competence, scope and legal role are different questions

An ISO/IEC 17025 accreditation can be strong evidence of laboratory competence, but it is not a blanket legal requirement for every test used in every CE self-assessment. Where EU legislation requires a notified body, the decisive question is whether that body is designated in NANDO for the relevant legislation and conformity-assessment tasks. A laboratory may also work as a subcontractor to a notified body, subject to the applicable controls.

Before accepting a quotation, ask for:

the exact test method and product category covered by the laboratory’s competence or accreditation scope;
the accreditation body and scope entry, if accredited results are required by your route, customer or risk policy;
the notified-body identification number and notified scope if the work is being sold as a legally required notified-body activity;
which tests will be subcontracted and how subcontracted results will appear in the final report;
the sample quantity, conditioning, destructive-test implications and whether spare samples are needed;
how deviations, failures, engineering changes and retests are documented;
whether the report will identify the tested configuration, standard edition, deviations and results with enough detail for the technical file.

Do not select a provider only because its marketing says “CE certified” or “CE approved.” The European Commission warns that there is no central EU body issuing permission to use the CE mark and that voluntary certificates may have no legal role in the applicable CE procedure.

For a broader comparison of laboratory and certification-provider roles, see CE testing and certification laboratory services in the EU.

Sample and variant logic: when one tested unit is not enough

A test report proves what was tested under the stated conditions. Extending that evidence to a family of models requires a documented technical rationale. “Same product family” is not, by itself, a test method or a legal conclusion.

Change between variants	Typical evidence question	Prudent action before relying on one report
Different power supply, voltage or rated power	Does the new electrical/thermal worst case remain covered?	Ask the laboratory to define the worst-case configuration and whether additional tests are needed.
Different enclosure, plastics or insulation materials	Can fire, mechanical, creepage/clearance or thermal results change?	Perform an impact review; retest affected clauses when the method or risk analysis requires it.
PCB, radio module, clock, cable or firmware change	Could emissions, immunity, radio or functional-safety behaviour change?	Reassess affected test families; do not assume a cosmetic model-number change.
Substitution of a safety-critical component	Are ratings, approvals and failure behaviour equivalent?	Document equivalence and test again where the applicable standard or assessment cannot be bridged by evidence.
Only colour, branding or non-functional packaging changes	Is the tested product technically unchanged?	Record the equivalence; check separately whether markings/instructions are affected.

When a standard defines a family, representative model or worst-case selection method, follow that method. Otherwise, agree the family rationale in writing with the laboratory or notified body before testing rather than after a failed audit or market-surveillance request.

Can an existing test report be reused?

An older report is not automatically unusable, and a newer report is not automatically sufficient. Reuse is an evidence decision: the report, tested specimen, current product and current legal/technical requirements must still line up.

Check	Reuse is more defensible when…	Review or retest is more likely when…
Product identity	The report clearly identifies the same model/configuration or a documented equivalent variant.	Key hardware, software, components or operating modes have changed.
Requirements	The applicable legal requirements remain the same for the claimed scope.	New or amended legislation introduces relevant obligations.
Standard status	The method remains suitable and any harmonised-standard presumption relied on is still valid for the requirement.	A reference has been superseded/withdrawn or the new state of the art exposes an uncovered risk.
Report quality	Sample identity, methods, deviations and results are traceable.	The report is a short certificate with no usable test evidence or cannot be linked to the marketed version.
Third-party route	The notified body, where involved, accepts the evidence for its procedure and scope.	The evidence falls outside the body’s procedure, scope or acceptance policy.

The final decision is product- and legislation-specific. If a notified-body certificate is involved, changes that may affect conformity or certificate validity can require additional review or approval under the relevant legislation.

Failure, retest and test-driven change control

A failed test should create a controlled evidence loop, not an undocumented “fix and rerun.” Use the following sequence:

Freeze the failure record. Keep the failed result, sample identity, configuration, photos and laboratory notes.
Identify the cause. Distinguish a test setup issue from a product design, component, software, assembly or instruction problem.
Document the corrective change. Record the exact revision and why it addresses the failure.
Assess collateral impact. A fix for one clause can affect EMC, thermal behaviour, electrical safety, mechanics, radio performance or another requirement.
Define the retest boundary. Retest the failed item and any technically affected items; full retesting may be justified when the change is broad or the original evidence can no longer be bridged.
Update the technical documentation. The final evidence package must correspond to the production version, not only to an engineering sample that passed after modification.

The 2022 Blue Guide states that, where a product has undergone redesigns and conformity reassessments, the technical documentation must reflect all product versions, the changes made and the corresponding conformity assessments so that the applicable evidence can be distinguished. This is why version control is part of CE testing evidence, not an administrative afterthought.

What to request in the testing evidence package

Before the job starts, agree the deliverable. For a report intended to support CE technical documentation, request enough information to reconstruct what was tested and against what criteria:

manufacturer/client, laboratory, report number and issue date;
product model, serial/sample identifiers, photographs and configuration;
hardware revision and software/firmware version where they affect conformity;
test standards/methods, editions, amendments and any deviations;
operating modes, accessories, loads, environmental conditions and sample conditioning relevant to the result;
results, limits/criteria and failures or non-conformities, not merely a marketing certificate;
accreditation status/scope or notified-body role where relevant to the conformity route;
identification of subcontracted activities and the related reports where applicable.

Keep the report with the requirement matrix and change-control record. Under the common New Legislative Framework model, technical documentation can include design calculations, examinations and test reports; the exact content and retention obligations come from the product-specific EU legislation.

Ten questions to answer before booking CE compliance testing

What exact product and intended use will be placed on the EU market?
Which CE-marking EU acts apply, and which requirements are in scope?
Which harmonised standards or other technical solutions will be used for each requirement?
Which standard editions and amendments are current for the intended evidence claim?
Does the conformity route permit manufacturer self-assessment, or is a notified body required?
Which model/variant is the technical worst case, and how will family coverage be justified?
How many samples are required, and will any tests destroy or alter them?
What exact report package will be delivered, including failures and deviations?
Which existing reports may be reused, and what gap analysis supports that decision?
Which design, component, supplier, firmware or standard changes will trigger review or retesting?

If these questions cannot be answered, the safe next step is a test-scope review before purchasing laboratory time. A price quote obtained before scope definition can be commercially attractive and still leave the technical file incomplete.

Where this testing page stops

This page owns testing evidence, laboratory questions, samples, report reuse and retesting. For the complete CE execution route, use CE marking services. For strategy/classification support, use CE marking consultant. For budgeting, use CE marking cost. For documentation ownership, use CE marking registration and documentation in the EU. These topics should not be reconstructed inside a testing brief.

Official sources for checking the test route

FAQ: CE compliance testing

Do I always need an ISO/IEC 17025 accredited laboratory for CE marking?

No universal EU rule makes an ISO/IEC 17025-accredited laboratory mandatory for every CE test. The applicable product legislation and conformity-assessment route control the legal requirement. Accreditation is nevertheless an important competence signal and may be required by a notified body, a specific scheme, a customer or an evidence-acceptance policy. Check the accreditation scope for the actual method, not only the laboratory name.

Can a test report from outside the EU be used for CE evidence?

Potentially, but geography alone does not decide acceptance. Check whether the method, laboratory competence, sample identity, report content and current EU requirements are suitable. If a notified body is legally required, ask that body whether and how it can use external test results in its procedure. Mutual-recognition or accreditation arrangements may help confidence in results, but they do not replace the product-specific EU conformity route.

Can one tested sample cover an entire product family?

Sometimes, if the applicable standard or a documented engineering rationale supports representative or worst-case testing. The family decision should identify which differences are technically irrelevant and which could affect the result. Do not extend a report to variants merely because they share a commercial family name.

Does any design change require a full CE retest?

No. The correct response is an impact assessment. A minor change may need only documented review; a targeted change may require partial retesting; a major change can make broader retesting necessary. If a notified-body approval or certificate is involved, the relevant legislation and the body’s procedure determine whether prior review or additional approval is required.

Can a laboratory issue my “CE certificate” after the product passes testing?

Not as a universal EU permission to use the CE mark. The manufacturer remains responsible for conformity and for the EU declaration of conformity, while some product laws require a notified body for specified conformity-assessment tasks. A laboratory test report, a voluntary certificate and a legally required notified-body certificate are different documents and should not be treated as interchangeable.