DPP BUYER GUIDES

Digital Product Passport QR Code: What to Test Before Print

A digital product passport QR code gives a reader a route from a physical label to product information. The useful test is what happens after the scan: does it open the right record, can the right people access it, and will the link survive a change of system? Use this checklist before approving a print run.

Understand the route from label to passport

GS1’s DPP guide separates identifiers, data carriers, discovery and data sharing. It describes GS1 options for model, batch and item identification. CIRPASS’s architecture also centres on the product identifier. These are useful technical references; confirm which standards and rules apply to your own product.

For a project review, draw four boxes: the printed carrier, the identifier it carries, the service that resolves the request and the record the reader receives. Name the owner of each box. A successful scan proves only the first part unless you inspect the resulting record.

The checks below are DPP Atlas’s suggested acceptance method. They are not certification tests or measurements from a product we tested. Give the checklist to your label supplier and software team so both work from the same expected result.

References: GS1 in Europe — Standards enabling the EU DPP, release 2.2 (January 2025), PDF · CIRPASS — DPP System Architecture, v1.9 (May 2024), PDF

Understand the route from label to passport
LayerQuestion for your teamSuggested evidence
Printed labelCan a reader scan the final material?Physical sample and scan results
Product identityWhich model, batch or item does it identify?Checked identifier-to-product map
ResolutionWho controls the destination?Domain and routing ownership record
Product dataDoes the right record appear?Record review against the source
AccessWhat can each audience retrieve?Public and restricted-access tests

Choose the identification level deliberately

A model record describes a shared product design; a batch record separates a production group; an item record distinguishes an individual unit. Keep these concepts clear in your test plan. The applicable ESPR product rules specify the required level, so a project preference cannot override that requirement.

Consider a fictional maker of rechargeable tools. Two units may share a model but come from different batches. If the pilot uses batch records, scanning each sample should retrieve its intended batch information. A page with the correct brand logo is not enough to pass that check.

Ask the provider to show how it prevents accidental reuse of your chosen identifiers. Then create two similar records in a test environment and make a controlled correction. Check which record changes. Keep the sample values separate from live product data so a demonstration cannot be mistaken for a released passport.

References: EU Regulation 2024/1781 — Articles 9–11 and Annex III

Test the QR code on the real label

Print a sample on the proposed material, at the proposed size and location. Test that sample rather than a large code on a laptop screen. Include the people and devices likely to read it. Let the label specialist define the relevant print-quality checks and acceptance thresholds.

For a fictional garment brand, a sewn care label may fold or sit inside a seam. Test it in that position. For a packaged appliance, test the expected surface and viewing distance. Record the device, lighting, material and failure so the supplier can reproduce the problem.

Also check the destination on a small screen and a slower connection. The product name and key information should be easy to find. Test keyboard access and text zoom on the destination page. These are proposed usability checks; they do not substitute for the technical standard that applies to the carrier.

Check public and restricted views

Use a fresh public browser session to test what any scanner can see. Then use each authorised role that your project supports. Keep a clear distinction between a public product page and restricted source documents. Do not rely on an unlisted URL as the only access control.

Try a copied link to a private document after signing out. Ask the technical team to confirm that the access check also covers downloads and exports. If the page hides a field but its data is still returned to the public browser, that test has failed.

Keep your pass criteria specific. “The page opens” is different from “the right customer view opens without exposing the supplier evidence”. Record the role, product and expected result before running the check so the team cannot reinterpret a failure after the fact.

Rehearse updates and a change of provider

Ask who controls the domain, redirect rules and product identifiers. Put those answers in the service agreement. Request a demonstration of an export and a planned switch to another test host. Check the existing printed sample again after the switch.

Use a correction scenario as well: replace an outdated care instruction through the approved process, then scan the old physical label. Verify that the intended current record appears and the change can be traced. Ask what happens during an outage and who receives the incident report.

The Commission’s Registry API guidance is a separate integration reference. Where that work is relevant, verify it as its own project step. Do not infer successful Registry integration from a working consumer page, or a working consumer page from a Registry response.

References: European Commission — DPP Registry resources, API and Semantic Data Guides (30 October 2026)

Approve the complete scan journey

Before the production run, bring the label sample, identifier map and test results to one review. List any failed scan, wrong-record result or access issue, along with the person who must resolve it. Retest changed parts before signing off.

Your digital product passport QR code is ready for the agreed pilot when the full journey meets your documented criteria. Use the implementation guide for the wider release decision and the data-register guide to review the information behind each destination. Keep the physical sample with the tested software version for later checks.

Sources and review context

Sources were reviewed for this editorial guide on 4 November 2026. Provider descriptions are attributed public statements. This guide does not report hands-on software testing or certify regulatory compliance. Check the current original source when a detail affects your decision.

  1. GS1 in Europe — Standards enabling the EU DPP, release 2.2 (January 2025), PDF
  2. CIRPASS — DPP System Architecture, v1.9 (May 2024), PDF
  3. EU Regulation 2024/1781 — Articles 9–11 and Annex III
  4. European Commission — DPP Registry resources, API and Semantic Data Guides (30 October 2026)
How DPP Atlas reviews evidence