Skip to main content

Directive 2012/19/EU and Directive 2011/65/EU

There is no electronics passport date, and we will not invent one. What is in force is a treatment information duty, a substance restriction and a producer register.

No delegated act covers this industry, so no passport content list and no passport date exist for it. The duties that are in force are about data all the same: what a recycler needs, what substances a product may not contain, and what a producer has to report. Norruva models those and leaves the rest open.

Start now Contact sales
ProductsSmartphone X1 128 GBPublished

Electronics and ICT passport

Northline Smartphone X1 128 GB · SKU PHONE-X1-128

Directive 2012/19/EU and Directive 2011/65/EU
GS1 Digital Linkdpp.brand.com/01/09506000134369

Sample data. Northline is a fictional brand and the GTIN comes from the GS1 example range.

Passport data4 of 8 fields
  • Energy classClass BVerified
  • Repairability index8.1 out of 10Verified
  • Spare part availability7 yearsVerified
  • Software support5 years of security updatesPending

+4 more

Last updated May 12, 2025 at 10:24 AM

Printed circuit boards moving along an automated assembly line
Electronics and ICTDirective 2012/19/EU and Directive 2011/65/EU

The law

The regulation that governs it. Every statement below names the instrument it comes from, the article it sits in, and the date of the copy we hold.

Held instrument

Directive 2012/19/EU

The waste electrical and electronic equipment directive is the in force data duty here. Its Article 15(1) is, in effect, a recycler facing passport that predates the word.

  • Producers must provide information free of charge on preparation for re-use and treatment for each type of new equipment placed on the Union market, within one year of that placing, identifying the components and materials and the location of dangerous substances and mixtures.Art. 15(1)In law
  • Member States had to bring into force the laws, regulations and administrative provisions needed to comply with the directive by the date in Article 24(1), so these duties reach producers through national law.Art. 24(1) · 14 February 2014In law
  • Producers must mark equipment placed on the market with the crossed out wheeled bin symbol shown in Annex IX, or print it on the packaging, the instructions for use and the warranty where the size or function of the product makes that necessary.Art. 14(4) and Annex IXIn law
  • Each producer, or its authorised representative, must be registered in the national register and able to enter the information on its activities in that Member State online.Art. 16(2)In law

Source: CELEX 32012L0019 · as of 24 July 2012

Held instrument

Directive 2011/65/EU

The hazardous substances directive is the restriction behind the material declaration every buyer asks for. It reaches producers through national law and it names the substances in its Annex II.

  • Member States must ensure that equipment placed on the market, including cables and spare parts for its repair, reuse, updating of functionality or upgrading of capacity, does not contain the substances listed in Annex II above the maximum concentration values by weight in homogeneous materials.Art. 4(1) and Art. 4(2)In law
  • Member States had to adopt and publish the laws, regulations and administrative provisions needed to comply with the directive by the date in Article 25(1).Art. 25(1) · 2 January 2013In law

Source: CELEX 32011L0065 · as of 1 July 2011

Held instrument

Regulation (EU) 2024/1781

The framework regulation names this industry in the first working plan. That is an adoption intention. It is not a product group with requirements, and it carries no date.

  • The first working plan must prioritise information and communication technology products and other electronics for the setting of ecodesign requirements.Art. 18(5)(k)Roadmap
  • No delegated act setting ecodesign and information requirements for this industry has been adopted, so there is no passport content list and no passport date for it.Art. 4Not adopted

Source: CELEX 32024R1781 · as of 28 June 2024

Dates

Dates that apply. Only obligations that carry a date in a held text appear here.

Electronics and ICT obligations

Each date below restates a dated obligation in the instrument named on the card.

  1. 12 January 2013

    Member States had to adopt and publish the laws, regulations and administrative provisions needed to comply with the directive by the date in Article 25(1).

    Art. 25(1) · In law

  2. 214 February 2014

    Member States had to bring into force the laws, regulations and administrative provisions needed to comply with the directive by the date in Article 24(1), so these duties reach producers through national law.

    Art. 24(1) · In law

Both dates here are transposition deadlines that have passed, which is why these duties reach producers through national law rather than as one EU date. No passport date exists for this industry in held law.

Data model

What the passport carries. Every field, the sample value it takes, and the platform module that models it.

