Book a call

All notes

Already selling? What the CRA asks of products on the market today

Products placed on the EU market before 11 December 2027 skip most CRA duties, unless you change them a lot. The 24-hour reporting duty already applies.

7 min read

You have sold the same gateway for three years. Hundreds of units are already out there, in buildings and in machines. Now the EU Cyber Resilience Act (CRA) is coming. Must you redo the paperwork for every unit you ever sold?

No. But two things already apply, and one detail catches many makers: the law counts each unit, not each model. This note explains what the CRA asks of products that are already on the market, with the exact articles.

A beaver engineer stands in front of a long shelf of identical small devices and thinks. Kavach the pangolin walks in with a clipboard.
Bina's shelf is full of devices that she sold long before the CRA. What does the law ask of them?

The short answer

  • Units already on the market: the full CRA requirements do not apply to them, unless you make a substantial modification from 11 December 2027 (Article 69(2)).
  • The reporting duty: it applies to them already. Since 11 September 2026, you report actively exploited vulnerabilities and severe incidents for all products in scope, old and new (Article 69(3) and Article 71(2)).
  • Units placed on the market from 11 December 2027: they need the full CRA, even when the model is older. The law looks at each unit (Commission guidance, paragraph 11).

What the CRA says about products already on the market

The rule is short. It sits in the transitional provisions.

Article 69(2)

Products with digital elements that have been placed on the market before 11 December 2027 shall be subject to the requirements set out in this Regulation only if, from that date, those products are subject to a substantial modification.

The next paragraph makes one exception.

Article 69(3)

By way of derogation from paragraph 2 of this Article, the obligations laid down in Article 14 shall apply to all products with digital elements that fall within the scope of this Regulation that have been placed on the market before 11 December 2027.

Article 14 holds the reporting duties. So older products skip the design and documentation work of the CRA, but not the reporting clock.

“Placed on the market” counts each unit, not each model

This is the detail that matters most for a maker with a long-running product. The CRA defines the moment like this.

Article 3(21)

‘placing on the market’ means the first making available of a product with digital elements on the Union market;

“Making available” means the supply of a product for distribution or use in the EU, in the course of a commercial activity, paid or free (Article 3(22)). The Commission’s guidance then explains what one “product” means here. It follows the EU’s Blue Guide on product rules.

Commission guidance on the CRA, paragraph 11

The Blue Guide indicates that the concepts of ‘placing on the market’ and of ‘making available’ are to be understood as referring ‘to each individual product, not to a type of product, and whether it was manufactured as an individual unit or in series’ (Section 2.3).

So the date of your model’s launch does not decide it. Each unit counts on its own. A unit that you first supply to a customer or a distributor before 11 December 2027 falls under Article 69(2). A unit of the same model that you first supply from that date is a new placing on the market, and it needs the full CRA.

A unit that is still in your own stock has not been made available yet (Article 3(21) and (22)). So when you supply it from 11 December 2027, plan for it as a new placing on the market. If your distribution chain makes the date unclear, ask your lawyer.

On the left, the shelf of older devices stays as it is. On the right, the beaver has fitted a large new part to one opened device, and Kavach puts a thick new folder next to it.
The old shelf stays as it is. The device that Bina changed a lot gets a new, full file.

When an older product becomes “new”: substantial modification

A product placed on the market before 11 December 2027 comes under the full CRA when it gets a substantial modification from that date (Article 69(2)). The CRA defines that term.

Article 3(30)

‘substantial modification’ means a change to the product with digital elements following its placing on the market, which affects the compliance of the product with digital elements with the essential cybersecurity requirements set out in Part I of Annex I or which results in a modification to the intended purpose for which the product with digital elements has been assessed;

The Commission’s guidance says what follows from it. A substantially modified product that is made available is treated as a new product, and making it available is a new placing on the market (paragraph 116). This is true when you make the change, and also when another company makes it (paragraph 116; Article 22(1)).

Security updates are usually not a substantial modification. Their main purpose is to lower the risk. An update that does not change the intended purpose and does not add new cybersecurity risks is not a substantial modification, even when it changes a lot of code (paragraph 108).

For other updates, the guidance gives four questions (paragraph 110). Does the update:

  1. add new ways in, such as new interfaces, communication channels, execution environments or external dependencies?
  2. make new attack scenarios possible?
  3. make known attack scenarios easier, for example by weakening a safeguard?
  4. make the impact of known attack scenarios bigger?

