EU Data Act Connected Product Definition (2026)

Last updated: 23 August 2026

The phrase “connected product” is one of the most important definitions in the EU Data Act.

It determines whether a physical product can enter the Data Act's Chapter II framework for access to data generated through the use of connected products and related services. It also matters for the pre-contractual product-information requirements in Article 3, which are increasingly showing up in manufacturer documentation and marketplace product-data workflows.

The definition is broader than “smart home device,” but narrower than “anything with software.”

A connected product can be a consumer device, vehicle, industrial machine, piece of agricultural equipment, building system or medical device. It does not need to depend entirely on the public internet, and it does not automatically fall outside the definition simply because data are accessed through a physical connection or directly on the device.

At the same time, not every digital or networked product is a connected product for Data Act purposes. The regulation includes an important exclusion where the item's primary function is storing, processing or transmitting data on behalf of a party other than the user.

This guide explains the current legal definition, a practical scope test, examples and borderline cases, the difference between a connected product and a related service, the Article 7 small-enterprise exemption, and what the classification means for Product Data Notices and marketplace listings.

Already working on Article 3 information? Use the free EU Data Act Product Data Notice Generator to structure product-data type, format, estimated volume, storage, retention and access information.

Important: RegCatalog provides informational product-data tooling, not legal advice. Whether a particular product, company or contractual arrangement falls within the Data Act can require product-specific legal and technical analysis.

Quick answer: what is a connected product under the EU Data Act?

Article 2(5) of Regulation (EU) 2023/2854 defines a connected product through three core characteristics.

A product must:

obtain, generate or collect data concerning its use or environment;
be able to communicate product data through an electronic communications service, a physical connection or on-device access; and
not have as its primary function the storing, processing or transmission of data on behalf of a party other than the user.

The authoritative definition is in Article 2 of the EU Data Act on EUR-Lex.

The European Commission describes examples including:

connected cars;
health-monitoring devices;
smart-home devices;
planes;
robots;
industrial machines;
agricultural machinery.

See the Commission's Data Act explained and general Data Act policy page.

However, product classification should not stop at an example list. A manufacturer should work through the legal definition using the actual technical behavior and role of the product.

A practical five-question connected-product test

For most product teams, the clearest starting point is a structured five-question analysis.

1. Is there an “item” rather than only a digital service?

The connected-product definition starts with an item.

That makes the connected product concept fundamentally product-oriented. A physical device, machine, component or equipment item can qualify when the rest of the definition is met.

Pure software is not automatically a connected product simply because it exchanges data.

Software associated with a connected product may instead be a related service, discussed later in this guide.

Examples of physical items that may qualify include:

smart thermostats;
EV chargers;
industrial sensors;
connected locks;
robotic equipment;
smart appliances;
vehicles;
wearables;
agricultural machinery;
connected medical equipment.

Do not interpret “physical product” to mean the item must operate without software. Modern connected products commonly contain embedded software, firmware and operating systems. Recital 14 of the Data Act specifically discusses connected products generating data by means of their components or operating systems.

2. Does the item obtain, generate or collect data about its use or environment?

A connected product is not defined merely by possessing a network interface.

The product must obtain, generate or collect data concerning its use or environment.

Depending on the product, this can include:

operating state;
operating hours;
temperature;
pressure;
flow rate;
battery condition;
speed;
acceleration;
position;
energy consumption;
environmental conditions;
fault events;
diagnostics;
maintenance information;
configuration status;
alarm events.

The Commission's current Data Act explanation gives sensor examples such as temperature, pressure, flow rate, audio, pH, liquid level, position, acceleration and speed.

That list is illustrative rather than exhaustive.

The key question is:

Does normal use of the product produce or collect machine-readable information about the product's operation, use or surrounding environment?

If the answer is clearly no, the connected-product analysis becomes much weaker.

3. Can the product communicate product data?

The communication requirement is deliberately broader than “connects to the internet.”

Article 2(5) recognizes three broad routes:

an electronic communications service;
a physical connection;
on-device access.

