Should a product tag carry a GS1 Digital Link?
Where the product already has GS1 keys, it is the obvious address to carry. A GS1 Digital Link is a web address that holds the identification keys in its path, so the printed code and the tag carry the same one, and a resolver behind it can serve a customer and a machine differently.
What a GS1 Digital Link is
The GS1 Digital Link URI syntax defines it as a particular form of URL, usable in exactly the same way as any other URL, which the standard calls an important design feature. A phone that opens it gets a web page like any other; nothing needs to know it is a GS1 address for the basic case to work.
What it adds is structure. The identification keys live in the path rather than in a query invented for the occasion, so the same address identifies the product to a machine and takes a person somewhere useful. The standard writes its examples as templates, such as https://example.org/01/{gtin}.
Keys, qualifiers and attributes
The syntax separates three things: primary identification keys, which express simple GS1 identifiers such as a GTIN or a GLN; key qualifiers, which express extensions such as a batch or lot and form compound identifiers; and attributes, which express informative data such as an expiry date.
That separation is what makes the level of identification explicit in the address itself: an address with a GTIN identifies a model, the same address with a serial qualifier identifies one item. The level page takes that decision, which the applicable act settles first.
What it means for the tag
Nothing unusual. It is a URL, so it goes in a URI record like any other address, which the URL writing page covers, and the tag is read by any phone with no application.
Two practical consequences follow. The printed code and the tag can hold the same address, which keeps one destination to maintain rather than two, the argument the carrier page makes. And the address is longer than a bare domain, so the memory it takes is worth checking against the tag before a production run, which the usable memory page measures.
When it does not fit
When the product has no GS1 keys and no reason to acquire them. A closed deployment where the same company writes the tags and runs the readers gains nothing from the syntax, and a plain address it controls is simpler to keep alive.
And the syntax is not what the law requires. regulation (EU) 2024/1781 requires a persistent unique product identifier that enables a web link to the passport, and ties identifiers to the ISO/IEC 15459 series, which the identifier page sets out; a GS1 key is one way of satisfying that, not the only one, and the act for the group remains the text to read.
Frequently asked questions
Does the product passport require a GS1 Digital Link?
No. The regulation requires a persistent unique product identifier complying with the standards it names. GS1 keys are one way of meeting that.
Can the printed code and the tag hold the same address?
Yes, and it is the reason to use one: a single address behind both carriers means one destination to keep alive for the life of the product.
Does a phone need an app to read it?
No. It is an ordinary URL in a URI record, so any phone opens it like any other web address.
Is it longer than a plain URL?
Usually, since it carries the keys in the path. Check the length against the tag memory before a production run.