Declaration of Conformity for IPL Devices: What It Must Contain

Short answer: a Declaration of Conformity is a legal statement signed by the manufacturer, not a certificate and not a test report. It has to name the legislation, the standards actually applied, the product and the signatory, and everything in it has to agree with the test reports, the label and the technical file.

It is a statement, not a document you buy

People describe the DoC as if it were something a lab issues. It isn’t. The lab issues reports. The notified body, where one is involved, issues a certificate. The DoC is the manufacturer saying, under its own name, that the product meets the legislation listed.

That difference matters when something goes wrong. A test report proves what was tested. A DoC asserts conformity for the products placed on the market. If the signatory cannot support the assertion, the document is worse than useless, because it reads as a warranty.

The required elements

Element	What it has to say	Where projects go wrong
Product identification	Type, model, batch or serial range, and any variant covered	”IPL device” with no model, so nothing is covered
Manufacturer	Legal entity name and postal address	Trading name only, no legal entity
Legislation	The directives and regulations applied, by number and date	Citing a directive that was replaced
Standards	The harmonised standards relied on, with editions	Listing a standard the report did not test
Notified body	Name, number and certificate reference, where one is involved	Omitted when the route required one
Place and date	Where and when issued	Blank, or a date after the shipment
Signatory	Name and function of the person signing	Signed by someone with no authority to bind the company
Language	The language the member state requires	English only, where the market requires the local language

The last row is the quiet one. A DoC has to be available in the language the destination market requires, and member states differ. Retailers ask for the local-language version, and a factory that only ever produced the English one ends up translating the DoC after the first order.

The four rejection reasons

The standard cited is not the standard tested. This is the most common failure. A declaration citing an earlier edition while the report covers the current one reads as a typo until somebody checks. It stops approvals.

The model on the DoC is not the model on the carton. A platform name, a model code and a customer SKU can all appear in one project. The DoC has to use the identification that the label and the reports use, or the operator cannot connect the shipment to the file.

The signatory has no authority. The signature is an assertion made by a legal entity. If the person who signs is a sales manager with no delegation, the document is defective on its face, and an importer’s compliance consultant will notice.

It covers more than the file covers. A declaration that names a family of devices, when the technical file covers one of them, invites a question the manufacturer cannot answer. If a variant has a different adapter, a different cell, or a radio module the base version does not have, it does not belong under the same declaration unless it was assessed.

What changes when the product changes

The DoC is the document that most often fails to keep up with the product. Four changes force a new or amended declaration:

• A new radio module. Adding Bluetooth brings the radio equipment directive into scope, and with it the requirement to show the frequency bands, the power and the restrictions by country.
• A different cell. The battery changes what the safety file rests on, and the declaration’s standards list is where that shows.
• A different adapter. An adapter is part of the delivered product. A declaration that lists the standards for the appliance while the shipment includes an adapter assessed under nothing is incomplete.
• A change in who is placing it on the market. Not a change to the declaration, but a change to the label block beside it.

Which regime the declaration is made under, and why the medical route changes the answer, is covered in EU MDR for home IPL devices. The regulatory landscape piece maps which markets require a declaration and which require a certificate.

Who signs, and who does not

The manufacturer signs. An importer does not sign a DoC on the manufacturer’s behalf, and an authorised representative does not become the manufacturer by being named.

What an EU responsible person signs is a different document: the written mandate under the product safety regulation. Confusing the two is a common error in the paperwork, and the result is a file where the party legally responsible is named in a document that gives them no authority over the product.

Two practical rules follow. Keep the signatory’s authority documented, and issue the DoC from the legal entity whose name is on the product.

The ten-year habit

Technical documentation has to be kept for ten years after the last unit is placed on the market, and the DoC travels with it. In practice that means a filing habit, not a filing event: one folder per model, containing the declaration, the reports it cites, the label artwork, and the change history.

Factories that do this well produce an amendment note every time a component changes, so the file tells a story. Factories that do it badly have a declaration dated to the first project and a product that has moved on twice.

What we do, and what we do not

We issue the declaration under our own name and legal entity, cite the standards the reports actually tested, list the adapter and the cell in scope, and keep the file for the retention period. We do not issue notified body certificates, we do not sign a declaration on a customer’s behalf, and we do not add a standard to the list because a buyer asked for it.

If you are assembling the file for a first launch, the private label process lists which documents are issued at which stage, and how regulators classify home IPL devices explains why the standards list differs between the consumer and medical routes.