Skip to content
qr3.app Docs

DPP Overview

DPP Overview

qr3.app supports the EU Digital Product Passport today for three product categories and ships with a built-in EU validator:

  • Battery — EU battery regulation 2023/1542, Phase 4a mandatory fields, own legal profile
  • Textile — French Loi AGEC + expected, not yet adopted ESPR delegated act, own legal profile
  • General — a generic category for anything outside battery/textile (carbon footprint, recyclability, material description, certifications); runs the same baseline checks (GTIN, GS1 URI, manufacturer, origin country) as the other categories, but without a dedicated legal profile — no battery- or textile-specific mandatory fields or rules
  • EU compliance validator — integrated rule checks with live preview and simulator

All categories and the validator run on the same API stack and the same dashboard. GS1 Digital Links resolve under /01/...; HTML, JSON-LD, and linkset views come out of the same resolver.

Quick start

  1. Register GS1 identifiers — see GS1 onboarding
  2. Create a DPP (battery, textile, or general) — in the dashboard at /dashboard/dpp/new
  3. Watch live EU compliance inside the form — errors and warnings before save
  4. Print the canonical GS1 URI as the QR target — https://qr3.app/01/{GTIN}/21/{SERIAL}

Core pages

What is usable out of the box today

  • Battery, textile, and general as complete DPP schemas (create, CSV/XLSX bulk import, update, delete) — battery and textile with their own legal profile, general generic without one
  • GTIN, serial, and lot handling
  • market_countries as a base field (AGEC-FR trigger) across all categories
  • Content negotiation for HTML, JSON, JSON-LD, and linksets
  • QR assets as SVG, PNG, vector PDF, and EPS
  • EU registry mock + webhook path — real adapter follows once the EU API is published
  • DPP scan analytics — aggregated access counts per passport (GET /v1/dpp/:id/stats) and workspace-wide (GET /v1/workspace/stats/dpp): scans by day, country, device, representation, and language, pseudonymised unique scanners

What is intentionally out of scope

  • DID / verifiable credentials workflows (Phase 4c)
  • ERP/PLM connectors (Phase 4c)
  • A dedicated legal profile for categories beyond battery + textile (roadmap dependent) — general already covers these products generically today, just without category-specific mandatory fields or rules