Back

Digital Product Passport

What Should Brands Ask a DPP Technology Provider?

Thomas


03 Nov 2026

abstract map gif

A procurement team sits through three DPP demos in one week. Each phone scan opens a page with materials, origin and care. Nobody asks what happens when supplier data never arrives, or when the contract ends and the codes are already printed on a million products. Brands should question providers on six areas: standards, carriers, data, security, exit and delivery. The passport page is the visible 10% of the programme.

Why are DPP demos so hard to compare?

The market filled fast. Regulation (EU) 2024/1781, the ESPR, created the legal basis. The central EU registry has been live since 20 July 2026 (European Commission). Product data, traceability, labelling and brand protection vendors have since added a passport offer.

Their demos converge. The differences sit in what a demo hides:

  • Supplier data: whether the provider can collect it, validate it and tie it to batches.
  • Production lines: whether identifiers can be encoded and commissioned at line speed, not tagged by hand in a pilot.
  • Identifier ownership: whether the codes on your products still resolve if you change provider.
  • Authenticity: whether the same investment can also resist counterfeiting. Counterfeit trade reached USD 467 billion in 2021, up to 2.3% of global trade (OECD/EUIPO, Mapping Global Trade in Fakes, 2025).
  • Cost over time: what pricing scales with in year three.

A good evaluation tests each of these before signature, not after.

What is a DPP technology provider?

A DPP technology provider supplies the software, identifiers and data connections that attach a Digital Product Passport to a physical product. The passport is a structured record, reachable through a data carrier on the item, that exposes product information to the right audience.

Three layers matter:

  • Identity: a unique identifier per product, typically GS1 Digital Link built on GTIN plus serial.
  • Carrier: the physical medium that holds it, such as a QR code, an NFC tag or a copy-resistant print.
  • Record: the data platform that serves public, restricted and owner views from that one identifier.

A provider strong on the record and weak on identity leaves the brand with a good page on a fragile foundation.

What should brands ask about compliance and standards?

Start with the regulation. It is the reason for the project and the easiest area to verify.

Ask A good answer
How do you track delegated acts for our product groups? A defined process for mapping new required fields onto your data model, with examples
Which identifier standards do you use? GS1 identifiers and GS1 Digital Link, on a domain you control
How do you handle registration with the EU registry? A defined process for registering identifiers as required for your product group
How are public, restricted and other access rights modelled? Role-based views from one identifier, with audit logs
Can you show what a passport said on a past date? Versioning of every change, retrievable by date

Timing helps frame the answers. The first delegated acts target textiles and apparel, indicatively in 2027. Application starts at least 18 months after each act, so enforcement lands around 2028 to 2029. Batteries follow their own passport rule from 18 February 2027.

The ESPR is carrier-neutral. In practice, a GS1 Digital Link QR is emerging as the default visible carrier. A sound answer reflects that: NFC for trust, visible carrier for compliance.

Which data carriers should a provider support?

The carrier is the most permanent decision in the project. It is also the one providers most often treat as a detail.

Ask A good answer
Which carriers do you support? Several: GS1 Digital Link QR, NFC, copy-resistant print
Can you issue passports at item level? Yes, with serialisation and line commissioning
Can one item carry more than one carrier? Yes, all resolving to the same identity and record
Can the same carrier prove the item is genuine? Yes, with a cryptographic chip or copy-resistant print, verified server-side
How do you handle metal, small formats and sealed goods? On-metal tags, flexible inlays, tamper-evident variants

Physical constraints decide more projects than software does. Standard tags detune on metal. On-metal tags with a ferrite layer solve it, at a premium of 7 to 30% in published catalogue prices (2026). Closures call for tamper-evident variants such as the TagTamper version of NTAG 424 DNA.

Phone compatibility is rarely a problem. iPhone XS, XR and later read NFC tags in the background without an app. Android reads natively with the screen on.

NFC vs serialised QR: how do they compare for DPP?

A passport on a copyable code gives counterfeits genuine product data. That is the practical gap between the two carriers.

Criterion Serialised QR (GS1 Digital Link) NFC (NTAG 424 DNA class)
Regulatory role Emerging default visible carrier Trust layer, not a regulatory equal
Copy resistance Low: a photo reproduces it High: new signed code per tap
Read method Camera Tap, background read on iPhone XS and later
Marginal unit cost About zero print cost; the real cost is serialisation and platform (industry sources, 2026) USD 0.45 to 0.65 per label at five-figure volumes; on-metal +7 to 30%; 50k+ quote-only (public catalogues, 2026)
Standards GS1 Digital Link, GTIN + serial ISO/IEC 14443-A, NFC Forum Type 4, AES-128, SUN messaging

