A Polish distributor wants to keep selling a sensor you launched in 2025. It asks for a CRA declaration covering all remaining stock. Before you sign, ask for the order and the batch list. Two identical sensors on the same shelf can have different legal status.
Under the Cyber Resilience Act (CRA), an in-scope product first placed on the EU market before 11 December 2027 comes under the new product requirements only if it undergoes a substantial modification on or after that date. Manufacturers’ reporting duties already cover older products.
Can we keep selling this product in the EU?
Answer up to seven questions about one batch, software release or update. See your result before entering an email address.
For in-scope products, manufacturers must report actively exploited vulnerabilities and severe incidents affecting product security under Article 14. This includes products placed on the market before 11 December 2027.
Your answers
Paste the buyer’s question or briefly describe the issue. Please leave out confidential contract terms.
One order, 250 sensors. Which units can you confirm?
Suppose it is January 2028. Your Polish importer holds 250 finished T-200 sensors in Poznań. Its distributor asks for a written statement before collecting them. The November order file contains two different records.
| Units | What the file shows | What you can confirm |
|---|---|---|
| 200 units • 27A0401–27A0600 | The agreed schedule identifies these serials. The distributor obtained the right to dispose of them on 20 November 2027 and asked the importer to hold them. | The records support first EU supply before the cut-off, even though collection takes place in January. |
| 50 units • 27A0601–27A0650 | These serials appear only in the warehouse export. The agreed schedule does not identify them. | Leave these units open. Find the earlier offer or agreement, if any. If first supplied in January, these units must meet the applicable CRA product requirements. |
A useful batch record fits on one page. Record the serial range, the first EU recipient, what right it acquired and when, and the document supporting each conclusion. Keep the unconfirmed serials in a separate row.
What counts as placing an existing product on the EU market?
For hardware, placing on the market means the first commercial supply of each individual product for distribution or use in the EU. An offer or agreement concerning a finished product can establish supply before physical delivery. Look for what the buyer was offered and on what terms. An internal stock reservation alone does not establish supply to a buyer.
In the sensor example, the signed November schedule explains why the 200 units could be collected in January under the earlier supply. Customs clearance and an invoice from the non-EU factory may help reconstruct the chronology. Neither identifies what rights the Polish distributor obtained in the remaining 50 units.
Can a distributor resell existing stock after the cut-off?
Yes, where the units were already placed on the EU market before the cut-off and have not since been substantially modified. Resale does not itself trigger a fresh CRA conformity assessment. A new shipment of the same model may have a different result. For finished units first placed on the market from 11 December 2027, check the applicable conformity assessment, EU declaration of conformity and CE marking before supply.
How to answer the distributor in writing
If procurement wants one statement for all future orders, offer a batch schedule it can reuse. Ask whether it needs evidence of first supply, a declaration of conformity for new units or a contractual warranty. Each request calls for a different document.
Which CRA duties already apply to existing products?
Since 11 September 2026, Article 14 has required manufacturers to report actively exploited vulnerabilities contained in an in-scope product and severe incidents affecting its security. Article 69(3) expressly includes products placed on the market before 11 December 2027. If a distributor forwards a customer report about an installed sensor, send it promptly to the team responsible for assessing reportability. Keep the time the manufacturer became aware and the affected versions with the file.
EU Cyber Resilience Act guide and key dates
Does a download after 11 December 2027 count as a new EU sale?
For standalone software supplied digitally, the European Commission treats copies of the same version as placed on the market together. Find the date that version was first offered on the EU market. A customer’s later download receipt can give you the wrong answer.
| Release history | CRA treatment |
|---|---|
| 10 September 2027. Version 3.2 for Windows is offered to EU customers. | Keep the offer, release archive and build identifier as evidence of the first EU release. |
| 15 January 2028. A new customer downloads exactly that Windows build. | The copy shares the earlier placing date. The January download does not trigger a fresh conformity assessment. |
| 1 February 2028. A distinct Linux edition is offered in the EU for the first time. | Assess the edition against its own first EU offer date. The Windows launch does not establish earlier supply of the Linux edition. |
A later version of the same edition, such as 3.2.1, is placed on the market anew only if it is a substantial modification. A new version number alone does not reset the date.
For software supplied with hardware, start with the device. A firmware download can affect the status of devices that receive it. The standalone-copy rule does not give every new sensor the date of its first firmware release.

