---
title: "GS1 Digital Link QR codes with Linkbreakers"
description: "How GS1 Digital Link puts a product's GTIN and batch in a web address that the checkout and a shopper's phone both read, and how to serve it on your own domain with Linkbreakers: one link per product, the batch saved on each visitor, a recalled batch sent to its notice from the first scan."
canonical: "https://linkbreakers.com/help/article/gs1-digital-link-qr-codes-with-linkbreakers"
last-updated: 2026-11-07
---

# GS1 Digital Link QR codes with Linkbreakers

> How GS1 Digital Link puts a product's GTIN and batch in a web address that the checkout and a shopper's phone both read, and how to serve it on your own domain with Linkbreakers: one link per product, the batch saved on each visitor, a recalled batch sent to its notice from the first scan.

Video: [GS1 Digital Link QR codes: how they work and how to create one for every batch](https://www.youtube.com/watch?v=zGneGBGGZlc)

:::try-ai-prompt {"prompt":"Create a link on my custom domain with the slug 01/09506000134352/10/{batch} that sends visitors to https://example.com/product, and add a visitor data condition that sends batch LOT42 to https://example.com/recall","description":"Set up a GS1 Digital Link with the Assistant.","target":"assistant"}:::

## Short answer

**[GS1 Digital Link](/help/article/gs1-digital-link-explained)** is a standard from GS1, the organization behind product barcodes, for writing a product's barcode number into a web address. The barcode on a pack carries the GTIN, the number that identifies the product; GS1 Digital Link writes that same GTIN, and the batch (the production run the pack came from), into an address such as `https://qr.brand.com/01/09506000134352/10/LOT42`, where `01` introduces the GTIN and `10` the batch. Encoded in a QR code on the pack, that one code serves two readers: a store's checkout scanner reads the GTIN straight from the code's text, and a shopper's phone opens the address like any link.

Linkbreakers, a platform for QR codes and links that decides what happens after each scan, serves that address on your own domain, so it runs the phone side. One [dynamic short link](/help/article/dynamic-slugs-capture-data-from-the-url-path) per product, a link whose address has a changing part, written `01/09506000134352/10/{batch}`, answers every batch of that product and saves the batch on the visitor, so you know which batches people scan. It works on every plan with a custom domain, Free included.

That pays off the day a batch is recalled. Say batch LOT42 of one of your products is recalled: a [visitor data condition](/help/article/how-to-use-visitor-data-conditions), a workflow step that routes each scan by what is saved on the visitor, reads the batch during the same scan, so anyone who scans a pack from LOT42 lands on your recall notice from their very first scan, while packs from every other batch keep opening the product page. Not one pack is reprinted.

### Who does what

| Part of the job | Done by |
|---|---|
| The GTIN printed on the pack | Your GS1 member organization issues it |
| Reading the code at the till | The store's checkout scanner and its own product database. It never opens the address |
| The address on your domain, the batch saved on each visitor, the recall branch | Linkbreakers |
| The recall notice and the product page | You: a page on your site, or a Linkbreakers page with a form |
| One QR code image per batch, in your QR design | Linkbreakers renders them, or your packaging system generates them from the same pattern |
| Printing the codes | Your printer, following GS1's size and contrast guidance |
| An alert when someone scans the recalled batch | Linkbreakers sends the batch to Slack or a webhook; your quality team acts on it |

## What GS1 Digital Link is

GS1 assigns product numbers worldwide. GS1 Digital Link puts them in a URL using GS1 Application Identifiers as path segments:

| Segment | Identifier | Example |
|---|---|---|
| `01` | GTIN, the product number | `01/09506000134352` |
| `10` | Batch or lot | `10/LOT42` |
| `21` | Serial number | `21/SN987654` |

The batch and serial always follow the GTIN, batch before serial. Other data, such as an expiry date (`17`), goes in the query string. The domain can be your own, so the address is `qr.yourbrand.com/01/...` rather than a GS1 address.

On a GS1 DataMatrix or a GS1-128 barcode, the same identifiers are element strings, printed under the code as `(01)09506000134352(10)LOT42`. GS1 Digital Link writes them as the path of a web address instead, which is what lets a phone open it.

The examples on this page use `09506000134352`, GS1's own example GTIN: GS1's resolver at `id.gs1.org` sends it to a fictional "Dal Giardino Risotto Rice with Mushrooms". Replace it with your own GTIN.

### Why brands are moving to it

The industry initiative known as **Sunrise 2027** aims for retail checkouts to read 2D codes, GS1 Digital Link QR codes and GS1 DataMatrix, alongside traditional barcodes by the end of 2027. It is driven by retailers rather than law, and linear barcodes are not being withdrawn. GS1 US says a brand does not need every 2D capability in place by that date. For brands, it means one QR code on the pack can replace both the barcode the checkout needs and the marketing QR code shoppers scan.

## Phones and checkout scanners read it differently

- **A shopper's phone** opens the address like any QR code. That visit reaches Linkbreakers: it runs your workflow, is counted and can capture a lead.
- **A checkout scanner** never opens the address. It decodes the code, finds the `01/` segment and looks up the GTIN in the store's own system. Nothing reaches Linkbreakers, and nothing needs to.

So the address has to follow the GS1 format to satisfy the checkout, and it has to be served by something useful to satisfy the shopper. That is the part Linkbreakers does.

## Set it up

1. **Get your GTINs from GS1.** Your GS1 member organization issues them. Linkbreakers does not assign or check them.
2. **Connect a custom domain**, such as `qr.yourbrand.com`. See [how to create branded links](/help/article/how-to-create-branded-links-in-linkbreakers).
3. **Create one link per product** on that domain. In the link form, pick your custom domain, then click **Advanced {}** next to the Short link label (the button only shows once a custom domain is picked). In the **Dynamic short link** dialog, under **Start from an example**, pick **GS1 Digital Link** ("Packaging codes with your GTIN, routed by batch"). It fills in `01/09506000134352/10/{batch}`: replace the GTIN with yours, in the 14-digit form that will be printed. The dialog shows **Saves on the visitor** with `batch`, then click **Use this short link**.
4. **Build the page shoppers see**: product information, registration form, recipes, a review request.
5. **Generate the codes per batch.** Click **Download QR code** on the link, enter the batch and download its GS1 Digital Link code as PNG, SVG, JPEG or WebP, in your QR design. For production runs, render them through the API: `POST /v1/links/{id}/qrcode-images:render` with one item per batch (`{"values": {"batch": "LOT42"}}`), up to 100 per call, from 256 to 4096 pixels. The CLI does the same with `linkbreakers links render-qrcode-images`, every SDK with `linksServiceRenderQrcodeImages`, and an AI agent over MCP with `links_render_qrcode`. Each batch comes back with its address and its image, ready for the print file; SVG holds up best in print at any size. Your packaging or printing system can also generate the codes itself from the same pattern. The full guide to rendering is [Print hundreds of on-brand QR codes from one link](/help/article/print-hundreds-of-qr-codes-from-one-link).

If some packs carry only the GTIN, with no batch, create a second link with the exact slug `01/09506000134352`. It does not conflict with the dynamic one.

### One link for every product

A single link with the slug `01/{gtin}/10/{batch}` answers every product and batch on your domain and saves both `gtin` and `batch`. It suits a catalogue where every product gets the same page. It cannot coexist with per-product dynamic links on the same domain, because both would match the same addresses.

## Route a batch under recall

Add a [visitor data condition](/help/article/how-to-use-visitor-data-conditions) right after the scan:

- `batch` equals `LOT42`: redirect to the recall notice and its form
- `batch` equals `LOT43`: the same notice
- everything else (the fallback): the normal product page

The condition sees the batch captured on that very scan, so it works for a shopper scanning the pack for the first time. The packs already on shelves and in kitchens need nothing: the code they carry stays the same, only the route behind it changes. When the recall ends, delete the branch.

To hear about it as it happens, turn on [Slack notifications](/help/article/linkbreakers-slack-integration-qr-scan-notifications-for-your-team) or a [webhook](/help/article/how-do-webhooks-work-in-linkbreakers) for the link: each scan carries the batch, so a scan of LOT42 can reach your quality team.

## See which batches get scanned

- Each product's link has its own scans, countries and devices in the dashboard. To read several products together, [tag them by product line and filter by tag and country](/help/article/how-to-track-qr-code-scans-by-product-and-country).
- Every visitor carries the `batch` they scanned, on their profile and timeline. On the **Visitors** page, **Export CSV** gives one row per visitor with a `visitor_attributes_batch` column, so a spreadsheet counts how many people scanned each batch.
- Webhooks and Slack notifications include the batch, for a script or a channel that watches one batch in particular.

Put together: the day a batch is recalled, you add one branch to a workflow instead of reprinting, the people holding that batch see the notice, and the export says how many of them scanned it.

## Limits and caveats

- **No GS1 certification.** Linkbreakers serves the address; it does not register GTINs, check their check digit, or certify your codes. It does not make your packaging Sunrise 2027 ready on your behalf: your GS1 member organization and your retailers say what they need.
- **No checkout data.** Checkout scans happen in the store's system and never reach us.
- **Path only.** Data in the query string (expiry date `?17=`) is not saved, and the compressed form of GS1 Digital Link is not read.
- **Your own domain.** The shared Linkbreakers domain does not serve dynamic slugs.
- **The GTIN is fixed once the link exists.** A link's slug and domain cannot change after creation, so create a new link for a new GTIN.
- **The batch is not passed on to the destination.** It is saved on the visitor and used by conditions, but it cannot yet be inserted into the redirect address (no `example.com/recall?batch=LOT42`). Route each recalled batch with its own branch.
- **100 codes per render call.** For a bigger run, call again with the next 100. Image links expire, so download the files rather than storing the links.
- **Print quality is yours.** Size, contrast and placement on the pack follow GS1's guidance and your printer's tests.

## Frequently asked questions

### Will the checkout read a QR code made with Linkbreakers?

The checkout reads the address inside the code, not where the code was made. If the code encodes a valid GS1 Digital Link address with your GTIN and the store's system knows that GTIN, it reads it. Test with your retailers' scanners before a production run.

### Do I need a link per batch?

No. One dynamic link per product answers every batch.

### Do I have to reprint packs when a batch is recalled?

No. The batch is already in every printed code, so a condition on `batch` sends that batch to the notice and leaves the others on the product page.

### Can I add a serial number too?

Yes: `01/09506000134352/10/{batch}/21/{serial}` saves both. Create it on its own; it does not overlap a slug with fewer segments.

### Is it available on the Free plan?

Yes. It needs a custom domain, and the Free plan includes one.

### Can my agent or script create these links?

Yes, through the REST API, the [MCP server](/help/article/mcp-server-setup), the CLI and the SDKs: send the pattern as the link's `shortlink` with your domain's `custom_domain_id`. They can also print the codes: `links_render_qrcode` (or `POST /v1/links/{id}/qrcode-images:render`) returns the GS1 Digital Link QR code of each batch in your design, up to 100 per call. "Create a GS1 link for GTIN 09506000134352 on qr.mybrand.com and make me the codes for batches LOT001 to LOT120" is a complete request: the agent creates the link, then renders the 120 codes in two calls.

### Do the codes keep my QR design?

Yes. Every code rendered for a batch uses the link's saved design: colours, dot and corner style, shape and logo. Change the design and the next render uses it.

## Next steps

- Learn every pattern a dynamic short link takes, beyond packaging, in [One short link, hundreds of QR codes](/help/article/dynamic-slugs-capture-data-from-the-url-path).
- Set up the recall branch and its fallback with [visitor data conditions](/help/article/how-to-use-visitor-data-conditions).
- Decide what the product page behind the pack should do with [QR codes on product packaging](/help/article/how-to-use-qr-codes-on-product-packaging).

## Sources

- GS1 Digital Link quick start guide: https://ref.gs1.org/docs/2024/digital-link-quick-start-guide
- GS1 UK, how to create a GS1 Digital Link URL for a QR code: https://www.gs1uk.org/standards-services/get-market-ready/connect-to-consumer/guides-resources/how-to-create-a-gs1-digital-link-url-for-a-qr-code
- GS1 UK, data you can encode in QR codes powered by GS1: https://www.gs1uk.org/knowledge-hub/what-additional-data-can-you-encode-in-qr-codes-powered-by-gs1
- GS1 US, Sunrise 2027: https://www.gs1us.org/industries-and-insights/by-topic/sunrise-2027
- Videojet, GS1 Sunrise 2027: https://www.videojet.com/us/homepage/resources/learn/gs1-sunrise-2027.html
- GS1 resolver for the example GTIN: https://id.gs1.org/01/09506000134352, checked on 2026-11-07.
- Linkbreakers dynamic slugs, checked in the product on 2026-10-30; the Dynamic short link dialog and the visitors CSV export, checked on 2026-11-07.

## Last reviewed

2026-11-07 by Laurent Schaffner.