The guidance asks for a case-by-case assessment (paragraph 110). Write down your answers for each release. That record shows later why a release did or did not count as a substantial modification.

The red security mailbox rings above the shelf of older devices. Kavach starts a red stopwatch right next to the shelf, and the beaver looks up.
The mailbox rings for an old device. The clock starts all the same.

What already applies today: the reporting clock

Since 11 September 2026, Article 14 applies (Article 71(2)), and it covers your older products too (Article 69(3)). For each product in scope:

  • Actively exploited vulnerabilities: when you become aware of one in your product, you notify it through the single reporting platform (SRP), with an early warning within 24 hours (Article 14(1) and (2)).
  • Severe incidents: when an incident has an impact on the security of your product, you notify it in the same way (Article 14(3) and (4)).
  • Your users: you inform the users who are affected, and where appropriate all users, and tell them what they can do to limit the impact (Article 14(8)).

One point surprises many makers. The reporting duty does not end when your support for a product ends. The Commission’s guidance says that, unlike the vulnerability handling duties, “the reporting obligations continue to apply after a product with digital elements is no longer supported” (paragraph 210).

So the device you stopped updating in 2023 can still start the 24-hour clock. The steps are in our note on the CRA’s 24-hour clock.

New units of the same small device come off a short conveyor belt. Kavach stamps a small tag on each new unit. The beaver holds a thick folder, calm now.
Each new unit counts. From 11 December 2027, new units go out with the full evidence.

A plan for the products you already sell

  1. List your products and versions. For each one, write down when you first placed units on the EU market, and whether you still sell it.
  2. Mark what you will still supply after 11 December 2027. Those units need the full CRA (Article 71(2)): the security requirements of Annex I, Part I (Article 13(1)), and the technical documentation and conformity assessment before you place them on the market (Article 13(12)).
  3. Set a rule for changes. Before each release of an older product, answer the four questions from the guidance (paragraph 110), and keep the answers.
  4. Be ready to report for every product now. This includes products that you no longer support (Article 69(3); guidance, paragraph 210). A person must read your security inbox every working day.
  5. Start the SBOMs early. Products that you will sell from 11 December 2027 need a software bill of materials (Annex I, Part II, point 1). It also tells you in minutes whether an old product contains a component that attackers now use. See our note on what the CRA asks for in an SBOM.

Where Relvault fits

Relvault prepares this evidence for small device makers: the product and version list, an SBOM for each version, the daily check against exploited-vulnerability lists, the report drafts, and a record of the change assessment for each release. Your engineers check each item, and your company signs and files. See how it works and the prices.

If you sell components to OEMs, read We only make a module next.

Common questions

Does the CRA apply to products already on the market?

Only in part. Products placed on the market before 11 December 2027 must meet the CRA requirements only if they get a substantial modification from that date (Article 69(2)). The reporting duties of Article 14 apply to them already, since 11 September 2026 (Article 69(3) and Article 71(2)).

I launched my model in 2025. Do units I sell in 2028 need the full CRA?

Yes. Placing on the market refers to each individual product, not to a type of product (Commission guidance, paragraph 11). A unit first made available from 11 December 2027 is placed on the market from that date, so it must meet the CRA (Article 71(2)).

Does a security update make my old product a new product?

Usually not. The Commission’s guidance says a security update that does not change the intended purpose and does not introduce new cybersecurity risks is not a substantial modification (paragraph 108).

Do I have to report flaws in products I no longer support?

Yes. The reporting duties continue after a product is no longer supported (Commission guidance, paragraph 210). They apply to all products in scope, also the ones placed on the market before 11 December 2027 (Article 69(3)).

What if another company changes my product?

If a company other than the manufacturer, importer or distributor makes a substantial modification and makes the product available, it is considered a manufacturer under the CRA (Article 22(1)). Its duties cover the part affected by the change, or the whole product if the change affects its cybersecurity as a whole (Article 22(2)).

Sources

  • Regulation (EU) 2024/2847, the Cyber Resilience Act, official text on EUR-Lex. This note uses Articles 3(21), 3(22), 3(30), 13(1) and (12), 14(1) to (4) and (8), 22, 69(2) and (3), and 71(2), and Annex I, Parts I and II.
  • European Commission, guidance on the application of the CRA, C(2026) 5252, 27 July 2026, paragraphs 10, 11, 108, 110, 116 and 210.

This note explains the law in plain words. It is not legal advice. For your own case, ask your lawyer.