CE Safety Testing Services In The Eu

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

CE safety testing is not a universal certificate or a fixed set of laboratory tests. It is the process of obtaining relevant, traceable evidence for the risks and essential requirements that actually apply to a defined product, configuration and intended use.

Before paying a laboratory, establish the applicable EU legislation and conformity-assessment route. CE marking applies only where EU harmonisation legislation requires it; some routes allow manufacturer assessment, while others require a notified body. An ISO/IEC 17025 test report and notified-body approval are not interchangeable.

Build the testing matrix before requesting a quotation

Use the product’s intended use, foreseeable misuse, risk assessment and all applicable legal acts to map each requirement to evidence. The rows below are planning examples, not an automatic list of directives or compulsory tests for every product.

Product characteristic / risk	Possible evidence stream	Scope question for the laboratory
Power supply, accessible circuits or heat	Electrical, insulation, temperature and fire-related evaluation where relevant	Which voltages, environments, load conditions and construction variants are covered?
Electronics, cables or switching circuits	Electromagnetic emissions and immunity where relevant	Which ports, cable lengths, operating modes and disturbances will be tested?
Radio transmitter or receiver	Radio, spectrum, EMC and safety evidence under the applicable rules	Which frequencies, antennas, firmware versions and combinations are represented?
Moving parts, pressure, accessible materials or user contact	Mechanical, pressure, chemical or other hazard-specific evidence as applicable	Which users, contact duration, accessories and worst-case uses are included?

Check the exact edition and the EU Official Journal (OJEU) citation of any harmonised standard, including restrictions and transitions. Such standards are normally voluntary; a cited standard may give a presumption of conformity only for requirements it covers. Other technical solutions need their own justified evidence.

Check the laboratory’s competence and the legal route

Ask for written confirmation of what the lab can test and what its report will establish:

Exact methods and editions, with any deviations and pass/fail criteria identified.
Accreditation body, certificate, current ISO/IEC 17025 scope and whether the quoted methods are inside that scope; verify with the accreditation body when material.
Whether tests are subcontracted, and who signs and retains raw data and the final report.
Model, sample ID, serial/batch, photos, configurations, calibration and uncertainties where relevant.
If legislation requires a notified body, its NANDO notification under the particular act and assessment task—not merely a laboratory accreditation or commercial “CE certificate”.

Choose representative samples and operating modes

Agree the sample plan before dispatch. The objective is a defensible link between tested specimen and products later manufactured, not merely a convenient prototype.

Freeze hardware revision, bill of materials, critical suppliers, firmware, software and accessories.
Document rated inputs, extremes, user modes, interfaces and the worst-case configuration; explain why it is representative.
Confirm sample quantity, preconditioning, destructive tests, shipping constraints and replacement samples with the laboratory.
Mark sample IDs, custody, photographs and deviations; keep tested units or records under the agreed retention plan.
Record which product variants are covered by the selected sample; test or justify uncovered differences.

Decide whether earlier reports can be reused

Treat an old report as conditional evidence, never as a transferable CE authorisation. Compare its product identity, test method and edition, laboratory competence, full results, deviations, limits and applicable legislation with the current design.

Change or situation	Working decision	Record required
Same model and unchanged critical design	Reuse may be supportable if scope and legal references still match	Identity and revision comparison; report scope and standard edition
New critical component or enclosure material	Perform impact analysis; targeted or full retest may be needed	Supplier specifications, risk review, affected clauses
Firmware, radio settings or power modes changed	Review the affected test modes and repeat relevant tests where necessary	Firmware versions, parameter delta, revised test plan
Standard revised or OJEU citation changed	Check coverage, restrictions and transition status; do not assume prior presumption continues	Edition comparison and documented gap closure

Handle failures and product changes without losing traceability

A failed result is an engineering and evidence-management issue, not a reason to omit the report from the technical-file history:

Identify the exact failed clause, limits, setup, sample and reproducibility; separate setup errors from product defects.
Implement corrective action and revise the risk assessment, drawings, parts or instructions as affected.
Agree targeted regression tests plus any interactions introduced by the fix; document why wider retesting is or is not needed.
Archive the original result, change record, retest report and final conclusion; update production controls and the technical documentation.

Send a complete test brief—not just a product photo

A useful request for quotation answers these six questions:

What is the product, intended user, market, model family and exact configuration?
Which EU acts and essential requirements have been screened, and which uncertainties remain?
Which hazards, functions and candidate standards/editions are in the test matrix?
What are the critical variants, worst-case modes, sample count and build revision?
What accreditation scope, report format, raw results, subcontracting and notified-body involvement are required?
Who approves the test plan, handles failures, controls design changes and receives the deliverables?

This page is about selecting and preserving testing evidence. For the broader delivery process, see CE marking services; for a laboratory-service comparison, see laboratory testing and certification services; for specialized electromagnetic testing, see EU EMC testing requirements. A quotation or voluntary certificate does not replace checking the applicable legal route.

Questions before booking CE safety testing

Does every CE-marked product need tests by an independent laboratory?

No universal rule says so. The applicable legislation and conformity-assessment module decide what independent involvement is required; the manufacturer still needs adequate evidence of compliance.

Is ISO/IEC 17025 accreditation the same as notified-body status?

No. Laboratory accreditation concerns competence for specified tests. Notification is an EU legal designation for specified conformity-assessment tasks; check NANDO when the relevant law requires it.

Can a supplier’s test report cover our branded product?

Possibly, but not automatically. Match the tested construction, components, intended use, standards and legal route; document ownership/access to evidence and gaps, and test differences where needed.

Does a passed report allow us to put CE on the product immediately?

Not by itself. The manufacturer must complete all applicable conformity-assessment steps, technical documentation and any required notified-body procedure before making the relevant declaration and affixing CE.

Does a firmware or component change always mean a complete retest?

Not always. Perform a documented change-impact and risk assessment, identify affected clauses and interactions, and justify targeted versus full retesting; requirements of a notified body may also apply.

Official reference points

These official materials explain the legal route, technical-file evidence, harmonised standards, notification and accreditation. Check the applicable sector legislation and the current OJEU references for your product.