That means a product may still satisfy the communication limb even if it:

has no permanent cloud connection;
exports data over USB;
exposes data through a local wired interface;
makes data accessible directly on the device;
communicates through local wireless connectivity rather than a conventional public internet connection.

Recital 14 gives examples of electronic communications networks including land-based telephone networks, television cable networks, satellite-based networks and near-field communications.

For product teams, the practical lesson is important:

“It is not cloud-connected” does not automatically mean “it is not a connected product.”

The technical route by which product data can be communicated matters.

4. What is the product's primary function?

This is the most important exclusion in the definition.

An item does not meet the connected-product definition where its primary function is storing, processing or transmitting data on behalf of a party other than the user.

This prevents the Data Act's connected-product rules from simply swallowing every piece of data infrastructure.

For example, Recital 15 distinguishes content or data that are generated, accessed or transmitted for storage or processing on behalf of third parties, referring to server or cloud infrastructure as examples of the issue.

This requires careful analysis.

A machine can contain substantial computing and communication capability without its primary function being data processing for another party.

A connected industrial compressor may collect and transmit diagnostics, but its primary function remains operating as industrial equipment.

A smart thermostat processes sensor data, but its core function remains controlling temperature.

By contrast, an infrastructure product whose central commercial function is to store, process or transmit third-party data needs a closer analysis under the primary-function exclusion.

Do not classify borderline infrastructure equipment using a simplistic rule such as:

“All routers are excluded.”

The wording of Article 2(5), ownership/use model and actual primary function matter. If the product is fundamentally data infrastructure, obtain product-specific advice rather than relying on a category label.

5. Is the product within the Data Act's territorial and market scope?

Being technically capable of meeting Article 2(5) is only part of the analysis.

Article 1 says the Regulation applies to manufacturers of connected products placed on the market in the Union, regardless of where those manufacturers are established, and to users in the Union of those connected products or related services.

Article 2 further defines:

making available on the market as supplying a connected product for distribution, consumption or use on the Union market in the course of commercial activity, whether for payment or free of charge;
placing on the market as the first making available of a connected product on the Union market.

See Article 1 and Article 2 on EUR-Lex.

This is why a manufacturer located outside the EU cannot assume that the Data Act is irrelevant simply because its headquarters are elsewhere.

If it places connected products on the EU market, the location of the manufacturer does not by itself remove the Regulation from consideration.

Connected-product scope: definition vs. obligations

One useful distinction is often missed:

A product can fit the Article 2(5) definition while a particular Chapter II obligation is limited or exempted for another reason.

For example, Article 7 contains a specific exemption for data generated through connected products manufactured or designed by qualifying micro and small enterprises in defined circumstances.

For the full threshold, partner/linked enterprise, subcontracting and medium-enterprise transition analysis, see the EU Data Act Article 7 SME Exemption guide.

That does not rewrite Article 2(5) so that the physical item suddenly stops being a connected product.

Instead, it affects the application of Chapter II obligations.

This distinction is useful when documenting scope:

Question A

Does the product fit the connected-product definition?

Question B

Are the relevant Chapter II obligations applicable to this manufacturer, provider, user and product?

Keeping those questions separate prevents a common reasoning error.

Examples of connected products

The Data Act is deliberately cross-sectoral.

Recital 14 says connected products can be found across private, civil and commercial infrastructure, vehicles, health and lifestyle equipment, ships, aircraft, home equipment, consumer goods, medical and health devices, and agricultural and industrial machinery.

The Commission likewise describes both consumer and industrial examples.

Smart-home equipment

Possible examples include:

smart thermostats;
app-controlled lighting;
smart appliances;
connected access systems;
home energy devices.

A typical product can generate data about:

device status;
environmental readings;
energy use;
configuration;
operating events;
diagnostics.

The Commission's related-service example uses a connected washing machine and an application that reads sensor data and adjusts the washing cycle.

Connected vehicles

Cars and other vehicles are a major Data Act use case.