Sample values are fictional. Northline is an invented brand.
FieldSampleModelled by
Energy classClass Bcompliance-kernel-contracts/domain/value-objects/ElectronicsPassport.ts
Repairability index8.1 out of 10compliance-kernel-contracts/domain/value-objects/ElectronicsPassport.ts
Spare part availability7 yearscompliance-kernel-contracts/domain/value-objects/ElectronicsPassport.ts
Software support5 years of security updatescompliance-kernel-contracts/domain/value-objects/ElectronicsPassport.ts
Restricted substancesScreened against Annex II, none above the limit valuescompliance-kernel-contracts/domain/value-objects/ElectronicsPassport.ts
Agency notificationReference number on filecompliance-sectors/domain/entities/FullREACHCompliance.ts
Dismantling instructionsSequence, tools and dangerous substance locationscompliance-kernel-contracts/domain/value-objects/ElectronicsPassport.ts
Equipment categoryCategory and collection point informationcompliance-kernel-contracts/domain/value-objects/ElectronicsPassport.ts

The cost of waiting

What happens if you don't adapt?

A passport is checked at the point a product enters the market. When the record is missing, the product is what waits.

Products blocked from the EU market

Where an instrument requires a Digital Product Passport for a product group, products without one risk restricted access to the EU market.

A data project that becomes an emergency

A passport is a data project before it is a compliance one. Started late, it turns into re-keying, chasing suppliers and rework across systems, against a fixed date.

Audit risk and regulatory exposure

Fragmented or incomplete product data raises the risk of a failed audit, penalties and a correction you have to make in public.

The workflow

From your systems to a verified passport. Five steps, the same on every industry page, because the path does not change with the product group.

01

Create the product record

Start from the SKUs you already hold. The product record is what the passport hangs on, one per trade item.

02

Collect supplier data

Request the fields you do not hold from the party that holds them, with a due date and a trail of who answered.

03

Attach evidence

Test reports, declarations and certificates land in the evidence vault, attached to the field they support.

04

Run compliance checks

The industry template checks every required field and names the gaps before anything is published.

05

Publish the passport

The passport resolves from the product GS1 Digital Link, showing each audience only what it is allowed to see.

The bundle

The products behind it. The same platform, assembled for this product group.

Product Passports

The passport record itself: its fields, its versions, and the resolver that answers a scan.

Explore ›

Compliance Automation

Checks every required field against the industry template and names the gaps it finds.

Explore ›

APIs and Integrations

The same operations over an API, so passports follow the release pipeline you already run.

Explore ›

Publishing and Data Exchange

Publishes the passport and exchanges it in the formats your partners already read.

Explore ›

Standards

The rails every passport runs on.

The passport data model, identifiers, data carriers and exchange formats follow EN 18216, EN 18219, EN 18220, EN 18221, EN 18222 and EN 18223, the six standards cited in the Official Journal by Implementing Decision (EU) 2026/1736. Norruva implements them as the rails every passport runs on.

See how we hold standards and evidence ›

Questions

Questions, answered. What teams in electronics and ict ask before they start.

If the answer you need names a date, it comes from the held text of the instrument cited above it.

  • No. No delegated act covering this industry has been adopted under the Ecodesign for Sustainable Products Regulation, so no passport content list and no date exist. A date quoted elsewhere is a working plan intention, not a law.

  • Because the data duties are already there. Article 15(1) of the waste electrical and electronic equipment directive requires treatment information per equipment type, Annex II of the hazardous substances directive restricts what a product may contain, and buyers ask for both in procurement.

  • Information, free of charge, on preparation for re-use and treatment for each type of new equipment, within one year of it being placed on the market, identifying components, materials and the location of dangerous substances and mixtures.

  • Both instruments are directives, so they reach producers through national law. The dates in the timeline are the deadlines by which Member States had to bring the provisions into force, which is the honest way to show them.

Get started

Start your first passport.

Model electronics and ict in test mode, or talk to us about the rollout across your catalog.

Start now Contact sales

Try it without an account

Run the whole journey on sample data. Nothing anchors, bills or leaves the sandbox.

Open the sandbox ›

Build it into your stack

Every endpoint, in HTTP, cURL, JavaScript, Python and Go.

Read the docs ›