The cost line carries a caveat. Standard non-secure NFC tags (NTAG213 class) list around €0.19 to 0.23 at 1 to 10k units, but they can be cloned. They suit engagement, not authentication.

The distinction that matters: a QR code states an identity. A cryptographic NFC chip proves one. A passport can run on either, but only one of them can be checked against a counterfeit.

Cryptographic NFC works through challenge and response. The chip generates a fresh SUN-signed message on every tap. The server verifies it with a key the phone never sees. A photographed or copied URL fails on the second read. For a deeper comparison of carrier families, NFC vs QR vs RFID vs digital watermarks covers the trade-offs.

When is a QR-only DPP the right choice?

Sometimes it is. A sober evaluation concedes it.

QR wins when:

  • Unit value is low and a chip would exceed a meaningful share of margin.
  • Volumes are very high and the line is cost-constrained.
  • No secondary market exists, so diversion and resale fraud are not live risks.
  • Counterfeiting is not a credible threat for the category.

In those cases, a serialised GS1 Digital Link QR on a brand-owned domain meets the visible-carrier need. The questions about data, domain and exit still apply in full. Only the authentication questions become optional.

The risk is lock-in by omission. Choose QR-only and a later need for authenticity may force a second provider. Ask whether the platform can add a carrier to the same identity without reissuing identifiers.

How does a provider deliver a DPP, step by step?

A credible provider can walk through the process end to end:

  1. Scope the product groups. Map delegated acts and required data fields to each range.
  2. Define the identifier. GTIN plus serial, expressed as a GS1 Digital Link on the brand’s own domain.
  3. Choose the carrier. Match QR, NFC or both to product material, format and risk.
  4. Connect source systems and suppliers. Link ERP, PIM and PLM data, and collect supplier fields through templates and validation. Connecting existing ERP, PIM and PLM data to product identities is where most projects succeed or stall.
  5. Encode and commission on the line. Keys are written under controlled encoding, one per chip, and each serial is bound to its product.
  6. Register and publish. Identifiers are registered as required, and the resolver serves role-based views.
  7. Monitor and version. Every change is logged and retrievable by date.

Ask which of these steps the provider performs, and which it expects the brand to perform. Supplier onboarding, co-packer feeds and ERP mapping are often assumed to be the brand’s job. That is acceptable if explicit and budgeted. It is expensive if discovered after signature.

What security questions matter for a DPP?

The regulation does not demand authentication. The questions matter the moment the same identity does anything else: proves an item is genuine, transfers ownership or accepts events from partners.

Ask A good answer
Where is authentication verified? On the server, never in an app on the phone
How are keys generated, written and stored? Controlled encoding, one key per chip, secure storage, never sent to co-packers as files
How is personal data separated from product data? Owner and consumer data held separately, with consent and retention rules
Who can write events to the record? Authenticated partners and readers only

An analogy helps. A basic NFC tag is a door with the key hanging next to it. A secure tag is a door that issues a one-time code on each approach, and only someone already inside can produce the right one. Ask providers which door they are selling, and to name the chip.

Beware ‘secure’ or ‘unclonable’ with no chip or feature named. Authentication also extends further than a single tap. Product authentication technology shows how verification fits into the wider identity.

What should brands ask about domain, hosting and exit?

Identifiers on your products will outlive any contract. These questions decide how dependent you become.

Ask A good answer
Whose domain will our identifiers use? Yours, with the provider operating the resolver if you wish
What happens to products in market if we leave? Identifiers keep working; data and resolution transfer
What availability do you commit to? A stated uptime and fallback behaviour
Where is data hosted? Stated regions, compatible with your data residency needs
Can we export everything, in a standard format? Yes, every item and event, at any time

Printed codes cannot be recalled. A domain that belongs to the provider turns a software contract into a permanent dependency.

How should brands compare DPP pricing?

Compare total cost for your volumes over three years, not headline rates.

  • What does pricing scale with? Units, scans, modules and markets behave very differently by year three.
  • Is there per-scan pricing? It penalises the engagement that makes the passport useful.
  • What is included? Carriers, encoding, integration and supplier onboarding. Software is usually the smaller part of the budget.
  • What does year three look like? Ask for comparable totals, not unit prices.

For the carrier line, a published breakdown of NFC product authentication costs gives a realistic baseline to test quotes against.

