Digital Product Passport Readiness for Small Businesses: What to Check First

Why this is different for a smaller business

The regulatory rule is not different because the business is small. The operating constraint often is.

A small team may have one person doing ecommerce, operations and supplier follow-up. Product identity may live in the ecommerce platform, composition in a spreadsheet, certificates in a shared drive and production details with a supplier. The problem is not simply whether a field exists. It is whether the business can identify the authoritative value, find the evidence behind it and keep the relationship current when the product changes.

So Product Evidence and SME Burden must stay separate. A fact may be well evidenced but awkward to retrieve. A fact may be easy to type into a catalogue but poorly evidenced. Those are different problems and need different fixes.

What SME support the ESPR requires, and what you still have to verify locally

The ESPR does not tell a small business to solve the transition alone.

Article 22 requires support for SMEs and micro-enterprises, but keep the support architecture in law separate from the specific service you can use today.

At EU level, the Commission is required to take initiatives that help SMEs integrate environmental sustainability into their value chain. Where appropriate, delegated acts establishing ecodesign requirements are to be accompanied by digital tools and guidelines covering the particular needs of SMEs and micro-enterprises.

Member States also have a job. Article 22 requires them to take appropriate measures to help SMEs comply. The Regulation names one-stop shops or similar mechanisms as examples and allows measures such as financial assistance, access to finance, specialist management and staff training, and organisational or technical assistance.

That doesn't mean there is already a single EU DPP helpdesk or a live Article 22 one-stop shop in every country.

The Commission's current Digital Product Passport FAQ describes SME support as being planned at EU and national level. It points to targeted guidelines and free digital tools where appropriate and to Member State support mechanisms. That makes Article 22 a route worth checking, not a reason to wait.

What is safe to rely on?

So the route is:

1. Do the readiness work you can already do. Product identity, source ownership, evidence location and missing-data triage do not depend on a future support service.
2. Check the applicable product rule. The timing and exact DPP requirement are still product-specific.
3. Check the Commission's current DPP resources when the requirement gets closer. Product-specific guidance and SME tools may be published alongside or after the relevant rule.
4. Check the relevant national authority or official business-support route. If a Member State has implemented an Article 22 mechanism, use the current official page rather than a vendor summary.
5. Record what you relied on and when. Support schemes, funding and contact routes can change faster than the underlying Regulation.

Don't treat a service provider and an Article 22 support mechanism as the same thing. A commercial DPP provider may help you implement the system. Article 22 is the public-support layer.

The small-business question remains: what is the next piece of evidence, product data or role information you need to control? Support can reduce the burden of getting there. It does not replace the underlying product requirement.

A five-pass readiness check

1. Start with the product and the regime

Use the category and regulatory Knowledge pages first. A Digital Product Passport is not one universal template. Product-specific law determines whether a passport applies, what information it contains and when obligations begin.

For a small business: do not spend time normalising fields that are based only on a generic DPP list. Establish the applicable product regime first.

2. Inventory what you already have

Look across the systems and files the business uses:

• ecommerce catalogue
• product or buying spreadsheets
• shared drives
• supplier specifications
• declarations and certificates
• test reports
• customs and origin records
• accounting or ERP records where present
• PIM or PLM where present.

The goal is not to move everything into one place immediately but to know what exists, where it came from and whether the current value can be relied on.

3. Separate visibility from possession

Don’t turn a website blank into a business-data gap: not found publicly does not mean the business does not have it, so check your own records before you log one. The five observability classes, from PUBLICLY_OBSERVABLE to NOT_MEASURABLE_RELIABLY, are set out in which product facts a small business can verify itself.

4. Separate the value from the evidence

For every important fact, ask two questions:

• What value are we currently using?
• What evidence supports that value?

A supplier specification can be an assertion source. A second document may corroborate it. Independent verification is a separate evidence role. Do not collapse those roles into one generic status called “verified”.

5. Route the gaps

Every gap should end in one of a small number of actions:

• search an existing internal source
• ask the supplier for the value or evidence
• check an authoritative external source
• obtain specialist classification or testing
• record the fact as unknown for now.

A gap with an owner and next access requirement is manageable. A blank with no classification is not.

What to do first this week

Keep the first pass modest:

1. choose a small set of representative products
2. list the facts you already publish or rely on
3. record where each value comes from
4. record the level at which it is true
5. attach or reference the evidence where it exists
6. classify missing facts by next access requirement
7. identify the few decisions that are difficult to reverse, such as printed identifiers or carrier ownership.

Do not turn this into a full-system migration. The purpose is to reveal the shape of the problem before you automate it.

Start by finding out what is missing before you start buying anything. It runs in your browser and nothing is uploaded.

Once you have identified your starting records, see how existing textile data becomes a governed passport. Use the worked example to distinguish supported information from genuine gaps before collecting more data.

Canonical Knowledge connections

Go deeper when the question changes:

• What does the law actually require? → Digital Product Passport Requirements by Product Category
• What already applies to my business today? → What Already Applies to a Clothing Brand Today
• What product data do I already have? → The Product Data You Already Have
• Which system should own the fact? → Which System Should Own Each Product Fact?
• Does the fact belong to the model, variant or SKU? → Which Product Facts Belong at Model, Variant and SKU Level?
• What counts as evidence? → How We Know, and What a Blank Means
• What should I do when the product changes? → Overwrite, Version or New Product?
• How to Prepare for a Digital Product Passport

What the Registry removes, and what is still yours

What does the EU Registry remove, and what is still mine to operate? → The EU DPP Registry is live. What does your business still need to do?

What not to assume

Do not assume:

• every product needs the same DPP fields
• a field visible on a website is the company’s system of record
• a field missing from a website is missing internally
• a supplier statement is automatically independent proof
• every fact belongs at SKU level
• a PIM is a prerequisite for governed product information
• one software system must own every fact.

Sources & legal basis

• ActivateDigital Product Evidence + SME Original Research Programme v1.1, especially the Product Evidence method, SME method, observability model and evidence-role codebook.
• ActivateDigital Knowledge: Digital Product Passport Requirements by Product Category.
• ActivateDigital Knowledge: What to Do Now, and What to Refuse to Do Now.
• ActivateDigital Knowledge: Which System Should Own Each Product Fact?

Last verified: 2 September 2026. This page is practical guidance, not personalised legal advice.