Connected vehicles can generate substantial operational and environmental data, and the European Commission has issued sector-specific guidance on vehicle data under the Data Act.

That guidance repeats the Article 2(5) test and states that an OEM or data holder must assess whether a vehicle qualifies as a connected product.

See the Commission guidance on vehicle data and the Data Act on EUR-Lex.

Industrial machinery

The Commission expressly uses industrial machines as connected-product examples.

Potential data can include:

machine state;
temperature;
pressure;
vibration;
cycle counts;
diagnostics;
error events;
production-related operational readings.

The commercial significance is substantial: users may want the data for maintenance, repair, performance optimization or third-party services.

Agricultural machinery

Agricultural machinery is another explicit example.

Connected tractors, harvesters, irrigation systems, agricultural sensors and other equipment can generate operational/environmental data useful for:

maintenance;
optimization;
fleet management;
precision agriculture;
third-party services.

Health and fitness devices

The Commission includes medical and fitness devices among examples.

That does not displace health, medical-device or data-protection law. It simply means that a product can potentially be a connected product under the Data Act while also being subject to other regulatory regimes.

Building systems

A useful 2025 Commission Recommendation on building data explains that systems operating in buildings can qualify as connected products when they generate data and are capable of communicating it, including technical building systems such as heating or ventilation systems.

See the Commission Recommendation on access to building-system data on EUR-Lex.

This is especially relevant to manufacturers of:

HVAC controls;
smart-building sensors;
access equipment;
energy systems;
elevators;
building automation equipment.

Robots, aircraft and other professional equipment

The Commission also names robots and planes.

The lesson is that “connected product” is not a consumer-electronics term. It is a cross-sector legal definition for data-generating physical products.

Real-world manufacturer implementations

The growth of Data Act product-information pages gives useful practical evidence about how companies are interpreting the connected-product concept.

HP

HP's current EU Data Act support material describes connected products as products that generate, obtain or collect data about use, performance or environment and can communicate it through wired or wireless connectivity.

See HP's European Union Data Act support page.

HARMAN

HARMAN publishes pre-contractual EU Data Act information for connected products and related digital services, explaining that certain products qualify where sensors, software or connectivity features collect or generate data and make it available electronically.

See HARMAN's EU Data Act page.

Toyotomi

Toyotomi identifies “SMART products” with connectivity such as integrated Wi-Fi that generate, collect and transmit data, and publishes Data Act transparency information for those devices.

See Toyotomi's EU Data Act information.

These company pages are useful implementation examples, but the legal definition in Article 2 remains the controlling starting point. A manufacturer statement should not be used as a substitute for analysing another manufacturer's product.

A related service is a separate defined concept under Article 2(6).

It is a digital service, other than an electronic communications service, including software, that is connected to the product:

at purchase, rent or lease in a way where its absence would prevent one or more product functions; or
later, when connected by the manufacturer or a third party to add, update or adapt product functions.

This distinction matters because the Data Act has separate pre-contractual information requirements for connected products and related services.

Example

Imagine a connected heating system.

The hardware device can be the connected product.

An application that changes target temperatures, modifies schedules or otherwise affects the product's functions may be a related service, depending on the actual arrangement.

The Commission gives a washing-machine example where an application uses sensor data and changes the washing cycle; that application is described as a related service.

An app that merely displays unrelated content or provides general support material is not necessarily a related service.

The test focuses on the connection to product functions.

For more detail, see the Data Act definition in Article 2(6) and the Commission's Data Act explained.

Connected product vs. “smart device”

Retailers and marketplaces often use practical labels such as smart device.

That can be useful operationally, but it is not necessarily identical to the legal Article 2(5) definition.

For example, Kaufland's current marketplace implementation asks sellers whether a product “Concerns Data Act” and uses a field named “Smart Device Info URL.” It also uses a feed field called is_smart_device.

See Kaufland Global Marketplace's EU Data Act guidance.

For the marketplace workflow and exact Kaufland field IDs, see the Kaufland EU Data Act seller guide. For bol's practical “connected items” screening and document-upload workflow, see the bol EU Data Act seller guide.

