> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://tieback.io/docs/knowledge-base/regulations/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server.

# Regulations

## Docs

- [Regulations](https://tieback.io/docs/knowledge-base/regulations/overview.md): A section overview of the EU legislation that creates Digital Product Passport obligations, and how those obligations arrive over time.
- [What is the Ecodesign for Sustainable Products Regulation (ESPR)?](https://tieback.io/docs/knowledge-base/regulations/what-is-the-ecodesign-for-sustainable-products-regulation-espr.md): What the EU Ecodesign for Sustainable Products Regulation is, why it exists, how it works through delegated acts, and where the Digital Product Passport fits within it.
- [What Are Delegated Acts?](https://tieback.io/docs/knowledge-base/regulations/what-are-delegated-acts.md): What EU delegated acts are, why they exist, who creates them, what they can and cannot change, and why they decide when Digital Product Passport obligations become real.
- [Which Products Will Require a Digital Product Passport?](https://tieback.io/docs/knowledge-base/regulations/which-products-will-require-a-digital-product-passport.md): How the European Commission decides which product groups need a Digital Product Passport, which categories are covered today, which are prioritised next, and which remain undecided.
- [When Will Digital Product Passports Become Mandatory?](https://tieback.io/docs/knowledge-base/regulations/when-will-digital-product-passports-become-mandatory.md): 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.
- [How Digital Product Passports Will Be Enforced](https://tieback.io/docs/knowledge-base/regulations/how-digital-product-passports-will-be-enforced.md): How Digital Product Passport obligations move from an applicable legal requirement through market surveillance, checks, findings, operator response, corrective or restrictive measures and penalties, why enforcement sits substantially with Member State authorities, and what enforcement readiness means in practice.
- [Who Is Legally Responsible for a Digital Product Passport?](https://tieback.io/docs/knowledge-base/regulations/who-is-legally-responsible-for-a-digital-product-passport.md): How legal responsibility for Digital Product Passport obligations is allocated between manufacturers, importers, distributors, authorised representatives, online marketplaces, fulfilment service providers, suppliers and technology providers, why legal accountability is not the same as data contribution, contractual allocation, operational ownership or internal data ownership, and how to map economic operator roles per product, market and obligation.
- [How Conformity Assessment Works for Digital Product Passports](https://tieback.io/docs/knowledge-base/regulations/how-conformity-assessment-works-for-digital-product-passports.md): What conformity assessment is, where product requirements come from, how assessment procedures differ between self-assessment and third-party involvement, what notified bodies do, how technical documentation, declarations, standards, harmonised standards and presumption of conformity fit together, and how the resulting compliance environment relates to the information published through a Digital Product Passport.