Digital Product Passport Readiness for Small Businesses: What to Check First
A practical DPP readiness sequence for small product businesses using simple systems, supplier evidence and existing product data.
Navigate this page
Direct Answer
A small business does not need to recreate an enterprise compliance stack to start preparing for Digital Product Passports or better governed product data.
Start by separating five questions:
- Which rules actually apply to this product? Do not start from a universal DPP checklist.
- What product facts do you already control? Separate catalogue data from evidence and from facts held only by suppliers.
- At what level is each fact true? Model, variant, SKU, batch and item are not interchangeable.
- Who or which system is authoritative for each fact? The answer can be Shopify, a spreadsheet, a shared file, an internal record or a supplier. It does not have to be a PIM.
- What is missing, and what kind of access would close the gap? Some gaps can be solved internally, some need suppliers and some need specialist evidence.
That sequence is more useful than buying software against an unconfirmed field list.
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 therefore 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.
That is why 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.
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, the practical implication is simple: 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 actually 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. The goal is to know what exists, where it came from and whether the current value can be relied on.
3. Separate visibility from possession
Use the observability boundary:
| Class | What it means for the first pass |
|---|---|
PUBLICLY_OBSERVABLE | A value can be directly found in a public source. |
PUBLICLY_INFERABLE_WITH_CAVEAT | A public source supports a bounded inference, not a clean fact. |
INTERNAL_ACCESS_REQUIRED | Public inspection cannot establish the answer; company records are needed. |
SUPPLIER_ACCESS_REQUIRED | The business cannot establish the answer from its own current record; supplier-side information is needed. |
NOT_MEASURABLE_RELIABLY | The fact cannot be established reliably with the available method or evidence. |
The important rule is: NOT FOUND PUBLICLY ≠ BUSINESS DOES NOT HAVE IT.
Do not turn a website blank into a business-data gap.
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 genuinely 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
A useful first pass is deliberately modest:
- choose a small set of representative products
- list the facts you already publish or rely on
- record where each value comes from
- record the level at which it is true
- attach or reference the evidence where it exists
- classify missing facts by next access requirement
- 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.
Canonical Knowledge connections
This page applies existing canonical truth. 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 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.
Keep exploring
The question a small business usually reaches next.
- Evidence behind thisWhich facts can I verify myself?Which Product Facts Can a Small Business Verify Itself?Natural next diagnostic after inventory.
- CompareWhat do I do with the gaps?When Product Information Is Missing: Solve It Internally, Ask a Supplier or Use a Specialist?Turns readiness findings into action.
- Another angleWhere should the data live?How to Organise Product Data Without a PIM: A Small-Business Operating ModelMoves from assessment to operating model.
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.
Help someone else make sense of product passports.
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.