Certification of Low-Voltage
Equipment under Directive 2014/35/EU
Certification under Directive 2014/35/EU: Low-Voltage Equipment (LVD)
Directive 2014/35/EU (LVD) establishes safety requirements for electrical equipment and applies when a product operates within a certain voltage range. In the context of the EU market, the task is usually one: to confirm safety and prepare the evidence so that it matches the actual supply – the specific model, version, configuration, and conditions of use.
We support LVD projects for placing products on the EU market: we quickly determine applicability and related requirements, select standards for your design and risks, and compile and review the technical file and documents for CE marking. As a result, you receive a clear work plan and an evidence base that stands up to buyer requests, supply chain audits, and surveillance inspections.
Link to download the Directive:
Directive 2014/35/EU – Low Voltage Equipment (LVD)
What we cover in an LVD project
First, we define the role of the economic operator (manufacturer, authorized representative, importer) and the format of market placement: serial products, project-based supplies, or supply as part of a system. This affects the structure of the technical documentation and what evidence will be required.
What LVD is and when it applies
LVD applies to electrical equipment designed to operate within the ranges of 50–1000 V AC and 75–1500 V DC. In practice, whether a product “falls under” it is determined not only by voltage, but also by the product’s intended purpose, environment of use, installation conditions, and the presence of related requirements (for example, EMC or radio modules).
Another important point is borderline cases and exclusions. There are product categories for which special rules and separate EU acts apply. Therefore, at the start we always make a brief applicability check: what exactly is regulated by LVD, and what belongs to another regulatory area.
Essential safety requirements: what exactly must be demonstrated
LVD is oriented toward user safety, protection of property, and proper operation. In practical terms, the evidence base must show that the design and use of the product do not create unacceptable risks: electric shock, overheating, fire, mechanical damage, as well as risks associated with misuse and insufficient information for the user.
Therefore, the logic is simple:
- we identify risks and protective measures,
- we select standards as the means of proof,
- we prepare the technical documentation and, where necessary, testing.
Standards: how the evidence base is formed
In LVD, standards work as a “language of proof”: they help demonstrate that the product meets safety objectives through understandable methods of testing and assessment. The mistake here is usually not that the standard is “bad,” but that it does not fit the design or the conditions of use – and then the evidence becomes questionable.
We link standards to the product through parameters and operating scenarios: operating modes, heating, installation conditions, critical components, marking, and the instructions. If the product is modified (versions, firmware, different configurations), this is recorded in advance so that it is clear which configurations are actually covered by the assessment.
Stages of conformity assessment and CE marking
-
Full Support Cycle
From analysis to document registration
-
Control at Every Stage
AnalysisRegulationsDocumentationTestingRegistration
After the assessment, we fix the “project passport”: precise product identification (model/version/configuration), the list of applicable requirements, and the evidence plan. This makes it possible to avoid situations where testing is performed on one configuration but another is sold.
Technical file and EU Declaration of Conformity: what must be included and how to compile it
- Product identification: model, version, parameters, intended purpose.
- Design description: diagrams, assemblies, critical components.
- Risk assessment: which hazards are considered and how they are reduced.
- Evidence: reports, calculations, records, applied standards.
- Marking and instructions + EU Declaration of Conformity.
An important practical point is consistency. The technical file must “match up” internally: the identification, marking, instructions, reports, and actual supply must describe the same product. If a gap appears anywhere (for example, one version in the report and another on the nameplate), this is exactly what most often raises questions from partners and auditors.
Testing: where problems most often arise
Testing is not the same step for all products: its scope depends on the design, the risks, and the selected standards. If testing is required, it is critical to define the initial conditions in advance – what exactly is being tested and in what form.
Most often, problems arise because the sample configuration does not match the actual supply (configuration, cables, accessories), because the operating modes are incorrect, because the acceptance criteria in the report are vague, or because the version/modification is identified weakly. Therefore, before the samples are submitted, the configuration, modes, and conditions (installation, load, duration, temperatures, limitations) are agreed – this reduces the risk of repeat testing and speeds up document issuance.
When LVD goes together with other requirements
For some products, LVD will be only one of the applicable EU acts. For example, for devices that create or are susceptible to electromagnetic interference, EMC requirements are added; for products with substance restrictions, requirements on the restriction of hazardous substances are added; for devices with a radio module, separate radio equipment requirements apply.
Therefore, we usually start the project with an applicability matrix: we establish which requirements apply to the product, and only then build the evidence and documentation plan.
Risks of nonconformity: what happens in practice
The main risks appear in the supply chain: shipment delays, requests for confirmation, buyer demands for re-approval of documentation, restrictions on listing on marketplaces, and interest from surveillance authorities. Most often, problems are not connected with the absence of a “paper,” but with inconsistency between the documents and the actual supply. Therefore, the key principle is precise product identification and a single logic of evidence.
How we support LVD on a turnkey basis
We manage the project so that the result is robust for supplies and inspections: correct applicability, a clear set of requirements, and evidence tied to your product version and actual configuration.
What we do within LVD:
- assessment of applicability and requirement boundaries;
- selection of standards for the design and risks;
- collection and review of the technical file (Technical File) and accompanying materials;
- organization and control of testing/reports (if required);
- preparation of the EU Declaration of Conformity and verification of the CE marking.
SITIX in figures
10+
years in certification
100+
completed projects
15+
partner countries
80%
returning clients
Frequently Asked Questions
Is a Notified Body required under LVD?
What must be included in the technical file?
Can reports from component suppliers be used?
What should be done when the product version changes?
Which languages are required for the instructions?
How is LVD different from EMC requirements?
What must be in the EU Declaration of Conformity?
We will analyze
the project and present an action plan