{"id":541,"date":"2026-08-18T11:13:10","date_gmt":"2026-08-18T10:13:10","guid":{"rendered":"https:\/\/www.unitag.io\/blog\/?p=541"},"modified":"2026-08-18T11:13:11","modified_gmt":"2026-08-18T10:13:11","slug":"dpp-resolver-requirements-european-standards","status":"publish","type":"post","link":"https:\/\/www.unitag.io\/blog\/dpp-resolver-requirements-european-standards\/","title":{"rendered":"DPP resolver: what the European standards actually require"},"content":{"rendered":"

You can check today, in about ten minutes, whether a resolver is ready for the Digital Product Passport. Since July 2026, six of the eight European standards framing the DPP are published, and they spell out what the infrastructure has to do. Here is the short version in plain language, and the questions worth asking any provider.<\/p>\n\n

\n

Unitag tracks 2.4 million scans daily<\/strong> across 189 countries. The platform is officially approved by GS1 and listed as a GS1 Solution Provider.<\/p>\n<\/div><\/div>\n\n\n

Three identifiers, one structured address<\/h2>\n

The standards define identifiers for the product, the economic operator and the production facility. The product identifier travels as a structured web address; with GS1 identification that is a GS1 Digital Link whose primary key is the GTIN, qualified down to batch or serial number when the sector’s delegated act demands that granularity. A serious resolver supports the whole hierarchy: if a GTIN is recognised, its batch-level and serial-level variants must resolve too.<\/p>\n

The QR code is the baseline carrier<\/h2>\n

The passport must be reachable from the physical product through a data carrier: QR code, Data Matrix or RFID. The rule that settles the debate in practice: at least one carrier per product must be readable free of charge with an ordinary smartphone, no app installed. That makes the QR code the baseline. Print quality, quiet zone and lifetime durability requirements sit on top, and the full document covers them standard by standard.<\/p>\n

A resolver does more than redirect<\/h2>\n

Resolver behaviour is now standardised, in line with the GS1 resolver standard. In short: every identified product has a default link, and the resolver takes each scan to the most relevant destination given the request’s context, language, country or device. Destinations are typed: product page, sustainability information, certification, instructions, recall status, and above all the passport’s own link type, which lets a customs system, an inspection tool or a recycler request the official document directly. A description file published at a well-known address declares what the resolver can do, so third-party systems know what to ask it.<\/p>\n

These mechanisms already exist in the Unitag platform: the language, country and device rules our clients use for marketing are the operational equivalent of the context values the standard defines. Getting to conformance is an extension of what runs today rather than a rebuild.<\/p>\n\n

\n
\n

Bonduelle already runs its ranges on this infrastructure<\/strong><\/p>\n <\/div>\n

Read the case study \u2192<\/a><\/p>\n<\/div><\/div>\n\n\n

Persistence, access, authenticity<\/h2>\n

Three requirements complete the picture. The passport must stay available for the product’s whole lifetime, with backup through a service provider and versioned archives, even if the economic operator ceases activity. Access control separates public data from business-confidential data, with roles aligned on eIDAS assurance levels. And passport data must be electronically signed so its authenticity can be verified. An infrastructure that skips these three at the start gets rebuilt mid-journey, precisely when the sector deadlines start pulling on it.<\/p>\n

Check before you choose<\/h2>\n

The first hard deadline is batteries in February 2027; textiles and the first sectors under the ESPR (Ecodesign for Sustainable Products Regulation, 2024\/1781) follow as delegated acts are adopted, applying roughly eighteen months after each one. There is time to choose well, provided the right questions are on the table now.<\/p>\n

We have collected the full requirements in one reference document: the standards cited clause by clause, expected resolver behaviour, link types, sample requests and the application timeline. It is the document we put in the hands of our clients’ IT teams and integrators. Get the complete technical specifications<\/a><\/p>\n

\n

See the resolver in action<\/p>\n

Free trial, EU hosting, no per-code fees.<\/p>\n

Start a trial \u2192<\/a><\/p>\n<\/div>\n\n

Read next<\/h2>\n