The resolver

The resolver behind the code — conformant, programmable, on your domain.

A GS1-conformant, programmable Digital Link resolver: linkset responses, content negotiation, and routing by geo, batch, serial and scan-count — with a batch-recall switch. Built to the GS1 resolver standard.

Plainly

The resolver decides what a scan returns

When someone scans the code on your pack, something has to answer: a shopper gets your product page, a recalled batch gets a recall notice, and a retailer's system asking for data gets machine-readable JSON. The service that makes that decision is the resolver — and whoever runs it controls the scan. With xengoroute, it runs on your domain.

Unsure whether you need a redirect or a full resolver? The plain-English guide: what a Digital Link is.

Conformance, stated honestly

Built to the GS1 Digital Link resolver standard

"Conformant" has a technical meaning, and every claim below is literal:

Programmable

Routing rules, not just redirects

Think of it as a programmable edge for GS1 identifiers: route by geography, language, device, batch, serial, scan-count or time. Send EU scans to the e-label, first scans to registration, the tenth scan of a "single-use" serial to an anti-counterfeit alert.

Batch-recall switch

Flip a lot, not a label

Mark a batch or range as recalled and every scan of it — across the whole catalogue — returns the recall notice. No reprint, no delay.

Same pack, no reprint

Redirect today, resolver tomorrow

Start on the redirect tier and upgrade to the conformant resolver by changing plan. The code on the shelf never changes.

Signed events

Every resolve, reported

Each resolution can fire a signed webhook — recall scanned, wrong-region scan, spike on a lot — into Slack, Teams or your ERP.

See it working against a recall scenario in the food & drink use case.

Put a real resolver behind your codes.

The Resolver tier is sales-assisted while it's new — talk to us and we'll walk your catalogue through it.