Where Do I Start With a Digital Product Passport?
Scope first. Then identity, then data, then evidence. The passport is what those four produce. Seven routes through Knowledge, and the one that matches the question you actually have.
Jump around this page
In 60 seconds
Start with scope, not with the passport. Work out whether a product rule applies to your product and when it bites, then fix product identity, then the product data, then the evidence behind it. The passport is what those four produce, not the thing you build first.
- Six routes run through Knowledge. Five follow that order one stage at a time and the sixth compresses it for a small team.
- Labelling, substance declarations, market-access duties and product-safety rules are in force now and are separate from the passport timeline.
- The rules do not change with company size. The route through them does.
- Eleven product categories have their own hub.
- Do not buy a passport platform before you know which rule applies to the product.
Almost every business that arrives here starts in the wrong place, because the passport is the part with a name. The order above is the one that stops work being redone: a passport built before identity is settled has to be rebuilt when identity changes, and a passport built before the evidence exists is a published claim nobody can stand behind.
There are seven routes through this Knowledge base. Five follow that order, one stage at a time. One compresses it for a small team. The battery route follows the evidence through a practical test.
Start with the question you have right now
Does any of this apply to my product?
Scope is decided by the product rule, not by the passport. Some categories have dated obligations, some have delegated acts still in drafting and some have nothing beyond the rules that already applied.
Does my product category need a passport
What already applies, today, before any passport?
Labelling, substance declarations, market-access duties and product-safety rules are in force now and are separate from the passport timeline. That is usually the more urgent list.
When does my category actually start?
Dates differ by instrument and by category, and several of them are still conditional on a delegated act.
Every dated EU product obligation
I know it applies. What do I do this quarter?
Some preparation pays back whatever the final rule says. Some of it cannot sensibly be done yet, and doing it early is how businesses end up paying twice.
My supplier has not given me the data
That is a normal state, not a failure. What matters is which facts you can establish yourself, which have to come from someone else and what you are allowed to publish when nobody answers.
What a supplier can and cannot be asked for
I run a small business and none of this is written for me
Six resources are, and they run end to end. The rules do not change with company size. The route through them does.
Find it by product category
Eleven product categories have their own hub: what applies, what is still unknown, the dates that are stated and the guidance underneath.
Category scope is the first question on every route above, so if you already know your category, the hub is a faster entrance than any of them.
Find it by subject
Five subjects hold the whole library. Each one has a flagship resource and a full catalogue behind it.
- Digital Product Passports: what a passport contains, category by category
- Regulation and market access: what has to be true before a product can be sold
- Product data and architecture: where a fact belongs, and which system owns it
- Evidence and trust: how you know a fact is true, and what a blank means
- Product identity: what the product is, and what a stable identity unlocks
Or open a section: all regulation pages, all product data pages, all implementation guides and what is established and what is moving.
What to refuse to do yet
- Do not buy a passport platform before you know which rule applies to the product.
- Do not allocate new identifiers across a catalogue to satisfy a requirement that has not been written.
- Do not publish a value you cannot evidence in order to avoid an empty field. A stated blank is a governed answer; a guess is not.
- Do not treat a passport as a second product master. It is a projection of data the business already governs, plus whatever the product rule adds.
Keep exploring
The questions this page usually raises next.
- Another angleNext questionDigital Product Passport Timeline: What Applies When?Adopted, in force, applying or only planned: every Digital Product Passport date by category, and which of those four kinds of date…
- Another angleNext questionHow to Build a Textile Digital Product Passport From Just a Handful of InputsActivateDigital builds the passport. You confirm the few facts only you can know.
- Another angleNext questionFrom Question to Published Passport: The Five Steps, and Who Does Each OneThe five steps between deciding you need a product passport and having one that works: identifier, carrier, resolver, access and…
- CompareNext questionKnowledge Terminology GlossaryEvery term used across ActivateDigital Knowledge, defined once and linked to the canonical page that owns it.
Sources and evidence boundary
-
EU law
This page is a route map, not a legal position. Every dated obligation, scope test and requirement named here is stated and sourced on the resource that owns it, and nothing on this page asserts that a passport requirement exists for a category before the product-specific rule says so.
Does this reach your products?
Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.