The 2D Barcode Sunrise (GS1 Digital Link) — and how to run your own infrastructure

Retail is moving to QR — target 2027

The barcode on the back of every product is being replaced. Under GS1’s global “Sunrise 2027” program, the familiar 1D UPC/EAN barcode is giving way to a 2D QR code powered by GS1 Digital Link — one scannable code that works at the checkout and takes a shopper straight to product information, provenance, promotions or authentication. This is the shift some are calling “GS2.”

What actually changes

A GS1 Digital Link is just a URL that encodes a product’s identifiers in a standard path — the GTIN, and optionally a batch/lot or serial:

https://id.example.com/01/09506000134352

The leading 01 is the GS1 Application Identifier for a GTIN. A resolver at id.example.com receives the scan and 302-redirects it to whatever that product should show right now — a spec page, a how-to video, a recall notice, a reorder link, or a plain product page. Point-of-sale systems read the same GTIN out of the QR to ring up the sale. One code, two audiences.

Two ways to run it

You can pay a QR SaaS (Bitly, Beaconstac/Uniqode, Scanova, QR TIGER, Flowcode…) to host the dynamic codes and the redirects for you — fast to start, but you rent the redirect, pay per feature, and your scan data and destinations live in their account. Or you can run your own resolver so every product code resolves through your domain.

Running your own is very much in reach — a GS1 Digital Link resolver is a small web service that maps GTIN paths to destinations. Benefits of owning it:

• No per-scan fees or per-feature paywalls — it’s your web server.
• Your data — first-party scan analytics, no third party in the path.
• Your domain, forever — codes printed on packaging keep working even if a vendor shuts a product line.
• Standards-compliant — a conformant resolver interoperates with GS1 tooling and other links.

Run it as a vendor with FrontierStack

FrontierStack is built to stand up and keep this kind of small, always-on web infrastructure running on your own Mac or a linked server:

• Host the resolver — run the resolver service behind Apache/Nginx as a normal site (a vhost on id.yourdomain.com), with PHP/Node/Go as you prefer. Open-source resolvers exist, including GS1’s reference implementation.
• TLS that never lapses — issue and auto-renew the certificate for the resolver domain; a lapsed cert would break every code at once, so FrontierStack watches its expiry.
• DNS & edge — point id.yourdomain.com and (optionally) put it behind Cloudflare from the same app.
• Monitor every code — the QR & Link Health pane checks, on a schedule, that each product code still resolves to the right destination, warns on unexpected destination changes, and alerts you (via your messaging gateways) the moment one breaks — for your own resolver or any hosted provider.
• Back it up — the GTIN→destination mapping is just data; keep it under version control and scheduled backups like the rest of your stack.

Not ready to self-host? Manage the SaaS instead

If you use a hosted QR service today, FrontierStack still helps: connect Bitly, Rebrandly, Short.io or Dub.co to see link and click totals, watch API connectivity, and health-check the destinations of the codes you’ve printed — independent of the provider. You can migrate to your own resolver later without reprinting, as long as the printed codes point at a domain you control.

The practical takeaway before 2027: print your product QRs against a domain you own, stand up a resolver you control, and monitor every code so a silent break never costs you a scan.