The important point is:

A marketplace field name is not a replacement for legal classification.

If Kaufland asks for Data Act information for a product category, that is commercially important for the seller. But the underlying legal analysis still starts with Regulation (EU) 2023/2854.

Does a connected product have to be connected to the internet?

No.

The definition covers communication through:

electronic communications services;
physical connections;
on-device access.

That is broader than internet connectivity.

A product with a physical service interface may still satisfy the communication component.

Similarly, a device may connect only intermittently and still potentially qualify.

The relevant question is whether product data can be communicated through one of the routes recognized by Article 2(5), not whether a permanent internet session exists.

Does Bluetooth make a product a connected product?

Bluetooth or another wireless interface can be evidence of a communication capability, but Bluetooth alone does not establish the whole definition.

You still need to ask:

does the product generate/collect data about use or environment?
can relevant product data be communicated?
what is the primary function?

A basic Bluetooth accessory that communicates no relevant product data may present a different analysis from a sensor device that records operating/environmental data and exposes it through Bluetooth.

What is “product data”?

After deciding that the item may be a connected product, the next question is which data matter.

Article 2(15) defines product data as data generated by use of a connected product that the manufacturer designed to be retrievable through an electronic communications service, physical connection or on-device access by a user, data holder or third party.

The Commission explains that Chapter II applies to relevant raw and pre-processed data that are readily available to the data holder, including metadata necessary to interpret and use them.

Examples can include individual or grouped sensor measurements.

Product data is not the same as content

The Commission provides a useful connected-TV example:

screen-brightness data can be product data;
the film being watched is content and is not brought into Chapter II simply because it is displayed on the connected television.

This prevents “data generated by the product” from being interpreted as every digital thing that passes through the device.

Inferred and derived data

The Commission also explains that inferred or derived data, including highly enriched data resulting from additional investment, can fall outside the Chapter II access obligations.

For manufacturers, this creates another important distinction:

The connected product can be in scope even though not every dataset associated with that product is necessarily within the same access obligation.

What does “readily available data” mean?

The connected-product definition and the exact set of data that must be made available are related but different questions.

Article 2(17) defines readily available data in relation to product/related-service data that a data holder lawfully obtains or can lawfully obtain without disproportionate effort going beyond a simple operation.

Recital 20 explains that readily available data does not include data where the connected-product design does not provide for the data to be stored or transmitted outside the component in which they are generated or outside the product as a whole.

That is important for product teams.

The Data Act should not automatically be read as requiring every internal electrical or transient signal to become a new cloud dataset.

When mapping product data, distinguish:

data the product generates;
data technically retrievable by design;
data readily available to a data holder;
derived analytics;
content.

Does the Data Act apply to products from non-EU manufacturers?

Potentially, yes.

Article 1 applies to manufacturers of connected products placed on the market in the Union regardless of where the manufacturer is established.

This makes the regulation relevant to manufacturers outside the EU where the relevant connected products are placed on the EU market.

TikTok Shop's current European seller guidance likewise tells sellers that EU Data Act obligations can matter for sellers outside the EU when relevant products/services are sold to EU customers.

See TikTok Shop's EU Data Act seller FAQ.

The platform's simplified guidance should not replace legal analysis, but it demonstrates that marketplaces are operationalizing the rule across international sellers.

What about prototypes and products still in development?

Recital 14 says connected products in scope are products on the market and identifies prototypes as an exception in that discussion.

The market-placement concept therefore matters.

This does not mean manufacturers should wait until launch day to think about the Data Act.

Article 3(1)'s design requirement is specifically intended to affect how connected products and related services are designed for data accessibility.

For product teams, scope analysis should therefore happen before launch even if the relevant market obligations attach at placement/use stages.

The Article 7 SME exemption

One of the most important limitations is Article 7.

Article 7(1) says Chapter II obligations do not apply to data generated through connected products manufactured or designed, or related services provided, by a microenterprise or small enterprise, provided the stated conditions are satisfied.

