DPP Backup

For DPP platforms and consultants

Independent Back-Up Architecture for Digital Product Passports

Designed to satisfy ESPR Article 10 mandates. By integrating an independent, automated back-up copy alongside any primary DPP platform, technical providers and consultants ensure client passports remain accessible through platform migrations or business changes.

  • White-label
  • Version history
  • Integrity checks
Review Technical Integration Contact us

DPP Backup keeps an independent secondary copy alongside the primary DPP service provider, which issues and manages the original passports.

Back-up copyExample

E-bike battery pack

Model EB-625 · Digital Product Passport

GTIN 09506000134352Serial 00417

Same QR code
Back-up status
Matches the original
Versions kept
3 of 3
Last copied
Today, 09:14 UTC
Stored in
EU data centre
Original
dpp.acme-cycles.example
Connected via
DPP Backup API
Checksum matches the originalVersion 3
Access levels kept
  • Public
  • Repairers
  • Authorities

Architecture

An independent secondary copy, alongside the primary platform

The primary DPP service provider issues, hosts and manages the passports. DPP Backup keeps a separate, automated back-up copy of each published version, apart from the primary platform.

White-label by design

Enables platforms and consultants to include the back-up in their own service. DPP Backup operates in the background and copies each passport exactly as published.

Built around ESPR Article 10

Designed to provide the back-up copy that Article 10 of the ESPR requires, held by an independent service provider, separate from the primary platform.

Scope by product group

Available when the primary goes offline

If a primary platform goes offline or a client ceases trading, the back-up copy can be served in place of the original, so printed QR codes continue to resolve.

Automated verification

Each published version is copied and verified against the original automatically, and missing or outdated copies are flagged per client account.

White-label

Operating in the background, on the client's own domain

DPP Backup runs behind the partner's service and copies everything the passport holds. A scanned QR code still leads to the client's own passport.

  • The whole passport. Data, access levels, identifier and documents are copied exactly as published.
  • Same identifiers and QR codes. Printed codes stay valid, and identifiers stay on the client's own domain.
  • Available when the original goes offline. The client's domain can be pointed at the back-up copy, so printed codes continue to resolve.
  • Part of the partner's service. Platforms and consultants include the back-up in what they offer their clients.
Example: the passport opens from its back-up copy, on the client's own domain. The client and domain are invented.

Partners

Built for DPP platforms, integrators and compliance consultants

DPP software platforms

By integrating DPP Backup, platforms add an independent back-up layer to their service, built and operated by DPP Backup.

  • Runs alongside the platform's own passport storage
  • Each client kept in a separate account
  • Back-ups of every client visible in one place

Integrators and compliance consultants

By setting up DPP Backup across a client portfolio, integrators and consultants put the back-up copy in place for every managed account, whatever primary platform each client uses.

  • Works with any primary DPP platform
  • Every version retained for as long as the rules require
  • Full export at any time, in open formats

Integration

How Platforms and Consultants Incorporate Independent Back-Up

  1. Connection

    Passports reach DPP Backup by routing each published version through the API, by managing scheduled collections via EN 18222, or by uploading structured JSON export files. The publishing flow of the primary platform stays as it is.

  2. Copy and verification

    Each published version is received, verified against the original and stored apart from the primary platform.

  3. Retention and availability

    Copies are retained for the period set for each passport and can be served in place of the original whenever the primary platform is offline.

Backup Service

Every client back-up in one view

Partners see which passports are backed up across all client accounts, how many versions are kept, and any new version still to be copied.

  • Every published version kept, side by side
  • A checksum per copy, verified against the original
  • Public and restricted data, with their access levels
  • Alerts when a back-up is missing or out of date
  • Full export at any time, in open formats
Backup Service overview
Back-ups Acme Cycles4 passports · 10 versions
PassportGTINBack-upVersionsLast copy
E-bike battery pack EB-62509506000134352Up to date3Today
E-bike battery pack EB-50009506000134369Up to date2Today
Cargo bike battery CB-100009506000134376Up to date1Yesterday
Scooter battery SC-36009506000134383New version43 days ago
Example back-up list. Every passport, the versions kept, and any new version still to be copied.

Product groups

Every product group supported

DPP Backup keeps the back-up copy of Digital Product Passports for every product group, including aluminium, batteries, chemicals, construction products, detergents, electronics and ICT, footwear, furniture, iron and steel, mattresses, textiles and apparel, toys and tyres.

Product group coverage

FAQ

Common questions

How the back-up integrates, and how it behaves when a primary platform or a client stops.

All questions

What is DPP Backup?

A white-label service that keeps the independent back-up copy of Digital Product Passports. It works alongside the platform where your passports are created and published: it copies every published version, checks each copy against the original and keeps it for as long as the passport must stay available.

Passports are created and issued on your DPP platform, as they are today. DPP Backup keeps their back-up copy.

What is copied?

The whole passport: its public and restricted data, with the access level of each field, its identifier and its attached documents. Every published version is kept exactly as received, with its date, next to the earlier ones.

What happens if our DPP platform stops working?

The back-up copy is kept apart from your platform, so it stays intact. It can be made available in place of the original, so that people with a right to access the passport can still open it. Because the identifier is on the company's own domain, it can be pointed at the back-up copy and printed QR codes keep working.

What happens if the company stops trading?

That is what the back-up copy is for. The copy stays with DPP Backup, independent of the company, for the period agreed for each passport, so the passport stays available to the people who have a right to read it.

Streamlining Article 10 Compliance for Your Client Portfolio

By establishing a reliable independent back-up, platforms and consultancies put the back-up copy required by upcoming EU product regulations in place across all managed accounts.

Enquire About Partner Integration