No account needed

GS1 Digital Link QR & SGTIN-96 Encoder

Sponsored by Avancir Print

Generate a GS1 Digital Link QR code, a retail barcode, and an SGTIN-96 RFID tag encoding from one GTIN and serial number — so all three carriers describe the same item instead of three near-misses.

Everything runs in your browser. Nothing you type is uploaded or stored. Paste an EPC or a Digital Link URL you already have and the tool works backwards, so you can prove a tag and a QR code really do agree.

Paste an EPC

A 24-character SGTIN-96 EPC hex value, or an urn:epc: URI. A GS1 Digital Link URL works too.

No EPC handy? Try this sample

One product identity — GTIN 00614141123452, serial 100000001 — carried three ways. Load sample EPC above fills the box with the SGTIN-96 EPC so you can decode it.

Digital Link QRScans to id.gs1.org
EAN-13 barcodeGTIN only — no serial
SGTIN-96 EPC (hex) 3034257BF40C0E4005F5E101

The RFID tag encoding — GTIN and serial in one 96-bit value. This is what the button loads.

Your product identity

One GTIN and serial number drive all three outputs, so the barcode, the QR code, and the RFID tag can't disagree.

Digits only for SGTIN-96, up to 274,877,906,943. Leave it blank for a GTIN-only Digital Link.

An AI is a GS1 Application Identifier — a two-digit code saying what the value after it means. AI 10 is a batch or lot number; AI 17 is an expiration date, written YYMMDD.

The domain used to build the web address for your Digital Link. Optional for the barcode and the RFID tag, but the QR code needs a domain to point at — leave it blank and there's no web address to encode. Use a domain you control that will answer these URLs; a shopper who scans one that doesn't resolve gets a dead page.

Filter 1 covers a single retail item — one sellable unit rather than a case or a pallet.

Generated output

Retail barcode

GS1 Digital Link QR

SVG stays sharp at any label size — use it for artwork and thermal printer software. PNG exports at 3× for slides and packaging comps.

SGTIN-96 RFID tag encoding

EPC (hex)
EPC Tag URI
Pure Identity URI

Copy the 24-character hex into your RFID printer or encoder, encode a tag, then read it back and confirm it matches.

SGTIN-96 bit layout for the values above
FieldBitsValue

Decoded results

Read-only — this is what the value you pasted actually contains.

EPC (hex)
EPC Tag URI
Pure Identity URI
SGTIN-96 bit layout of the decoded EPC
FieldBitsValue
Share this tool

GS1 Sunrise 2027

What Sunrise 2027 means for you

GS1's Sunrise 2027 initiative asks retail point-of-sale systems worldwide to be able to scan 2D barcodes — QR codes carrying GS1 Digital Link — at the checkout by the end of 2027, alongside the linear UPC and EAN barcodes they read today. For brand owners that means one thing in practice: the code on your pack stops being just a number and starts being a web address that also contains that number.

The transition is additive, not a switch-over. Your existing barcode keeps working. What changes is that a single QR code can carry the GTIN for the till, a serial number for traceability, and a link that opens your product page for the shopper — while the RFID tag inside the same item carries a matching serialised identity for inventory. The three only work together if they encode the same GTIN and serial, which is what the tool above is built to check.

What a brand owner has to do

  1. Confirm your GS1 company prefix and its digit length on your GS1 licence.
  2. Decide whether you're serialising items — a serial is required for RFID, optional in the QR.
  3. Stand up a resolver domain (for example id.yourbrand.com) that answers Digital Link URLs.
  4. Generate the Digital Link QR and place it on artwork alongside the existing barcode.
  5. Encode RFID tags with the SGTIN-96 EPC built from the same GTIN and serial.
  6. Scan-test all three carriers on a real product before the print run.

Anatomy of a GS1 Digital Link URL

A GS1 Digital Link is an ordinary HTTPS URL whose path is built from GS1 Application Identifiers (AIs). Each AI is a two-digit code that says what the value after it means. Read left to right, it's a sentence: on this domain, the product with this GTIN, batch, and serial number.

https://id.yourbrand.com/01/00614141123452/21/100000001?17=271231
└──────── resolver ────────┘└AI┘└── GTIN-14 ──┘└AI┘└ serial ┘ └AI┘└ date ┘

The Application Identifiers you'll use most

AIMeaningFormatWhere it goes
01GTIN — the product identifier14 digitsFirst path segment. Always required.
10Batch or lot numberUp to 20 charactersPath segment, before the serial.
21Serial number — identifies one individual itemUp to 20 charactersPath segment, last of the qualifiers.
17Expiry dateYYMMDDQuery parameter, not a path segment.

