How We Know: Sources, Status and Evidence for Digital Product Passport Requirements

ActivateDigital separates what the law requires, what has been adopted but applies later, what regulators are developing, what is required under other law and what current evidence does not yet establish. That separation is necessary because DPP information changes at different speeds and because a Commission study, a Working Plan, an adopted Regulation and a vendor checklist do not have the same legal weight. This page explains the regulatory evidence method used for the Digital Product Passport Observatory. It is deliberately separate from product evidence: how a business proves that a particular product contains 80% cotton, has a given test result or was made at a particular facility. For product evidence, use Passport Evidence: How We Know, and What a Blank Means. For the broad regulatory landscape, use Digital Product Passport Requirements by Product Category.

Regulatory evidence versus product evidence

The word evidence applies to both, but they are not the same workflow.

The source hierarchy

For material regulatory claims, ActivateDigital uses the strongest available source in this order.

1. Enacted EU legislation / Official Journal / EUR-Lex

This is the primary basis for claims such as:

• a passport is legally required
• a law applies from a fixed date
• a mandatory field appears in an Annex
• access or granularity is specified in adopted law.

Where the exact Article or Annex is known, the legal provision is preferred over a generic landing page.

2. Adopted delegated or implementing acts

These can add the product-specific or technical rules that a parent Regulation leaves to the Commission.

An adopted implementing act is different from a roadmap saying an act is planned.

3. European Commission implementation material

Official Commission pages, Registry material and implementation guidance are used to explain:

• current operational status
• implementation timelines
• Registry availability
• guidance on how adopted provisions are being prepared or applied.

Where Commission shorthand conflicts with the exact legal scope, the legislation remains the controlling source for the legal claim.

4. Official institutional guidance and Working Plans

A Working Plan can establish that a product group is prioritised and indicate expected timing.

It does not make every proposed field mandatory and does not turn an adoption target into a compliance date.

5. Official studies and consultations

These are valuable for understanding direction.

The May 2026 textile DPP study, for example, explores production sites, origin, circularity and other information territories. It is strong evidence of official development. It is not the final textile delegated act.²

6. Official standards bodies / harmonised-standard decisions

Standards claims are checked against the relevant standards decision and standards bodies.

A standard can be important or harmonised without making a vendor-specific implementation technology universally mandatory.

7. Credible secondary sources

Used only where needed for explanation or discovery.

They do not override primary law for a mandatory legal claim.

Why vendor blogs are not regulatory authority

Vendor content can be useful for:

• finding terminology
• seeing implementation patterns
• identifying common market questions
• discovering a primary source to verify.

It is not sufficient authority for claims such as:

• “every DPP must use GTIN”
• “textile factory data is already mandatory”
• “all DPPs are item-level”
• “Q4 2027 is the textile compliance deadline”.

Those propositions have to survive a primary-source check.

The public status taxonomy

The Observatory uses controlled public states.

Required now

The relevant legal requirement currently applies.

Adopted, applies later

The requirement is in adopted law, but its application date has not arrived.

Example: the Battery Passport is adopted and applies from 18 February 2027 for covered battery categories.³

Proposed / draft

An official legislative or regulatory draft exists but is not final law.

In official development

There is a Commission plan, official study, preparatory process or other strong institutional development signal, but the final requirement is not settled.

Example: textile DPP product-specific rules at the 1 September 2026 verification point.⁴

Required under other law

The information is already legally required under a different regulatory regime, but is not established as DPP content in the context being discussed.

Example: textile fibre composition under Regulation (EU) No 1007/2011 while final textile DPP treatment remains future.⁵

Not established

Current evidence does not establish the proposition.

Not established does not mean No.

It means the evidence has not reached the threshold needed to state the proposition as law or official development with greater certainty.

Not applicable

The regime or field does not meaningfully apply in the context.

Example: food is expressly outside ESPR product scope.¹

Evidence and claim states

Two additional labels are useful for claims that sit below a formal regulatory status.

Evidence suggests, not established

There is meaningful evidence pointing in a direction, but not enough to call the proposition a settled requirement.

Industry claim, not verified

The proposition appears in market or vendor content but has not been verified against sufficient primary/official evidence.

These labels stop a plausible statement from quietly becoming “law” through repetition.

Qualifiers are separate from status

A claim can be legally adopted and still need a qualifier.

The controlled qualifiers include:

• conditional
• optional
• mixed
• restricted
• implementation pending
• indicative date.

For example:

• Battery Passport: Adopted, applies later; some data/access detail is implementation pending.
• Q4 2027 textile delegated act: In official development + indicative date.
• Battery legitimate-interest information: adopted architecture + restricted access.

Status and qualifier answer different questions.

What counts as law?

A Regulation, Directive, Decision or formally adopted delegated/implementing act has legal status according to the EU legal framework and its own provisions.

A Commission web page can explain that law. A study can support future policy. A Working Plan can set priorities.

Neither becomes enacted law merely because it is official.

This is why every material claim is expressed in a way that matches its evidence class:

