EU Regulation

Does Your Company Need a Digital Product Passport? A 5-Question Check

Not every product is in scope yet, and not every company that is in scope is actually ready. Five questions, five honest branches.

Tylko Academy·19 October 2026·6 min read

Whether your company needs a Digital Product Passport (DPP) isn't a single yes-or-no fact, it depends on where your product is sold, what technical specifications already apply to it, and how prepared your own organization is internally. This is a practical self-assessment, not a legal determination, walk through five questions below and see where you actually land.

Quick answer: if you sell into the EU and your product already requires a Declaration of Performance under CPR, the GWP declaration is already phasing in from 8 January 2026 regardless of whether a full DPP delegated act has named your category yet. The rest of this check is about whether your organization is actually ready to act on that, not just whether the law technically applies.
Question 1

Do you sell, distribute, or import this product into the EU market?

If yes

DPP and CPR obligations are triggered by the EU market, not by where your company is headquartered. Continue to Question 2.

If no

These specific obligations generally don't reach you yet. If that changes, or if you supply a company that does sell into the EU, revisit this check then.

Question 2

Does your product already require a Declaration of Performance under a harmonized technical specification (hEN or EAD) under CPR?

If yes

The GWP declaration requirement already applies to you in phased form, GWP only from 2026, an expanded indicator set from 2030, a full life-cycle assessment by 2032. Continue to Question 3.

If no

A confirmed DPP obligation for your category hasn't landed yet, no official source has set a fixed construction-specific delegated act date, the Commission's own roadmap treats Q2 2027 as indicative only. Still continue, but treat the rest as preparation rather than an active deadline.

Question 3

Do you already have an EPD (Environmental Product Declaration) for this product?

If yes

You have a head start on the underlying life-cycle data. Remember it's a separate, voluntary document though, not a substitute for the GWP declaration or the DPP itself, see our EPD vs DPP comparison. Continue to Question 4.

If no

You'll need to either commission one or build equivalent life-cycle data directly for your DPP and DoPC fields. Continue to Question 4.

Question 4

Do you already know, inside your company, which department or role holds and maintains this product's compliance data?

If yes

Good, that puts you ahead of most manufacturers, since neither ESPR nor CPR specifies this internally, see our piece on who owns product data. Continue to Question 5.

If no

Worth fixing before any deadline arrives. "Economic operator" is a legal role under ESPR, not an org-chart title, and no regulation assigns it for you internally. Continue to Question 5.

Question 5

Is there a named person or team accountable for this specific product's DPP and CPR compliance, with real time allocated to it?

If yes

You're ahead of where most companies in this position actually are.

If no

This, not the regulation's complexity, is usually the real blocker.

Most companies aren't blocked by the regulation being unclear. They're blocked by nobody owning the question internally.

Your simple result

Count how many questions you answered "yes" to, and be honest about it.

Where you land

4-5 "yes" answers

You're in a genuinely strong position, in scope or close to it, with internal ownership already in place. The work left is mostly execution, not discovery.

2-3 "yes" answers

You're not behind, but there are real gaps, usually around data ownership or who's actually accountable, worth closing before the pressure builds rather than after.

0-1 "yes" answers

Either this genuinely doesn't apply to you yet, Question 1 or 2 answered "no", or it does and almost nothing is in place internally. Those are very different situations, and it's worth being clear with yourself about which one you're actually in.

DPP

If your honest answer landed in the "not ready" range, that's exactly the gap we help close. A real readiness review for your specific products, not a generic checklist.

Check your readiness with us →

Frequently asked questions

Does a Digital Product Passport requirement depend on where my company is based?

No. It depends on whether the product is placed on the EU market, sold, imported, or distributed there, not on where the manufacturer is headquartered.

If my product isn't yet named in a delegated act, am I safe to ignore the Digital Product Passport for now?

Not entirely. If your product already requires a Declaration of Performance under CPR, the GWP declaration inside it is already phasing in from 8 January 2026, separately from whether a full DPP delegated act has named your category yet.

Does having an EPD mean I can skip the readiness check?

No. An EPD gives you a head start on life-cycle data, but it's a separate, voluntary document from the DPP and the CPR's mandatory GWP declaration, so it answers only one of the five questions, not all of them.

Is this 5-question check a legal determination of whether I need a DPP?

No. It's a practical self-assessment tool to show where a company stands today. A binding determination for a specific product and market should come from compliance counsel or a regulatory specialist.

If you answered this honestly, which number surprised you more, how many questions were "yes," or how many were "no"?
Digital Product Passport CPR Compliance EU Regulation

Learn DPP Properly,
Not Just the Headlines

Why it's worth it:

  • The full regulatory picture, not just the deadline. ESPR and CPR explained together, with the real timeline.
  • What's actually inside a DPP. Real data fields and how governance works once it's a system of record.
  • Where this is going next. A bonus module on AI in DPP.
  • A certificate on completion, plus team licenses for whole organizations.
Write your awesome label here.