Encode a normalized GTIN
The builder pads GTIN-8, GTIN-12, and GTIN-13 values to 14 digits for AI (01). GTIN-14 is not a consumer-unit identifier for retail POS.
GS1 Digital Link URI tools · Ambition 2027 for retail
Build a limited GS1 Digital Link URI
GS1's voluntary Ambition 2027 is for retail POS systems worldwide to read and process the GTIN from existing linear and GS1-compliant 2D barcodes by the end of 2027. Keep the existing linear POS barcode during the transition; processing additional data is a separate implementation step.
9:41
Ethiopia Yirgacheffe Single Origin
Coffee beans • Specialty grade
Illustrative content
Origin & terroirFairtrade • 100% organic Arabica
Yirgacheffe, Ethiopia (1,950 m)
Nutrition & ingredients
100% Arabica • 0g sugars / 0 kcal
Sustainability & recycling
Mono-material pouch with plastic packaging
Batch: LOT-2026-A4Best before: 2027-04-30
How GS1 Digital Link Works
One URI can carry product identifiers and resolve to web content
Use a brand-controlled host
A smartphone can open the HTTPS URI. Your host must supply the content or route to a configured resolver; this builder does not provision either.
Add supported qualifiers
Lot (AI 10), serial (AI 21), and expiry (AI 17) can be included. Recall behavior requires your own resolver and operational systems.
GS1 implementation scope
Estimate URI variants and API batches
A planning estimate based on your SKUs and production batches. It is not a cost, compatibility, or compliance forecast.
25 SKUs
12x / year
URI variants per year:
Bulk API requests at max. 500 items:
Final packaging/POS status:
Supported capabilities and important limits
Modulo-10 check digit
The tool checks the supplied GTIN digit. It does not verify GS1 assignment, product identity, symbol quality, or packaging conformance.
Link to product information
The URI can point to a product page or passport run by your systems. QRCodeMaster does not determine DPP compliance.
Browser PNG and dashboard exports
Exports are prototypes. Retail POS use still requires compliant HRI, sizing, quiet zone, placement, print verification, and end-to-end testing.
Use a controlled HTTPS host
Prefer a brand-controlled HTTPS subdomain for on-pack use. The builder checks only the host shape and does not provision a resolver or redirect.
Explicit qualifier fields
Build the supported GTIN, lot, serial, and expiry subset without manually assembling path and query components.
REST batch records
The generic REST endpoint accepts up to 500 saved QR records per bulk request. There are no built-in SAP, Exact, or Akeneo connectors.
Frequently asked questions
What is GS1's Ambition 2027 for retail?
It is a voluntary industry goal, not a hard deadline or a Digital Link version. The minimum goal is to read and process the GTIN from existing linear and GS1-compliant 2D barcodes; additional data processing is separate.
Can our current cash registers scan this 2D QR code?
Possibly, but camera support alone is not enough. Keep the existing EAN/UPC or GS1 DataBar POS barcode during the transition. Consider 2D-only packaging only after pervasive adoption and end-to-end tests with every relevant retailer.
What can a GS1 Digital Link URI look like?
A reference example for the supported subset is https://id.gs1.org/01/{14-digit AI (01) representation}/10/{LOT}?17={YYMMDD}. This tool does not register content at id.gs1.org; a production host or resolver must be configured separately.
Can we create QR records with GS1 Digital Link syntax in bulk?
The REST bulk endpoint can create up to 500 saved QR records per request. It returns record data, not retail-ready symbols; exports need the same GS1, print, and chain validation.
Build the URI, then validate the full chain
QRCodeMaster checks the GTIN digit and supported URI fields. It does not certify the final symbol, packaging, resolver, POS workflow, or regulatory compliance.
Open the GS1 builder