What a GS1 resolver actually does

Updated July 2026

A resolver is the server that receives a scan of your Digital Link URL and decides where to send it. It sounds like a redirect service. The difference is what it can do that a redirect cannot.

One code, many destinations

The same symbol should serve different audiences. A consumer wants ingredients. A trading partner wants a spec sheet. A regulator wants safety data. A recall system wants to know if this specific lot is affected.

A conformant resolver handles this through link types. The scan arrives, the resolver looks at who is asking and what they asked for, and routes accordingly:

• ?linkType=gs1:pip — the consumer product information page
• ?linkType=gs1:recallStatus — recall information for this item or lot
• ?linkType=all — the full machine-readable linkset, so another system can discover everything available

Requesting application/linkset+json in the Accept header returns the same linkset. This is how machine-to-machine integration works without anyone agreeing on a bespoke API.

Context-aware routing

A conformant resolver can route by language and country. The same printed code can open a French page in Québec and an English page in Ohio — without reprinting anything.

Lot-level overrides

This is the capability that justifies the whole architecture. If lot LOT2027A is recalled, you point that one lot at a stop-sale notice while every other lot continues to resolve normally. No reprint, no blanket recall page for unaffected stock.

Why a URL shortener is not enough

Shorteners give you a redirect and analytics. They typically do not parse GS1 syntax, do not serve linksets, cannot route by link type, and — most importantly — the URL belongs to the shortener. When you print their domain on a million packages, you have made their business continuity your problem.