The duty that already applies

Almost every compliance calendar lists the Data Act with 12 September 2026. The date is right, the conclusion usually is not. What begins on that day is only one part, and the more useful part has been running for a while.

What arrives in 2026

Article 3(1) requires connected products to be designed and manufactured so that the data they generate is accessible to the user by default. The wording is unusually concrete: easily, securely, free of charge, in a comprehensive, structured, commonly used and machine-readable format and, where relevant and technically feasible, directly.

That is a design rule, not a disclosure duty. A manufacturer does not satisfy it by producing an export on request. The data has to be accessible without anyone asking, and it must not cost anything.

The cut-off is not 12 September

Article 50 words the transitional rule like this: the obligation resulting from Article 3(1) applies to connected products placed on the market after 12 September 2026. The German text says the same.

After 12 September is not on 12 September. A product placed on the market on that very day is not yet covered by the design duty. It is a detail, but exactly the kind of detail that matters in a tender.

More important is the second half of that sentence: it turns on placing on the market, not on use. The entire existing stock stays outside. Anyone operating a machine today gains no data access from this rule that they did not have before.

And what has applied for a year

For the transitional rule Article 50 names only Article 3(1). Everything else has applied since 12 September 2025, and that includes paragraph 2.

It obliges sellers, renters and lessors to tell the user before the contract is concluded what data the product can generate: type, format and estimated volume, and whether the product generates data continuously and in real time.

That is the lever you already have today. Not in the legal department, but in procurement.

Why this is an inventory question

Obtaining that information before purchase tells you something that otherwise only surfaces in operation: whether a device releases its operating data at all, in what form, and whether a contract with the manufacturer is needed for it. Those very details later decide whether a system can be monitored, taken into an inventory and assessed in an emergency.

In practice: the question belongs in the procurement process, the answer in the system documentation. Both are processes that exist anyway.

What remains to be done

For operators the regulation is not a project at this point but one more question in purchasing and one more field in the inventory. For manufacturers of connected products it is the opposite; there the design duty reaches into development in a good year's time.

We track deadlines like this in the legal register with source and cut-off date, and they appear in the compliance calendar. Product-related context, not legal advice.