Digital Link

Digital Product Passport back-up: what happens to your passport if your provider disappears?

Mia

By Mia

Writer specializing in GS1 standards and EU product-labeling regulation.

An operations manager and an IT colleague at a warehouse office desk, comparing a printed supplier contract with a laptop while holding a product box with a QR code

TL;DR

  • A Digital Product Passport back-up is a legal requirement under the ESPR: a back-up copy must be held by an independent service provider, and the passport must stay available for the period the delegated act sets, including after insolvency or liquidation.
  • The weakest point is usually the web address printed on the pack, not the data. A code on your provider's domain depends on that provider; a code on a subdomain you own can be pointed elsewhere without reprinting.
  • Before you sign, ask any provider about export in open formats, exit assistance, notice periods, who holds the back-up, and what happens to restricted data when the contract ends.

A Digital Product Passport is meant to last as long as the product. A washing machine, a sofa or an industrial battery can stay in use for many years, and the passport has to be there for the repairer, the second owner and the recycler. Software companies may not last that long: they get acquired, retire products or close.

The ESPR wrote continuity into the law. Our guide to who is responsible for the Digital Product Passport sets out the duties; this one covers the practical side: what the back-up rule says, what breaks when a provider disappears, and the contract clauses and checks that keep a passport online. Everything below is stated as of November 2026.

What does the ESPR say about keeping a passport available?

Three provisions of the Ecodesign for Sustainable Products Regulation, (EU) 2024/1781, work together.

  • How long. Article 9(2)(i) says each delegated act will set the period during which the passport must remain available, and that period must correspond to at least the expected lifetime of the product.
  • Through what. Article 11(e) says the passport shall remain available for that period "including after an insolvency, a liquidation or a cessation of activity in the Union" of the economic operator that created it.
  • Where it lives. Article 11(c) allows the passport to be stored by the economic operator responsible for creating it, or by digital product passport service providers.

Article 11(e) is about the economic operator going under, not the provider. But the same logic applies when the provider goes, and that is the scenario a brand can prepare for today. There is no single period yet: each delegated act sets its own. Plan for the product's realistic life, not for the length of your software contract.

What is the back-up copy, and who can hold it?

Article 10(4) is short: the economic operator, when placing the product on the market, "shall make available a back-up copy of the digital product passport through a digital product passport service provider". Articles 27(1)(c) and 29(2)(c) repeat the duty for manufacturers and importers and add a useful detail: the back-up is of the most up-to-date version of the passport. A copy taken at launch and not refreshed since is unlikely to meet that wording.

Recital 38 explains the purpose: access to the passport for the required period, including after insolvency, liquidation or cessation of activity. Article 2(32) defines the service provider as an independent third party authorised by the economic operator, that processes the passport data to make it available to those with a right to access it. Two consequences follow:

  • A copy on your own servers does not fit the back-up the ESPR describes. You can store the primary passport yourself under Article 11(c), but the back-up goes through an independent provider.
  • The passport points to its back-up. Annex III, point (l), lists among the passport data "the reference of the digital product passport service provider hosting the back-up copy".

The EU registry knows about it too. Under Implementing Regulation (EU) 2026/1778, the registry checks, where relevant, "the link to the back-up hosted by a digital product passport service provider" at registration (Article 8(7)(e)) and, where relevant, stores a reference to the provider (Article 8(9)(c)). As our EU DPP registry guide explains, the registry holds identifiers, links and references, not the passport data, and a shopper's scan does not go through it.

What is not settled is how the back-up works in practice. Article 11 lets the Commission set requirements for service providers, and possibly a certification scheme; its DPP page lists that delegated act on its indicative timeline for 2027. Until then there are no detailed rules on format or refresh frequency, so treat the checklist below as good practice, not a legal standard.

Does the battery passport have the same rule?

Not in the same words. The Battery Regulation, (EU) 2023/1542, has its own continuity rules for the battery passport, required from 18 February 2027 for LMT batteries, industrial batteries over 2 kWh and EV batteries.

  • Article 77(4) keeps the economic operator placing the battery on the market responsible for the passport, and lets it authorise another operator in writing to act for it.
  • Article 78(c) and (d) allow authorised operators to store the data, but not to sell, re-use or process it beyond the service.
  • Article 78(e) requires the passport to remain available after the responsible operator ceases to exist or ceases its activity in the Union, and Article 77(8) ends it once the battery is recycled.

There is no explicit back-up copy duty in the Battery Regulation text, but the continuity requirement and the practical risk are the same.

What actually breaks when a provider disappears?

A passport is a chain, and each link can fail separately.

LayerWhat it isWhat happens if the provider goesHow to protect it
Code on packThe QR code and the web address inside itIf the address uses the provider's domain, scans stop working or land somewhere you do not controlPut codes on a subdomain your company owns
ResolverThe service that reads the address and redirects to the passportScans fail until a new resolver answers on the same addressKeep DNS control so you can point the subdomain to a new resolver
Passport dataThe public and restricted data, documents and versionsData may be lost or locked in a proprietary formatKeep the master data in your own systems and test exports
Access rightsWho can read or write restricted data, and how they log inRepairers, recyclers or authorities lose access, or credentials stay with a company that no longer existsContract terms on credentials, handover and deletion
Registry entryThe identifiers and links registered with the EUThe registry still points to an address that no longer answersSame as the code on pack: an address you control keeps the link valid

The address matters most. Data can usually be re-uploaded from your own systems; printed packaging and products already in people's homes cannot be changed.

Why does the domain on the pack matter so much?

Article 10(1)(a) of the ESPR requires the passport to be connected through a data carrier to a persistent unique product identifier. Article 2(30) says that identifier "also enables a web link to the digital product passport", which for most brands means a web address in a QR code.