• “Regulation X requires…” for adopted law
• “The law is adopted and applies from…” for future application
• “The Commission currently plans…” for an official plan
• “Official preparatory work considers…” for studies
• “Current evidence does not establish…” for unresolved propositions.

Is a Commission study a requirement?

No.

A Commission/JRC study can be high-quality official evidence and still not be binding law.

For textiles, the May 2026 study is precisely the kind of evidence worth using for WATCH decisions. It should not be transformed into a final mandatory field list.²

Is a Working Plan date a deadline?

No.

The ESPR Working Plan indicates regulatory priorities and expected timing for product measures.⁶

A planned delegated-act date is a date for a future regulatory decision. A compliance date needs an adopted legal basis and the applicable transition/application provisions.

That is why the Observatory timeline labels every material date by type.

See Digital Product Passport Timeline: What Applies When?.

What is adjacent law?

Adjacent law is existing regulation that requires useful product information but is not itself proof that the same information is DPP content.

Examples include:

• textile fibre-composition law
• tyre-label/product-database rules
• food information and traceability
• cosmetics PIF/notification requirements
• GPSR product identity
• REACH substance obligations.

Adjacent law matters because businesses can often structure the data now. The Observatory labels it Required under other law rather than upgrading it to DPP status.

How conflicts are handled

Sources can disagree or appear to point to different dates.

The method is:

1. preserve both propositions
2. compare legal authority
3. compare publication/currentness
4. identify whether the difference is a true contradiction, a scope difference or an implementation delay
5. state the current best interpretation
6. keep the conflict visible where it remains consequential.

Example: Battery access rights

Battery Regulation Article 77(9) set 18 August 2026 as the date by which the Commission should adopt the detailed legitimate-interest implementing act.³

The Commission's current DPP roadmap instead shows Q4 2026.⁷

The Observatory does not silently replace the statutory date with the roadmap date. It records that the statutory deadline has passed and that the Commission currently signals Q4 2026 delivery.

What does “Last verified” mean?

It means the material, time-sensitive claims on the page were genuinely checked against the relevant current primary or official sources on that date.

It is not a decorative publication date.

A page should be reverified when a trigger occurs, for example:

• a delegated or implementing act is adopted
• a fixed application date arrives or changes
• the Commission changes its implementation roadmap
• a new standards decision is published
• Registry guidance changes
• a product-specific field, access or granularity rule becomes final.

How often is the information updated?

Update cadence follows the nature of the resource.

Event-driven

Timeline, category status, access, granularity and factory/origin references should be reviewed when a material regulatory event occurs.

Living

Identifiers and readiness need review when standards, product-specific rules or important implementation guidance changes.

Periodic

The methodology itself changes less frequently, but should be reviewed when source hierarchy, public status language or governance policy changes.

A monthly rewrite is not a substitute for event-driven evidence review.

What happens when a source changes?

The system should record:

• prior public position
• new evidence
• source and date
• affected claims/resources
• whether the change is material
• whether P0 or frozen research requires a controlled update.

If the new source only clarifies an implementation detail without changing the shared claim, it can be logged without rewriting the core truth.

If it overturns a frozen shared fact, it needs an explicit evidence-update record rather than silent divergence.

The public/private method boundary

ActivateDigital should be transparent about:

• source hierarchy
• legal status language
• how uncertainty is handled
• why a source is considered stronger
• last-verified dates
• material change history.

It does not need to expose proprietary internal extraction, scoring, reconciliation or research-orchestration machinery.

Public trust comes from reproducible claims and visible primary sources, not from publishing every internal workflow detail.

Direct answers

What sources does ActivateDigital use?

Primary EU legislation first, then adopted delegated/implementing acts, Commission implementation material, official guidance/Working Plans, official studies and standards sources.

What does “Not established” mean?

Current evidence does not establish the proposition. It is not a definitive No.

Why not use vendor blogs as authority?

They can be helpful secondary material, but they are not sufficient proof of a mandatory legal requirement.

What does “Last verified” mean?

The material time-sensitive regulatory claims were actually checked against current primary/official evidence on that date.

What happens when sources conflict?

The conflict is preserved, authority and timing are compared and the current best interpretation is stated without hiding unresolved tension.

Primary sources and governance anchors

• Regulation (EU) 2024/1781 (ESPR)

  View official source

• JRC/Product Bureau, Study in support of the Digital Product Passport for textiles

  View official source

• Regulation (EU) 2023/1542 concerning batteries and waste batteries

  View official source

• European Commission, Textile apparel and the Digital Product Passport

  View official source

• Regulation (EU) No 1007/2011 on textile fibre names and labelling

  View official source

• ESPR and Energy Labelling Working Plan 2025–2030, COM(2025) 187 final

  View official source

• European Commission, Digital Product Passport implementation timeline: This methodology explains how regulatory claims are classified and sourced. It is not a substitute for product-specific legal advice.

  View official source

This methodology explains how regulatory claims are classified and sourced. It is not a substitute for product-specific legal advice.