CRA Reference

EU declaration of conformity

Primary audience:LegalDeadline:

Published on

What the declaration is

The document by which the manufacturer attests, under its sole responsibility, that the product satisfies the applicable essential requirements. It is drawn up before placing on the market and accompanies the product.

It is short — one or two pages — but binding: it is what turns the CE marking into an enforceable statement.

Mandatory content (Annex V)

  1. Name and type of the product, with the elements allowing its traceability: reference, version number, and where useful a photograph.
  2. Name and address of the manufacturer or its authorised representative.
  3. A statement that the declaration is issued under the sole responsibility of the manufacturer.
  4. The object of the declaration: identification of the product allowing traceability, including where necessary a sufficiently clear colour image.
  5. A statement that the object is in conformity with Regulation (EU) 2024/2847 and, where applicable, with other applicable Union harmonisation legislation.
  6. References to the harmonised standards applied, to common specifications or to European certification schemes, with their version date.
  7. Where applicable, the name and number of the notified body, a description of the assessment procedure followed and the reference of the certificate issued.
  8. Any additional information.
  9. Place and date of issue, name, function and signature of the signatory.

The simplified declaration (Annex VI)

An abbreviated form is permitted, containing at minimum the product identification, the statement of conformity with the Regulation, and the exact internet address where the full declaration can be accessed. It is useful on packaging and notices, but does not replace the full declaration, which must remain available.

Language requirements

The declaration is translated into the language or languages required by the Member State in whose market the product is made available. In practice, for Union-wide distribution, that means planning a translation chain and a consistency check across versions.

The authoritative version is the one drawn up by the manufacturer; translations must be faithful to it.

Template

EU DECLARATION OF CONFORMITY

1. Product: Acme Gateway, reference AG-4200, software version 4.2.1

2. Manufacturer: [Legal name]
   [Full postal address]
   [Email address] — [Website]

3. This declaration of conformity is issued under the sole responsibility
   of the manufacturer.

4. Object of the declaration: product with digital elements
   "Acme Gateway", version 4.2.1, identified by [hash / serial number].

5. The object of the declaration described above is in conformity with the
   relevant Union harmonisation legislation:
   — Regulation (EU) 2024/2847 (Cyber Resilience Act)
   — [where applicable, other applicable acts]

6. References to the harmonised standards applied, or to the other
   specifications against which conformity is declared:
   — [standard reference and date]
   — [description of the solutions adopted for requirements not covered]

7. Notified body: [name], number [NNNN], performed [procedure] and issued
   certificate [reference].
   [Or: not applicable — assessment carried out under module A, internal control.]

8. Additional information: support period until [month/year].

Signed for and on behalf of: [Legal name]
Place and date: [city], [date]
Name and function: [name], [function]
Signature: ____________________

Update rules

Event Is a new declaration needed?
New security-fix version, no other change No, if the declaration expressly covers the version line
New functional version Yes, if the declared version changes
Substantial modification Yes, after a new assessment
Change of legal name or address Yes
A new harmonised standard cited in the OJ replacing the one applied To be examined; the declaration must reflect the references actually applied

The question of version scope must be settled with the first declaration: declaring a precise version is stricter, declaring a version line is more manageable. The choice must be consistent with the versioning strategy, and documented.

Retention

Ten years after placing on the market, or the support period if longer — like the technical documentation. See Evidence retention.