Should we start with the entire catalogue?

Start with a representative pilot and prove the evidence and review process. Expand after the team can explain the result and maintain it when the product changes.

Is a QR code already a compliant passport?

A code provides an access path. The relevant product rules, information, permissions and operating arrangements still need assessment; a working link alone cannot settle those questions.

What should the first project deliver?

A documented scope, an evidence-backed record, approved sharing decisions and a tested maintenance process. Keep unresolved legal or technical dependencies visible in the handover.

Digital Product Passport: A Practical Decision Guide

1. Establish the legal and product scope

A DPP connects product information with an accessible digital record. Under ESPR, product measures determine whether and how a passport is required; inclusion in the working plan alone does not establish an application deadline. Separate legislation can create its own obligations.

As an operational first step, write a short scope note: the product, intended market, your role, the legal source and the decision still missing. Keep a confirmed requirement separate from a planning assumption. Use the linked eligibility and battery guides where those distinctions affect your case.

Source: European Commission — Digital Product Passport FAQs

2. Define what one record represents

The applicable rules determine whether information belongs at model, batch or individual-item level. Your internal SKU structure is useful evidence, but it is not automatically the required passport structure. First distinguish changes in identity from changes in description.

For a pilot, choose a product with a meaningful variant: a different material, supplier or construction. Explain which documents cover both versions. The linked model, batch and item guide develops this decision; a serialised label alone does not prove that independent item data is maintained.

Source: Regulation (EU) 2024/1781 — Articles 9–11 Source: Passvanta — Data Carrier Studio

3. Build an evidence map

Make one row per information need, then record the source, product reference, owner and review state. This is a preparation method, not a universal legal checklist. Start with documents already held by engineering, quality or procurement instead of asking suppliers to recreate them.

In Passvanta, document extraction proposes values with source references. Check those proposals against the original and resolve conflicting values explicitly. A high completion indicator does not remove a publication blocker or establish that a preparation pack covers every applicable legal requirement.

Source: Passvanta — Documented product evidence and review workflow

4. Request only the supplier information still missing

Turn a gap into a specific question: identify the component, requested value, unit and acceptable evidence. Assign one person to resolve ambiguous answers. The supplier-data guide explains how to handle incomplete responses without silently converting assumptions into accepted product data.

Passvanta guest requests collect selected field values through limited links. Supporting documents require the signed-in, linked supplier portal with customer-enabled uploads. Customer review remains separate from the supplier submission; an answer cannot directly publish the customer's passport.

Source: Passvanta — Supplier Portal

Read the supplier data collection guide →

5. Test the information people will actually receive

Review public content, restricted content and the intended scan journey before approving release. In Passvanta, authorised publication records a revision; restricted fields are excluded from the public response. Check the actual output rather than assuming an internal document will be public or private because of its filename.

Carrier generation follows publication. Print a sample on the intended surface and check the destination and legibility. A successful software decode concerns the generated file. It does not certify the printed mark, its durability or suitability for your product.

Source: Passvanta — Passport publication and lifecycle Source: Passvanta — Data Carrier Studio

6. Give the pilot an owner after launch

Define what triggers a review: a changed component, revised evidence, corrected claim or new applicable rule. Test a revision and a suspension, and keep an export that another team can interpret. The preparation guide turns these checks into acceptance steps.

Keep publication and registry registration as separate decisions. Passvanta's registry adapter is preparation; official interface mapping, test access and acceptance remain outstanding. Use the registry guide for that boundary, and the software-comparison and cost guides to plan procurement without assuming every dependency is already available.

Source: Passvanta — Passport publication and lifecycle Source: Passvanta — EU Registry preparation and acceptance boundary

Plan a DPP pilot →Compare DPP software →Build an implementation budget →