Those conditions include enterprise-group relationships and subcontracting.

The same provision creates transitional treatment for certain newly medium-sized enterprises and connected products they place on the market.

See Article 7 in the EU Data Act.

What counts as a small enterprise?

The European Commission's SME definition uses:

Category	Staff	Turnover	OR balance sheet
Micro	<10	≤ €2m	≤ €2m
Small	<50	≤ €10m	≤ €10m
Medium	<250	≤ €50m	≤ €43m

The Commission also warns that a business in a larger group may need to include staff/financial information from partner or linked enterprises.

See the Commission's official SME definition.

Why “we have fewer than 50 employees” is not enough

A manufacturer with 35 employees is not automatically entitled to conclude that the Article 7 exemption applies.

Questions can include:

turnover/balance-sheet thresholds;
partner enterprises;
linked enterprises;
parent-company structure;
subcontracted manufacturing/design.

RegCatalog therefore treats scope and exemption analysis as a review question, not a one-click legal certification.

The 12 September 2025 and 12 September 2026 dates

These dates are frequently mixed together.

12 September 2025

The Data Act generally began to apply on 12 September 2025.

12 September 2026

Article 50 states that the obligation resulting from Article 3(1) applies to connected products and related services placed on the market after 12 September 2026.

Article 3(1) is the design/accessibility requirement: product data and related-service data, together with relevant metadata, should by default be easily, securely and freely accessible in a structured, commonly used, machine-readable format and, where technically feasible, directly accessible to the user.

See Article 50 on EUR-Lex.

Do not interpret the 2026 milestone as meaning that the entire Data Act or Article 3 only starts then.

Why connected-product classification matters for Product Data Notices

If a product is relevant to the Chapter II framework and the applicable obligations are not excluded or exempted, Article 3(2) requires pre-contractual information before purchase, rent or lease.

The seller, rentor or lessor — which may be the manufacturer — must provide at least information about:

product-data type;
format;
estimated volume;
continuous and real-time generation;
on-device or remote storage;
retention where applicable;
user access/retrieval;
erasure where relevant;
technical means;
terms of use;
quality of service.

For a detailed breakdown, read:

EU Data Act Product Data Notice: Article 3 Guide for Connected Products

Or create a structured draft with:

Free EU Data Act Product Data Notice Generator

Why connected-product classification matters to ecommerce teams

This is no longer only a legal-department question.

Marketplaces are turning the Data Act into product-listing data.

Kaufland

Kaufland's current seller documentation asks sellers to identify whether relevant products concern the Data Act and to provide the manufacturer's information link.

Its portal includes:

Concerns Data Act
Smart Device Info URL

Its CSV/XML feed uses:

is_smart_device
smart_device_manufacturer_information_url

Kaufland says the process must be repeated for each individual affected item and reserves the right to deactivate listings if relevant information is not submitted correctly.

See Kaufland's EU Data Act seller guidance.

TikTok Shop

TikTok Shop's March 2026 guidance for several EU markets similarly tells sellers that connected products can create obligations to disclose data information in product listings.

See TikTok Shop's seller FAQ.

The practical consequence is important:

A product-scope decision can affect product compliance, technical documentation, ecommerce content and marketplace operations at the same time.

A connected-product scope checklist for manufacturers

Use the following as an internal review checklist, not as a legal determination.

Product characteristics

Is there a physical item/product?
Does it obtain, generate or collect data?
Does that data concern product use or the product's environment?
Can product data be communicated electronically, through a physical connection or through on-device access?
Is the product's primary function something other than storing, processing or transmitting data on behalf of a party other than the user?

Market scope

Is the product being placed on the EU market?
Are relevant users in the Union?
Is this a production/commercial product rather than only a prototype?

Enterprise scope

Have we checked Article 7?
Have we checked micro/small enterprise thresholds?
Have we checked parent/linked/partner enterprise relationships?
Have we checked whether subcontracting affects the Article 7 analysis?
If recently medium-sized, have we reviewed the transitional provision?

