bol EU Data Act Requirements for Connected Products: Seller Guide (2026)

Last verified against bol Partnerplatform guidance: 23 August 2026

If you sell smart or connected products on bol, the EU Data Act has become a product-listing requirement rather than just a legal-policy topic.

bol tells selling partners that they must inform customers before purchase about the data collected by relevant connected items. The marketplace provides its own European Data Act information template, accepts a manufacturer's own document if it contains the required information, and has built the requirement into the new-product publication flow for relevant electronics.

The dates matter:

• since 12 August 2025, bol has allowed sellers to upload the requested information as a document through the seller account;
• the EU Data Act has applied since 12 September 2025;
• from the end of December 2025, bol says that when new electronics are uploaded, sellers are asked whether the item collects data and, when the answer is yes, the requested product information must be added before the item goes online;
• from 1 April 2026, bol says it began phased enforcement by taking items offline where required content is missing.

That makes bol one of the clearest examples of an EU marketplace turning Article 3 information into a live ecommerce checkpoint.

This guide explains exactly what bol currently asks sellers to provide, how its template maps to EU Data Act Article 3, when a manufacturer's document can be used, what sellers should do when the manufacturer has not supplied the information, how enforcement works in 2026, and how manufacturers can prepare one structured source record that supports bol as well as other marketplaces.

Need to create the manufacturer document? Use the free EU Data Act Product Data Notice Generator to structure the product-data information before review and marketplace handoff.

Important: RegCatalog is independent and is not affiliated with or endorsed by bol. This guide is informational, not legal advice. Marketplace processes and enforcement can change, so verify current bol Partnerplatform guidance before production submission.

Quick answer: what does bol require under the EU Data Act?

bol's current Partnerplatform guidance says sellers of relevant connected items must make specified information available to customers before purchase.

bol's practical examples include:

• robot vacuum cleaners;
• smartwatches and other fitness equipment;
• smart lighting controlled through an app;
• connected washing machines;
• baby monitors;
• smart scales;
• connected doorbells;
• thermostats;
• refrigerators.

For relevant products, bol tells sellers to provide information covering:

1. the type, format and volume of data the item can generate;
2. whether data can be generated continuously and in real time;
3. whether data are stored on the item itself or on an external server, including retention;
4. how the user can consult, request/share or delete the data, including method, terms of use and quality of service.

Official bol source:

European Data Act (EDA) — bol Partnerplatform

bol also publishes an English template:

European Data Act Information Requirement — bol template

The template is not mandatory. bol explicitly says a manufacturer's own document can be uploaded instead, provided it contains the necessary information.

Why bol asks sellers for this information

The legal source is Article 3 of Regulation (EU) 2023/2854, the EU Data Act.

Article 3(2) requires specified information to be given before a contract for the purchase, rent or lease of a connected product is concluded.

The current legal text requires, at minimum, information about:

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

Primary source:

Regulation (EU) 2023/2854 — EUR-Lex

For a full field-by-field explanation, read:

EU Data Act Product Data Notice Guide

Seller responsibility matters

bol's FAQ emphasizes that the Data Act explicitly refers to the seller, rentor or lessor as parties that must provide the pre-contractual product information.

That is why a marketplace seller cannot always respond:

“The manufacturer should deal with this.”

The manufacturer is usually the best source of the technical facts, but the seller still needs the information available in the sales flow where the legal obligation applies.

Operationally, that creates a chain:

Manufacturer technical facts
        ↓
Product Data Notice / manufacturer document
        ↓
bol seller account
        ↓
Customer sees required product information before purchase

bol's EU Data Act timeline

The bol timeline is unusually useful because it shows the shift from guidance into actual listing operations.

12 August 2025 — document upload became available

bol says sellers could start uploading the requested Data Act information as a document through their seller account from 12 August 2025.

The seller can use:

• bol's template;
• or the manufacturer's own document.

12 September 2025 — EU Data Act applies

The Data Act generally became applicable on 12 September 2025.

bol's template states that from this date the information requirement applies to sellers in the relevant connected-item context.

End of December 2025 — new electronics listing gate

bol says that from the end of December 2025, when uploading new electronics assortment, it asks whether items collect data.

If the seller answers yes, the requested content must be uploaded.

bol states:

the items only go online once that information has been added.

This is a much stronger commercial mechanism than a generic compliance reminder.

