> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://tieback.io/docs/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server. # Digital Product Passports for Electronics: What Companies Need to Know > A practical, legally disciplined guide to Digital Product Passports for electronics: why no electronics passport date exists under Regulation (EU) 2024/1781, how the 2025-2030 working plan treats ICT through two horizontal measures rather than a sector act, what RoHS, WEEE, energy labelling and existing ecodesign rules already require, and how to prepare bill of materials, component, supplier and evidence data before product-specific requirements arrive. ## Executive Summary Electronics is the sector where the gap between existing product regulation and future Digital Product Passport obligations is widest, and where the preparation problem is hardest. Electronics companies already live inside a dense regulatory environment: substance restrictions, waste and treatment information duties, energy labelling and product registration, product-specific ecodesign rules with spare parts and repair information obligations, and general product safety traceability. None of those regimes is a Digital Product Passport. All of them generate data that a future passport is likely to draw on. The instrument that will eventually create an electronics passport is **Regulation (EU) 2024/1781**, the Ecodesign for Sustainable Products Regulation, in force since 18 July 2024. It is a **framework**. Articles 9, 10 and 11 set out what a passport must be and what a product-specific measure has to specify. Article 4 gives the Commission the power to adopt those product-specific measures as delegated acts. A passport becomes a legal obligation for a given product only when a delegated act covering that product group says so. **No ESPR delegated act imposing Digital Product Passport requirements on any electronics or ICT product group has been adopted. There is therefore no electronics passport date, no electronics passport dataset, and no electronics passport deadline.** Anyone quoting one is quoting an estimate or an invention. What does exist is a published sequence. The **Ecodesign for Sustainable Products and Energy Labelling Working Plan 2025-2030**, adopted on 19 April 2025 as COM(2025) 187, does **not** list electronics or ICT among its ranked priority product groups. Those ranked groups are textiles and apparel, furniture, tyres and mattresses for final products, and iron and steel and aluminium for intermediate products. Instead the working plan states that ICT products are included in the plan because they will be covered by the work preparing **two horizontal measures**: a measure on **repairability, including scoring**, with an indicative adoption target of **2027**, and a measure on **recycled content and recyclability of electrical and electronic equipment**, with an indicative adoption target of **2029**. It also notes that some specific ICT products will continue to be handled through the work on energy-related products. Those are targets in a planning document, not law, and Article 4 requires at least **18 months** between the entry into force of a delegated act and its application, barring justified exceptions. That structure matters more than it first appears. For most sectors, passport requirements will arrive through a single product-group act. For electronics, the current plan points towards obligations arriving **horizontally and in pieces**, cutting across many product families at once, layered on top of an existing stack of product-specific rules that already differ by product. Preparation cannot be organised around waiting for one act with one date. Meanwhile a great deal is already law. Substance restrictions and conformity documentation under **Directive 2011/65/EU** on the restriction of hazardous substances. Treatment and reuse information for recyclers, and product marking, under **Directive 2012/19/EU** on waste electrical and electronic equipment. Energy labelling and registration in the European Product Registration Database for Energy Labelling under **Regulation (EU) 2017/1369**. Product-specific ecodesign rules such as **Regulation (EU) 2023/1670** for smartphones and slate tablets, **Regulation (EU) 2019/2021** for electronic displays and **Regulation (EU) 2019/424** for servers and data storage products, which impose durability, spare parts availability and repair information duties. Traceability duties under **Regulation (EU) 2023/988**, the General Product Safety Regulation, applicable since 13 December 2024. None of these is a passport. All of them are sources of passport-relevant data and evidence, and most of them are already imperfectly governed inside the companies that must comply with them. The practical message of this guide is simple. **Electronics passport implementation is not primarily a web page problem. It is a product data, component, supplier, evidence and lifecycle management problem.** A passport for a laptop or a washing machine is only as good as the bill of materials behind it, the component declarations behind that, and the change control that keeps both true after a component is substituted six months into production. This guide creates **no new framework**. It applies models the library already teaches. Nothing here is legal advice, and the electronics position will change as the horizontal measures develop. Verify the current position on EUR-Lex before making any decision with legal consequences. ## Table of Contents * [What Is an Electronics Digital Product Passport?](#what-is-an-electronics-digital-product-passport) * [Do Electronics Already Require Digital Product Passports?](#do-electronics-already-require-digital-product-passports) * [Which Electronic Products Could Be Affected?](#which-electronic-products-could-be-affected) * [Why Electronics Are Difficult](#why-electronics-are-difficult) * [What Information May Matter?](#what-information-may-matter) * [Where Does Electronics Passport Data Come From?](#where-does-electronics-passport-data-come-from) * [Bills of Materials and Component Data](#bills-of-materials-and-component-data) * [Supplier and Contract Manufacturer Data](#supplier-and-contract-manufacturer-data) * [Evidence and Regulatory Claims](#evidence-and-regulatory-claims) * [Data Quality and Validation](#data-quality-and-validation) * [Product Identity, Serialisation and Data Carriers](#product-identity-serialisation-and-data-carriers) * [GS1, Digital Link, EPCIS and Other Standards](#gs1-digital-link-epcis-and-other-standards) * [Repairability and Lifecycle Information](#repairability-and-lifecycle-information) * [Enterprise Architecture](#enterprise-architecture) * [Legal Responsibility](#legal-responsibility) * [Conformity and Existing Product Regulation](#conformity-and-existing-product-regulation) * [Preparing Before Final Requirements Exist](#preparing-before-final-requirements-exist) * [Pilot Strategy](#pilot-strategy) * [Worked Example](#worked-example) * [Common Mistakes](#common-mistakes) * [Preparation Checklist](#preparation-checklist) * [Frequently Asked Questions](#frequently-asked-questions) * [References](#references) ## What Is an Electronics Digital Product Passport? Start with the object itself, because the vocabulary is routinely collapsed and the collapse causes bad architecture decisions. A structured, machine-readable record of regulated information about a specific product, model, batch or item, reachable through a persistent unique identifier carried on the product by a data carrier, with defined access rights for defined actors. Under Regulation (EU) 2024/1781 it becomes an obligation for a product only when a delegated act adopted under Article 4 covers that product group and says so. Seven things are distinct, and an electronics programme that keeps them distinct will make better decisions than one that does not. **The electronic product.** The physical article placed on the market: a monitor, a router, a cordless drill, a dishwasher, a network switch. It has a physical configuration that may change during its production life. **Product identity.** The conceptual answer to "which thing is this". Electronics answers that question at several levels at once: a product family, a model, a commercial variant, a regional configuration, a production batch, an individual serialised unit. Identity is a modelling decision before it is a data decision. **Product identifier.** The actual string that names one of those levels. A model number, a commercial code, a global trade item number, a serial number, a manufacturer specific code. An identifier is only useful if the organisation can say precisely which identity level it names. **Data carrier.** The physical or digital thing that carries the identifier so that a machine can read it: a printed QR code, a data matrix, a bar code, an NFC tag, a label on the rating plate. The carrier is plumbing. **The passport.** The governed record reached by resolving the identifier, presenting the required information to the audience entitled to see it. **The underlying data.** The engineering, commercial, compliance and service information the passport draws on, which lives in product lifecycle management, enterprise resource planning, product information management, quality, compliance and service systems, and in supplier submissions. **The evidence.** The test reports, supplier declarations, certificates, calculations and analyses that substantiate a claim. Evidence is not the claim. A recycled content figure in a passport is a claim; the supplier mass balance record behind it is evidence. #### A QR code on the rating plate is a Digital Product Passport A QR code is a data carrier. It encodes a string. Whether that string resolves to a governed, access-controlled record of regulated information, whether that record is accurate, and whether it stays accurate after a component substitution, are entirely separate questions. Electronics manufacturers frequently already print QR codes for warranty registration, manuals or support. None of that is a passport, and reusing the same carrier does not make it one. ## Do Electronics Already Require Digital Product Passports? The direct answer: **no**. There is no adopted EU legal requirement for a Digital Product Passport for any electronics or ICT product group, and therefore no date. The honest answer needs five separations, because "electronics already have to publish product information" is true, and it is not the same statement. ### Existing environmental and product obligations, which are law today These are in force and enforceable. None of them is a passport. * **Directive 2011/65/EU** restricts hazardous substances in electrical and electronic equipment, including lead, mercury, cadmium, hexavalent chromium, polybrominated biphenyls and polybrominated diphenyl ethers, with four phthalates added by Directive (EU) 2015/863. It requires CE marking, an EU declaration of conformity, and technical documentation held by the manufacturer. * **Directive 2012/19/EU** on waste electrical and electronic equipment requires producers, under Article 15, to make reuse and treatment information available free of charge to reuse centres and treatment and recycling facilities within one year of placing equipment on the market, identifying components and materials and the location of hazardous substances, through manuals or electronic media. It also requires the crossed-out wheeled bin marking under Annex IX for equipment placed on the market after 13 August 2005, with producer identification and a date reference. * **Regulation (EU) 2017/1369** on energy labelling requires suppliers to register models in the European Product Registration Database for Energy Labelling before placing them on the market, with a public part and a compliance part accessible to market surveillance authorities. * **Product-specific ecodesign measures adopted under Directive 2009/125/EC** remain in force and impose real duties on named product groups. Regulation (EU) 2023/1670 for mobile phones, cordless phones and slate tablets, together with the energy labelling Regulation (EU) 2023/1669, sets durability and reliability requirements, spare parts availability duties towards professional repairers and in part end users, obligations on indicative spare part pricing, and repair and disassembly information duties. Regulation (EU) 2019/2021 does comparable work for electronic displays, and Regulation (EU) 2019/424 for servers and data storage products. * **Regulation (EU) 2023/988**, the General Product Safety Regulation, applicable since 13 December 2024, imposes traceability duties, including identification of the economic operator and of the product by type and batch or serial number. > **Tip** > > Read that list as a data inventory rather than a compliance inventory. Almost every element a > future electronics passport is likely to want already exists somewhere in an organisation that > complies with these regimes. The problem is that it exists in declarations, technical files, > database submissions, service manuals and supplier emails, not in a governed, machine-readable, > per-product dataset. ### The ESPR framework, which is law but not yet a product obligation Regulation (EU) 2024/1781 has applied since 18 July 2024. Its passport provisions are real law, and they constrain what any future electronics measure can require. Article 9 makes passport availability a market access condition once a product group is covered, requires passport data to be accurate, complete and up to date, and lists what a delegated act must specify: the data to be included by reference to Annex III, the data carriers, their layout and positioning, whether the passport applies at model, batch or item level, who may access what, and how long the passport must remain available, which must be at least the expected lifetime of the product. Article 10 sets essential requirements including a persistent unique product identifier, a data carrier physically present on the product, its packaging or its documentation, an open and interoperable machine-readable format, and back-up arrangements. Article 11 addresses interoperability and free access for a broad list of actors, including professional repairers, independent operators, refurbishers, remanufacturers and recyclers, which is a notably electronics-relevant list. None of that applies to a specific electronic product until a delegated act brings that product group in. ### Commission prioritisation, which is stated intention and not law COM(2025) 187 of 19 April 2025 is a planning communication. Its ranked priority product groups are textiles and apparel, furniture, tyres and mattresses among final products, and iron and steel and aluminium among intermediate products. Electronics and ICT are **not** among them. The working plan addresses ICT explicitly by stating that ICT products are included in the plan because they will be covered in the preparation of the two horizontal requirements, and that some specific ICT products will be covered in the work on energy-related products. The horizontal measure on repairability, including scoring, carries an indicative target of 2027, and the horizontal measure on recycled content and recyclability of electrical and electronic equipment carries an indicative target of 2029. The working plan itself notes that the repairability scope could include products such as consumer electronics and small household appliances, subject to the preparatory study. Those are indicative adoption targets for the Commission's own work. They are not application dates, they are not commitments, and they can move. ### Adopted product-specific measures, of which there are none for electronics under ESPR No Article 4 delegated act under Regulation (EU) 2024/1781 has been adopted for an electronics or ICT product group. The measures that currently bind electronics products, listed above, were adopted under the earlier Ecodesign Directive 2009/125/EC and under separate instruments, and they do not create passports. ### Future passport obligations, whose shape is not yet fixed When electronics obligations arrive, several structural questions will be answered that cannot be answered now: which product families are in scope, whether the passport sits at model, batch or item level, which data elements are mandatory, which access tier each element sits in, which data carrier is required, and how long the passport must remain available. Every one of those is reserved to the delegated act by Article 9. Designing a rigid system around a guess at any of them is the main avoidable failure mode in this sector. Electronics have extensive existing obligations and no Digital Product Passport obligation. The framework law is in force, the sector is not separately prioritised, and the current plan routes electronics through horizontal measures on repairability and on recycled content and recyclability of electrical and electronic equipment, with indicative targets of 2027 and 2029 for adoption, not application. ## Which Electronic Products Could Be Affected? "Electronics" is a commercial category, not a legal one. EU product law does not regulate electronics as a single group; it regulates named product groups, and the boundaries differ instrument by instrument. Directive 2011/65/EU and Directive 2012/19/EU each define electrical and electronic equipment for their own purposes with their own category lists. Ecodesign measures name narrow groups such as electronic displays or servers. A future ESPR horizontal measure would define its own scope again. The practical consequence is that any electronics company must work product family by product family, not by a single corporate answer. Families worth separating when scoping, on the basis of how existing rules already treat them: * **Consumer electronics**, such as mobile phones, tablets, audio equipment, cameras and games hardware. Mobile phones, cordless phones and slate tablets are already the subject of a dedicated ecodesign measure with durability, spare parts and repair information duties, and the working plan flags consumer electronics as a possible scope area for the horizontal repairability measure. * **ICT equipment**, such as laptops, desktops, monitors, printers, networking hardware and servers. Electronic displays and servers and data storage products already carry ecodesign obligations. The working plan states that ICT will be reached through the horizontal measures and continuing energy-related products work rather than through a ranked sector act. * **Displays**, treated separately because they already have their own adopted regime under Regulation (EU) 2019/2021 and its energy labelling counterpart, including spare parts availability and dismantling information. * **Household electrical equipment**, such as washing machines, dishwashers, refrigeration, ovens and small domestic appliances. Many of these are already covered by product-specific ecodesign and energy labelling measures with repair information duties, and small household appliances are named in the working plan as a possible repairability scope area. * **Professional and industrial electronics**, such as instrumentation, medical devices, industrial controls and building systems. These often sit under additional sectoral regimes, and scope questions here are harder than in consumer categories. * **Components and subassemblies**, such as printed circuit board assemblies, power supplies, batteries and displays supplied into other products. These may be regulated in their own right. A battery inside an electronic product is the clearest example, and it already has an explicit passport obligation of its own. > **Tip** > > If your portfolio contains rechargeable batteries above the relevant thresholds, the battery > passport obligation under Regulation (EU) 2023/1542 may reach your product before any electronics > measure does. See [Digital Product Passports for Batteries](/docs/knowledge-base/industry-guides/digital-product-passports-for-batteries) for the > one electronics-adjacent case where a passport, a date and a defined dataset already exist in law. Two further scoping notes matter. First, **Article 25 and Annex VII of Regulation (EU) 2024/1781, the prohibition on destroying unsold consumer products, currently list only apparel and clothing accessories and footwear.** Electronics are not covered by that prohibition as adopted, although the Commission holds a delegated power to extend the list in future. Second, a **Circular Economy Act has been announced as a Commission initiative** and is discussed widely in relation to electronics circularity, but no adopted instrument, number or text exists that this guide can cite, so nothing in this article depends on it. ## Why Electronics Are Difficult This is the section most electronics companies should read twice, because the difficulty is not regulatory interpretation. It is the shape of the product and its data. **Bills of materials are deep and wide.** A mid-range consumer device can contain several hundred distinct part numbers; a complex ICT product can contain several thousand, arranged in a multi-level structure of assemblies within assemblies. Product-level statements about substances, materials or recycled content are aggregations over that structure. If the structure is wrong, the aggregate is wrong, and the error is invisible at product level. **Component counts turn every product claim into a supply chain claim.** A single restricted substance statement about a finished laptop is a statement about every solder joint, connector, cable, plastic housing and adhesive in it. No manufacturer generates that information; it is collected. **Supplier chains are multi-tier and opaque.** The brand contracts with a contract manufacturer. The contract manufacturer buys modules. The module maker buys components. The component maker buys materials. Distributors sit between several of those layers, sometimes with no visibility of the original manufacturer's declaration. The brand carries the legal duty for a product built largely from information it cannot originate. **Model cycles are short.** Consumer electronics ranges refresh annually or faster. Data collection cycles built around a single annual supplier campaign do not survive contact with a portfolio that renews itself before the campaign completes. **Products are commonly serialised, and serialisation is used for other purposes.** Serial numbers already exist for warranty, service, anti-counterfeiting and returns. Whether the passport uses that same serialisation, and whether the passport is even required at item level, is a delegated act question. Assuming the existing serial number is the passport identifier is an assumption, not a design. **Firmware and software change after sale.** A product's behaviour, energy performance, feature set and even its safety posture can change through an update. Static product information records were never built for an object that changes after it leaves the factory. **Repairability is an information obligation, not just a design property.** Existing measures already require spare parts availability, indicative pricing and repair or disassembly information for named product groups. That information has to be maintained for years after production ends, which is longer than most product data systems are governed to support. **Spare parts are products with their own data.** A replacement display module is itself an article with substance, material and supplier data. Service organisations rarely feed that data back into the product record. **Restricted substances change.** The restricted list is not static, and neither are exemptions. A declaration that was correct at launch may not be correct three years later, for a product still being manufactured and still being repaired. **Recycled content claims are hard to substantiate.** Recycled plastic or metal content is usually a supplier claim backed by mass balance or chain of custody records, not a property measurable in the finished device. The evidence lives several tiers away. **Product variants multiply everything.** Regional power configurations, colour and memory options, carrier specific builds and channel exclusives can turn one engineering design into dozens of commercial products with materially different data. **Contract manufacturers own the production reality.** The brand owns the design intent. The factory owns what was actually built, which lot of which component went into which production run, and which substitution was approved on a Tuesday to keep the line running. **Component substitution is normal, not exceptional.** Allocation shortages, end of life notices and cost engineering all cause approved alternates to enter production. Every substitution is a potential change to substance, material, recycled content, weight and repair data. **Multiple regulatory regimes overlap on one product.** Substance restrictions, waste and treatment information, energy labelling and registration, ecodesign, safety, radio equipment, chemicals and, where batteries are present, battery law. These are administered by different internal teams with different systems and different update cycles. **Service and support periods are long.** A product supported for seven to ten years needs its information to remain accurate and available across that window, which will exceed the tenure of the people, and often of the systems, that created it. The electronics passport problem is a component, supplier, evidence and change management problem wearing a publishing problem's clothes. Any programme whose first workstream is choosing a passport display template has already mis-sequenced itself. ## What Information May Matter? There is no mandatory electronics passport field list, and this guide does not invent one. What follows is a set of representative categories, each classified so that its status is unambiguous. Four classifications are used throughout. **Current legal information** means information that EU law already requires today, though not in passport form. **Product-specific or existing rule** means information required only for named product groups under an existing measure. **Potential future passport area** means information plausibly relevant to a future requirement, based on the essential requirements in Regulation (EU) 2024/1781 and the stated direction of the horizontal measures, and carrying no legal status. **Enterprise preparation data** means information no rule requires but which an organisation needs internally to be able to produce any of the above reliably. | Category | Representative content | Classification | | ---------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Product identity | Model, commercial variant, type designation, batch or serial reference | Current legal information for traceability duties; passport identity level is a future delegated act question | | Manufacturer and economic operator | Manufacturer name and address, importer details, authorised representative | Current legal information | | Model and variant structure | Regional, memory, colour and configuration variants and their relationships | Enterprise preparation data | | Manufacturing information | Production site, production date or period, production lot | Partly current legal information through marking and traceability duties | | Materials and components | Bill of materials structure, part numbers, material composition, part weights | Enterprise preparation data, with an existing duty to give treatment operators component and material information under Directive 2012/19/EU Article 15 | | Substances and compliance | Restricted substance status, exemption use, substance location in the product | Current legal information under Directive 2011/65/EU and Directive 2012/19/EU | | Energy and performance | Energy class, consumption figures, registration in the energy labelling database | Product-specific or existing rule | | Recycled content | Recycled share by material or component, chain of custody basis | Potential future passport area, targeted by the planned horizontal measure | | Durability and reliability | Drop and endurance testing, battery cycle endurance, expected lifetime | Product-specific or existing rule, for example under Regulation (EU) 2023/1670 | | Repairability | Disassembly information, repair instructions, tools required, repair scoring | Product-specific or existing rule today; scoring is a potential future area under the planned horizontal measure | | Spare parts | Part list, availability period, indicative pre-tax prices, ordering route | Product-specific or existing rule | | Software and firmware | Version, update policy, support period | Enterprise preparation data, unless a specific rule applies to the product | | Safety and conformity | CE marking basis, EU declaration of conformity, applicable harmonised standards | Current legal information | | Environmental information | Carbon or environmental footprint figures where a rule requires them | Potential future passport area | | End of life and recycling | Treatment information, hazardous substance location, separate collection marking | Current legal information under Directive 2012/19/EU | | Conformity related documentation | Technical documentation, test reports, notified body involvement where applicable | Current legal information, retained rather than published | #### Treating this table as a specification It is a scoping aid. The moment a delegated act defines an actual dataset, the mandatory list will be narrower in some places and wider in others, and it will assign access tiers that this table cannot predict. Use the table to find out what you can and cannot currently produce, not to build a schema. ## Where Does Electronics Passport Data Come From? This is where the library's data origin model earns its place. The [Passport Data Origin Model](/docs/knowledge-base/digital-product-passports/what-data-goes-in-a-digital-product-passport) separates four questions that organisations habitually merge: what the information is, where it originates, who has authority over it, and what evidence substantiates it. Applied to electronics, it produces an uncomfortable result: the brand originates identity and design intent, and very little else. | Information | Origin | Authoritative source | Evidence | | ---------------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | Model identity | Internal, at product definition | Product master data in the product information or resource planning system | Approved product release record | | Serial or batch identity | Factory, at production | Manufacturing execution or production records at the build site | Production and packing records, serial allocation log | | Manufacturer and operator details | Internal, corporate | Legal entity and regulatory affairs records | Registration and corporate records | | Bill of materials structure | Internal engineering, then modified in production | Engineering system for design intent, production system for as-built | Released engineering change records and production build records | | Component and material data | Component supplier | The supplier that manufactures the component | Supplier material declaration, datasheet | | Restricted substance status | Component and material suppliers, aggregated internally | Each supplier for its own part, the manufacturer for the assembled product | Supplier declarations, analytical test reports, exemption records | | Energy and performance data | Internal or external testing | The test laboratory that produced the measurement | Test report against the applicable measurement standard | | Recycled content claim | Material or component supplier | The supplier that produced the material | Mass balance or chain of custody records, scheme certificates | | Repair and disassembly information | Internal engineering and service functions | Service documentation owner | Approved service manual and revision history | | Firmware and software version | Internal engineering, changing after sale | Release management system | Release records and update logs | | Conformity documentation | Internal, drawing on external testing | Regulatory affairs, as holder of the technical documentation | EU declaration of conformity, test reports, notified body outputs where applicable | | Supplier declarations | Supplier | The declaring supplier | The signed declaration and its validity period | | End of life instructions | Internal, informed by the bill of materials | Environmental compliance function | Treatment information issued under Directive 2012/19/EU Article 15 | Two patterns are worth naming. First, **authority almost never transfers**. When a component supplier declares a substance status, that supplier remains the authority for it even after the brand aggregates it into a product-level claim and publishes it. If the supplier revises the declaration, the published claim is stale from that moment. Second, **origin and authority frequently diverge from the system of record**. The as-built bill of materials originates at the factory, but many brands treat the engineering system as the authority for it, which is precisely how substitutions become invisible. ## Bills of Materials and Component Data Electronics deserves a dedicated treatment of the bill of materials because it is the single structure on which almost every passport-relevant product claim depends. Organisations use different names and different systems, and not every company separates these layers formally. The distinctions still exist even where the vocabulary does not. **The engineering bill of materials** expresses design intent: the parts the design calls for, in a functional structure, usually maintained in an engineering or product lifecycle system. It is the correct authority for what the product is meant to be, and the wrong authority for what was actually shipped. **The manufacturing bill of materials** expresses build reality: the parts consumed, in the structure the factory builds them in, including approved alternates actually used, sourced by supplier and often by lot. It typically lives with the manufacturing organisation, which in electronics is frequently a contract manufacturer rather than the brand. **Supplier data** is what each component supplier states about its own part: composition, materials, mass, substance status, sometimes recycled content and country of manufacture. It arrives in inconsistent formats on inconsistent cycles, and it is versioned by the supplier, not by the brand. **The compliance bill of materials or material declaration** is the derived structure used for regulatory work: parts mapped to materials and substances, rolled up to assembly and product level so that a product-level statement can be made and defended. It is derived, which means it is only as current as its last derivation. **The passport dataset** is a further derivation: the subset of information a rule requires, at the identity level the rule requires, expressed in the format the rule requires, with access tiers applied. #### How the layers diverge in practice A power supply module is released in the engineering bill of materials as part number PS-4410 from supplier A. Six months into production, supplier A goes on allocation and the contract manufacturer moves to the approved alternate PS-4410-B from supplier B, which is functionally equivalent and correctly approved. The engineering bill of materials is not updated because the alternate was already approved. The compliance bill of materials was derived from the engineering structure and still points to supplier A's declaration. The product-level substance and recycled content statements are now supported by evidence for a part that is no longer being fitted. Nothing is broken in any single system, and the product claim is nevertheless unsupported. The lesson is not that engineering systems are wrong. It is that **a passport dataset derived from design intent will drift from the physical product**, and electronics drifts faster than most sectors because substitution is routine. Any serious electronics preparation programme has to decide, explicitly, which layer is authoritative for each passport-relevant claim, and how a change in the build reality triggers a re-derivation. #### Bind claims to the as-built structure, not the design structure For every passport-relevant claim, record which bill of materials layer it derives from and which change events invalidate it. Component substitution, supplier change, material change, revised supplier declaration and design change are all invalidation events. If nothing in your process listens for them, the claim is unmanaged from the moment it is published. ## Supplier and Contract Manufacturer Data The [Supplier DPP Readiness Model](/docs/knowledge-base/implementation/how-to-prepare-suppliers-for-digital-product-passports) applies to electronics with one adjustment: the chain is longer than the contractual relationship, and the most important tier is often the one the brand does not contract with. An illustrative chain: Explanatory article diagram, not a tieback framework The electronics product data spine How component and material information becomes a passport dataset in an electronics organisation, and how change in production and in the field feeds back into the governed data environment. Read top to bottom. Each layer shows the contributors that supply it. * Suppliers and external parties * Internal systems and functions * Testing, certification and treatment bodies - 1 Component and material suppliers Material producers, component makers, module suppliers and distributors. The only parties that can originate composition, substance and recycled content information for their own parts. * Material declarations * Substance status * Recycled content basis * Part mass and materials - 2 Bill of materials and product engineering Design intent released as an engineering structure, then reconciled against what the factory actually builds, including approved alternates and lot level sourcing. * Engineering structure * As-built structure from the factory * Variant and configuration model * Change records - 3 Compliance and evidence Declarations aggregated to product level, testing commissioned where declaration is not sufficient, conformity documentation assembled and retained. * Test reports * Compliance roll-up * Technical documentation * Supplier declarations - 4 Product identity Decide and record the identity level each claim attaches to: model, variant, batch or serialised unit. Allocate identifiers and bind them to the underlying records. * Model and variant codes * Serial allocation at build * Identifier register - 5 Passport dataset The governed subset, derived rather than authored, validated for completeness, consistency, plausibility and evidence sufficiency before anything is exposed. * Derived dataset * Validation controls * Access tiering - 6 Passport and data carrier Publication of the record and resolution from the carrier on the product, its packaging or its documentation, to the content each audience is entitled to see. * Publication service * Carrier and resolution - 7 Service, repair and end of life Repair events, spare part fitment, refurbishment, firmware updates, second life and treatment. Consumers of the record, and generators of new information about the product. * Service records * Spare part data * Treatment and recycling operators Feedback path: change and substitution A component substitution, a revised supplier declaration, an engineering change, a firmware release or a repair that fits a different part all re-enter at layer two and layer three. Each must be assessed for impact, must refresh the affected data and evidence, must be revalidated, and only then may update the published record. A programme without this return path publishes a record that is correct once. Four things follow for supplier management in this sector. **Contractual flow-down has to reach past tier one.** The brand contracts with the contract manufacturer, but the substance and recycled content information originates with component and material suppliers. The practical mechanism is a contractual obligation on tier one to obtain and pass through equivalent commitments from its own suppliers, with the right to see the underlying declarations rather than a summary. **Evidence must travel with the data.** A substance status without the declaration behind it cannot be defended to a market surveillance authority. Collect the artefact, not just the answer. **Update obligations are the part everyone forgets.** Most supplier programmes are built around initial collection. In electronics the recurring events matter more: a substitution, an end of life notice, a revised declaration, a change of manufacturing site. Contract for notification of change, with a defined notice period, not just for an annual refresh. **Supplier capability varies enormously.** A large semiconductor manufacturer will have a mature declaration process; a small connector or enclosure supplier may not. Tier suppliers by capability and design different routes for each, rather than issuing one portal invitation and treating silence as compliance. **Provenance and exceptions need a named route.** Some information will be unobtainable: a distributor cannot reach the original manufacturer, a supplier refuses on confidentiality grounds, a legacy part has no declaration. Record the gap, its reason, its owner and its resolution date. An unrecorded gap becomes an unsupported published claim. ## Evidence and Regulatory Claims The [DPP Evidence Lifecycle](/docs/knowledge-base/implementation/how-to-manage-evidence-for-digital-product-passports) applies directly, and electronics gives it unusually sharp examples. Consider what actually substantiates each of these: * **Restricted substances.** A supplier declaration for each part, sometimes supported by analytical testing, plus records of any exemptions relied on and their expiry. * **Recycled content.** Supplier mass balance or chain of custody records, and any scheme certification. The finished product usually cannot be tested to confirm the claim. * **Energy and performance.** A test report produced under the measurement standard the applicable measure specifies, for the specific model or a properly justified representative model. * **Repairability.** Approved service documentation, spare parts availability commitments, disassembly records and, where a future measure requires scoring, whatever the scoring methodology requires. * **Materials.** Component level material declarations aggregated to product level, with the aggregation method recorded. * **Conformity.** The technical documentation and the EU declaration of conformity, retained rather than published, together with any notified body outputs where the applicable regime requires them. Each piece of evidence has a lifecycle: it is requested, received, assessed for sufficiency, accepted or rejected, bound to a specific claim about a specific part or product, and then it ages. It expires when the part changes, when the declaration is superseded, when an exemption lapses or when the standard it was produced against is replaced. #### A supplier declaration proves the product complies It does not. A supplier declaration is a statement by a supplier about a part, made at a point in time, under the supplier's own assumptions about its own supply chain. The product-level claim is made by the manufacturer and is the manufacturer's responsibility. The declaration is an input to that claim, and its value depends on the part it covers still being the part fitted, the declaration still being current, and the aggregation to product level being sound. ## Data Quality and Validation Two models apply together. The [Trusted Product Data Quality Model](/docs/knowledge-base/enterprise-systems-and-data-architecture/what-is-product-data-quality) addresses the condition of the data; the [DPP Data Validation Control Model](/docs/knowledge-base/implementation/how-to-validate-digital-product-passport-data) addresses the controls that stop bad data reaching a published record. Electronics-specific failure patterns worth building controls for: * **The bill of materials and the passport dataset disagree.** The dataset was derived at launch and the structure has moved since. Control: re-derive on change, and compare rather than trust. * **A component was replaced without a corresponding data update.** The substitution is correctly recorded in production and nowhere else. Control: make substitution an event that reaches the compliance data environment, not just the factory. * **A declaration refers to an obsolete component.** The part number in the evidence no longer appears in the as-built structure. Control: reconcile the evidence set against the current structure, and flag orphans. * **Serial and model mismatch.** A serialised unit is bound to the wrong model or variant record, so it reports the wrong energy class or the wrong repair documentation. Control: validate identity bindings at the point of serial allocation. * **Stale firmware or service information.** The published support period, update policy or service manual revision no longer matches reality. Control: treat release and documentation events as data events. * **Test evidence applies to the wrong variant.** A report for the 15 inch model is used to support the 13 inch model without a documented representativeness justification. Control: bind each report explicitly to the identities it covers and require justification for extension. * **Units and terminology differ between sources.** Grams against kilograms, percentage by mass against percentage by part count, one supplier's material name against another's. Control: normalise on intake, and reject rather than silently convert what cannot be normalised. #### Validate before publication, not after complaint Completeness, consistency, plausibility and evidence sufficiency should all be checked before a record is exposed to anyone. Plausibility catches what completeness cannot: a 4 kilogram laptop, a 140 per cent recycled content figure, or a spare part price that is an order of magnitude out. ## Product Identity, Serialisation and Data Carriers Electronics companies usually already serialise, which creates a specific risk: the assumption that the existing serial number is automatically the passport identifier at the correct identity level. Six things are separate. **Model.** The engineering and commercial design. Most existing electronics obligations, including energy labelling registration and most ecodesign requirements, attach at this level. **Variant.** A commercial or regional configuration of a model, which may differ in materials, components, power supply, packaging or supported markets. Variants often share a model name and diverge in the data. **Batch or lot.** A production run, which is where sourcing differences typically become visible. Two batches of the same variant may contain different approved alternates. **Serialised unit.** An individual physical article, which is what service, warranty and returns already track. **Product identifier.** The string naming any one of the above. Different identifiers may be needed for different levels. **Data carrier.** The physical means of presenting the identifier on the product, its packaging or its documentation. **Passport.** The governed record reached by resolving the identifier. Which identity level a future electronics passport attaches to is a delegated act question. Article 9 of Regulation (EU) 2024/1781 explicitly requires the delegated act to specify whether the passport applies at model, batch or item level. It is entirely possible that different data elements sit at different levels within one product: energy performance at model level, as-built composition at batch level, repair history at item level. #### Model identity now, decide granularity later Build the capability to describe a product at model, variant, batch and unit level, and to attach a claim to the correct level. Do not hard-code a single granularity into your data model, your identifier scheme or your carrier strategy before the applicable requirement exists. The capability is durable; the granularity decision is not yours to make yet. For the underlying mechanics, see [What Is a Product Identifier?](/docs/knowledge-base/standards-and-technology/what-is-a-product-identifier) and [What Is a Data Carrier?](/docs/knowledge-base/standards-and-technology/what-is-a-data-carrier). ## GS1, Digital Link, EPCIS and Other Standards The library covers these in depth in the Standards and Technology pillar, so this section positions rather than reteaches. See [The Digital Product Passport Standards Landscape](/docs/knowledge-base/standards-and-technology/the-digital-product-passport-standards-landscape) for the full picture. Four statements matter in an electronics context, and all four are limiting statements. **[GS1](/docs/knowledge-base/glossary/gs1) standards may support identification and interoperability.** Electronics already uses global trade item numbers extensively for retail and logistics, so the identification infrastructure is often partly present. **A [GTIN](/docs/knowledge-base/glossary/gtin) is not a passport.** It identifies a trade item. It says nothing about substances, materials, repairability or evidence, and in electronics a single GTIN routinely spans production batches with different component sourcing. **[GS1 Digital Link](/docs/knowledge-base/glossary/gs1-digital-link) is not a passport.** It is a syntax for expressing identifiers as web addresses so that a scan can resolve to a destination. Resolution is not content, and a resolver is not a governed record. **[EPCIS](/docs/knowledge-base/glossary/epcis) is not a passport.** It is an event data standard describing what happened to an object, where and when. Useful for chain of custody and for repair or treatment events; not a substitute for a product information record. **No standard is universally legally required.** Absent an applicable legal requirement adopted for your product group, no standards body's specification is mandatory. Choosing GS1, or choosing something else, is currently an implementation decision. Treat any supplier claim that a particular standard is legally mandatory for electronics passports as a claim requiring a citation. ## Repairability and Lifecycle Information Repairability is the area where electronics is furthest ahead of the rest of the passport landscape, and where the boundary between existing law and future possibility must be drawn most carefully. **What existing measures already require, for named product groups.** Regulation (EU) 2023/1670 for mobile phones, cordless phones and slate tablets imposes durability and reliability requirements, obligations to make spare parts available to professional repairers and in part to end users for a defined period after production ends, obligations regarding indicative pre-tax spare part prices, and duties to provide repair and disassembly information. Regulation (EU) 2019/2021 imposes comparable spare parts and dismantling information duties for electronic displays, and Regulation (EU) 2019/424 addresses material efficiency for servers and data storage products. Directive 2012/19/EU Article 15 separately requires producers to give treatment and reuse operators the information needed to identify components and materials and to locate hazardous substances. **What is planned but not adopted.** The working plan targets a horizontal measure on repairability, including scoring, for adoption in 2027, and notes that its scope could include consumer electronics and small household appliances. That is an intention. There is no adopted repairability scoring requirement, no adopted scoring methodology and no application date. **What is speculation and is treated as such here.** Whether a future passport will carry repair history, whether repair events will be written back to a passport by third party repairers, whether refurbishment will create a successor passport, and how software support periods will be expressed are all open. Regulation (EU) 2024/1781 provides relevant hooks: Article 11 lists professional repairers, independent operators, refurbishers, remanufacturers and recyclers among the actors who must have free access, and it addresses linkage of successive passports. Hooks are not requirements. Lifecycle events an electronics organisation should be able to describe internally, regardless of what any future rule demands: * **Repair events**, including which part was replaced, with what, by whom and when. * **Spare parts**, as products with their own material and substance data. * **Service documentation**, versioned and retained for the full support period. * **Product changes**, including changes made after sale. * **Refurbishment**, where the physical configuration of a unit diverges from its original build. * **Firmware and software lifecycle**, including version, update policy and support end date. * **Second life**, where a unit is resold, redeployed or repurposed. * **End of life**, including the treatment information already owed to recyclers. > **Tip** > > The single most valuable lifecycle capability to build before any rule exists is the ability to > say what a specific unit actually contains today, rather than what its model contained at launch. > Every speculative future requirement in this section becomes tractable if that capability exists, > and intractable if it does not. ## Enterprise Architecture The [Enterprise Digital Product Passport Reference Architecture](/docs/knowledge-base/enterprise-systems-and-data-architecture/building-an-enterprise-digital-product-passport-architecture) applies without modification. Electronics simply has more source systems than most sectors. ### The SME path A small electronics manufacturer, a specialist instrument maker or a hardware startup does not need enterprise software to prepare, and should not buy any yet. * **Structured files with a fixed schema.** One row per part, one row per product, with agreed column definitions and units. A spreadsheet with a governed schema beats an ungoverned system. * **Manual product setup with a defined owner.** One named person responsible for the correctness of each product record, with a documented process for creating it. * **Supplier evidence upload into a controlled folder structure.** Declarations named consistently, filed by part number and version, with the receipt date and validity period recorded. * **Controlled documentation.** Service manuals, declarations of conformity and treatment information kept under version control with a retention rule that matches the support period. The discipline is what transfers to a larger system later. The spreadsheet does not. ### The enterprise path A larger electronics organisation will typically already have most of the following, in varying states of governance: * **Product lifecycle management**, holding the engineering bill of materials, change records and specifications. * **Enterprise resource planning**, holding commercial product master data, part masters, sourcing and production orders. * **Product information management**, holding commercial and channel-facing product content. * **Bill of materials and manufacturing execution systems**, holding the as-built structure and lot level consumption, often at the contract manufacturer rather than the brand. * **Supplier portals**, collecting declarations and material data at scale. * **Compliance and material data systems**, aggregating substance data to product level. * **Service and field systems**, holding repair events, spare part fitment and installed base data. * **Evidence repositories**, holding test reports, certificates and technical documentation with retention rules. * **Application programming interfaces and integration**, moving data between the above without manual re-keying. * **Master data management**, resolving which system is authoritative for which attribute. #### The passport consumes, it does not master The passport capability should read authoritative data from the systems that own it and publish a derived view. It should not become the master source for bills of materials, substance data, service documentation or product master data. Every organisation that lets the passport layer become a second place to enter product data creates a divergence problem that outlives the programme. ## Legal Responsibility The [DPP Legal Responsibility Model](/docs/knowledge-base/regulations/who-is-legally-responsible-for-a-digital-product-passport) sets out the general position. Electronics adds a specific complication: the party with the legal duty is frequently not the party that manufactured the product or generated its data. Roles worth distinguishing, without drawing universal liability conclusions, because the answer depends on the applicable instrument and the facts: * **The brand or original equipment manufacturer** typically places the product on the market under its own name and carries manufacturer obligations even where it operates no factory. * **The manufacturer**, in the legal sense used by EU product law, is the party that manufactures, or has manufactured, and markets under its own name or trade mark. * **The importer** brings a product from outside the Union into it and carries duties to verify that the manufacturer has met its obligations, with the importer's own identification requirements. * **The distributor** acts with due care in relation to applicable requirements and generally must not supply products it knows or should presume to be non-compliant. * **The component supplier** is responsible for its own part and its own declarations, and may itself be a manufacturer of a regulated product where the component is separately regulated. * **The contract manufacturer** builds to the brand's specification and holds the as-built truth, but is usually not the party placing the product on the market under its own name. * **The service provider or repairer** may generate information about a unit after sale without being the party responsible for the product record. Note that Regulation (EU) 2024/1781 Article 10 contemplates a distinct role of digital product passport service provider for back-up and technical operation, which does not transfer the economic operator's responsibility. #### Outsourcing the passport transfers the liability It does not. Engaging a software vendor, a data provider or a passport service provider transfers work, not legal responsibility. The economic operator that places the product on the market remains answerable for whether the information is accurate, complete and up to date. ## Conformity and Existing Product Regulation Electronics companies already run a conformity machine. Read [How Conformity Assessment Works for Digital Product Passports](/docs/knowledge-base/regulations/how-conformity-assessment-works-for-digital-product-passports) alongside this section. Four things must not be blurred. **Conformity assessment** is the process by which a product is shown to meet the applicable requirements. For most electronics it is manufacturer self-assessment against harmonised standards, with notified body involvement only where the applicable regime requires it. **Technical documentation** is the internal file demonstrating conformity: designs, calculations, test results, risk assessment, standards applied. It is retained and made available to authorities on request, not published. **Declarations** are the formal statements of conformity, principally the EU declaration of conformity, accompanied by CE marking. **Passport information** is a published, machine-readable, access-tiered record. It may draw on the same underlying facts as the technical documentation, and it is not the same artefact. The productive way to think about the relationship is that the conformity environment is a **source of supply** for a future passport, not a thing the passport replaces. A test report already produced for ecodesign compliance is evidence that can substantiate a passport claim. A registration already made in the energy labelling database contains data a passport may need. A treatment information document already produced for recyclers under Directive 2012/19/EU is close in intent to end of life content a passport might carry. #### The passport replaces the technical documentation It does not. Technical documentation and declarations continue to exist, with their own retention and availability rules, whatever a future passport requires. A passport that published technical documentation wholesale would in most cases disclose information that no rule requires to be public. ## Preparing Before Final Requirements Exist This is the section with the highest return, because everything in it is useful whether the electronics measures arrive in 2028, 2031 or in a different shape entirely. It applies the [Digital Product Passport Readiness Model](/docs/knowledge-base/implementation/how-should-organisations-prepare-for-digital-product-passports) and the [Digital Product Passport Implementation Roadmap](/docs/knowledge-base/implementation/how-to-build-a-digital-product-passport-implementation-roadmap). **Identify the relevant product families.** Split the portfolio by the way EU law already treats it, not by commercial category. Which products are already covered by an adopted ecodesign or energy labelling measure. Which contain batteries above the relevant thresholds. Which are plausibly in scope of a repairability measure that could cover consumer electronics and small household appliances. Which are professional equipment under other sectoral regimes. **Map existing obligations per family.** For each family, list what is already required, by which instrument, with what data and what evidence. Most organisations discover during this step that they cannot produce a single consolidated view of their own obligations. **Map product and bill of materials data.** For each family, record where the engineering structure lives, where the as-built structure lives, who owns each, and whether the two can be reconciled at all today. **Map supplier tiers.** Identify which information you can obtain from tier one and which requires reach past it. Record where distributors block visibility of the original manufacturer. **Identify authoritative systems.** For each passport-relevant attribute, name one system and one function as authoritative. Where two systems disagree today, that is a finding, not an obstacle to be worked around. **Assess material and compliance evidence.** Sample real products. Take a shipped device, pick ten parts, and try to produce the current supplier declaration for each within a working day. The result of that exercise is usually more informative than any maturity assessment. **Establish an identifier strategy.** Decide how models, variants, batches and units are identified, how identifiers are allocated, and how they are bound to records. Do not commit to a single passport granularity. **Improve version control.** Bills of materials, declarations, service documentation and firmware all need a version and an effective date. Undated documents cannot support a claim about a specific product. **Improve data quality.** Units, material vocabularies, part numbering and mass data are the usual weak points. Normalise them now, because every future requirement multiplies the cost of not having done so. **Design evidence governance.** Decide how evidence is requested, assessed, bound to claims, stored, and expired. Assign an owner. **Pilot a flexible passport architecture.** Something that can express a dataset, change that dataset, and publish at more than one identity level, without a rebuild. **Monitor the product-specific development.** Watch the preparatory work on the two horizontal measures and on energy-related products, and the EUR-Lex register of delegated acts. Assign this to a named person, with a review cadence. **Avoid hard-coding unfinalised requirements.** No fixed field list, no assumed granularity, no assumed carrier, no assumed access model. Every one of those is a delegated act decision. #### Waiting for the final delegated act is the safe option It is the most expensive option available. The work with the longest lead time, reaching component suppliers across multiple tiers, reconciling as-built structures, and building evidence governance, is entirely independent of the final field list. An organisation that starts when the act is adopted has to do multi-year supply chain work inside an 18 month application window. ## Pilot Strategy Run one bounded pilot on one representative product family. Representative means it exercises the hard parts: a real multi-level bill of materials, real external component suppliers, at least one product-specific existing obligation, and a service or spare parts dimension. What the pilot should test: * **Identity.** Can you describe the product at model, variant, batch and unit level and attach a claim to the right level. * **Bill of materials and component data.** Can you produce the as-built structure for a specific production batch, not just the engineering structure. * **Supplier data.** Can you obtain current declarations for the parts that matter, including from suppliers you do not contract with directly. * **Evidence.** Can you bind each claim to a current artefact and say when that artefact expires. * **Validation.** Do your controls catch a deliberately introduced error, such as a mass in the wrong unit or a declaration for a superseded part. * **Data carrier.** Can you carry an identifier on the product, its packaging or its documentation and resolve it reliably. * **Passport publication.** Can you publish a dataset with more than one access tier. * **Product change.** Introduce a component substitution and see whether it propagates. * **Repair or service update.** Where relevant, record a repair event against a unit and see whether the record can reflect it. > **Tip** > > Measure the pilot on how much it teaches you about your own gaps, not on how convincing the > resulting passport page looks. A pilot that surfaces three unreachable suppliers and two > irreconcilable bills of materials has succeeded. A pilot establishes capability and surfaces gaps. It does not establish compliance with any future legal requirement, and it should never be described internally or externally as doing so. ## Worked Example A hypothetical manufacturer, Northvale Instruments, makes a professional 27 inch reference display in Portugal. It sells across the EU, holds an existing energy labelling registration for the model, and complies with the display ecodesign and energy labelling measures, substance restrictions and waste equipment duties. It has around 480 part numbers in the product, buys its panel from one supplier, its power supply from another, and has final assembly done in house. Nothing in this example is a legal requirement for displays beyond what is already noted; the point is the data chain. **Product.** One model, four commercial variants differing by stand, input configuration and regional power cord. Serialised at final assembly for warranty and service. **Bill of materials.** Five levels. The engineering structure is maintained in the product lifecycle system; the as-built structure exists in the production system, including which panel lot went into which build week. **Component suppliers.** The panel supplier and the power supply supplier are direct and responsive. The enclosure plastics come through a distributor, which cannot immediately reach the original compounder for recycled content substantiation. Cables and connectors come from eleven small suppliers of varying capability. **Data sources.** Model identity and variant structure from product master data. As-built structure from the production system. Substance and material data from supplier declarations. Energy performance from the test report. Repair and disassembly information from the service documentation set. Treatment information from the environmental compliance function. **Evidence.** Supplier declarations for each part with receipt dates and validity periods. Analytical test reports for two high risk plastic components. The energy performance test report bound explicitly to the model. Mass balance records from the plastics compounder, once the distributor route is opened. **Validation.** Completeness against the derived dataset. Consistency between the as-built structure and the declaration set. Plausibility on masses and percentages. Evidence sufficiency, which fails initially because three connector suppliers have declarations more than four years old. **Passport dataset.** Derived, not authored: identity at model and variant level, substance and material data aggregated from the as-built structure, energy data at model level, repair and spare parts information at model level, treatment information at model level, and unit level identity for serialised traceability. **Identifier and carrier.** Model and variant identified in product master data, unit serial allocated at assembly, a data matrix on the rating plate carrying the unit identifier, resolving to the record. **Publication.** Public content limited to what is intended to be public; service and treatment content exposed to the audiences entitled to it; technical documentation retained and not published. **Change: a component substitution after launch.** Eight months into production the power supply supplier issues an end of life notice. Engineering approves an alternate from a second supplier. Here is what has to happen, and what usually does not. * **Impact assessment.** Which passport-relevant claims does this part touch: substance status, recycled content contribution, product mass, energy performance because efficiency differs, spare parts list, service documentation, and treatment information because the hazardous substance location changes. * **Data update.** New supplier declaration obtained and bound to the new part. As-built structure updated from the build week the alternate enters production, which means the record becomes batch dependent where it was previously model level. * **Evidence update.** A new energy performance test is commissioned because the efficiency delta is outside the tolerance the original report supports. The old report remains valid for units built before the changeover and must not be deleted. * **Validation.** Re-run completeness, consistency, plausibility and evidence sufficiency for the affected batches. * **Passport update.** Units built before the changeover keep their original data; units built after carry the new data. This is the moment Northvale discovers whether its identity model can express a batch dependent claim, or whether it silently overwrites the model level record and misrepresents 40,000 units already in the field. **Service.** A repair centre later replaces a power supply in a pre-changeover unit with the newer part. That unit's physical configuration now differs from both batch records. Whether any rule will require that to be reflected is unknown; whether Northvale can describe it is a capability question it can answer today. ## Common Mistakes #### Every electronic product already has a Digital Product Passport deadline None does. No ESPR delegated act imposing passport requirements on an electronics or ICT product group has been adopted. The working plan targets two horizontal measures with indicative adoption targets of 2027 and 2029, which are neither application dates nor commitments. #### A Digital Product Passport is a QR code The carrier is the least difficult component. The record, its accuracy, its evidence and its maintenance after a component change are the difficult components. #### The final electronics passport fields are already known They are not. Article 9 of Regulation (EU) 2024/1781 reserves the data content, the identity level, the carrier, the access rights and the availability period to the delegated act. Any published electronics field list is somebody's estimate. #### Our resource planning system already contains everything It contains commercial product master data and often the purchased part master. It rarely contains multi-level as-built structures, component material composition, substance declarations, evidence artefacts with validity periods, or service documentation versions. #### Bill of materials data is automatically passport ready An engineering bill of materials expresses design intent, in engineering units, with part numbers that carry no material or substance content. Making it passport ready means resolving it to as-built reality, enriching it with supplier data, and binding evidence to it. #### A supplier declaration proves the finished product complies It is an input to a manufacturer's claim, not the claim. Its value depends on covering the part actually fitted, being current, and being aggregated soundly. #### Component changes do not affect the passport Substitution is the single most common cause of a published electronics claim becoming unsupported. Every substitution is a potential change to substance, material, mass, recycled content, energy performance, spare parts and treatment information. #### Using GS1 is legally mandatory No adopted EU instrument mandates a specific issuing agency for electronics passport identifiers. GS1 standards are widely used and may be a sensible choice; legal necessity is a different claim and requires a citation. #### Our software vendor becomes legally responsible Regulation (EU) 2024/1781 contemplates a digital product passport service provider role for technical operation and back-up. Responsibility for the accuracy, completeness and currency of the information stays with the economic operator. #### The passport replaces technical documentation Technical documentation and declarations of conformity continue to exist with their own rules. The passport is an additional, published, access-tiered record. #### Small manufacturers cannot prepare without product lifecycle and information management systems The highest value preparation, a governed schema, a reconciled bill of materials, current supplier declarations with validity dates and a defined owner per product record, requires discipline rather than software. A small manufacturer with 40 products can be substantially more ready than a large one with 4,000. #### Waiting for the delegated act is the safe option The long lead time work is supply chain work, and it is independent of the final field list. Starting at adoption compresses multi-year work into an application window. ## Preparation Checklist ### Now, with no adopted electronics requirement * Segment the portfolio by the way EU law already treats each family. * Build one consolidated view of existing obligations per family, covering substances, waste equipment, energy labelling and registration, ecodesign, safety and, where present, batteries. * Determine, per family, where the engineering and as-built bills of materials live and whether they can be reconciled. * Run a sampling exercise: pick ten parts on a shipped product and try to retrieve current supplier declarations within a working day. * Tier suppliers by data capability and design a different route for each tier. * Add data and change notification obligations to supplier contracts as they renew. * Name an authoritative system and owner for each passport-relevant attribute. * Normalise units, material vocabularies and mass data. * Establish evidence governance: request, assess, bind, store, expire. * Define an identifier strategy across model, variant, batch and unit without committing to a granularity. * Version and date all service documentation, declarations and treatment information. * Assign a named person to monitor the two horizontal measures and the delegated acts register. ### When product-specific requirements emerge * Determine precisely which of your product families the measure covers. * Map the mandated dataset onto your existing data, marking each element as available, partially available or absent. * Identify the identity level the measure requires and confirm your model supports it. * Confirm the carrier requirements and whether existing carriers can be reused. * Map the access tiers onto your publication capability. * Re-plan supplier collection against the actual mandated elements. * Establish the availability period the measure requires and confirm retention arrangements can meet it. ### Before application * Complete supplier collection and close recorded gaps or document exceptions. * Validate completeness, consistency, plausibility and evidence sufficiency across in-scope products. * Verify carrier presence, durability and resolution on physical products. * Test access tiering against each entitled audience. * Rehearse the change path end to end, including a component substitution. * Confirm retention and back-up arrangements for the required availability period. * Brief service, sourcing and commercial teams on what changes operationally. ## Frequently Asked Questions **Do electronics already need Digital Product Passports?** No. There is no adopted EU requirement for a Digital Product Passport for any electronics or ICT product group. Substantial other obligations already apply, including substance restrictions, waste equipment information duties, energy labelling registration and product-specific ecodesign requirements, and none of them is a passport. **When will electronics passports become mandatory?** No date exists. The Ecodesign for Sustainable Products and Energy Labelling Working Plan 2025-2030 does not list electronics among its ranked priority product groups and instead routes ICT through two horizontal measures, on repairability including scoring with an indicative adoption target of 2027, and on recycled content and recyclability of electrical and electronic equipment with an indicative adoption target of 2029. Those are targets for adoption of a measure, not application dates, and Article 4 of Regulation (EU) 2024/1781 requires at least 18 months between entry into force and application, barring justified exceptions. **Which electronics will be affected?** Unknown in detail. The working plan states that repairability scope could include products such as consumer electronics and small household appliances, subject to the preparatory study, and that some specific ICT products will continue to be covered through the work on energy-related products. Scope will be defined by the eventual measures. **What data may be required?** Article 9 of Regulation (EU) 2024/1781 reserves the data content to the delegated act, by reference to Annex III. Representative categories likely to matter include identity, economic operator details, materials and components, substances, energy and performance where relevant, recycled content, durability, repairability and spare parts, and end of life information. Treat any specific field list as an estimate. **Will every product need a QR code?** Not necessarily. Article 10 requires a data carrier physically present on the product, its packaging or its documentation, and Article 9 leaves the choice of carrier and its placement to the delegated act. Nothing currently mandates a QR code for electronics. **Is GS1 required?** No adopted instrument mandates GS1 for electronics passports. GS1 standards are widely used in electronics and may be a practical choice for identification and interoperability, but that is an implementation decision until a specific legal requirement says otherwise. **How does a bill of materials relate to a passport?** Almost every product-level claim about substances, materials, mass or recycled content is an aggregation over the bill of materials. The passport dataset is derived from it, which means the passport is only as accurate as the structure and the component data behind it. **Who is responsible for component and supplier data?** Each supplier is responsible for its own declarations about its own parts. The economic operator placing the product on the market is responsible for the product level claim, including for the soundness of the aggregation and the currency of the inputs. **Do repair events change the passport?** No current rule requires it for electronics, because no electronics passport rule exists. Regulation (EU) 2024/1781 Article 11 requires free access for professional repairers, independent operators, refurbishers, remanufacturers and recyclers, and addresses linkage of successive passports, so the direction of travel is towards lifecycle relevance. Anything more specific is speculation. **Can an SME prepare without enterprise systems?** Yes. A governed schema, a reconciled bill of materials, current supplier declarations with validity dates, controlled documentation and a named owner per product record cover most of the value. Buy software when a defined requirement makes it necessary, not before. **Should companies pilot now?** Yes, on one representative product family, bounded, and framed explicitly as a capability exercise. A pilot does not establish compliance with any future requirement. ## Related Articles * [Digital Product Passports for Furniture: What Companies Need to Know](/docs/knowledge-base/industry-guides/digital-product-passports-for-furniture) * [Digital Product Passports for Textiles and Apparel: What Companies Need to Know](/docs/knowledge-base/industry-guides/digital-product-passports-for-textiles-and-apparel) * [Digital Product Passports for Steel and Aluminium: What Companies Need to Know](/docs/knowledge-base/industry-guides/digital-product-passports-for-steel-and-aluminium) * [Digital Product Passports for Batteries: What Companies Need to Know](/docs/knowledge-base/industry-guides/digital-product-passports-for-batteries) * [Digital Product Passports for Construction Products: What Companies Need to Know](/docs/knowledge-base/industry-guides/digital-product-passports-for-construction-products) * [Which Products Will Require a Digital Product Passport?](/docs/knowledge-base/regulations/which-products-will-require-a-digital-product-passport) * [Battery Passport](/docs/knowledge-base/glossary/battery-passport) * [Digital Product Passport](/docs/knowledge-base/glossary/digital-product-passport) ## References * Regulation (EU) 2024/1781 establishing a framework for the setting of ecodesign requirements for sustainable products, OJ L, 2024/1781, 28.6.2024: [https://eur-lex.europa.eu/eli/reg/2024/1781/oj](https://eur-lex.europa.eu/eli/reg/2024/1781/oj) * European Commission, Ecodesign for Sustainable Products and Energy Labelling Working Plan 2025-2030, COM(2025) 187 final, 19 April 2025: [https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52025DC0187](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52025DC0187) * Directive 2011/65/EU on the restriction of the use of certain hazardous substances in electrical and electronic equipment: [https://eur-lex.europa.eu/eli/dir/2011/65/oj](https://eur-lex.europa.eu/eli/dir/2011/65/oj) * Commission Delegated Directive (EU) 2015/863 amending Annex II to Directive 2011/65/EU: [https://eur-lex.europa.eu/eli/dir\_del/2015/863/oj](https://eur-lex.europa.eu/eli/dir_del/2015/863/oj) * Directive 2012/19/EU on waste electrical and electronic equipment: [https://eur-lex.europa.eu/eli/dir/2012/19/oj](https://eur-lex.europa.eu/eli/dir/2012/19/oj) * Regulation (EU) 2017/1369 setting a framework for energy labelling: [https://eur-lex.europa.eu/eli/reg/2017/1369/oj](https://eur-lex.europa.eu/eli/reg/2017/1369/oj) * Commission Regulation (EU) 2023/1670 laying down ecodesign requirements for smartphones, mobile phones other than smartphones, cordless phones and slate tablets: [https://eur-lex.europa.eu/eli/reg/2023/1670/oj](https://eur-lex.europa.eu/eli/reg/2023/1670/oj) * Commission Delegated Regulation (EU) 2023/1669 with regard to the energy labelling of smartphones and slate tablets: [https://eur-lex.europa.eu/eli/reg\_del/2023/1669/oj](https://eur-lex.europa.eu/eli/reg_del/2023/1669/oj) * Commission Regulation (EU) 2019/2021 laying down ecodesign requirements for electronic displays: [https://eur-lex.europa.eu/eli/reg/2019/2021/oj](https://eur-lex.europa.eu/eli/reg/2019/2021/oj) * Commission Regulation (EU) 2019/424 laying down ecodesign requirements for servers and data storage products: [https://eur-lex.europa.eu/eli/reg/2019/424/oj](https://eur-lex.europa.eu/eli/reg/2019/424/oj) * Directive 2009/125/EC establishing a framework for the setting of ecodesign requirements for energy-related products: [https://eur-lex.europa.eu/eli/dir/2009/125/oj](https://eur-lex.europa.eu/eli/dir/2009/125/oj) * Regulation (EU) 2023/988 on general product safety: [https://eur-lex.europa.eu/eli/reg/2023/988/oj](https://eur-lex.europa.eu/eli/reg/2023/988/oj) * Regulation (EU) 2019/1020 on market surveillance and compliance of products: [https://eur-lex.europa.eu/eli/reg/2019/1020/oj](https://eur-lex.europa.eu/eli/reg/2019/1020/oj) * Regulation (EU) 2023/1542 concerning batteries and waste batteries: [https://eur-lex.europa.eu/eli/reg/2023/1542/oj](https://eur-lex.europa.eu/eli/reg/2023/1542/oj) * European Product Registration Database for Energy Labelling: [https://eprel.ec.europa.eu/](https://eprel.ec.europa.eu/) * EUR-Lex, register of delegated and implementing acts, for the current adoption status of measures under Regulation (EU) 2024/1781: [https://eur-lex.europa.eu/homepage.html](https://eur-lex.europa.eu/homepage.html) ## About This Article About This Article
Last Reviewed
2026-08-09
Next Scheduled Review
2027-08-09
Article Version
1.0
tieback Knowledge is a continuously maintained reference library covering Digital Product Passports, product traceability, product compliance and related regulations. Articles are reviewed regularly as legislation, standards and implementation guidance evolve. ## Related Docs * [Industry Guides](/docs/knowledge-base/industry-guides/overview) * [Digital Product Passports for Batteries: What Companies Need to Know](/docs/knowledge-base/industry-guides/digital-product-passports-for-batteries) * [Digital Product Passports for Construction Products: What Companies Need to Know](/docs/knowledge-base/industry-guides/digital-product-passports-for-construction-products) * [Digital Product Passports for Textiles and Apparel: What Companies Need to Know](/docs/knowledge-base/industry-guides/digital-product-passports-for-textiles-and-apparel) * [What is the Ecodesign for Sustainable Products Regulation (ESPR)?](/docs/knowledge-base/regulations/what-is-the-ecodesign-for-sustainable-products-regulation-espr) * [What Data Goes in a Digital Product Passport, and Where Does It Come From?](/docs/knowledge-base/digital-product-passports/what-data-goes-in-a-digital-product-passport) * [Who Is Legally Responsible for a Digital Product Passport?](/docs/knowledge-base/regulations/who-is-legally-responsible-for-a-digital-product-passport) * [The Digital Product Passport Standards Landscape](/docs/knowledge-base/standards-and-technology/the-digital-product-passport-standards-landscape) * [How to Prepare Suppliers for Digital Product Passports](/docs/knowledge-base/implementation/how-to-prepare-suppliers-for-digital-product-passports) * [How to Validate Digital Product Passport Data](/docs/knowledge-base/implementation/how-to-validate-digital-product-passport-data) * [How to Manage Evidence for Digital Product Passports](/docs/knowledge-base/implementation/how-to-manage-evidence-for-digital-product-passports) * [How to Build a Digital Product Passport Implementation Roadmap](/docs/knowledge-base/implementation/how-to-build-a-digital-product-passport-implementation-roadmap) * [Building an Enterprise Digital Product Passport Architecture](/docs/knowledge-base/enterprise-systems-and-data-architecture/building-an-enterprise-digital-product-passport-architecture)