shipcra

EU declaration of conformity and CE marking for software under the CRA

Reviewed 3 min read

From 11 December 2027, before you place an in-scope product on the EU market, you complete a conformity assessment, draw up an EU declaration of conformity that follows Annex V of the Cyber Resilience Act, and affix the CE marking. For software, the CE marking goes on the declaration or on the website that accompanies the product.

Key facts

Content of the declaration
Annex V (a simplified version is described in Annex VI)
Technical documentation
Annex VII, kept at least 10 years or for the support period if longer
Route for default products
Module A, internal control (Annex VIII)
CE marking for software
On the declaration or on the website accompanying the software
Who signs
The manufacturer, which takes sole responsibility

Where the declaration fits

The declaration of conformity is the last document in a sequence, not the first:

  1. Decide whether the product is in scope and in which category.
  2. Assess its cybersecurity risks.
  3. Meet the Annex I essential requirements and record how.
  4. Write the technical documentation (Annex VII).
  5. Carry out the conformity assessment. For default products, that is Module A, internal control.
  6. Draw up and sign the EU declaration of conformity.
  7. Affix the CE marking and place the product on the market.

By signing, the manufacturer declares that the requirements are met and takes responsibility for it. Everything before step 6 is what makes that statement true.

What Annex V asks you to include

  1. The name and type of the product, and any information that uniquely identifies it.
  2. The 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: an identification that allows traceability, such as the version.
  5. A statement that the object is in conformity with the relevant Union harmonisation legislation.
  6. References to the harmonised standards, common specifications or cybersecurity certifications used.
  7. Where applicable, the notified body, the procedure followed and the certificate issued.
  8. Additional information: signed for and on behalf of, place and date, name, function and signature.

A working template

This skeleton follows the order of Annex V. Every bracket is a decision or a fact only you can supply.

EU DECLARATION OF CONFORMITY
Regulation (EU) 2024/2847 (Cyber Resilience Act)

1. Product: [name], [type, e.g. mobile application for iOS and Android]
2. Manufacturer: [legal name], [postal address]
3. This declaration of conformity is issued under the sole responsibility
   of the manufacturer.
4. Object of the declaration: [product name], version [x.y.z],
   [build or release identifier]
5. The object of the declaration described above is in conformity with
   Regulation (EU) 2024/2847 [and other applicable Union legislation].
6. Standards, common specifications or certifications applied:
   [references, or "none"]
7. Notified body: [name, number, procedure, certificate], or "not applicable:
   conformity assessed by internal control (Module A)"
8. Signed for and on behalf of: [legal name]
   [place], [date]
   [name], [function]
   [signature]

The technical documentation behind it

Annex VII lists what the technical file contains. For a small software product, that means:

  • A general description: intended purpose, versions, how users get updates, and the user information from Annex II.
  • How the product is designed, developed and maintained, including how you handle vulnerabilities and where your SBOM is kept. You provide the SBOM to authorities on reasoned request.
  • The cybersecurity risk assessment.
  • The information used to set the support period.
  • The standards or specifications applied, and test and review reports.
  • A copy of the EU declaration of conformity.

Keep the file, and the declaration, for at least ten years after the product is placed on the market, or for the support period if that is longer.

CE marking for software

The CE marking must be visible, legible and indelible. For a product in the form of software, it is affixed either to the EU declaration of conformity or on the website that accompanies the software. A store listing that links to your product page with the declaration is a common way to make it findable.

Before you sign

  • The product version in the declaration matches the build you are releasing.
  • Every Annex I requirement has a documented answer, including the ones you consider not applicable.
  • The category and the conformity route match the product’s core function.
  • The support period end date is decided and appears in the user information.
  • The declaration is reachable at a stable URL, and a copy is in the technical file.

shipcra prepares a draft of the declaration from your questionnaire answers, with a one-page summary of what you are about to sign. The decision and the signature stay with you.

Questions

Who signs the EU declaration of conformity?

The manufacturer, through a person authorised to sign on its behalf. The declaration states that it is issued under the manufacturer’s sole responsibility, so a template provider or a consultant can’t sign it for you.

Do I need a notified body to issue the declaration?

Not for products in the default category: you assess them yourself under Module A. Class II and critical products, and class I products without harmonised standards applied in full, involve a notified body whose details then appear in the declaration.

Can I publish a short version of the declaration?

Yes. Annex VI describes a simplified declaration that names the product and gives the internet address where the full text can be found. The full declaration must still exist and be reachable.

When do I need CE marking for software?

For products in scope placed on the EU market from 11 December 2027. The marking has to be in place before the product is placed on the market.

Sources

  1. Regulation (EU) 2024/2847, Articles 28 and 30 and Annexes V to VIII, EUR-Lex
  2. Cyber Resilience Act: conformity assessment, European Commission

This guide explains the regulation in general terms. It isn’t legal advice for your product.

Draft the paperwork from your answers.

The pack turns your Annex I answers into a gap report, technical documentation and a draft declaration that you review and sign.

Join early access