Data map

Have we identified product-data categories?
Do we know which data are retrievable by design?
Do we know which data are readily available to a data holder?
Have we separated product data from content?
Have we separated raw/pre-processed data from inferred/derived information?

Is there an app/software/digital service connected to product functions?
Would the product lose a function without the service, or does the service add/update/adapt product functions?
Have we separately assessed Article 3(3) related-service information?

Illustrative classification examples

These examples are deliberately simplified. They show how to reason through Article 2(5); they are not legal conclusions for real products.

Example 1: connected environmental sensor

A commercial sensor:

measures temperature and humidity;
logs device state;
sends readings through a wireless gateway;
exposes historical readings through an application.

Likely reasoning:

physical item: yes;
generates environmental/use data: yes;
communicates product data: yes;
primary function is sensing/monitoring, not third-party data infrastructure.

This is a strong connected-product pattern.

Example 2: smart lock

A lock:

records lock state;
reports battery level;
records operating events;
communicates with a mobile app.

Again, the core product function remains access control. Data generation and communication support that function.

This is another strong connected-product pattern.

Example 3: industrial pump with USB diagnostics only

The pump:

generates operating hours and diagnostics;
stores the data locally;
exposes it through a service USB interface;
has no cloud connection.

The absence of internet connectivity does not automatically remove the product from Article 2(5), because physical connection and on-device access are explicitly recognized.

Example 4: generic cloud server

A server's commercial primary function may be storing or processing data for other parties.

That requires careful analysis under the primary-function exclusion.

The fact that the server generates temperature or utilization telemetry does not automatically make the connected-product analysis straightforward if its main purpose is data-processing infrastructure.

Example 5: smartphone application without dedicated hardware

A standalone app is not itself a physical “item.”

It may be a related service if it is linked to a connected product in the way defined by Article 2(6), or it may simply be a separate digital service.

Do not label every app a connected product.

Common connected-product classification mistakes

Mistake 1: “If it has Wi-Fi, it is in scope”

Wi-Fi can demonstrate communication capability, but the product must also generate/collect relevant data and satisfy the primary-function test.

Mistake 2: “If it has no internet, it is out”

Incorrect as a general rule.

Physical connections and on-device access are expressly included.

Mistake 3: “Any product with firmware is connected”

Embedded software does not itself establish the definition.

Mistake 4: “All data associated with a connected product are product data”

Content and inferred/derived data need separate treatment.

Mistake 5: “If the company is small, the product is not a connected product”

Article 7 affects Chapter II obligations; it does not erase the Article 2(5) technical definition.

The product and related service are separate defined concepts, even though both can fall within Chapter II.

Mistake 7: “The manufacturer must be established in the EU”

Article 1 expressly covers manufacturers of connected products placed on the Union market regardless of establishment location.

Mistake 8: “Marketplace categories decide legal scope”

Marketplace workflows matter commercially, but the Regulation remains the legal reference.

What product teams should do after identifying a likely connected product

A practical workflow is:

1. Record the scope rationale

Document:

product function;
generated data;
communication route;
primary-function assessment;
market-placement context.

Do not rely on a one-word spreadsheet entry with no rationale.

2. Check enterprise-level exemptions

Review Article 7 and corporate relationships.

3. Map product data

Work with:

engineering;
firmware;
cloud/backend;
product management;
product compliance.

Identify the data categories and what is technically retrievable.

Separate:

hardware product;
app;
cloud service;
digital service;
data holder.

5. Prepare Article 3 information

Capture product-data:

type;
format;
estimated volume;
generation behavior;
storage;
retention;
access/retrieval/erasure;
technical means;
terms;
quality of service.

6. Plan publication/distribution

Decide whether the manufacturer will maintain:

product webpage;
Product Data Notice PDF;
stable URL;
QR;
marketplace product attributes.

7. Assign ownership

The classification can affect multiple teams.

A useful internal owner may be Product Compliance or Regulatory Affairs, supported by Product/Engineering and Product Data/Ecommerce.