Why the order matters

GS1 splits AIs into key qualifiers and data attributes. Key qualifiers — batch (10), then serial (21) — narrow down which thing you mean, so they sit in the path in that fixed order after /01/. Data attributes such as expiry date (17) describe the thing, so they belong in the query string. Reorder them and a strict resolver won't recognise the URL. The tool above always emits the canonical order for you.

What the resolver actually does

Generating the URL is the easy half. The resolver is the service sitting at your domain that decides what comes back when someone opens that URL — a product page for a shopper, a spec sheet for a technician, a recall notice, or a machine-readable response for another system. The GTIN in the path scans at the till whether or not the domain resolves, but a shopper who scans a domain that answers nothing gets a dead page. Point the resolver domain at something you control before the code goes on artwork.


Carrier selection

What goes where: barcode, QR, and RFID tag

The same product can carry three codes, and each holds a different amount of the story. This is the most common source of confusion — and of mismatched data.

Linear

Barcode — UPC, EAN, ITF-14

The GTIN and nothing else. Every point-of-sale scanner in service today reads it, which is exactly why it isn't going away.

Holds
GTIN only
Read by
Every POS scanner today
Typical use
Price lookup at the checkout, case labels

2D

Digital Link QR

A URL that contains the GTIN, plus batch, serial, and expiry if you need them. One symbol serves the till and the shopper's phone.

Holds
GTIN plus optional batch, serial, expiry — as a URL
Read by
2D-capable POS, and any phone camera
Typical use
Checkout, product info, recalls, authenticity

RFID

RFID tag — SGTIN-96

A serialised identity in 96 bits of EPC memory. No URL, no line of sight, and hundreds of items readable at once.

Holds
GTIN plus a numeric serial, 96 bits, no URL
Read by
UHF RFID readers — no line of sight needed
Typical use
Inventory counts, loss prevention, shipping

The rule of thumb: the barcode says what the product is, the RFID tag says which one it is, and the Digital Link QR can say both — and take a shopper somewhere useful.


Step by step

How to generate your codes

A Digital Link QR code

  1. Enter your GTIN in step 1. Any valid length works — we pad it to GTIN-14 and verify the check digit.
  2. Add a serial number if you're serialising items, plus batch or expiry if you need them.
  3. Set the resolver domain to a domain you control that will answer these URLs.
  4. Check the assembled URL under the QR code.
  5. Download SVG for artwork, or PNG for a quick test print.

An SGTIN-96 RFID tag

  1. Keep the same GTIN and serial — the whole point is that all three carriers agree.
  2. Set your company prefix length from your GS1 licence certificate. It decides the partition value.
  3. Pick a filter value — for a single retail item that's 1, point of sale item.
  4. Copy the 24-character EPC hex into your RFID printer or encoder software.
  5. Encode a tag, read it back, and confirm the hex matches.

Decoding what you already have

  1. Switch the tool to Decode.
  2. Paste an EPC hex value, a urn:epc: URI, or a Digital Link URL.
  3. The GTIN, serial, filter, and prefix length fill in automatically.
  4. All three outputs rebuild from what was decoded, so you can confirm a tag and a QR describe the same item.

Understanding SGTIN-96

SGTIN stands for Serialised Global Trade Item Number: a GTIN plus a serial number. The 96 is how many bits it occupies in an RFID tag's EPC memory bank — the standard tag size, and the reason SGTIN-96 is the most widely used EPC encoding in retail.

The bit layout

Those 96 bits divide into six fields: an 8-bit header (always 0x30, meaning SGTIN-96), a 3-bit filter value, a 3-bit partition, the company prefix, the item reference, and a 38-bit serial. The tool shows the exact split for your input.

Company prefix length and the partition value

The company prefix and item reference share a fixed 44 bits, but the boundary between them moves depending on how long your GS1 company prefix is. The partition value records where that boundary sits, so a reader can split the number back apart.

PartitionCompany prefixItem reference (incl. indicator digit)
012 digits / 40 bits1 digit / 4 bits
111 digits / 37 bits2 digits / 7 bits
210 digits / 34 bits3 digits / 10 bits
39 digits / 30 bits4 digits / 14 bits
48 digits / 27 bits5 digits / 17 bits
57 digits / 24 bits6 digits / 20 bits
66 digits / 20 bits7 digits / 24 bits

Filter values

The filter isn't part of the product's identity — it's a hint that lets a reader ignore tags it doesn't care about. 1 means a point-of-sale item, 2 a full case, 4 an inner pack, 6 a unit load such as a pallet. When in doubt for a single retail item, use 1.