It means incomplete Data Act product information can prevent a new connected electronics listing from becoming sellable.

1 April 2026 — bol's own phased enforcement

bol says that from 1 April 2026, it also began enforcement and takes items offline in phases where the required product content is missing.

As of August 2026, this date is in the past.

For current sellers, the Data Act workflow should therefore be treated as an active product-catalogue requirement, not a future deadline.

A note on ACM enforcement in the Netherlands

bol's seller guidance says the Netherlands Authority for Consumers and Markets (ACM) monitors Data Act compliance and may contact sellers or bol in response to complaints.

There is an important timeline nuance.

ACM itself states that the Dutch implementing act made ACM formally authorized to enforce the Data Act from 21 November 2025.

ACM also says transparency is a specific 2026 enforcement focus. It plans information activity and research into compliance with the obligation to explain what data smart devices collect and how users can access those data.

Official ACM sources:

• ACM is now authorized to enforce the Data Act
• Data from smart devices — ACM
• Data Sharing Guidelines — ACM

For sellers in the Netherlands, this gives the bol requirement a second layer:

bol can enforce marketplace content requirements, while ACM is the national authority with Data Act enforcement powers.

What does bol's Data Act template contain?

bol's English template is particularly useful because it reveals the exact information model the marketplace expects sellers to be able to supply.

The template is titled:

European Data Act Information Requirement

It tells the seller to describe the following.

1. What kind of data are collected?

The template asks for product data about use and environment, with examples such as:

• location data;
• usage statistics;
• sensor readings.

Then it asks for:

• file format, for example .csv or .json;
• approximate amount/volume;
• whether collection is continuous;
• whether it happens in real time.

Better implementation

Do not collapse everything into:

“The device collects usage data.”

A useful manufacturer record might look like:

This gives the seller a factual document rather than generic legal prose.

2. Where is the data stored?

bol's template asks:

• whether data are stored locally on the item;
• whether data are stored on an external server;
• how long the data are retained.

This aligns with Article 3(2)(c).

A product can have more than one answer.

Example:

Temperature readings:
- 24-hour rolling buffer on device
- 30-day retention in manufacturer cloud

Diagnostic events:
- local until overwritten
- uploaded to server only when remote diagnostics is enabled

If storage varies by account configuration, firmware or optional cloud service, say so rather than forcing a misleading single retention number.

3. How can the user view, share or delete data?

bol's template asks for a manufacturer's solution that explains at least:

• how users access data;
• how they request or share data;
• how they delete data;
• terms of service;
• quality of service.

The template describes quality-of-service concepts using examples such as:

• availability;
• speed;
• reliability;
• support.

This is important because terms of use and quality of service are often omitted from simplistic Product Data Notice templates.

For RegCatalog, they should be first-class fields.

The bol template is useful — but it is not an official EU form

bol says its template includes the minimum legal requirements and can be used to collect the information.

But the Data Act itself does not mandate:

• the bol template;
• its exact headings;
• one universal PDF structure;
• bol-specific wording.

A manufacturer's own document is acceptable to bol where the necessary information is included.

That means a manufacturer should ideally maintain one authoritative source rather than a separate legal narrative for every sales channel.

A stronger model is:

Structured product data
        ↓
Canonical Product Data Notice
        ↓
bol-ready PDF
        ↓
Kaufland manufacturer URL
        ↓
MediaMarktSaturn attribute mapping
        ↓
Distributor documentation

The underlying facts stay the same; the output format changes.

bol document vs. manufacturer Product Data Notice

For many sellers, the best solution is not to fill bol's template independently.

If the manufacturer already publishes a complete product document, use that source.

Manufacturer document advantages

• facts come from the party that knows the device;
• one document can cover multiple resellers;
• product updates can be centrally controlled;
• the manufacturer's engineering/compliance team can review it;
• different sellers are less likely to publish contradictory technical information.

Seller-created template advantages

bol's template is useful when:

• the manufacturer supplies the facts but no formatted document;
• the seller owns/private-labels the product;
• the seller is also the manufacturer/importer with access to the technical details;
• the seller needs a temporary structured way to collect information.

The seller should not invent missing facts

A reseller usually cannot independently know:

• exact server retention;
• whether data are generated in real time;
• firmware-level generation frequency;
• all export formats;
• manufacturer backend quality of service.