Frequently asked questions

What is the legal definition of a connected product under the EU Data Act?

Article 2(5) defines it as an item that obtains, generates or collects data concerning its use or environment, can communicate product data through an electronic communications service, physical connection or on-device access, and does not have as its primary function storing, processing or transmitting data on behalf of a party other than the user.

Is every IoT device a connected product?

Many IoT devices will fit the pattern, but “IoT” is not the legal test. Apply Article 2(5) to the actual product.

Does a connected product have to use Wi-Fi?

No. Article 2(5) also recognizes physical connections and on-device access.

Does Bluetooth count as connectivity under the Data Act?

Bluetooth can support the communication element, but the entire connected-product definition still has to be satisfied.

Are industrial machines covered by the EU Data Act?

They can be. The European Commission expressly identifies industrial machinery as a connected-product example, subject to the actual Article 2(5) characteristics and the other scope provisions.

Are smart-home products connected products?

Many smart-home devices fit the definition because they generate data about use/environment and communicate that data. Classification should still be made product by product.

Are servers connected products under the Data Act?

Data infrastructure requires closer analysis because Article 2(5) excludes items whose primary function is storing, processing or transmitting data on behalf of a party other than the user. Do not classify a server using telemetry alone.

Is a mobile app a connected product?

A standalone app is not a physical item. It may instead qualify as a related service when it is connected to a product in the manner defined by Article 2(6).

The connected product is the physical item. A related service is a digital service, including software, that is connected to the product and affects one or more of its functions under the Article 2(6) test.

Does the Data Act apply to non-EU manufacturers?

Yes, potentially. The Regulation applies to manufacturers of connected products placed on the Union market regardless of where those manufacturers are established.

Are small manufacturers exempt?

Article 7 provides a Chapter II exemption for certain micro and small enterprises, subject to group-relationship and subcontracting conditions. It also contains transitional treatment for certain newly medium-sized enterprises. Review the exact provision and the EU SME definition.

Does the 12 September 2026 date determine whether something is a connected product?

No. The Article 2(5) definition already exists. The 12 September 2026 date in Article 50 concerns when the Article 3(1) design/accessibility obligation applies to connected products and related services placed on the market after that date.

Is all data generated by a connected product covered?

No. The Data Act distinguishes product data, readily available data, content, and inferred/derived information. Classification of the product is only the first step.

Do sellers need to know whether a product is a connected product?

Increasingly, yes. Article 3(2) places pre-contractual information obligations on sellers, rentors or lessors, and marketplaces such as Kaufland and TikTok Shop have implemented seller-facing Data Act workflows.

Is a Product Data Notice required for every connected product?

The answer depends on the applicability of Article 3 and other scope/exemption conditions. Article 3(2) requires specified pre-contractual information for covered connected products, but the Regulation does not mandate that the artifact carry the specific title “Product Data Notice.”

Next step: document the product facts

Connected-product classification is not the final output.

It is the starting point for a structured product-data workflow:

Product scope
    ↓
Generated data categories
    ↓
Format + estimated volume
    ↓
Continuous / real-time behavior
    ↓
Storage + retention
    ↓
Access + retrieval + erasure
    ↓
Product Data Notice
    ↓
Website / PDF / marketplace information

If you already have a likely connected product, RegCatalog's free generator can help structure those product facts without requiring an account:

**Generate an EU Data Act Product Data Notice**

For a deeper explanation of the Article 3 fields, read:

**EU Data Act Product Data Notice: Article 3 Guide for Connected Products**

Primary sources and further reading

For product-scope decisions, start with the legislation and official guidance.

Manufacturer implementation examples

_RegCatalog provides product-data tooling and informational resources. It does not provide legal advice, legal representation, certification or a guarantee that a product is within or outside the scope of Regulation (EU) 2023/2854. Product scope can depend on technical design, contractual roles, enterprise status, market placement, sector-specific rules and the facts of the specific case._

What Is a Connected Product Under the EU Data Act? (2026)