Explaining a resolver to a marketing director or a plant manager usually goes better without the words "HTTP" and "redirect". One analogy works well: a resolver is a receptionist for a product. This article walks through that analogy carefully, then maps each part of it onto what the GS1 standard actually specifies, so you can use the picture without being misled by it.
If you have not met the term before, start with what a GS1 resolver is.
The building and the visitor
Picture a large office building belonging to a fictional cable maker, Volta Cables. Inside are many departments: product information, installation guidance, warranty registration, the trade loyalty scheme, quality and recalls.
Every coil of cable Volta sells carries a QR code. That code is like a visitor's slip of paper with an exact name on it: "Volta Cables, 2.5 sq mm house wire, 90 m coil, batch 26-118, coil 004417". The slip says precisely who the visitor is asking about. It does not say which room to go to.
At the front desk sits the receptionist — the resolver. Every visitor arrives there first.
How the receptionist handles visitors
The visitor who just walks in. Most people arrive with their slip and no particular request. The receptionist sends them to one standard place: the main product office. There is always exactly one such place, so nobody is left standing in the lobby.
The visitor who names a desk. An electrician arrives and says "loyalty scheme, please". The receptionist sends him straight to that desk. An installer asks for "installation guide" and goes to a different room. Same slip, different request, different destination.
The visitor who speaks another language. A visitor addresses the receptionist in Hindi. Instead of sending her to the English-language main office, the receptionist sends her to the Hindi-speaking one.
The visitor asking about one specific coil. The slip names coil 004417, but nobody has set up a desk for that individual coil. The receptionist does not turn the visitor away; they fall back to the desks that serve the whole product line.
The visitor asking for a desk that does not exist. Someone asks for the "sustainability office", but Volta has not set one up for this product. The receptionist says so plainly: no such desk.
The visitor whose request fits two desks equally. If two rooms answer the request equally well, the receptionist lists both and lets the visitor choose.
The visitor who wants the directory. A distributor's purchasing system does not want to be walked anywhere. It wants the list. The receptionist hands over the lobby directory: every desk available for this product, with what each one does.
The precise version
Each part of that story corresponds to something the GS1-Conformant Resolver Standard (Release 1.2.1, August 2026) actually defines.
| In the analogy | In the standard |
|---|---|
| The visitor's slip of paper | The GS1 Digital Link in the code, carrying the GTIN and optionally batch and serial |
| The main product office | The default link. Each identified item has exactly one, and the resolver redirects to it unless the request asks for something else |
| Naming a desk | Requesting a link type from the GS1 Web Vocabulary, for example ?linkType=gs1:loyaltyProgram |
| Speaking another language | The optional gs1:defaultLinkMulti, which lets the default be chosen by language or other details the browser sends |
| Falling back to the product line's desks | Inheritance "up the tree": a serial-level request falls back to links registered at GTIN level |
| "No such desk" | A 404 response when no link matches |
| "Two desks fit, please choose" | A 300 response when several links match equally |
| The lobby directory | The linkset: the full list of links for the item, in RFC 9264 format, requested with linkType=linkset or the header Accept: application/linkset+json. The resolver does not redirect when a linkset is requested |
| The sign on each desk | Each link's title, alongside its target address and link type |
The departments in the story map onto real link types: gs1:pip for product information, gs1:instructions for installation guidance, gs1:registerProduct for registration, gs1:loyaltyProgram, and gs1:recallStatus. Do not invent your own names and present them as GS1 ones; only the terms in the GS1 Web Vocabulary carry shared meaning. How brands combine these into a coherent service is the subject of how one product identity can lead to product info, warranty, loyalty and traceability.
Why the receptionist matters
The main benefit of the arrangement is the same in a building and on a pack: departments can move without reprinting the visitor slips.
If Volta's installation guide moves to a new website next year, only the receptionist's list changes. Every coil already in a warehouse, on a van or behind a wall keeps working. Without a receptionist, every slip would have to carry a room number, and every office move would strand old visitors in empty corridors.
The second benefit is consistency. Because every request passes through one front desk that follows known rules, partners and apps can rely on it. A retailer's app that asks any conformant resolver for gs1:recallStatus knows what kind of answer to expect.
Where the analogy breaks down
Analogies are useful until someone acts on the parts that are not true. Three limits matter here.
The receptionist does not keep the files. A resolver holds links, not content. The product page, the warranty system and the loyalty platform all live elsewhere, and the resolver simply knows where.
The receptionist is not a security guard. In a real building, reception might check your badge. A resolver answers for any well-formed address, including one copied from a genuine pack onto a fake one. Any access control — who may see traceability data, who may claim loyalty points — is enforced by the destination systems, not by the act of resolving. Even the gs1:verificationService link type points to a service that checks the status of an identifier, not whether the item in someone's hand is genuine.
Not everyone visits reception. A supermarket checkout reading the same code does not go to the front desk at all. It reads the GTIN straight from the slip and looks up the price in the retailer's own system, offline. The resolver only matters for devices that open the address as a web link.
Using the analogy well
When briefing colleagues, the receptionist picture answers the most common early questions quickly: why one code can serve many purposes, why destinations can change after printing, and why the brand needs to keep its domain alive. Pair it with the precise table above when the conversation turns to implementation, so that "front desk" becomes "default link" and "directory" becomes "linkset" before anyone writes a specification.
It also helps frame the next decision: does your product need a full receptionist, or would a single signpost do? That trade-off is laid out in resolver vs redirect. And if you want to see the whole route a scan takes before it reaches the front desk, follow how a GS1 Digital Link works, from packaging to browser.