A GS1 resolver is the web service that answers when a GS1 Digital Link is scanned. The printed code holds the question, one URL naming a product, batch or item; the resolver decides the answer for each audience. It is the piece of infrastructure that turns a static symbol into different correct behaviours for a shopper, a checkout, a regulator and a machine.
What the standard requires of it
The GS1-Conformant Resolver Standard pins the behaviour down: content negotiation (HTML for browsers, structured data for machine clients), linkset responses listing every available link in the RFC 9264 format, redirect semantics for requested link types, honest HTTP status codes (400 for malformed URIs, 404 for unknown items, never errors hidden inside 200s), CORS so browser scripts can read answers, and a resolver description file at a well-known address. GS1 publishes a conformance test suite; Onpack runs all of its checks continuously, a claim examined in conformant vs certified.
What a scan looks like from the inside
A request arrives for /01/09506000134352/10/LOT42. The resolver parses the identifiers, loads the product, overlays the batch record, then asks: who is asking, from where, in which language? A phone in Madrid gets the Spanish page, with EU passport data. The same phone in California sees the Prop 65 warning. A POS till asking for JSON-LD gets structured product facts. If LOT42 was recalled an hour ago, every one of those answers changes immediately, which is the property that makes recall communication through the pack possible.
Why brands should not build one
None of this is exotic engineering, but all of it is permanent responsibility: the URLs are printed on physical goods with a decade of shelf life, so the service needs uptime, conformance maintenance and a succession plan. That is a strange burden for a beverage brand to carry. The build-vs-use economics are covered in the cost breakdown, and the selection criteria in choosing a resolver.
The strategic property: separation of print from truth
The resolver is what makes the printed code permanent and the behaviour editable. Destinations change after printing, batches gain recalls, countries gain their own routes, and none of it touches artwork. Once a brand internalizes that the pack is an interface and the resolver is the implementation, most of the 2027 agenda reduces to filling in settings.
Common questions
Is a resolver just a URL redirector?
No. Redirecting humans is one behaviour of many. A conformant resolver also serves structured data to machines, linksets on request, correct errors, and jurisdiction-aware content, all defined by the GS1 standard.
Can I point my Digital Link codes at my own website instead?
Your site can be the human destination, but something still has to answer machines and implement the standard behaviours. That is exactly the role of the resolver sitting at the printed URL, redirecting people to you.
What is the resolver description file?
A JSON document at /.well-known/gs1resolver declaring what the resolver supports. The conformance standard makes it mandatory, and test suites check it first.
How do I test whether a resolver is conformant?
GS1 publishes the resolver conformance test suite. Run it against the candidate, or ask the operator for their results; Onpack runs the full suite in continuous testing.