The architecture in one line
A GS1 Digital Link URI expresses an established GS1 identifier in a web address. A conformant resolver can then route that identity to a DPP, product information, traceability, care, recall or other typed resources without changing the identifier printed on the product.
Why it aligns with the ESPR
The ESPR requires a DPP to connect a persistent unique product identifier through a data carrier, use open and interoperable formats and support product-group access rights. It also lists GTIN among the possible DPP data elements. The textile delegated act will still determine the required granularity and data carrier.
Model, batch and item are different identities
- Model: one identity shared by equivalent products.
- Batch: adds a production-lot dimension.
- Item: adds a serial so every physical unit can resolve independently.
Do not issue item-level serials merely because a QR can contain them. Choose the level required by regulation and by the operational use cases you can actually maintain.
A durable implementation sequence
- Confirm ownership of GTINs and allocation rules.
- Define the canonical product, batch and unit relationships.
- Create persistent Digital Link URIs on a controlled domain.
- Configure resolver link types for DPP and other destinations.
- Keep the public destination replaceable without changing the printed carrier.
- Test scanning, redirects, access rights and long-term availability before printing at scale.
What Cycle contributes
Cycle connects catalogue and supply-chain records to persistent product and unit identities, then publishes the correct experience by audience. The resolver is infrastructure; the value lies in governed data, evidence, access and the decisions that remain linked to each product.