TL;DR
- GS1 Digital Link for AI agents turns the GTIN already printed on a pack into a web address that names one exact product, and where needed one batch or one serialised item.
- A resolver behind that address answers people and machines differently: a consumer is redirected to a page, while an agent can ask for the full, typed list of links the brand publishes for that item.
- The same identifier can sit in schema.org product data and, in our reading, fits the persistent unique product identifier the ESPR requires for the Digital Product Passport, so one investment serves shoppers, retailers, regulators and agents.
GS1 Digital Link for AI agents is the answer we gave in Zurich to a simple question: when an agent buys on someone's behalf, how does it know it is acting on the right product? At the W3C/GS1 Workshop on E-commerce for Humans and AI Agents in September 2026 we called this the last meter of agentic commerce. Agents are getting very good at searching, comparing and paying. They are still weak at the noun. GS1 Digital Link gives them the noun: a standard, brand-controlled web identifier for the exact item, which any agent can resolve without a private integration.
This guide sets out why we think identity is the missing layer, how GS1 Digital Link works as that layer, and how it fits with schema.org, the Digital Product Passport and the agent protocols. Standards facts are checked against GS1's reference pages and EUR-Lex, and everything below is stated as of October 2026. Where we describe how the pieces fit together, that is our reading, and we say so.
The standards behind the identity layer at a glance
GS1 Digital Link is not new, and neither is the GTIN it carries. What is new is that retail is moving to 2D barcodes and agents have started to transact.
| Date | Milestone |
|---|---|
| August 2018 | First version of the GS1 Digital Link standard published |
| 12 February 2024 | GS1-Conformant Resolver standard 1.0.0 published |
| 18 July 2024 | ESPR, Regulation (EU) 2024/1781, enters into force, with a persistent unique product identifier for every Digital Product Passport |
| December 2025 | GS1 guideline on 2D barcodes at retail point of sale, release 1.1.0, ratified |
| August 2026 | GS1 Digital Link URI Syntax release 1.7.0 and GS1-Conformant Resolver release 1.2.1 ratified |
| 8–9 September 2026 | W3C/GS1 Workshop on E-commerce for Humans and AI Agents, Zurich |
| End of 2027 | GS1 ambition: retail point-of-sale scanning globally able to read the GTIN from both linear and 2D barcodes |
Why do AI agents need an exact product identity?
Because a description is a guess. When a person asks an agent to "reorder my usual curly-hair shampoo", the agent has to turn a name into a product, usually by matching text across retailer pages and listings. The brand may sell four curly-hair shampoos in two sizes. A model can rank those candidates well. It cannot be certain which one the person meant, and for a purchase, certainty is the point.
We framed it on stage in Zurich in four words: names describe, identifiers identify. A GTIN identifies one trade item at one level: one formulation, one variant, one pack size. If the agent knows the GTIN, the question "which shampoo?" has one answer. If it only knows a name, it has a shortlist.
Some decisions depend on the batch or the individual unit:
- Recalls and safety notices usually apply to specific batches, not to every unit with the same GTIN.
- Authenticity and warranty are about one serialised item.
- Expiry and freshness change from lot to lot.
- Regulatory data under the ESPR may be set at model, batch or item level, depending on the delegated act for the product group.
An agent that can only say "this product" cannot answer "is the bottle in my cupboard affected by the recall?" An agent that holds the batch number can. That is what we mean by the last meter: the final step between a correct transaction and the correct physical thing.
Names and images will stay how agents find candidates. But similarity is not identity: two variants can look identical in a photograph and differ in an allergen, a voltage or a pack count. Price, availability and delivery are variables. The item the person wants is the constraint.
How does GS1 Digital Link work as an identity layer?
GS1 Digital Link is GS1's standard for expressing GS1 identifiers, such as the GTIN, inside a web address. GS1 describes the URI Syntax standard as the one that should be seen as synonymous with the term "GS1 Digital Link". The latest release, 1.7.0, was ratified in August 2026 and is published on ref.gs1.org. For a fuller introduction, see our GS1 Digital Link basics.
Four properties make it work as an identity layer for agents.
1. The identifier and its qualifiers sit in the path
A GS1 Digital Link URI puts the primary key, such as the GTIN under Application Identifier 01, in the URI path. Key qualifiers follow in a fixed order: the consumer product variant (AI 22), then the batch or lot (AI 10), then the serial number (AI 21). Data attributes, such as an expiry date (AI 17), go in the query string as key=value pairs.
| What the agent needs to pin down | GS1 element | Example path |
|---|---|---|
| The product | GTIN (AI 01) | /01/09520123456788 |
| A consumer variant | GTIN + CPV (AI 22) | /01/09520123456788/22/2A |
| A batch | GTIN + batch/lot (AI 10) | /01/09520123456788/10/ABC123 |
| One serialised item | GTIN + batch/lot + serial (AI 21) | /01/09520123456788/10/ABC123/21/12345XYZ |
Because the order is fixed, two systems that see the same physical pack derive the same path, so they are talking about the same thing.
2. Any domain, the same identity
The standard says a GS1 Digital Link URI can be built on any domain name, so a brand can use its own. The identifier in the path stays the same whichever domain carries it, and the standard defines a canonical form on GS1's own domain, id.gs1.org. We see this as the property that makes it agent-independent: the identity belongs to the brand and the GS1 system, and no single platform owns it.
3. A resolver answers the request
A resolver is the service behind the URI. Under the GS1-Conformant Resolver standard, release 1.2.1 ratified in August 2026, it connects an identified item to one or more online resources related to it. Every identified item has exactly one default link, and the resolver redirects to it unless the request carries information that allows a better match, such as the requested link type, the language or a declared context.
For agents, the most useful rule is this. When a client asks for linkType=linkset, or sends an application/linkset+json Accept header, the resolver does not redirect. It returns the full list of links available for that item, in the Linkset format of RFC 9264. A shopper scanning the pack lands on a product page, while software can ask what the brand publishes about this exact item and get a structured answer. Each conformant resolver must also publish a description file at /.well-known/gs1resolver, so a machine can discover what the resolver supports. Our guide to the GS1 Digital Link resolver covers the mechanics in more depth.
4. Link types tell the machine what each link is
Links are typed with terms from the GS1 Web Vocabulary. As of October 2026 the vocabulary lists 59 stable link types. A few that matter for agents:
| Link type | What GS1 says it points to | Why an agent cares |
|---|---|---|
gs1:pip | A product information page about the identified item | The brand's own description, for comparison |
gs1:masterData | Structured master data, typically for B2B | Machine-readable attributes instead of scraped text |
gs1:recallStatus | Whether the product has been recalled, typically an API | A check before buying or using |
gs1:dpp | A Digital Product Passport | Regulatory and sustainability data |
gs1:certificationInfo | Certification information | Evidence behind claims |
gs1:hasRetailers | A list of retailers | Where the exact item can be bought |
gs1:instructions | Instructions such as assembly or usage tips | After-sale help |
A typed link tells the agent what is behind it before it reads anything.
One QR code for consumers, retailers and machines
GS1's own page on the standard describes the retail vision as a single multipurpose 2D barcode on each product, used at the point of sale and to reach digital content such as certifications, instructions, product information and traceability data. Its guideline on 2D barcodes at retail point of sale sets the ambition that, by the end of 2027, point-of-sale scanning can read the GTIN from both linear and 2D barcodes. GS1 also notes that retailers and third-party apps can keep using the barcode as an entry point to their own systems.
We think agents are the third audience for that same code. An agent may meet the identifier when a person photographs the pack, when a device scans it, or in structured data on a product page or an order history. In each case the starting point is the same URI, and nobody has to print a second code for machines.
Where the QR code does not help matters just as much. A code can be copied, so on its own it proves nothing about authenticity, and it carries no price, stock or delivery terms. Identity is necessary for the last meter. It is not sufficient, as the table further down sets out.
How does it relate to schema.org Product data?
Most agents that read the web will meet product data as schema.org markup long before they meet a QR code. Schema.org already has a bridge. Its gtin property, used on Product, Offer and Demand, takes an all-numeric GTIN of 8, 12, 13 or 14 digits, or a GS1 Digital Link URL based on one. It generalises the older gtin8, gtin12, gtin13 and gtin14 properties and is declared equivalent to the GS1 Web Vocabulary's own gtin. Schema.org also defines a hasGS1DigitalLink property, used on Product, Offer, Organization and Place, for the GS1 Digital Link associated with the item.
So the identifier on the pack and the identifier in the page markup can be the same thing. When a retailer's offer and the brand's product page both state the GTIN, an agent can tell they describe the same item without guessing from the title. In our reading this is the cheapest step most brands can take.
How does it relate to the ESPR's unique product identifier?
The ESPR builds the same idea into EU law. Regulation (EU) 2024/1781 defines a unique product identifier as a unique string of characters that identifies a product and also enables a web link to the Digital Product Passport. It defines a data carrier as a linear barcode, a two-dimensional symbol or another automatic identification medium that a device can read.
Article 10(1) then requires every passport to be connected through a data carrier to a persistent unique product identifier, with the carrier physically present on the product, its packaging or accompanying documentation. Annex III lists the GTIN under ISO/IEC 15459-6 among the elements a delegated act can require, and requires the data carrier and identifiers to comply, where relevant, with the ISO/IEC 15459 series. Article 10(1)(d) adds that passport data must be based on open standards, interoperable and, as appropriate, machine-readable, structured and searchable, without vendor lock-in.
| Requirement | ESPR | GS1 Digital Link |
|---|---|---|
| A unique identifier for the product | Unique product identifier, Article 2(30) | GTIN, with optional CPV, batch and serial |
| A web link from the identifier | Identifier "also enables a web link" to the passport | The identifier is itself a URI |
| A physical data carrier | Article 10(1)(b) | QR code or Data Matrix carrying the URI |
| Model, batch or item level | Set by each delegated act, Article 10(1)(f) | Key qualifiers in a fixed order |
| Machine-readable, open, no lock-in | Article 10(1)(d) | Open GS1 standards, brand-chosen domain, typed links |
The ESPR does not name GS1 Digital Link, and the delegated acts will set the carrier and identifier for each product group. Our reading is that a GS1 Digital Link URI in a QR code fits the structure the Regulation describes closely, and that the passport becomes one more typed link, gs1:dpp, behind the same identifier an agent already uses. Our guides to the ESPR and to Digital Product Passport data requirements cover the legal detail.
Where does it sit next to the agent protocols?
Several protocols for agentic commerce are now being published, covering how agents call tools, how they negotiate a checkout and how payments are authorised. Another guide looks at them in detail. Here we only want to place identity next to them.
Protocols tell agents how to act. Identity tells them what they are acting on. A checkout can be flawless and still carry the wrong item if the item was chosen by guesswork. A standard identifier carried through the flow lets the person, the merchant and later the returns desk point to the same thing.
We are not claiming that any agent protocol requires a GS1 Digital Link URI. That is our reading of how the layers fit, and the case we made in Zurich: product identity should live on the open web, controlled by the brand and owned by no single platform. The alternative is a private catalogue and private product IDs per AI platform, with brands maintaining a mapping for each.
What GS1 Digital Link does and does not solve
| It does | It does not |
|---|---|
| Name the exact item, down to batch or serial where encoded | Prove on its own that a physical item is genuine |
| Give brands control of the domain and the links | Replace the retailer's offer, price or stock data |
| Let one code serve shoppers, point of sale and machines | Make incomplete or inaccurate product data reliable |
| Return a typed, machine-readable list of links on request | Decide which agent protocol a merchant should use |
| Provide a natural home for the ESPR passport link | Satisfy an ESPR delegated act by itself |
What brands should do now
- Check your GTINs. Every variant and pack size should have its own GTIN, used consistently across your catalogue, retailers and marketplaces.
- Publish the identifier in your structured data. Add the GTIN, and the GS1 Digital Link URI where you have one, to the schema.org markup of every product page.
- Run a conformant resolver on your own domain, with the linkset response enabled so machines can ask for every link at once.
- Type your links. Start with a product information page, then add master data, instructions, certification and recall status.
- Decide the identity level. Model level is enough for discovery. Recalls, authenticity and some passports need batch or serial level, so plan the encoding with production now.
- Put the QR code on pack. One code serves shoppers today, point of sale as retailers upgrade, and agents as they arrive.
- Plan the passport link. When your ESPR delegated act lands, the passport can sit behind the same identifier as a
gs1:dpplink.
Digital Link is a GS1 solution partner, and our platform gives every product a standards-based GS1 Digital Link identity: a conformant resolver on the brand's own domain, typed links behind one QR code, and pages and data that can be updated without reprinting packaging. We built it for shoppers and passports first, and the same identity is ready for agents. If you want to check whether your products are identifiable at the last meter, get in touch and our team will review your catalogue with you.
Frequently asked questions
Why can't an AI agent just use the product name?
A name can match several products: different variants, sizes or formulations from the same brand. A GTIN identifies one trade item, and a GS1 Digital Link URI can go further to a batch or a single serialised unit. Agents can use names to find candidates, but they need an identifier to be certain.
How does an AI agent read a GS1 Digital Link?
It requests the URI like any web address. A GS1-conformant resolver redirects to the default link or, when asked for a linkset, returns the full list of links for that item, typed with terms from the GS1 Web Vocabulary.
Do agent protocols require GS1 Digital Link?
We are not aware of any official agent protocol specification that requires it, and we do not claim one does. Our view is that identity and protocols are separate layers: protocols define how an agent acts, and a standard identifier defines what it acts on.
Does schema.org support GS1 Digital Link?
Yes. The schema.org gtin property accepts a numeric GTIN or a GS1 Digital Link URL based on one, and the hasGS1DigitalLink property holds the GS1 Digital Link associated with a product, offer, organisation or place.
Is GS1 Digital Link the ESPR's unique product identifier?
The ESPR does not name it. It requires a persistent unique product identifier that enables a web link to the passport, carried on a physical data carrier and compliant, where relevant, with the ISO/IEC 15459 series. In our reading a GS1 Digital Link URI in a QR code fits that structure, but each delegated act sets the carrier and identifier for its product group.
Do I need a separate QR code for AI agents?
No. The same GS1 Digital Link QR code serves shoppers, retail point of sale and machines. What changes is the response: a person is redirected to a page, while an agent can ask the resolver for the typed list of links.
