DPP Backup

Backup Service

Independent Back-Up Service for Digital Product Passports

Designed to satisfy ESPR Article 10 mandates. By integrating a dedicated independent back-up copy alongside any primary DPP platform, service providers and consultants ensure every published passport version remains verified, secure, and retained for the required period.

Review Technical Standards Enquire About Integration

How it works

From Primary Platform to Independent Back-Up Copy

By connecting the primary platform, partners route each published version to DPP Backup. It is received, verified against the original and stored apart, ready if the original goes offline, while the primary platform keeps issuing and managing the passports.

Primary platform

  • Routed through the DPP Backup API
  • Uploaded as JSON export files
  • Collected via EN 18222 on a schedule

DPP Backup

  1. Receive
  2. Verify
  3. Keep

The back-up copy

  • Every version, kept apart from the original
  • Verified against the original
  • Available if the original goes offline

Integration

Three Integration Routes

Routes can be combined per client account. Passports stay on the primary platform, and its publishing flow stays unchanged.

API integration

By routing each published version through the DPP Backup API, the primary platform keeps the back-up copy current at the moment of publication.

Structured file upload

By uploading structured JSON export files, for example in the EN 18223 format, integrators maintain back-up copies of passports from platforms that work with file exports. Each file is validated, and any issue is reported with its fix.

Scheduled collection

By managing scheduled collections via EN 18222, DPP Backup reads new versions from the primary platform's passport API, while the platform side stays as it is.

Features

Architected for Continuous ESPR Article 10 Compliance

Multi-Platform Compatibility

Operates independently alongside any primary DPP platform, while existing user workflows continue as they are.

Immutable Versioning

Preserves every published passport version with exact timestamps, keeping historical versions side by side.

Automated Integrity Verification

Validates stored back-up copies via cryptographic checksums upon arrival and at regular automated intervals.

Granular Access Control Retention

Preserves public, repairer and authority access tiers, as set under ESPR Articles 9 and 11, while maintaining strict payload encryption.

Full Data Portability

Enables full-portfolio exports in open formats, JSON and EN 18223, at any time.

Gap Monitoring

Flags any passport whose copy is missing or out of date, so issues are resolved before they affect a client account.

Rule-Based Retention

Retains each passport for the period set by the rules for its product group, with schedules tracked automatically for every client.

Roles and Audit Trail

Owner, editor and viewer roles, two-factor sign-in and an audit log of significant actions support governance across every client account.

Multi-tenant and white-label

Multi-Tenant Management for Consultants & Service Providers

By managing clients under isolated sub-accounts, consultancies and integrators maintain centralised visibility while keeping client data completely separated.

Isolated client sub-accounts

  • Each client in a separate sub-account with its own passports, back-ups and users
  • One central view of the back-ups of every client
  • Works alongside the primary platform each client already uses
  • Each client remains the economic operator for its own passports

Silent, white-label operation

  • Operating transparently in the background, so original QR codes and URLs stay as they are on the client's own custom domain
  • Each passport copied exactly as published, with everything it holds
  • The client's domain can be pointed at the back-up copy if the primary platform goes offline
  • Clients see only their own back-ups

Access levels

The Whole Passport, with the Same Access Tiers

The back-up copy holds the public and the restricted layers of each passport. The rules for each product group define who may see which data, and every field keeps its access level, so the copy serves each audience exactly what the original would and client data exposure stays unchanged.

Public

Data for everyone

  • Product identity and manufacturer
  • Composition and materials
  • Use, repair and recycling information
  • The identifier and its scheme
Restricted

Repairers, recyclers and others with a legitimate interest

  • Detailed composition
  • Repair and dismantling information
  • Safety measures
Restricted

Market surveillance authorities, notified bodies and the Commission

  • The repair and dismantling data
  • Test-report results

Open standards

Built on Harmonised European Standards

DPP Backup is based on the six harmonised European standards for Digital Product Passports: EN 18216, EN 18219, EN 18220, EN 18221, EN 18222 and EN 18223. EN 18221 shapes how passport data is stored and preserved, EN 18222 defines the API structures, and GS1 Digital Link keeps identifiers resolvable. Because the service is updated centrally, partner integrations stay aligned as the European standards evolve.

Open formats in, open formats out: partner and client data stays portable and can be exported at any time.

  • EN 18221 data storage and data persistence
  • EN 18222 passport APIs
  • EN 18223 system interoperability
  • EN 18219 unique identifiers
  • GS1 Digital Link
  • JSON and JSON-LD

Hosting and security

Isolated Hosting in Europe

A back-up only adds value if it survives what happens to the original. Copies are checked at regular intervals and held apart from the platforms where passports are created, so the back-up copy stays independent of any single provider.

  • Hosted in European data centres
  • Kept apart from the platforms where passports are created
  • Encrypted in transit and at rest
  • Regular integrity checks of every stored copy
  • Two-factor sign-in, and strict separation of each client's data
  • An audit log of significant actions, for owners

Implementation

Four Steps to Portfolio Back-Up Deployment

  1. Account Provisioning

    Establishing dedicated agency or platform tenant environments, with a separate sub-account for each client.

  2. Data Pipeline Connection

    Integrating via API endpoints, batch EN 18223 JSON file uploads or automated EN 18222 polling.

  3. Retention Rule Configuration

    Assigning retention schedules to each product group, based on the EU rules that apply to it.

  4. Automated Monitoring

    Gaining single-pane-of-glass visibility across all client passport back-ups, with export available at any time.

Equip Your Platform or Practice with Article 10 Back-Up Infrastructure

By establishing independent DPP back-up copies today, platforms and consultancies put the back-up copy that EU product regulations require in place across all managed product accounts.

Contact us