If those facts are missing, ask the manufacturer.

What if bol says the content is “optional”?

bol currently explains that for a small part of the assortment, the seller interface may show the content as optional.

bol then makes an important distinction:

in those cases, bol may not actively enforce the requirement yet, but it says the legal information obligation can still apply.

bol warns that a regulator can still request action.

Therefore:

Optional in the bol interface does not automatically mean optional under the Data Act.

This is a crucial operational point.

Marketplace validation status and legal applicability are different things.

Do not build an internal rule saying:

bol says optional → ignore

Instead:

1. assess product scope;
2. check Article 7 where relevant;
3. obtain the manufacturer information;
4. complete the marketplace content even if bol has not yet made the field technically blocking.

How do I know whether an item is “connected”?

bol describes connected items in practical seller language:

items that collect data and/or work with an app

and gives consumer examples such as smartwatches, robot vacuums, smart lighting and connected appliances.

That is helpful for screening.

But it is not the complete legal test.

The Data Act's Article 2(5) definition looks at whether an item:

• obtains, generates or collects data concerning its use or environment;
• can communicate product data through electronic communications, a physical connection or on-device access;
• does not have as its primary function storing, processing or transmitting data on behalf of a party other than the user.

For the detailed scope test, read:

What Is a Connected Product Under the EU Data Act?

Important: internet connection is not the only route

bol's examples understandably focus on internet-connected consumer devices.

The Data Act definition is broader.

A product can potentially qualify where data are accessible through:

• a physical connection;
• on-device access;

even without a permanent internet connection.

So do not use:

no Wi-Fi = not connected

as your legal classification rule.

Are small sellers exempt from bol's requirement?

Do not assume so.

The Data Act has an Article 7 carve-out for certain products manufactured/designed or related services provided by qualifying micro and small enterprises, subject to additional conditions.

But that is not the same as:

every small marketplace seller is exempt.

Example:

• seller has 8 employees;
• seller lists a smart camera;
• camera is manufactured by a large electronics company.

The seller's own headcount does not transform the large manufacturer's product into a small-enterprise product.

For the Article 7 analysis, read:

EU Data Act Article 7 SME Exemption: Who Is Actually Exempt?

What if the manufacturer refuses to provide information?

This is a real seller problem.

bol's FAQ specifically addresses a manufacturer refusing to share data because it claims trade-secret concerns. bol directs sellers in special cases to the ACM and says they should proactively report the situation.

However, sellers should be careful not to oversimplify this.

The Data Act's trade-secret regime is detailed. Articles 4 and 5 contain mechanisms around identifying trade secrets, agreeing technical and organizational confidentiality measures, withholding/suspending data sharing in specific circumstances, and notifying the competent authority. Exceptional refusal requires substantiation.

A generic statement:

“trade secret, therefore we provide no information”

should not be treated as a complete Article 3 strategy without legal review.

Practical seller response

If a manufacturer refuses:

1. ask exactly which information it says cannot be disclosed;
2. distinguish pre-contractual descriptive information from later data-access requests;
3. ask the manufacturer for a compliant public Product Data Notice covering what can be disclosed;
4. retain the written response;
5. consult bol's current guidance;
6. seek legal advice / ACM guidance where necessary.

Do not fabricate the missing product data yourself.

Does bol require a URL or a document?

This is an important difference between bol and Kaufland.

Kaufland's current workflow prominently uses a manufacturer Smart Device Info URL.

bol's current public Data Act guidance instead describes document upload through the seller account.

It says sellers can:

• use bol's template;
• or upload a manufacturer's own document.

As of 23 August 2026, the public bol Data Act guidance reviewed for this article does not document a dedicated Data Act marketplace field analogous to Kaufland's smart_device_manufacturer_information_url.

Therefore, do not assume the same channel integration.

For RegCatalog, the practical bol output should be:

bol-ready Product Data Notice PDF/document

rather than inventing an unsupported bol URL or API field.

Does bol offer a Data Act API field?

The current public Data Act guidance reviewed for this article focuses on the seller-account document upload and listing workflow.

RegCatalog should not claim a bol Data Act-specific API integration unless bol documents one and it has been implemented/tested.

That distinction is important for product architecture.

Today

Useful RegCatalog outputs:

• Article 3 Product Data Notice;
• PDF;
• structured source JSON;
• bol readiness checklist.

