> 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.
# When Will Digital Product Passports Become Mandatory?
> Why there is no single Digital Product Passport start date, which dates are already fixed in EU law, which depend on future delegated acts, and what to do in the meantime.
## Executive Summary
There is no single date on which the
[Digital Product Passport](/docs/knowledge-base/glossary/digital-product-passport) becomes
mandatory. Any article, briefing or vendor slide that gives you one date for the whole economy is
either simplifying a legal structure it has not read, or selling urgency.
The reason is structural rather than political. The
[Ecodesign for Sustainable Products Regulation](/docs/knowledge-base/regulations/what-is-the-ecodesign-for-sustainable-products-regulation-espr)
(ESPR) is a framework. It creates the power to require a passport, defines what a passport must be
capable of doing, and sets the machinery for enforcement. It does not, by itself, require any
individual product to carry one. That step happens in a
[delegated act](/docs/knowledge-base/glossary/delegated-act) adopted for a specific product group,
and each delegated act carries its own date of application and its own transition period.
So the honest answer has three parts. Some dates are already fixed in adopted law, most notably the
battery passport under Regulation (EU) 2023/1542, which applies to the battery categories it names
from 18 February 2027. Some dates do not yet exist because the delegated act that would set them
has not been adopted. And some product groups have no date and no scheduled rule making at all.
This article sets out that structure precisely, introduces the Digital Product Passport Compliance
Timeline as a way to locate your organisation on the path rather than guess at a deadline, and
separates the preparation work that depends on knowing the specification from the preparation work
that does not. The second category is larger than most organisations expect, and it is the work
that is worth starting now.
* There is no economy wide Digital Product Passport start date. Obligations begin product group by
product group, through delegated acts. - The date fixed in adopted EU law today is 18 February
2027, for the battery passport under Regulation (EU) 2023/1542, for the battery categories that
regulation names. - ESPR has applied since 18 July 2024, but applying is not the same as
requiring: it switched on the power, not the obligations. - A [working plan](/docs/knowledge-base/glossary/working-plan) priority is a commitment to do rule making work.
It carries no compliance date and creates no duty. - Every delegated act sets its own transition
period, typically counted from [entry into force](/docs/knowledge-base/glossary/entry-into-force)
to date of application, and typically measured in months rather than years. - Waiting for a date
before starting is the expensive strategy, because the longest lead time work, identifiers, data
ownership and supplier contracts, does not depend on the specification.
This is the fourth and final core article in the Regulations section, and the eighth in the learning
path that begins with
[What is a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/what-is-a-digital-product-passport).
Framework TBF-008
The Digital Product Passport Compliance Timeline
Separates confirmed legal dates from expected and indicative ones so planning rests on what is
actually fixed.
> **Educational scope**
>
> This article provides general educational information about EU product regulation concepts. It
> does not determine the compliance dates applying to any particular organisation or product, and it
> is not legal advice. Applicable dates depend on the delegated act covering the product group in
> question.
## Table of Contents
* [Definition](#definition)
* [Why There Is No Single Compliance Date](#why-there-is-no-single-compliance-date)
* [How Implementation Actually Happens](#how-implementation-actually-happens)
* [The Digital Product Passport Compliance Timeline](#the-digital-product-passport-compliance-timeline)
* [What Is Already Fixed](#what-is-already-fixed)
* [What Depends on Delegated Acts](#what-depends-on-delegated-acts)
* [Preparation Periods Explained](#preparation-periods-explained)
* [What Manufacturers Should Do Now](#what-manufacturers-should-do-now)
* [What Importers Should Do Now](#what-importers-should-do-now)
* [What Retailers Should Do Now](#what-retailers-should-do-now)
* [Preparing Before Requirements Apply](#preparing-before-requirements-apply)
* [Common Misconceptions](#common-misconceptions)
* [Frequently Asked Questions](#frequently-asked-questions)
* [Key Takeaways](#key-takeaways)
* [Related Articles](#related-articles)
* [Related Glossary Terms](#related-glossary-terms)
* [References](#references)
* [About This Article](#about-this-article)
## Definition
The date from which a legal obligation must actually be met. In EU law it is distinct from the
date of adoption, when the institutions agree the text, and from the date of entry into force,
usually twenty days after publication in the Official Journal, when the act becomes part of the
legal order. A Digital Product Passport requirement bites on the date of application set in the
act that creates it, and only for the products that act covers.
Three dates therefore matter for every act, and confusing them is the single most common source of
timeline error:
| Date | What happens | What it means for you |
| ------------------- | ----------------------------------------------------------------- | -------------------------------------------------------------- |
| Adoption | The institutions agree the final text | The requirement is knowable and stable enough to build against |
| Entry into force | The act becomes part of EU law, usually 20 days after publication | The clock on the transition period starts |
| Date of application | The obligation must be met | Products placed on the market from this date must comply |
The gap between the second and third of these is the preparation period. It is the only window in
which you can build against a known specification, and it is deliberately finite.
## Why There Is No Single Compliance Date
ESPR is a framework regulation. It entered into force on 18 July 2024 and has applied since that
date. Neither of those facts means that any product needs a passport today.
What ESPR does is establish the legal architecture: it defines the Digital Product Passport, sets
out what it must contain in general terms, requires that it be accessible through a
[data carrier](/docs/knowledge-base/glossary/data-carrier) linked to a unique
[product identifier](/docs/knowledge-base/glossary/product-identifier), provides for a registry and
for verification, and empowers the Commission to adopt delegated acts that turn the general
architecture into product specific duties. The obligation to carry a passport for a given product
group is created in the delegated act, not in the framework.
That design is intentional. A single date for all products would require a single specification for
all products, and a battery, a jumper and a structural steel beam have almost nothing in common in
terms of what should be disclosed, who holds the data, how it is measured or what an inspector would
check. The EU legislator chose sequencing over uniformity.
#### Treating 2027 as the deadline for everything
2027 appears in almost every DPP presentation because of the battery passport date of 18 February
2027\. That date is real, but it belongs to Regulation (EU) 2023/1542 and to the battery categories
that regulation covers. It is not an ESPR date, it is not a textiles date, and it is not a
deadline for your product unless you place those batteries on the EU market. Anchoring an
enterprise programme to a date that does not apply to your portfolio produces either wasted spend
or, more often, a credibility problem when the date passes without consequence and the programme
loses its sponsor.
## How Implementation Actually Happens
The sequence from a policy ambition to an enforceable duty on your products runs through several
distinct instruments. They are frequently conflated, and they carry very different weight.
| Instrument | Legal status | Creates a duty? | Sets a date? |
| --------------------- | -------------------------------------------- | ----------------- | --------------------------------- |
| Framework regulation | Binding law, directly applicable | Architecture only | No, for passports |
| Working plan | Commission planning document | No | Indicative rule making dates only |
| Consultation document | Evidence gathering, non binding | No | No |
| Delegated act | Binding law once in force | Yes | Yes |
| Implementing act | Binding law, uniform application detail | Procedural | Sometimes |
| Harmonised standard | Voluntary, confers presumption of conformity | No | No |
| Guidance document | Commission interpretation, non binding | No | No |
Only two rows in that table can put a compliance date on your calendar: a framework regulation that
contains its own self standing obligation, as the Batteries Regulation does, and a delegated act
adopted under a framework. Everything else informs planning. It does not create duties.
> **A simple test before you diarise a date**
>
> Ask one question: can someone give you the Official Journal reference for the act that contains
> this date? If the answer involves a working plan, a press release, a conference slide, a
> consultancy forecast or a vendor roadmap, the date is not law. Note it as an expectation, not as a
> deadline, and record which of the two it is in your compliance register.
For the full mechanics of how a delegated act is developed, scrutinised and published, see
[What Are Delegated Acts?](/docs/knowledge-base/regulations/what-are-delegated-acts). For which
product groups are in scope of that work, see
[Which Products Will Require a Digital Product Passport?](/docs/knowledge-base/regulations/which-products-will-require-a-digital-product-passport).
## The Digital Product Passport Compliance Timeline
The framework below is an original tieback model. It is not a legal instrument and it does not
predict dates. Its purpose is to let an organisation answer a more useful question than "when is the
deadline": namely, which stage is my product group at, what is the Commission doing at that stage,
what is my industry doing, and what should I be doing.
Each stage runs three parallel lanes, because the three actors are never doing the same thing at the
same time. The mistake most programmes make is to wait for the Commission lane to reach stage 6
before starting work in the organisation lane.
1
Today
No obligation for most products
-
Commission
-
Running preparatory studies, impact assessments and the ecodesign forum alongside the
registry and technical groundwork.
-
Industry
-
Trade associations gathering member evidence, piloting data exchange, and forming
positions ahead of consultation.
-
Your organisation
-
Establish the facts: which categories you place on the market, in which role, and where
your product data actually lives.
2
ESPR in force
Power created, applies since 18 July 2024
-
Commission
-
Holds the delegated power, operates the framework, and builds the shared infrastructure
the passport regime depends on.
-
Industry
-
Standardisation bodies begin the technical work on identifiers, data models and access
rights that later acts will reference.
-
Your organisation
-
Read the framework rather than the commentary. Understand what a passport is required to
be capable of, independent of category.
3
Working plans
Prioritisation, still no duty
-
Commission
-
Publishes the product groups selected for rule making and the indicative sequence of
work, applying the ESPR selection criteria.
-
Industry
-
Assesses exposure, builds the evidence base, and identifies where a proposed measure
would be unworkable in practice.
-
Your organisation
-
Determine whether your category is named. If it is, move from watching to preparing. If
it is not, keep the watch cheap and scheduled.
4
Delegated acts
The obligation is created
-
Commission
-
Drafts, consults publicly, takes expert group input, adopts, and submits the act for
Parliament and Council scrutiny before publication.
-
Industry
-
Responds during the feedback window, and begins converging on shared data formats and
supplier templates for the category.
-
Your organisation
-
Respond to the consultation, then read the adopted text and extract the actual data
fields, dates and scope boundaries.
5
Preparation period
Known specification, finite window
-
Commission
-
Issues guidance, mandates or endorses [harmonised standards](/docs/knowledge-base/glossary/harmonised-standard), and readies the registry
and verification arrangements.
-
Industry
-
Publishes sector implementation guides and runs pilots so that suppliers are asked for
data in a consistent way.
-
Your organisation
-
Collect supplier data, populate and validate passports, apply data carriers, and test
the whole chain end to end before it is inspected.
6
Mandatory compliance
Date of application reached
-
Commission
-
The requirement is live. Placing a covered product on the EU market without a compliant
passport is a breach.
-
Industry
-
Commercial expectations harden: customers and platforms start refusing products that
cannot present a passport.
-
Your organisation
-
Every covered unit placed on the market from this date carries a passport, and you can
evidence how each value was derived.
7
Market surveillance
Enforcement in practice
-
Commission
-
National authorities inspect, coordinated through the EU market surveillance framework,
with customs controls at the border.
-
Industry
-
Early enforcement cases establish what "good enough" looks like far more concretely than
any guidance note.
-
Your organisation
-
Maintain passports, respond to authority requests, and correct data promptly when a
defect is found.
8
Continuous improvement
Revision cycle
-
Commission
-
Reviews measures, tightens thresholds and extends coverage as evidence and capability
improve.
-
Industry
-
Data quality expectations rise, and voluntary disclosure moves ahead of the legal
minimum in competitive categories.
-
Your organisation
-
Treat the passport as a maintained product asset with an owner and a budget, not as a
completed project.
Different product groups sit at different stages simultaneously. A diversified manufacturer can
be at stage 6 for batteries and stage 3 for textiles in the same financial year, which is why
the timeline is a per category position rather than a corporate one.
## What Is Already Fixed
Two things are fixed in adopted EU law today. Everything else in the passport landscape is either
planning or expectation.
The Batteries Regulation contains a self standing battery passport requirement. It applies to
light means of transport batteries, industrial batteries with a capacity greater than 2 kWh, and
electric vehicle batteries. From 18 February 2027, each such battery placed on the market or put
into service must have an electronic record accessible through a QR code printed or engraved on
the battery, carrying information on the battery model and the specific battery unit, with access
differentiated between the general public, [notified bodies](/docs/knowledge-base/glossary/notified-body), authorities and persons with a legitimate
interest. The passport is the responsibility of the economic operator that places the battery on
the market, and it must remain available until the battery reaches end of life. This obligation
exists independently of ESPR and is not conditional on any delegated act.
The second fixed point is ESPR itself. Regulation (EU) 2024/1781 entered into force on 18 July 2024
and has applied since that date. Its practical effect today is that the power exists, the definition
of a passport exists, and the enforcement architecture exists. No product owes a passport because of
it yet.
Two further points are worth stating plainly for the sake of accuracy, because they are often
mangled in summaries. First, the Construction Products Regulation, Regulation (EU) 2024/3110, also
provides for a digital product passport for construction products, with its own system and its own
phased arrangements. Second, ESPR repealed and replaced the previous Ecodesign Directive framework,
so existing ecodesign measures for products such as electronics continue to operate and will be
progressively revised under the new regulation.
#### How a fixed date reads in practice
A company placing 5 kWh industrial battery systems on the EU market has a hard date: 18 February
2027\. It can name the regulation, cite the article, and read the information requirements from an
annex today. The same company's cordless power tool housings, an electronics adjacent category,
have no passport date at all. Those two product lines belong on the same compliance register with
visibly different statuses: one with a legal date, one marked "no adopted requirement, monitored".
Recording both in the same column is how organisations end up either over investing or being
surprised.
## What Depends on Delegated Acts
Everything else. For any product group other than those covered by an adopted act, the following are
all unknown until the delegated act for that group is adopted and published:
* Whether a passport is required for that group at all
* Exactly which products within the group fall inside scope, and which are excluded
* Which data fields must be carried, at what granularity, and at model, batch or item level
* Which fields are public and which are restricted to authorities or to holders of a legitimate
interest
* Which [data carrier](/docs/knowledge-base/glossary/data-carrier) is mandated and how it must be
physically applied
* How long the passport must remain available after the product is placed on the market
* The date of application, and any staggered dates for different sub categories or company sizes
Because none of that is knowable in advance, no responsible source can tell you when your textiles,
furniture or steel products will need a passport. What can be said accurately is that those groups
are prioritised for rule making in the ESPR working plan, that consultation will precede adoption,
and that a preparation period will follow adoption.
#### Reading a working plan date as a compliance date
Working plans contain indicative years for when the Commission intends to adopt measures. Those
are dates for the Commission's own work, not for your compliance. Adoption in a given year does
not mean obligations in that year: the transition period runs afterwards. Treating an indicative
adoption year as a compliance deadline typically overstates urgency by a year or more, and it
destroys the credibility of the compliance function when the year passes uneventfully.
## Preparation Periods Explained
The preparation period is the interval between an act entering into force and its date of
application. It exists so that businesses can adapt to a requirement that is, by then, fully
knowable. Three properties of it matter for planning.
It is finite and set by the legislator, not by you. It is usually expressed in months from entry
into force, and for product information duties it has historically been measured in months to a
small number of years rather than in decades. It is not a negotiation.
It is the only period in which the specification is stable. Before adoption, requirements can and do
change in response to consultation. After adoption, they are fixed. Any build performed before
adoption is a bet on a draft, which is precisely why the sensible pre adoption work is
infrastructural rather than specification driven.
And it is shared with your entire supply chain. If a delegated act gives eighteen months, you do not
have eighteen months. You have eighteen months minus the time your suppliers need to establish the
data, minus the time your systems need to carry it, minus the time your packaging and labelling
cycles need to apply a carrier. In practice, the supplier data collection step is the long pole, and
it is the step you control least.
#### Work backwards from the date, not forwards from today
When a delegated act relevant to you is adopted, build the plan in reverse from the date of
application: last shippable production date under the old regime, carrier artwork freeze, data
freeze and validation, supplier data returned, supplier data requested, contract clauses in place.
Most organisations discover that the supplier request has to go out within the first quarter of
the preparation period. Planned forwards from today, that same task tends to land in the final
quarter, where it cannot succeed.
## What Manufacturers Should Do Now
Manufacturers carry the primary duty in EU product law, and under a passport regime they are
normally the party responsible for creating and maintaining the record.
#### Fix your identifier strategy
Decide how each product model, batch and item is uniquely identified, and make that identifier
stable across your systems. A passport is anchored to a unique [product identifier](/docs/knowledge-base/glossary/product-identifier), and identifier rework is the most
disruptive change to make late. Established schemes such as
[GS1](/docs/knowledge-base/glossary/gs1) and [GS1 Digital Link](/docs/knowledge-base/glossary/gs1-digital-link) exist precisely for this.
#### Locate your product data
Map where each class of [product data](/docs/knowledge-base/glossary/product-data) lives today:
PIM, ERP, PLM, specification documents, supplier emails, spreadsheets. The distribution matters
more than the volume, because scattered data is what makes later collection slow.
#### Put data clauses into supplier contracts
Add data provision, accuracy and update obligations at the next renewal rather than at the point
of legal need. Contracts renegotiated under deadline pressure are expensive and slow.
#### Build a traceability baseline
Establish [product traceability](/docs/knowledge-base/glossary/product-traceability) sufficient
to answer where a component came from and which units it went into. This underpins almost every
plausible passport requirement and has independent value in
[recall](/docs/knowledge-base/glossary/recall) and quality management.
#### Assign ownership
Name an accountable owner for passport readiness. Requirements arriving with no owner get
assigned to whoever is least able to refuse, usually late.
## What Importers Should Do Now
An importer places a third country product on the EU market, and EU product law consistently treats
that as a position of real responsibility rather than a pass through.
The immediate work is diligence and contract. Establish, for each supplier, whether they can produce
the underlying data at all, in what form, and how quickly. Many non EU manufacturers will not have
been asked before, and the answer is frequently that the data exists in production records that have
never been structured for disclosure. That discovery takes months and is best made now, when nothing
depends on it.
Then write the requirement into the purchase terms: what data must accompany each shipment, in what
format, with what accuracy commitment and what remedy if it is missing. Importers who leave this to
the preparation period find that their leverage is lowest exactly when their need is highest.
> **Check whether you are actually the manufacturer**
>
> If you import under your own brand, or you modify a product in a way that affects its compliance,
> EU product legislation generally treats you as the manufacturer for that product, with the full
> set of manufacturer duties. Private label ranges frequently sit in this category. Confirm your
> legal role per range before you plan around the importer duties, because the two roles carry
> materially different obligations.
## What Retailers Should Do Now
Retailers and distributors are not usually the party that creates a passport, but they are
frequently the party that a consumer or an inspector encounters first, and duties of care apply.
The practical readiness work is threefold. Confirm that goods you list can be accompanied by the
required record when the requirement arrives, and make that a supplier onboarding question now.
Ensure that the [QR code](/docs/knowledge-base/glossary/qr-code) or other carrier on the product and
on packaging survives your own labelling, repackaging and relabelling processes, because a carrier
covered by a price sticker is a defective carrier. And decide how passport information will appear
in your online listings, since [sustainability data](/docs/knowledge-base/glossary/sustainability-data)
that is present on the physical product but absent online creates an inconsistency that customers
and authorities both notice.
Online marketplaces should also note that EU product law increasingly places specific obligations on
platforms, so the question of who is the responsible
[economic operator](/docs/knowledge-base/glossary/economic-operator) for a marketplace listing
deserves a documented answer rather than an assumption.
## Preparing Before Requirements Apply
The strongest argument for starting before your category has a date is that most of the necessary
work is not category specific. Sort your programme into two buckets.
Work that does not depend on the delegated act:
* A stable, unique identifier scheme applied consistently across models, batches and items
* A single authoritative source for each product attribute, with a named owner
* Supplier data clauses in contracts, with format and accuracy commitments
* A traceability baseline linking components to finished goods
* Governance for who may change a published product claim and how that change is evidenced
* An understanding of your [product lifecycle](/docs/knowledge-base/glossary/product-lifecycle) data
events: manufacture, distribution, repair, resale, recycling
Work that must wait for the delegated act:
* The exact list of mandatory data fields and their permitted values
* Public versus restricted access allocation for each field
* The mandated carrier type and its physical application rules
* Any [conformity assessment](/docs/knowledge-base/glossary/conformity-assessment) or verification
step tied to the passport
* Registration and retention duration specifics
#### Build the foundation, defer the specification
The first list is the one that takes eighteen to thirty six months in a large organisation, and
none of it is wasted if the requirements land differently than expected, because every item has
independent operational value in quality, recall, warranty and [circular economy](/docs/knowledge-base/glossary/circular-economy) programmes. The second list can be
delivered in a matter of months once the text exists. Sequencing them the other way round, which
is what "wait for clarity" produces in practice, compresses the slow work into the window designed
for the fast work.
Dates decide when work must be finished, not what the work is. For the work itself, see
[How to Build a Digital Product Passport Implementation Roadmap](/docs/knowledge-base/implementation/how-to-build-a-digital-product-passport-implementation-roadmap)
for sequencing,
[How to Validate Digital Product Passport Data](/docs/knowledge-base/implementation/how-to-validate-digital-product-passport-data)
for the controls that make published information defensible, and
[How to Test and Assure a Digital Product Passport](/docs/knowledge-base/implementation/how-to-test-and-assure-a-digital-product-passport)
for confirming readiness before an application date rather than after it.
## Common Misconceptions
* **"Digital Product Passports become mandatory in 2027."** The 2027 date is the battery passport
date under Regulation (EU) 2023/1542, for the battery categories that regulation names. It is not
a general date.
* **"ESPR already requires a passport, since it applies."** ESPR applies, but it creates the power
and the definition. The product level duty arrives in a delegated act.
* **"My category is in the working plan, so I have a deadline."** A working plan sets the
Commission's rule making agenda. It does not create an obligation and it does not set a compliance
date.
* **"There will be a long transition, so there is time."** Transition periods are counted in months
and are shared with your suppliers. The part you control least takes the longest.
* **"Non EU manufacturers are unaffected."** The obligation attaches to placing a product on the EU
market. Where the product was made is irrelevant to whether the requirement applies.
* **"Once we publish the passport, we are done."** Passport information generally has to remain
available and accurate for a defined period, and
[market surveillance](/docs/knowledge-base/glossary/market-surveillance) authorities can check it
at any point in that period.
* **"A voluntary passport now will not count later."** It may well not match the eventual
specification, which is why the sensible early investment is in identifiers, data quality and
governance rather than in a speculative published artefact.
## Frequently Asked Questions
#### Is there any date I can rely on today?
Yes, one that is widely relevant: 18 February 2027, for the battery passport under Regulation
(EU) 2023/1542, applying to light means of transport batteries, industrial batteries above 2 kWh
and electric vehicle batteries. If you do not place those on the EU market, that date does not
apply to you. Construction products have their own regime under Regulation (EU) 2024/3110 with
its own phasing.
#### When will textiles need a Digital Product Passport?
There is no adopted date. Textiles and apparel are a priority group in the ESPR working plan,
which means rule making work is scheduled. The compliance date will be set in the delegated act
for that group, and it will fall some period after that act enters into force. Anyone quoting a
specific textiles compliance date today is quoting an expectation, not law.
#### Does ESPR applying since July 2024 mean anything for me right now?
It means the legal architecture is live and the Commission can adopt product specific acts. It
does not impose a passport duty on your products. The practical consequence is that the rule
making pipeline is running, so consultation windows relevant to your category may open at any
time.
#### How much notice will we get once an act is adopted?
The act itself states its date of application, so notice is exactly the preparation period it
defines, plus whatever lead you gained by tracking the draft through consultation and scrutiny.
Organisations that follow the process from the call for evidence typically gain a year or more
of visibility over those that first read the act on publication.
#### Do requirements apply to products already on shelves?
EU product requirements normally attach to products placed on the market from the date of
application. Stock lawfully placed on the market beforehand is generally not made
retrospectively non compliant, though the precise treatment of existing stock is set by the act
concerned and must be read there.
#### Are small businesses exempt or given longer?
ESPR requires the Commission to consider effects on small and medium sized enterprises when
designing measures, and acts can include proportionate arrangements or later dates. Whether any
such arrangement exists, and what it is, is decided in each delegated act. There is no general
SME exemption from the framework.
#### What happens if we miss the date?
Placing a covered product on the EU market without a compliant passport is a breach of EU
product law. Enforcement sits with national [market surveillance authorities](/docs/knowledge-base/glossary/market-surveillance-authority) under Regulation (EU)
2019/1020 and with customs at the border, and can extend to [corrective action](/docs/knowledge-base/glossary/corrective-action), withdrawal from the market and
penalties set by each member state. The commercial consequence, goods stopped or delisted,
usually arrives before the legal one.
#### Should we wait for standards before building anything?
No. Harmonised standards will shape how requirements are met, but the foundational work,
identifiers, data ownership, supplier clauses and traceability, is standard independent. Waiting
for standards means starting the slowest work last.
## Key Takeaways
* There is no single date. Passport obligations arrive product group by product group, each with
its own date of application. - The reliable date in adopted law today is 18 February 2027 for the
battery passport under Regulation (EU) 2023/1542, for the battery categories that regulation
names. - ESPR has applied since 18 July 2024, but it creates the power and the definition, not the
product level duty. - Working plans, consultations, guidance and vendor roadmaps do not set
compliance dates. Only an adopted act with an Official Journal reference does. - Preparation
periods are finite, shared with your supply chain, and best planned backwards from the date of
application. - Manufacturers, importers and retailers have different immediate priorities, and
private label importers are often legally manufacturers. - The longest lead work, identifiers,
data ownership, supplier clauses and traceability, does not depend on the specification, so it is
the right work to start before your category is named.
## Related Articles
* [What Are Delegated Acts?](/docs/knowledge-base/regulations/what-are-delegated-acts)
* [What is the Ecodesign for Sustainable Products Regulation (ESPR)?](/docs/knowledge-base/regulations/what-is-the-ecodesign-for-sustainable-products-regulation-espr)
* [Which Products Will Require a Digital Product Passport?](/docs/knowledge-base/regulations/which-products-will-require-a-digital-product-passport)
* [How Digital Product Passports Will Be Enforced](/docs/knowledge-base/regulations/how-digital-product-passports-will-be-enforced)
* [Digital Product Passport](/docs/knowledge-base/glossary/digital-product-passport)
* [How Does a Digital Product Passport Work?](/docs/knowledge-base/digital-product-passports/how-does-a-digital-product-passport-work)
* [What Information Does a Digital Product Passport Contain?](/docs/knowledge-base/digital-product-passports/what-information-does-a-digital-product-passport-contain)
* [What is a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/what-is-a-digital-product-passport)
## Related Glossary Terms
Definitions of record for the terms used above live in the
[glossary](/docs/knowledge-base/glossary/overview).
* [Digital Product Passport](/docs/knowledge-base/glossary/digital-product-passport)
* [ESPR](/docs/knowledge-base/glossary/espr)
* [Delegated Act](/docs/knowledge-base/glossary/delegated-act)
* [Economic Operator](/docs/knowledge-base/glossary/economic-operator)
* [Market Surveillance](/docs/knowledge-base/glossary/market-surveillance)
* [Conformity Assessment](/docs/knowledge-base/glossary/conformity-assessment)
* [Product Data](/docs/knowledge-base/glossary/product-data)
* [Product Identifier](/docs/knowledge-base/glossary/product-identifier)
* [Product Traceability](/docs/knowledge-base/glossary/product-traceability)
* [Product Lifecycle](/docs/knowledge-base/glossary/product-lifecycle)
* [Sustainability Data](/docs/knowledge-base/glossary/sustainability-data)
* [Circular Economy](/docs/knowledge-base/glossary/circular-economy)
* [Data Carrier](/docs/knowledge-base/glossary/data-carrier)
* [QR Code](/docs/knowledge-base/glossary/qr-code)
* [GS1](/docs/knowledge-base/glossary/gs1)
* [GS1 Digital Link](/docs/knowledge-base/glossary/gs1-digital-link)
## References
* Regulation (EU) 2024/1781 establishing a framework for the setting of ecodesign requirements for
sustainable products, Official Journal of the European Union:
[https://eur-lex.europa.eu/eli/reg/2024/1781/oj](https://eur-lex.europa.eu/eli/reg/2024/1781/oj)
* Regulation (EU) 2023/1542 concerning batteries and waste batteries, including the battery passport
and its date of application, Official Journal of the European Union:
[https://eur-lex.europa.eu/eli/reg/2023/1542/oj](https://eur-lex.europa.eu/eli/reg/2023/1542/oj)
* Regulation (EU) 2024/3110 laying down harmonised rules for the marketing of construction products,
Official Journal of the European Union: [https://eur-lex.europa.eu/eli/reg/2024/3110/oj](https://eur-lex.europa.eu/eli/reg/2024/3110/oj)
* Regulation (EU) 2019/1020 on market surveillance and compliance of products, Official Journal of
the European Union: [https://eur-lex.europa.eu/eli/reg/2019/1020/oj](https://eur-lex.europa.eu/eli/reg/2019/1020/oj)
* European Commission, ESPR working plan 2025 to 2030, COM(2025) 187:
[https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52025DC0187](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52025DC0187)
* Treaty on the Functioning of the European Union, Article 290, delegated acts:
[https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A12012E%2FTXT](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A12012E%2FTXT)
* European Commission, Have Your Say portal, calls for evidence and draft acts open for feedback:
[https://ec.europa.eu/info/law/better-regulation/have-your-say](https://ec.europa.eu/info/law/better-regulation/have-your-say)
* European Commission, Ecodesign and energy labelling policy pages:
[https://energy.ec.europa.eu/topics/energy-efficiency\_en](https://energy.ec.europa.eu/topics/energy-efficiency_en)
* EUR-Lex, official portal for European Union law: [https://eur-lex.europa.eu](https://eur-lex.europa.eu)
## About This Article
About This Article
-
Last Reviewed
-
2026-08-07
-
Next Scheduled Review
-
2027-08-07
-
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
* [Regulations](/docs/knowledge-base/regulations/overview)
* [What is the Ecodesign for Sustainable Products Regulation (ESPR)?](/docs/knowledge-base/regulations/what-is-the-ecodesign-for-sustainable-products-regulation-espr)
* [What Are Delegated Acts?](/docs/knowledge-base/regulations/what-are-delegated-acts)
* [Which Products Will Require a Digital Product Passport?](/docs/knowledge-base/regulations/which-products-will-require-a-digital-product-passport)
* [What is a Digital Product Passport?](/docs/knowledge-base/digital-product-passports/what-is-a-digital-product-passport)