A QR code can take someone to your website. A GS1-Conformant Resolver goes further: it connects an identified product to a set of related resources, tells applications what each link is for, and lets them request the information they actually need. That makes the code useful long after the first purchase — for cooking, setup, maintenance, troubleshooting and warranty registration.
This is an independent explanation of the GS1-Conformant Resolver Standard, release 1.2.1, checked on 2 November 2026. gtin.app is not affiliated with or endorsed by GS1.
A resolver is a directory, not just a redirect
A basic redirect says “go to this page”. A resolver can say “here is the product page, here are its instructions, here are its FAQs, and here is where to register it”. An ordinary phone camera can still reach a sensible default destination, while a product-support app can go directly to the instructions instead of searching your website.
The standard defines how those links are described, requested and returned. It does not prescribe your website addresses, require every product to have every link type, or write the content for you. You supply the relevant destinations and keep them accurate. A food product may have recipes; a washing machine may have installation instructions and a registration form.
Recipes, FAQs, manuals and registration: the actual link types
A link type gives an address a shared meaning. In this guide, gs1: is shorthand for https://gs1.org/voc/. These terms are defined in the official GS1 link-type vocabulary; the destinations described below are practical examples, not mandatory content for every product.
| Resource | GS1 link type | What it points to |
|---|---|---|
| Recipes | gs1:recipeInfo | A recipe website or collection showing how to use the food or ingredient. |
| FAQs | gs1:faqs | Product-specific questions, troubleshooting answers and common problems. |
| Manuals & assembly instructions | gs1:instructions | A manual, assembly PDF or usage instructions. “Manual” is a content label, not a separate GS1 link type. |
| Getting started | gs1:quickStartGuide | The essentials needed to start using the product. |
| How-to guides & videos | gs1:tutorial | Step-by-step tutorials, online classes or how-to videos. |
| Service & maintenance | gs1:serviceInfo | Cleaning, maintenance and servicing instructions. |
| Warranty registration | gs1:registerProduct | An entry point for registering ownership, including for warranty purposes. |
| Contact support | gs1:support | A helpdesk, chat service, email contact or other source of help. |
| Product information | gs1:pip | The consumer-facing page for this specific product, rather than a generic brand homepage. |
| Safety & recall checks | gs1:safetyInfo / gs1:recallStatus | Safety information and a separate recall-status resource; recallStatus is typically an API. |
A PDF manual and an assembly video can both be instructions. Their titles, languages and media types help an application choose between them. For regulated healthcare content, use the dedicated vocabulary terms such as gs1:eifu or gs1:epil where appropriate; the generic gs1:instructions term is not intended for those regulated applications.
What happens when a phone or app asks?
1. A normal scan: follow the default
With no more specific preference, the resolver redirects to the product's default link. This could be a useful product hub with clearly labelled instructions, FAQs and support — it need not be a generic marketing homepage. The printed Digital Link remains the product identity; the destination is managed separately.
2. A targeted request: go straight to the answer
An application can add the case-sensitive linkType parameter. For example, a support app could request:
https://brand.example/01/09506000134352?linkType=gs1:instructions
Or an ownership app could request:
https://brand.example/01/09506000134352?linkType=gs1:registerProduct
When the requested link type is available, the resolver redirects to the matching resource. When it is not available, the current standard requires 404 Not Found, rather than silently sending the app to an unrelated default page. Where selection remains ambiguous, a 300 Multiple Choices response can offer the available choices. Apps should handle these outcomes rather than assume every product has a manual or registration service.
3. Discovery: ask for the complete linkset
A linkset is a machine-readable directory of the available resources. A client can request it with ?linkType=linkset, or send the HTTP header Accept: application/linkset+json. The resolver returns the linkset instead of redirecting. The JSON response follows the Linkset standard (RFC 9264) and the GS1 linkset schema.
The links identify their target addresses and relationships to the product; attributes such as title, language and media type describe the resources. An app can use these to show “Read the manual”, “See recipes” or “Register this product” without guessing from a website's navigation. The resolver also publishes a description of its capabilities at /.well-known/gs1resolver.
4. Match language, format and product detail
A request can include preferences such as language and media type. These are matched against the available link attributes, not a guarantee that every translation or format exists. Multiple language-aware defaults through gs1:defaultLinkMulti are optional, so check the resolver's supported behaviour.
Batch or serial qualifiers can identify more specific resources. For qualified product requests, linksets also include inherited links from broader levels up to the primary identifier: shared model instructions can coexist with more specific batch or serial information. This only works when those resources and associations have actually been configured.
Why this matters for customer support
Customers often contact support because they cannot find the right answer — not because the answer does not exist. A product-aware scan removes the “which model do you own?” search, and typed links remove the “where is the manual?” search.
- Scan the actual product. A compatible app reads its GTIN and any batch or serial qualifiers present.
- Discover relevant resources. It obtains the linkset or requests FAQs, instructions or a quick-start guide directly.
- Offer self-service first. Show the relevant answer, guide, recipe or maintenance instructions for that product.
- Escalate with context. If the customer still needs help, open the support destination. Your app can pass product context through a separately designed, consent-aware integration.
- Keep helping after purchase. Make registration and service information easy to find as ownership continues.
This can reduce avoidable enquiries, improve first-contact resolution and shorten time spent identifying products. Those are potential benefits, not guaranteed savings: measure resource usage, unresolved questions and support outcomes. The resolver itself does not create support tickets, register warranties or grant access to private customer records.
Typed links and schema data do different jobs
The resolver tells an app where to go; structured data tells it what the content means. A gs1:recipeInfo link points to a recipe website. That page may separately publish schema.org Recipe data. An instructions link might lead to a PDF, a video or a structured guide. A linkset is not the same thing as the full product record, FAQ answers or manual text.
Using both makes a stronger foundation: predictable discovery at the resolver, clear content and structured data at the destination. Compatible apps and AI assistants can then find authoritative resources more directly, but they must implement discovery, retrieve the resources and interpret them. A resolver does not automatically make every assistant aware of your product or guarantee search visibility.
Start simply now; prepare for richer apps later
- Quick start: use a valid Digital Link URI on a domain you control and send scans to an existing product page. A simple redirect is useful, but it is not proof of GS1 resolver conformance.
- Next step: catalogue your existing FAQs, manuals, recipes, guides and registration destinations. Assign the appropriate link types and meaningful titles rather than producing new content unnecessarily.
- Future-ready discovery: choose a resolver that exposes conformant linksets, handles explicit link requests and supports the language, format and qualifier behaviour your products need. Test with real clients, including missing-link requests.
- Richer support: improve structured destination content, connect support workflows where needed, and keep link ownership, availability and updates under control.
You can add destinations behind the same printed code as your service improves, provided you retain control of its domain and keep that address working. “Future-ready” is an interoperability goal, not an automatic guarantee of compliance with every product-passport or sector-specific rule.
Where SmartLinks fits
SmartLinks.app is a practical place to explore turning a packaging scan into an ongoing product relationship, rather than a one-off website visit. Its Digital Link offering advertises link management, routing and localisation; its product overview describes manuals, owner registration and support queries.
The opportunity is to bring the product's useful destinations together: recipes for food, setup guides for new owners, FAQs for common problems, and registration or human support when needed. A managed service can be a more practical route than building and maintaining all of this yourself.
When evaluating SmartLinks for an app-discovery deployment, ask to see a real product's linkset, explicit link-type requests, missing-link behaviour and the relevant language or serial-level features. These are advertised product capabilities, not an independently verified GS1 conformance assessment. This guide does not claim that every example above is currently implemented by SmartLinks.
Official references
- GS1-Conformant Resolver Standard 1.2.1 — normative request, selection and response behaviour.
- GS1 Web Vocabulary: link types — the standard names and their meanings.
- GS1 resolver artefacts — schemas and supporting implementation resources.
- RFC 9264: Linkset — the underlying linkset format.
For the basics, read how GS1 Digital Link works, or build and inspect a Digital Link URI.