Later, only if documented

• direct bol API/feed mapping.

Do not confuse a generic marketplace API with a documented Data Act submission interface.

A practical bol workflow for marketplace sellers

Step 1 — identify likely connected items

Start with:

• electronics;
• products with apps;
• products with sensors;
• devices generating usage/environment data.

Use bol's examples for screening, then apply the actual connected-product test.

Step 2 — obtain manufacturer information

Ask for:

• Product Data Notice;
• Data Act notice;
• connected-product information;
• Article 3 information.

Confirm:

• exact product/model;
• date/version;
• completeness.

Step 3 — validate the four core information groups

Check that the document covers:

• type / format / volume;
• continuous / real-time;
• local / external storage and retention;
• access / request / deletion, technical means, terms and QoS.

Step 4 — upload through the seller account

Use bol's current seller workflow.

If using the bol template, fill it with actual technical facts.

If using a manufacturer document, ensure the required information is present.

Step 5 — verify listing status

For affected new electronics, bol says the item only goes online when the requested content has been added.

Step 6 — monitor existing catalogue

Since April 2026, bol says it removes items with missing content in phases.

Do not focus only on new listings.

Step 7 — keep a source register

For every relevant EAN/SKU:

EAN
Product
Manufacturer
Manufacturer document
Document version/date
bol upload status
Last reviewed
Internal owner

This is especially useful for multi-brand sellers.

A practical bol workflow for manufacturers

Manufacturers should make sellers' job easier.

Step 1 — identify connected product families

Maintain:

• product;
• model;
• SKU;
• EAN/GTIN;
• related service;
• country/market scope.

Step 2 — collect product-data facts

Obtain them from:

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

Step 3 — create one canonical Product Data Notice

The notice should be reviewed internally and identify exactly which models it covers.

Step 4 — generate a bol-ready PDF

The output should be understandable without access to your internal systems.

Step 5 — create a reseller package

Example:

Product: Smart Thermostat T100
EAN: ...
Article 3 document: T100-data-act.pdf
Manufacturer canonical page: https://...
Last updated: 2026-08-01

Step 6 — distribute proactively

If you have 20 distributors, do not wait for 20 individual support tickets.

Make the documentation available in:

• dealer portals;
• reseller product feeds;
• compliance libraries;
• sales documentation.

Step 7 — review on product changes

Trigger review when:

• firmware changes generated data;
• a cloud service is introduced;
• retention changes;
• an API/access method changes;
• a model joins/leaves a family notice.

Why bol's workflow is a manufacturer product-data problem

At first glance, bol's requirement looks like seller compliance.

But sellers depend on manufacturers for technical facts.

That creates a hidden upstream workflow:

bol listing requirement
        ↓
Seller asks manufacturer
        ↓
Manufacturer asks compliance
        ↓
Compliance asks engineering
        ↓
Engineering identifies data
        ↓
Document created
        ↓
Seller uploads document

If this happens every time a distributor lists a new SKU, the organization is paying for the same translation repeatedly.

A better model is:

Manufacturer structured source
        ↓
Product Data Notice
        ↓
bol-ready document
        ↓
Seller/distributor package

That is the workflow RegCatalog is designed to support.

bol vs. Kaufland: the same facts, different channel output

The comparison is commercially important.

Kaufland

Current workflow:

• Data Act status;
• manufacturer information URL;
• CSV/XML/API-supported product attributes.

bol

Current public workflow:

• seller indicates data collection in relevant new electronics flow;
• required content/document is uploaded;
• bol template or manufacturer's own document can be used.

Same underlying regulation.

Different marketplace representation.

That is exactly why connected-product manufacturers should not maintain marketplace-specific legal prose independently.

One structured source record can generate:

Article 3 source record
   ├── bol PDF
   ├── Kaufland manufacturer URL
   ├── MediaMarktSaturn fields
   ├── distributor document
   └── manufacturer web page

For the Kaufland workflow, see:

Kaufland EU Data Act Requirements for Connected Products

What should a bol-ready Product Data Notice contain?

A practical document can use this structure.

Information about the connected item

Product identification

• manufacturer;
• brand;
• product;
• model;
• EAN/GTIN;
• document version;
• last updated.

1. Product data generated

For each category:

• data type/nature;
• example data;
• format;
• estimated volume.

2. Continuous and real-time generation

State:

