The Digital Product Passport and carbon footprint, for connected devices
After the Cyber Resilience Act, the next EU rules on the list of every electronics maker are about sustainability: a Digital Product Passport, carbon footprint figures and limits on green claims. Some of it already applies, most of it is years away. This is what is decided, what is not, and what is worth preparing while you build the product anyway.
The short version
- No Digital Product Passport is required for electronics yet. The Commission plans to decide the rules for ICT products around 2029; obligations follow after that.
- Batteries come first: a battery passport from 18 February 2027, for EV, light-transport and industrial batteries over 2 kWh.
- Green claims are already regulated: since 27 September 2026, generic claims such as "eco-friendly" are banned in the EU unless backed by recognised excellent environmental performance.
- For a small connected device, most of the carbon footprint is in making it, not in running it. What the firmware decides is how much power it uses and how long it stays useful.
What the Digital Product Passport is
The Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781) lets the Commission set ecodesign requirements per product group, and with them a Digital Product Passport: a record of the product reached through a data carrier on the product, its label or its packaging, such as a QR code, and linked to a unique product identifier.
What goes into it is decided group by group, in delegated acts. According to the Commission's FAQ it may include durability, reparability and recyclability, the materials and components used, manuals, repair instructions and spare parts, end-of-life guidance, and documents showing compliance with other EU law. The delegated act also says whether there is one passport per model, per batch or per item.
The data is not kept by the EU. The maker (or a service provider for it) hosts the passport; the EU keeps a registry of identifiers, which has been running since July 2026.
When it reaches electronics
The first ESPR Working Plan (April 2025) gives an indicative schedule for when the Commission aims to adopt the rules:
- 2026: iron and steel
- 2026 to 2029: energy-related products
- 2027: textiles, tyres and aluminium
- 2028: furniture
- 2029: mattresses and ICT products
Being on the plan does not mean a passport will be required: each group gets a study and an impact assessment first, which decides the requirements, whether a passport is the right tool, and the date it applies. Requirements under the ESPR normally apply no earlier than 18 months after the delegated act enters into force. For most connected electronics, a mandatory passport is therefore unlikely before about 2031.
Two things come sooner. A device with a battery is covered by the Batteries Regulation (EU) 2023/1542, whose battery passport applies from 18 February 2027 to EV, light means of transport and industrial batteries over 2 kWh; small batteries in sensors and gadgets are not among them. And mains-powered connected equipment already has energy limits: Regulation (EU) 2023/826 has capped standby and networked standby power since 9 May 2025, with stricter limits from 9 May 2027.
Where carbon footprint comes in
A carbon footprint figure is not a general part of every passport. It appears where a specific rule asks for it:
- Batteries. The Batteries Regulation requires a carbon footprint declaration for EV batteries, but it starts only once the calculation method is adopted in a delegated act, which has not happened yet.
- Product groups under the ESPR. A delegated act may require a carbon footprint as a product parameter. None does for electronics yet.
- Large companies' reports. After the 2026 simplification (Directive (EU) 2026/470), sustainability reporting under the CSRD covers EU companies with more than 1,000 employees and more than €450 million turnover. If you supply one of them, they may ask for data, but they cannot require more from smaller suppliers than the voluntary standard covers.
What you may say about it
The Empowering Consumers Directive (EU) 2024/825 applies from 27 September 2026, through each country's law. It bans generic environmental claims such as "green", "eco-friendly" or "environmentally friendly" without recognised excellent environmental performance, and sustainability labels that are not based on a certification scheme or set by a public authority. It applies to the box, the website and the datasheet. The separate Green Claims Directive, which would have set detailed rules for proving specific claims, has not become law.
In practice: a measured figure with its method ("0.4 W average in operation, measured at 230 V") is fine; "energy-efficient smart sensor" on its own is a risk.
Where the footprint of a connected device actually is
For small electronics, most of the life-cycle footprint comes from manufacturing, chips above all. Studies of mobile and IoT devices put production at roughly 60 to 80 percent, and higher for smaller devices (Pirson and Bol estimate the production footprint of IoT edge devices from the bottom up). Always-on devices on mains power can shift that balance, as the use phase adds up over a decade.
A rough example: an ESP32 that keeps WiFi connected draws about 0.2 to 0.5 W, depending on its power saving. Over a year that is 2 to 4.5 kWh, under 1 kg of CO2e at an average European grid. A sensor that sleeps and wakes every ten minutes uses a small fraction of that. The firmware decides which of the two your product is.
The firmware also decides the other half: how long the product stays useful. A device that gets security fixes and new features over the air for ten years has a smaller footprint per year of use than one replaced after three, and durability is exactly what the ESPR is about. The Cyber Resilience Act already asks for a support period of at least five years in most cases.
What to prepare now
None of this needs a passport system today. These are things a connected product benefits from anyway, and that a passport, a customer audit or a large customer's questionnaire will ask for later:
- A unique identifier per device, readable remotely, and tied to the serial number on the label.
- For every device, the firmware it runs, and the history of its updates.
- An SBOM for every build, and a record of known vulnerabilities and how you handled them (the Cyber Resilience Act asks for these anyway).
- The support period: until when the product gets security and functional updates.
- Measured power in each mode (active, idle, networked standby, sleep), and the conditions of the measurement.
- Materials and components from your suppliers: a bill of materials with the module and PCB data sheets, which is where the manufacturing footprint is.
- Wording on the box and the website checked against the ban on generic claims.
Where Pinscope fits
Pinscope already keeps part of that list for every device it connects: its identifier, the firmware version it runs and the history of its updates, the SBOM of each build with its known vulnerabilities, and the support period of the product (how that works). It does not know your hardware, materials or manufacturing footprint, and it does not issue Digital Product Passports.
We are looking at what a public product page built from that data could look like, the part of a future passport that is about software. If you are preparing for the Digital Product Passport and that would help, write to hello@pinscope.dev; what makers ask for decides what we build.
Dates and scope are from the texts linked above and the Commission's DPP FAQ, as of November 2026. Delegated acts and national rules change; check them for your product before relying on this page.
More
- Remote access to an ESP32 without TLS: what it measured and what it costs
- Reaching an ESP32 web server from outside its network
- Updating ESP32 firmware over the internet, with rollback
- Guru Meditation Error: decoding the backtrace, and crashes from the field
- Remote logging: ESP_LOG without a serial cable
- Heap and stack monitoring in the field
- An ESP32 behind CGNAT, 4G or Starlink
- TLS memory usage on the ESP32, and how to reduce it
- Sharing an ESP32 sensor page with anyone, without port forwarding
- ArduinoOTA over the internet, with a rollback
- ESP32 remote access compared: port forwarding, ngrok, Cloudflare Tunnel, Tailscale
- esp_http_server slow? The 250 ms delay and the fix
- Before the first ESP32 ships: a field support checklist
- ESP32 exception decoder: a Guru Meditation backtrace to lines, in the browser