Serial number limits

The 38-bit serial field holds a whole number from 0 to 274,877,906,943. It can't store letters, and it can't preserve leading zeros — 000123 comes back as 123. If your serials contain letters or must keep leading zeros, you need SGTIN-198, which stores an alphanumeric serial in 198 bits and requires tags with a larger EPC memory bank.


Common mistakes

  • Getting the check digit wrong. The last digit of a GTIN is calculated from the ones before it. Typing it from memory is the most common error we see — leave it off and the tool calculates it for you.
  • A serial that's too long or not numeric. SGTIN-96 caps the serial at 274,877,906,943, digits only. A QR code will happily carry A-1042/B; the 96-bit tag won't. Decide your serial scheme with the tag's limit in mind, not the QR's.
  • Guessing the company prefix length. Change the prefix length and the same GTIN produces a completely different EPC — your tags read as the wrong product. Check the licence certificate rather than inferring it from the digits.
  • A Digital Link domain that doesn't resolve. The QR still scans at the till, because the GTIN is inside the URL. But a shopper who scans it gets a dead page. Point the domain at a working resolver before the codes go on packaging.
  • Reordering the AIs in the URL. /01/…/21/…/10/… looks reasonable but isn't canonical — batch (10) comes before serial (21), and expiry (17) belongs in the query string.
  • Skipping the scan test. Artwork that validates on screen can still fail on press. Print a sample, encode a tag, and read both at the real distance and angle before the production run.

Print · Label · Encode

Printing and encoding at scale

Generating one code is the easy part. Producing thousands of serialised labels — each with a unique Digital Link QR and a matching encoded RFID inlay — is a production problem, not a design problem. Avancir Print handles serialised print-and-encode runs so your QR codes, barcodes, and tags leave the press already agreeing with each other.

  • Serialised runs: unique GTIN and serial pairs across a full production batch.
  • Print and encode in one pass: the label prints and the inlay encodes together, then gets verified.
  • Verified output: tags read back and codes scan-tested before they ship.
Avancir Print label software previewing a serialised barcode label next to a Zebra thermal printer

GS1 & serialisation resource center

Where to go next, whether you're planning for Sunrise 2027, choosing an encoding scheme, or specifying the hardware that prints and reads it.

Articles

Shop the hardware

Frequently asked questions

A Digital Link QR code is a web-enabled 2D symbol holding a URL — a GTIN plus, optionally, serial, batch, and expiry — readable by a 2D point-of-sale scanner or any phone camera, and able to take a shopper to product information. SGTIN-96 is a 96-bit EPC encoding written to a UHF RFID tag's memory: GTIN plus a numeric serial, no URL, read in bulk without line of sight. They aren't alternatives. The same item's QR code and RFID tag can carry the same GTIN and serial, each serving a different part of the product's journey — which is exactly what this tool generates in one pass.
No. Sunrise 2027 asks retailers to be able to scan 2D codes; it doesn't retire linear barcodes. Most brands will carry both on pack for years, which is why this tool generates them from the same input.
Yes — that's the point of GS1 Digital Link. A 2D-capable point-of-sale system reads the GTIN out of the URL, while a phone camera opens the same URL as an ordinary web link.
Only if you want item-level traceability, authenticity checks, or recalls down to an individual unit. A GTIN-only Digital Link is valid and is enough for price lookup. An RFID tag is different — SGTIN always carries a serial.
SGTIN-96 stores a numeric serial up to 274,877,906,943 in 96 bits and fits standard retail tags. SGTIN-198 stores an alphanumeric serial of up to 20 characters but needs 198 bits of EPC memory, so it requires tags with a larger memory bank.
On the licence certificate GS1 issued you. It's the number of leading digits of your GTINs that GS1 assigned; the rest is your own item reference. It isn't carried in a Digital Link URL, so decoding a URL can't tell you what it is.
No. All the encoding, decoding, and image generation runs locally in your browser. Nothing is uploaded and nothing is stored.

Planning for Sunrise 2027?

Getting the encoding right is step one. Choosing the tags, printers, and readers that carry it — and proving the whole chain reads before you commit to a print run — is where most projects stall. Our specialists do this every day.

  • The right encoding: SGTIN-96 or SGTIN-198, matched to your serial scheme and tag memory.
  • The right tags: inlays and labels chosen for your product, packaging, and read environment.
  • The right hardware: RFID printers, encoders, and 2D scanners sized to your volume.
A 2D barcode on a product being scanned at a retail checkout