• continuous yes/no/conditional;
• real-time yes/no/conditional;
• frequency/trigger.

3. Storage and retention

State:

• local/on-device storage;
• external/remote storage;
• retention;
• configuration differences.

4. User access, request/share and deletion

State:

• access mechanism;
• retrieval/export mechanism;
• deletion/erasure mechanism where relevant;
• technical means;
• relevant URL/contact.

5. Terms and quality of service

State:

• terms URL;
• availability/speed/reliability/support where applicable.

6. Manufacturer/data-holder contact

Provide a usable route.

7. Version information

• effective date;
• last updated;
• canonical manufacturer URL if available.

This structure is more reusable than a one-off marketplace document.

Common bol EU Data Act mistakes

Mistake 1: waiting until a listing is blocked

For new relevant electronics, bol says the information can be required before publication.

Prepare documents before product launch.

Mistake 2: uploading a generic privacy policy

A privacy policy does not necessarily contain Article 3 product-data fields.

Mistake 3: using a manufacturer brochure

Marketing specifications rarely include:

• estimated data volume;
• retention;
• access mechanism;
• quality of service.

Mistake 4: writing technical details without manufacturer confirmation

Sellers should not guess.

Mistake 5: leaving “optional” content blank automatically

bol says optional in some UI cases can still correspond to a legal requirement even where bol is not actively enforcing it yet.

Mistake 6: assuming only Wi-Fi products matter

The legal connected-product definition is broader than bol's consumer-friendly examples.

Mistake 7: forgetting existing listings

bol's April 2026 phased enforcement applies to missing content, not only new uploads.

Mistake 8: ignoring document versioning

If a manufacturer replaces a product notice, your uploaded copy can become stale.

Mistake 9: using one family document where models differ materially

If one model adds location data or a cloud service, document the difference.

Mistake 10: treating trade secret as a blanket exclusion

Use the Data Act's actual trade-secret framework and seek specialist advice.

Mistake 11: assuming bol has a Data Act API field because another marketplace does

The current public bol guidance reviewed here describes document upload. Do not invent an API integration.

Mistake 12: creating a different source document for every marketplace

Maintain one structured product source and transform it into channel-specific outputs.

bol EU Data Act checklist

Scope

• Product is screened for connected-product characteristics.
• Manufacturer/designer identified.
• Related service identified if relevant.
• Article 7 SME rules checked where applicable.
• Internal scope owner assigned.

Manufacturer information

• Product/model is clearly identified.
• Product-data types are listed.
• Formats are listed.
• Estimated volumes are provided or meaningfully explained.
• Continuous generation is stated.
• Real-time generation is stated.
• Local storage is stated.
• Remote storage is stated.
• Retention is stated where applicable.
• User access is explained.
• Retrieval/request method is explained.
• Deletion/erasure is explained where relevant.
• Technical means are documented.
• Terms of use are linked/described.
• Quality of service is described.

bol workflow

• Current Partnerplatform guidance checked.
• Correct document prepared.
• Document uploaded through seller account where required.
• New listing publication status verified.
• Existing catalogue checked for phased enforcement.
• “Optional” fields reviewed rather than ignored automatically.

Maintenance

• Manufacturer source/version recorded.
• Document review date recorded.
• Product changes trigger re-review.
• Marketplace guidance rechecked periodically.

Frequently asked questions

What is the bol EU Data Act requirement?

bol requires sellers of relevant connected items to provide customers with specified information about the data those products generate and how users can access/manage that data. For relevant new electronics, bol can require the information before the item is published.

When did bol start requiring Data Act product information?

bol enabled seller-account document upload from 12 August 2025. The EU Data Act has applied since 12 September 2025. From the end of December 2025, bol says relevant new electronics can be gated on the information, and from 1 April 2026 bol began phased enforcement for missing content.

What happens if I do not add the information?

bol says relevant new items may not go online until requested information is added. It also says that since 1 April 2026 it has been taking items with missing content offline in phases.

Who enforces the Data Act in the Netherlands?

The Netherlands Authority for Consumers and Markets (ACM) is authorized to enforce the Data Act in the Netherlands. ACM says its formal enforcement powers began when the Dutch implementing act entered into effect on 21 November 2025.

What is the bol Data Act template?

bol provides a European Data Act information template that helps sellers collect product-data type/format/volume, continuous/real-time generation, storage/retention and user access/request/delete information including terms and quality of service.

