Search for "Digital Product Passport example" and you mostly find screenshots of products that do not exist — invented model names, placeholder data, nothing you can actually open. That is not very convincing when you are trying to understand what a DPP is.
These are working demos with fictitious product data and example GTINs from GS1 prefix 952. They do not represent assigned product identifiers, a registry entry or a certification.
Example 1 — an EU battery passport
It resolves to the consumer page for EcoMax 5000 (Demo) by GreenPower GmbH (Germany), sold in FR/DE/IT. The passport carries the fields the EU Battery Regulation 2023/1542 expects:
| Field | Value |
|---|---|
| Capacity | 5.2 kWh |
| Carbon footprint | 42.5 kg CO₂e |
| Recycled content | 35 % |
| Recyclability | 95 % |
| Manufacturer warranty | 8 years |
| Certifications | CE, UN38.3 |
Want the machine-readable version a recycler or authority would consume? Same URL, JSON-LD:
curl "https://qr3.app/dpp/09520000000011/DEMO-BAT-01?format=jsonld"
# { "@context": ["https://schema.org","https://gs1.org/voc/"],
# "@type": "Product", "gtin": "09520000000011", "name": "EcoMax 5000 (Demo)", ... }
Example 2 — an EU textile passport
This is Cotton T-Shirt (Demo) by Fabric AG — a textile DPP under the ESPR, including the supply-chain transparency fashion brands now have to provide:
| Field | Value |
|---|---|
| Fibre composition | 70 % cotton (TR) · 30 % recycled polyester (CN, 100 % recycled) |
| Recycled content | 30 % |
| Durability class | B (≈ 80 wash cycles) |
| PEF carbon footprint | 12.4 kg CO₂e |
| Microplastics | No |
| Supply chain | Weaving PT · Dyeing TR · Assembly FR |
| Certifications | OEKO-TEX STANDARD 100 |
API
Unlike a static mock-up, each example:
- resolves through a live GS1 Digital Link resolver — the URL is the access point, not a screenshot;
- has scannable QR codes in print formats (SVG/PNG/PDF/EPS);
- returns JSON-LD (
schema.org+ GS1 vocabulary) for machines via?format=jsonld; - renders a localized consumer page (these demos default to German).
Build your own in minutes
These demo passports use seeded data. The following example illustrates the public API; register your product GTIN for your organisation before creating a passport:
import { QR3 } from "@qr3/sdk";
const client = new QR3({ apiKey: process.env.QR3_API_KEY! });
const passport = await client.dpp.create({
gtin: "09506000134376",
serial: "SN-00012345",
product_name: "PowerCell 5 kWh LFP",
manufacturer: "ExampleTech GmbH",
origin_country: "DE",
category: "battery",
battery_data: {
capacity_kwh: 5,
carbon_footprint_kg: 62,
recycled_content_pct: 12,
recyclability_pct: 95,
manufacturer_warranty_years: 8,
},
});
console.log(passport.qr.svg); // print-ready GS1 Digital Link QR
(Full walkthrough: Generate EU Digital Product Passports via API.)
FAQ
Can I scan these with a normal phone? Yes. Each passport page exposes a standard QR code carrying its GS1 Digital Link — any camera opens it.
Is the data real or placeholder? These are working demos with fictitious product data and example GTINs from GS1 prefix 952. They do not represent assigned product identifiers, a registry entry or a certification.
How do authorities read it? They request JSON-LD (or the linkset) from the same URL. Humans get the page, machines get the data.
Sources
Open the live passports above, then start for free and build your own.