The GS1 Digital Link URI Syntax standard says a GS1 Digital Link URI "can be constructed in any domain name", a flexibility it describes as deliberate, so that brands "can remain in control of the domains they use". The product identity (the GTIN, and batch or serial number where used) sits in the path and does not change. Only the domain says which server answers. Keeping that domain safe for years (renewals, registrar locks, subdomain takeovers) is its own job, covered in our guide to QR code domain security.

So continuity is decided when the first code is printed:

  • A code on the provider's domain works as long as that provider runs it. If it closes or ends your account, you depend on it or its administrator.
  • A code on your own subdomain, such as id.yourbrand.com, is yours. A provider runs the resolver behind it through a DNS record. If you change provider, you point the record at the new resolver and the printed codes keep working. Our resolver guide explains how this works.

The registry entry follows the same logic: the DPP Registry API requires the identifier to be an HTTPS URL, so an address on your own domain stays valid through a change of provider.

Owning the domain also means keeping it. Register it to the company, not to a former employee or an agency, with auto-renewal on and more than one person able to manage DNS. A lapsed domain breaks every code printed with it.

How do you keep the passport data portable?

Article 10(1)(d) of the ESPR requires passport data to be based on open standards and, as appropriate, transferable through an open interoperable data exchange network without vendor lock-in. Article 77(5) of the Battery Regulation says the same.

The CEN DPP standards turn that into engineering. EN 18216 covers data exchange, EN 18221 covers data storage, archiving and persistence, and EN 18222 covers the APIs for managing a passport through its life. When you compare providers, ask which of these they follow and how.

Two habits help more than any feature list:

  • Keep the master data in your own systems. The passport should be an output of your PIM, ERP or product database, not the only place the data exists.
  • Export regularly and open the file. An export nobody has tried to read is not a back-up. Check that it includes restricted data, documents, all languages and older versions where the delegated act requires them.

What should a provider contract cover?

Most continuity problems are settled, or not, in the contract. These are questions to raise with any provider, including us; they are not legal advice.

  • Export on demand. Full passport data, documents and history, in an open, documented format, at any time, at a price agreed upfront.
  • Exit assistance. A defined period after termination during which passports and redirects keep running.
  • Notice periods. For termination, and for material changes to service, pricing or hosting location.
  • Domain and DNS. Confirmation that the domains in your codes are yours, with cooperation when you repoint them.
  • The back-up. Who holds the back-up copy, where, how often it is refreshed, and how it is reached if the primary host fails.
  • Restricted data and credentials. How restricted data is handed over, how authorised users keep access during the move, and how keys are revoked afterwards. Our access rights guide covers who may see what.
  • Use of your data. Article 11 of the ESPR restated: no selling, reuse or processing beyond the service unless you agree.
  • Deletion after exit. Written confirmation of deletion once the migration is complete.
  • Insolvency. What happens to your data and the service if the provider becomes insolvent or is acquired.

When you budget for a passport, as in our DPP cost guide, add a line for an annual exit test.

A short continuity checklist

  1. Codes on your own subdomain before the first print run, with the domain registered to the company and auto-renewal on.
  2. Master data in your own systems, with the passport generated from them.
  3. A back-up copy with an independent service provider, kept to the most up-to-date version, and its reference included in the passport where the delegated act requires it.
  4. A tested export at least once a year, checked by someone who did not produce it.
  5. Contract clauses on export, exit assistance, notice, DNS, back-up, restricted data, data use, deletion and insolvency.
  6. A written runbook for a provider switch: who changes the DNS record, who updates the registry entry if needed, who tells repairers and recyclers.
  7. A named owner for the passport's whole required life, not just the launch.

For the setup itself, see how to create a Digital Product Passport.

Digital Link is a GS1 solution partner. Our platform runs a GS1 conformant resolver for your codes, either on our domain or on your own subdomain through a DNS record, and we recommend your own subdomain for codes that go on pack. Each link can be changed at any time without reprinting. Product data can come from your ERP or PIM, from a spreadsheet upload or through our API, so the master copy stays in your systems, and team permissions control who can edit what. We are preparing our own EU Registry integration and are not connected to the Registry yet. To review how your codes would carry over in a change of provider, get in touch.

Frequently asked questions

Is the back-up copy the same as registering in the EU DPP registry?

No. The registry stores identifiers, links and registration data, not the passport. The back-up copy is a full, current copy of the passport held by an independent service provider. Under Implementing Regulation (EU) 2026/1778, the registry may check the link to that back-up and store a reference to the provider, but it does not hold the back-up itself.

Can our own IT team hold the back-up copy?

Not as the ESPR is written. Article 10(4) requires the back-up to be made available through a digital product passport service provider, which Article 2(32) defines as an independent third party authorised by the economic operator. You can host the primary passport yourself under Article 11(c).

Do we have to reprint packaging if we change provider?

Not if the codes use a domain you control. The GS1 Digital Link address keeps the same product identity in its path, and you point your subdomain at the new provider's resolver. If the codes use the old provider's domain, you depend on that provider to keep redirecting them, and new print runs may need new codes.

How long does a Digital Product Passport have to stay online?

For the period set in the delegated act for your product group, which under Article 9(2)(i) of the ESPR must be at least the product's expected lifetime. For battery passports, Article 77(8) of the Battery Regulation says the passport ceases to exist once the battery has been recycled.

Who is responsible if our passport provider goes bust?

The economic operator that placed the product on the market. A service provider stores or processes the passport on its behalf, but the duty to keep the passport available stays with the manufacturer or importer. That is why the back-up copy and the exit plan are worth settling before you need them.

Be a leader in the transition from barcodes to GS1 QR codes