How do DPP requirements differ by product category?

Priorities shift with the product.

  • Textiles, apparel and leather goods: the first delegated acts target textiles, indicatively 2027. Clothing, footwear and leather goods account for 62% of seized counterfeits (OECD/EUIPO, 2025), so authentication belongs in the brief from day one.
  • Batteries: a separate passport regime applies from 18 February 2027. Do not assume a generic provider covers it.
  • Watches and metal goods: on-metal tags with a ferrite layer are the baseline question.
  • Wine and spirits: closures need tamper-evident chips, and grey market diversion is a core risk.
  • Cosmetics and fragrance: small formats and curved packaging test inlay flexibility.
  • Cigars and furniture: humidity, wood and large sites test read reliability and encoding logistics.

Ask each provider for a reference in your category, not an adjacent one.

How should brands score provider answers?

Use a three-level scale for every provider.

Score Meaning Example
Proven Shown in a live deployment at production scale Line commissioning demonstrated at a reference site
Possible Supported, not yet deployed at your scale Item-level passports run only in pilots
Promised Roadmap or ‘available on request’ Brand-owned domain ‘can be arranged’

Weight categories by permanence. Carrier, granularity, domain and export are hard to change once products ship. A ‘promised’ answer there should count for far less than a ‘promised’ dashboard feature.

Red flags that should each prompt a follow-up:

  • Identifiers on the provider’s domain by default, with migration described as ‘possible’.
  • One carrier only, so the next product group needs a second provider.
  • Model-level passports only, ruling out later authentication and resale use.
  • Supplier data assumed to exist, with no collection process.
  • Export ‘on request’, with no format or scope.
  • No production-line reference.

Two or three together usually mean the provider sells a passport page, not a passport programme. Why DPP projects fail when product identity is an afterthought explains the pattern.

How do you run a DPP provider evaluation?

  1. Write requirements first: product groups, timelines, carriers and other teams’ needs.
  2. Shortlist on the hard questions. Carrier, domain, export and production references remove most candidates quickly.
  3. Ask each provider for your hardest case: a cloned code rejected, an item-level passport with batch data, a provider exit.
  4. Speak to a customer at production scale, not only a pilot customer.
  5. Pilot on a real line with success criteria agreed in advance.

40+ brands · 12 years · €1.5B protected

Selinko, part of Toppan, treats the Digital Product Passport as one view of an item-level identity that also supports authentication, grey market detection and ownership. Every question above is one we expect brands to ask us.

FAQs

What questions should I ask a DPP provider?

Ask about six areas: compliance and standards, carriers, data and integration, security, domain and exit, and delivery references. In each, look for a verifiable answer: GS1 Digital Link on your domain, item-level issuance, ERP and supplier connections, server-side verification, full data export and production-line references.

Why does domain ownership matter for a DPP?

Printed identifiers cannot be recalled once products ship. If they resolve through the provider’s domain, leaving the provider can break every code in the market. A brand-owned domain keeps identifiers working after a contract ends, because resolution and data can move to a new operator.

Should a DPP provider support NFC?

Yes, where authenticity or ownership matters. The ESPR is carrier-neutral, and a GS1 Digital Link QR is emerging as the default visible carrier. NFC, in the NTAG 424 DNA class, adds cryptographic proof that an item is genuine. NFC for trust, visible carrier for compliance.

What are red flags when choosing a DPP provider?

The main red flags are identifiers on the provider’s domain, a single carrier, model-level passports only, no supplier data process, unnamed ‘unclonable’ security, export only on request and no production-line reference. One is a prompt for questions. Several together signal a page, not a programme.

How should DPP pricing be compared?

Compare total three-year cost for your own volumes. Establish what pricing scales with: units, scans, modules or markets. Per-scan pricing penalises engagement. Check whether carriers, encoding, integration and supplier onboarding are included, because software is usually the smaller share of the budget.

Does a DPP provider need to handle supplier data?

Yes, or the brand must budget for it explicitly. Most passport projects stall on data, not technology. A good provider offers templates, a supplier route and validation tied to batches, and references data from source systems rather than copying it, keeping one source of truth per field.

Can one provider handle both DPP and authentication?

Yes, if the identity is item-level and the carrier can prove authenticity. A cryptographic NFC chip or copy-resistant print, verified server-side, lets the same identifier serve the passport, authentication, grey market detection and ownership. The passport becomes one view of that identity.

Talk to our team

Blog

Discover more articles

All our articles