Digital Product Passport: A Practical Guide for Brands

The central EU registry has been live since 20 July 2026 (European Commission). The legal framework exists. The operational work does not map to any single department.

Five drivers explain most of the delay:

• Supplier data that has never been requested. Material composition, origin and substances of concern sit in suppliers’ systems, if anywhere.
• No single owner. Legal tracks the rules, sustainability chases data, IT hosts, operations applies carriers. Each assumes another holds the file.
• Product-group timing. The Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781) is a framework. Obligations arrive through delegated acts, group by group. Textiles and apparel are indicatively expected in 2027, enforceable around 2028 to 2029, since application starts at least 18 months after each act.
• Irreversible physical choices. The identifier and the carrier end up on every unit shipped. Changing them later means touching products already in the market.
• Parallel needs. Brands exposed to fakes and grey market diversion need item identity anyway. Counterfeit trade reached USD 467 billion in 2021, up to 2.3% of global trade (OECD/EUIPO, Mapping Global Trade in Fakes 2025). Clothing, footwear and leather goods made up 62% of seized counterfeits (OECD/EUIPO, 2025).

A Digital Product Passport (DPP) is a structured set of product information, accessible through a data carrier on the product and linked to a unique identifier. ESPR defines access rights for the public, authorities and other parties. The delegated act for each product group sets the actual data points, the identifier granularity and the timeline.

The passport is not a PDF attached to a product page. It is a record that must stay reachable for the life of the product, and it can be corrected, versioned and queried by role.

The distinction that matters: a supplier certificate stored in a compliance folder is documentation. A passport is that same fact, bound to one identifier, readable by the person holding the product.

Four decisions drive every project: granularity, data carrier, data content and hosting. The sequence below works without waiting for the final delegated act of your product group.

1. Map your range to product groups. Identify which products fall in early priority groups, such as textiles, and which do not. Food and beverages are outside ESPR scope, so wine and spirits themselves are not expected to need an ESPR passport. Check by product group, not by sector. Products with integrated batteries follow the separate battery passport from 18 February 2027.
2. Start supplier data collection. Request material composition, origin and substances of concern. This is the slowest stream and the least dependent on final text.
3. Set identity standards. Use GS1 Digital Link with a GTIN plus serial, resolving through a domain the brand owns. Identifiers on products outlive vendor contracts.
4. Choose granularity. Model, batch or item. Delegated acts set a minimum. Nothing prevents going finer.
5. Pilot the carrier on one production line. Test application, durability and read experience before scaling.
6. Build the passport as a view of item records. Public, restricted and owner views come from the same identifier, with role-based access.
7. Map new required fields as acts are adopted. The structure is already live, so each act becomes a content exercise.

Steps 2 to 5 can run in parallel. Item-level identity also allows precise corrections. If a batch certificate is withdrawn, the brand can find the affected units and see where they are. For how serial identities work at volume, Serialization Explained covers the mechanics.

The ESPR is carrier-neutral. In practice, a GS1 Digital Link QR code is emerging as the default visible carrier, and NFC serves as the trust layer. The working rule is NFC for trust, visible carrier for compliance. The two are not equals on every axis.

Sources: industry sources and public converter catalogues, 2026.

Chip class matters. NTAG 424 DNA (ISO/IEC 14443-A, NFC Forum Type 4, AES-128) uses Secure Unique NFC (SUN) messaging. Each tap produces a new signed code that the backend verifies. A copied URL fails.

An analogy helps. A printed QR code is a name on a door. A cryptographic NFC tag is a door that issues a one-time code on each approach, and only the genuine tag can produce a valid one.

Two practical constraints apply. Standard tags detune on metal, so metal products need ferrite-backed on-metal tags, typically 7% to 30% more per unit. The TagTamper variant adds first-open evidence for sealed products and closures. ISO 15693 chips such as ICODE DNA suit vicinity-class supply chain scanning. They are not the phone-tap authentication standard. A deeper comparison sits in NFC vs QR vs RFID vs digital watermarks.

QR wins in several cases, and a credible plan says so.

• Low unit value and high volume. A printed QR adds almost no marginal print cost. A standard non-secure NFC tag (NTAG213 class) lists around €0.19 to 0.23 at 1,000 to 10,000 units (public catalogues, 2026), and a secure one costs more.
• No secondary market and no counterfeit exposure. If nobody has an incentive to clone the passport, authentication adds cost without return.
• Cost-constrained lines. Applying a chip needs a line step. Printing does not.
• Model-level passports. If the delegated act only asks for model or batch data, one code per model on the product is enough.

The cost to watch in QR is not the print. It is serialisation and the platform behind it.

The trade-off reverses for premium goods. A fake with a genuine-looking passport is more credible than a fake without one. A copyable carrier on high-value goods gives counterfeiters a free certificate.

The flow runs from the line to the owner.

1. Encode. On the production line, each NTAG 424 DNA tag is commissioned with a unique identity and keys, linked to the product record by GTIN and serial.
2. Apply. The tag goes inside the product or packaging, on or in the item. Placement follows one rule: the carrier must stay with the product, not with a carton recycled on day one.
3. Tap. A phone reads the tag. iPhone XS/XR and later read in the background. Android reads natively with the screen on.
4. Verify. The tag returns a freshly signed code. The backend checks it and confirms the item is genuine, or flags a replayed or cloned read.
5. Resolve. The identifier resolves through the brand’s domain to the passport, with public, restricted and owner views.
6. Update. Corrections, repair events and ownership changes are written to the record, versioned so the brand can show what a passport said on a past date.

What the consumer sees on tapping a leather tote: “Genuine item. Leather from batch 24-117, tanned in Tuscany. Care and repair guidance below.” The brand’s team sees the same tap as a scan event with time and location.

Three models exist.

Hybrid is increasingly common among premium brands. The brand keeps control of the identifiers and can switch providers without breaking products already sold. A good test for any vendor: what happens to the identifiers already in market if the contract ends. A platform such as Selinko’s platform can serve public, restricted and owner views from one identifier on a brand-controlled domain.

Sequence by regulatory timing and business value. Lead with the category that has an early obligation and build identity and passport together. For categories with high counterfeiting or resale risk but no near-term obligation, build identity for protection now, on the same standards. For low-risk categories, prepare the data model and wait. Brands in luxury should read how the passport affects luxury supply chains before setting priorities.

Most delays come from unnamed owners.

A small steering group with one accountable owner, often in operations or sustainability, works best. Its first job is to agree the four decisions, because every workstream depends on them.

Budget follows the same logic. Software is usually the smaller line. Data collection, carrier application on the line and ongoing corrections cost more. Where identity is shared with authentication and traceability, the cost is shared too. That is the largest saving available, and only if the decision precedes the carrier purchase.

• Waiting for the final act to start supplier data. It is the slowest stream.
• Putting the carrier on disposable packaging. The passport fails at the “accessed” stage.
• Letting a vendor own the resolver domain. It fails at “updated” when the contract ends.
• Building a passport-only system. It duplicates identity work needed for authentication and traceability.
• Choosing the carrier on unit cost alone. Carrier and granularity are fixed once products ship.

Brands that build identity for commercial reasons get compliance as a by-product. Brands that build for compliance alone pay again for everything else.