Is the bol template mandatory?

No. bol explicitly says sellers may instead upload a manufacturer's own document as long as it contains the necessary information.

Can I upload the manufacturer's Product Data Notice?

Yes, according to bol's guidance, provided the document contains the requested/required information.

What products does bol call connected items?

bol gives examples including robot vacuum cleaners, smartwatches, smart lighting, washing machines, baby monitors, scales, doorbells, thermostats and refrigerators. These are practical examples, not a complete legal definition.

Does a product need internet access to qualify?

Not necessarily under the EU Data Act. Article 2(5) also recognizes physical connection and on-device access. bol's examples are simplified for marketplace sellers.

What if bol marks the Data Act content as optional?

bol says that for a small part of its assortment the content may be shown as optional even though the legal requirement can still apply. bol may simply not be actively enforcing that part yet.

Can a small seller ignore the requirement?

Do not assume so. Article 7's carve-out relates to qualifying manufacturers/designers/related-service providers and additional conditions, not simply the size of the marketplace seller.

What if the manufacturer has no Data Act document?

Contact the manufacturer and request product-specific information. If necessary, use bol's template to organize manufacturer-supplied facts. Do not guess technical details.

What if the manufacturer says the data are trade secrets?

bol's FAQ directs sellers in special trade-secret situations toward ACM. The EU Data Act contains a detailed trade-secret protection mechanism, so obtain appropriate legal guidance rather than treating trade-secret status as an automatic reason to omit all information.

Does bol require a manufacturer URL?

The current bol public Data Act guidance reviewed for this article focuses on document upload. That differs from Kaufland, which explicitly uses a manufacturer information URL.

Is there a bol Data Act API field?

The current public bol Data Act guidance reviewed as of 23 August 2026 does not document a dedicated Data Act API field comparable with Kaufland's product attributes. Do not assume a direct integration unless bol publishes one.

Can one document cover several EANs or variants?

Potentially, if it clearly identifies all covered products and the relevant data characteristics are accurate across them. If models differ materially, document the differences or use separate notices.

What should “quality of service” contain?

bol's template gives examples such as availability, speed, reliability and support. The correct description depends on the actual method users use to access or retrieve the data.

Is a privacy policy enough?

Usually not by itself. A GDPR privacy notice focuses on personal-data processing, while Article 3 requires product-data information such as formats, estimated volume, real-time generation, storage and access.

Does RegCatalog upload directly to bol?

Not unless a documented integration is actually implemented. RegCatalog's current role is to help structure the manufacturer source information and generate review-ready/channel-ready artifacts.

Build the source once, then adapt it for bol

The most important lesson from bol is not the PDF template.

It is the workflow dependency.

The seller must publish product information, but the manufacturer usually controls the technical facts.

That means the scalable solution is upstream:

Manufacturer product data
        ↓
Structured Article 3 record
        ↓
Reviewed Product Data Notice
        ↓
bol-ready document
        ↓
Seller account

The same record can then support other channels:

                        ┌─ bol PDF
Product source record ──┼─ Kaufland URL
                        ├─ MediaMarkt fields
                        ├─ distributor pack
                        └─ manufacturer webpage

That is the RegCatalog model:

Maintain product regulatory data once. Publish it everywhere.

Useful next steps

• Generate a Product Data Notice
• Read the Article 3 Product Data Notice guide
• Check what counts as a connected product
• Understand the Article 7 SME exemption
• Compare the Kaufland Data Act workflow

Primary sources and further reading

bol

1. bol Partnerplatform — European Data Act (EDA)
2. bol — European Data Act Information Requirement template (English PDF)
3. bol — New European legislation: provide insight into data from connected items
4. bol Partnerplatform — Legislation and regulations
5. Selling via bol as a Dutch or Belgian partner

EU / Netherlands

1. Regulation (EU) 2023/2854 — EU Data Act
2. European Commission — Data Act explained
3. ACM — Data from smart devices
4. ACM — now authorized to enforce the Data Act
5. ACM — Data Sharing Guidelines

_RegCatalog is an independent informational product-data tool. It is not affiliated with, sponsored by or endorsed by bol. RegCatalog does not provide legal advice or certification. bol seller-account requirements, enforcement processes and content workflows can change; verify current bol Partnerplatform guidance before production submission._