Retail & E-commerce
What Should a Consumer See After Scanning?
Designing the consumer experience of a DPP — information hierarchy, mobile performance, language, accessibility and practices that lift engagement.
The compliance side of a passport is about data fields. The commercial side is entirely about the first five seconds: the consumer scans, the page opens, and either holds their attention or does not.
Information hierarchy
| Priority | Content |
|---|---|
| 1 | What is this? (brand, model, image) |
| 2 | What is it made of? (composition summary) |
| 3 | How do I care for it? (care, repair) |
| 4 | How do I dispose of it? (recycling) |
| 5 | Evidence (certificates, carbon, methodology) |
| 6 | Detail (full data, route into restricted tiers) |
Most consumers stop after the first three. The rest should be reachable but secondary. See textile DPP data points.
Mobile performance
A passport is usually opened in a shop on a weak mobile connection. Rules:
- Keep the page small; avoid heavy frameworks and large images.
- Serve content ready from the server rather than fetching after load.
- Use caching; passport content changes rarely.
- Accessibility: sufficient contrast, legible type, screen reader support.
See cyber security for DPP systems.
Language
Default to the browser language but include a visible switcher — an inspector or recycler may arrive in another language. Reducing free text in favour of coded fields lowers both cost and inconsistency. See multilingual passports.
Care with green claims
The moment a passport page becomes a marketing surface, green claims rules apply. An unevidenced "eco-friendly" is a risk. Show the data, skip the adjectives. See the Green Claims Directive.
Practices that lift engagement
- A small prompt on the label: "scan the product passport".
- One strong fact on the first screen (a recycled content share, for instance).
- Visible links to repair and spare parts. See the Right to Repair Directive.
- Ownership and status information for second-hand owners. See DPP in resale and second-hand.
Frequently asked questions
Should I show every field?
No. Mandatory public-tier fields must be reachable, but not all of them need to be on the first screen.
Can I ask for registration?
Not for the public tier. Requiring registration breaks the free, unobstructed access requirement.
Can I measure scans?
Aggregated measurement without personal data is possible. See GDPR and DPP data.