When is a software update a substantial modification?
Under Article 3(30), a change after placing on the market is substantial if it affects compliance with the essential cybersecurity requirements or changes the intended purpose for which the product was assessed. Compare the released change with the original instructions, cybersecurity risk assessment and mitigations.
Temperature monitoring versus remote control
Firmware 1.4.2 corrects message validation on an installed sensor. It reduces risk and preserves the sensor’s functions. That will generally be a security fix. Keep the release notes and the engineer’s explanation of the security impact.
Firmware 2.0 lets the same sensor switch refrigeration equipment off remotely. A compromised account could now stop cooling, whereas it could previously only read the temperature. If the sensor was assessed for monitoring alone, this change is likely substantial. Resolve the conformity question before enabling remote control.
If remote control was already assessed and its safeguards built in, check that the released implementation matches those assumptions. A feature on a roadmap is weak evidence. For a legacy product substantially modified by its original manufacturer, the Commission’s guidance allows the assessment of obligations to focus on the modified parts unless the change adversely affects the cybersecurity of the whole product.
What should the supply agreement say about older stock?
Watch for wording such as “all products and future updates may be lawfully sold in the EU without further assessment”. Signing it could turn a defensible conclusion about 200 units into a promise about future hardware, software and changes made by the buyer.
A narrower starting point for the product schedule
Before signing, check who approves changes, who can enable optional features and who receives field reports. Read the indemnity and warranty provisions alongside the schedule. A limitation in an email may have little value if the signed agreement incorporates an unqualified answer from the procurement portal.
CRA clauses in software and distribution contracts
Can we keep selling this product in the EU?
Check one batch, one software version or one planned update. See which document to pull and what you can already tell your buyer.
If the buyer is waiting for a signature, CGO Legal can review the order, the evidence of first supply and the proposed warranty together. We can prepare a response for the documented units and mark the points that still need confirmation.
Review my distributor’s CRA clause
Related reading: CRA legal support · EU authorised representatives · CRA guide
Frequently asked questions
Is there a blanket CRA exemption for legacy products?
No. Article 69(2) looks at when the specific product was first placed on the EU market and whether it underwent a substantial modification from 11 December 2027. Article 14 reporting already applies to qualifying events involving existing products.
Will an invoice dated before 11 December 2027 be enough?
It can help if it identifies the finished units, the recipient and the actual supply. Check it against the order and terms. An advance invoice for an unspecified quantity or a stock report showing only location leaves material questions open.
Can security patches continue for pre-2027 products?
Yes. A patch that reduces risk while preserving the intended purpose generally falls short of substantial modification. Review a purported fix more closely if it moves a local function to a remote service or introduces a new dependency. Document the actual change and its effect on security.
Does a new firmware version reset the placing date for every device?
No. Identify the units receiving the release and assess what the update changes. Devices that stay on the previous firmware need a separate entry if the buyer wants a statement covering the entire installed fleet.
Who takes responsibility if our distributor modifies the product?
Under Article 21, an importer or distributor that substantially modifies a product already placed on the market assumes manufacturer obligations. Article 22 covers another person that substantially modifies a product and makes it available on the market. Ask who will supply the modified product and under whose name. A customer changing a device solely for its own use requires a separate analysis of its role and the warranty terms.
Does the same transition rule apply to a cloud subscription?
First identify what the customer receives. A hosted service, installed agent and self-hosted edition can lead to different scope decisions. Check the deployment before applying the dates to the subscription. Does the Cyber Resilience Act apply to SaaS?

