Chapter 3 — full chapter
Chapter 3 — full chapter
3.1.2 Reading the requirement through the data carrier it will need
Chapter 5 examines the specific carriers — GS1 identifiers, QR codes, RFID, and NFC — in detail. What matters here is that a data requirement cannot be finalised without deciding how it will be attached to the physical product. A requirement that changes at batch level, such as a certified recycled-content share, needs a carrier and a registry design that can resolve to the right batch record, not just the right product model. Getting this link wrong is one of the most common integration failures reported in early passport pilots, and it is a data-requirements problem before it is a technology problem.
This is also where the EU’s planned infrastructure becomes relevant to a data-requirements decision rather than a purely technical one. Article 13 of the ESPR requires the Commission to stand up a central digital registry, targeted for July 2026 (Chapter 2, section 2.1), whose job is precisely to let an authorised actor locate where a given product’s passport data actually lives, whichever platform or supplier hosts it. A business that defines its data requirements without deciding, at the same time, how each field will resolve through that kind of registry is building a dataset it will later have to re-engineer.