How it works

One service: generate the Digital Link, run the resolver, read every scan.

Most tools stop at the QR image. xengoroute generates the GS1 Digital Link, runs the resolver behind it on your own domain, and turns every scan into analytics and a signed event — one platform, self-serve.

Three kinds of tool — only one runs the whole thing

A Digital Link you can't re-point is a Digital Link you'll have to reprint

Generate-and-walk-away

A code, then silence

Free generators hand you a static image and end the relationship. No resolver behind it, so once it's printed it can never change — and nobody can tell you it was ever scanned.

Resolver-only

Re-pointable, but thin

A redirect exists, so the code can change — but the own-domain, the analytics depth, or the scan-time events are missing or gated behind an enterprise quote.

xengoroute — full stack

Generate + resolve + analyse

One service that builds the code, runs the resolver on your domain, and turns every scan into analytics and a signed event. We don't walk away after any layer.

1 · Generate

Correct codes, on your domain, print-ready

Build a GS1 Digital Link — GTIN, batch, expiry, serial — with GTIN and company-prefix validation before anything reaches a press. Codes live on a domain you own, and export as prepress-grade vector artwork a printer can drop straight into a job. Bulk-import a whole catalogue via CSV or the API.

https://go.yourbrand.com/01/09506000134352/10/LOT01/17/271231 ← GTIN · batch · expiry, one URL

2 · Resolve

The resolver decides what every scan returns

Behind every code sits our resolver — the part most tools don't run. Re-point a destination and every printed pack follows instantly. Step up to the conformant Resolver tier for linkset responses, content negotiation and programmable routing by geo, batch, serial or scan-count — including a batch-recall switch.

The resolver, in full →

3 · Analyse

Every scan, an event your systems can act on

Per-scan analytics — geo (resolved offline, the shopper's IP never leaves to a third party), device, referrer, bot detection — plus a signed webhook with retries and a delivery log, and 25 alert channels. A scan can trigger a recall check, a grey-market alert, or an ERP update. Rivals' analytics stop at the click; ours start there.

The route story

Same code, same pack — the plan changes, the shelf doesn't

Start on a simple redirect and move to the full conformant resolver by changing your plan. The URL printed on the pack never changes — which is the entire point of putting a route, not a destination, on your product.