GS1 Resolver: What It Is and Why Your Brand Needs One

A GS1 resolver is the server that makes GS1 Digital Link work. When someone scans a product’s QR code, the resolver receives the request and decides what content to return — product information for a consumer, identification data for a POS terminal, safety data for a regulator.

Without a resolver, a GS1 Digital Link URL is just a URL that goes nowhere.

What a Resolver Actually Does

Think of a resolver as an intelligent router for product information. It sits between the barcode and the content, making decisions in real time:

1. Receives the scan request — Someone scans a product QR code, which sends an HTTP request to the resolver’s domain
2. Parses the identifier — Extracts the GTIN, batch number, serial number, and any other Application Identifiers from the URL path
3. Determines context — Identifies who’s asking (consumer phone, POS terminal, supply chain system) and what they want
4. Routes to content — Returns the appropriate response: a redirect to a product page, JSON product data, a safety document, or any other configured link type

A single scan can be routed to completely different destinations depending on the context. The same code on a bottle of olive oil might show a recipe page to a consumer in France, nutrition data to a consumer in the US, and a product identification number to a checkout scanner.

How Routing Works

GS1 resolvers use three primary routing dimensions:

Link Type

The GS1 specification defines 55 link types — standardized categories of content that a resolver can serve. Common ones include:

Link Type	Code	Typical Use
Product information page	gs1:pip	Consumer product details
Electronic patient leaflet	gs1:epil	Pharmaceutical information
Recipe	gs1:recipeInfo	Food products
Certification information	gs1:certificationInfo	Organic, fair trade, etc.
Safety information	gs1:safetyInfo	MSDS, hazard data
Recall status	gs1:recallStatus	Active recall notices
Promotional offer	gs1:promotion	Current deals, coupons

A consumer scanning a product might request gs1:pip (product info) by default, while a regulatory system might request gs1:safetyInfo.

Language

The resolver can return content in the consumer’s preferred language. A scan from a phone set to Japanese returns Japanese content. A scan from a Spanish-language browser returns Spanish content. The resolver reads the Accept-Language HTTP header and routes accordingly.

Media Type

Different clients expect different data formats. A web browser expects HTML. A POS system expects GS1 product data. An API client expects JSON-LD. The resolver reads the Accept HTTP header to determine the appropriate format.

Resolver Architecture Options

1. Cloud-Hosted Resolver (Most Common)

A managed service that handles all resolver infrastructure:

Pros:

• No infrastructure to manage
• Automatic scaling for scan volume spikes
• Global CDN for low-latency responses worldwide
• Provider handles GS1 conformance updates

Cons:

• Ongoing subscription cost
• Data is hosted by a third party
• Dependent on provider’s uptime

This is what Sprouter provides — a fully managed, GS1-conformant resolver as part of the platform.

2. Self-Hosted Resolver

Running your own resolver on your infrastructure:

Pros:

• Full data control
• Custom business logic
• No third-party dependency

Cons:

• Significant engineering effort to build and maintain
• Must achieve and maintain GS1 conformance certification
• Global availability requires your own CDN/edge infrastructure
• You handle all scaling, monitoring, and security

GS1 provides an open-source reference implementation that can be a starting point, but production deployment requires substantial work.

3. Custom Domain on Managed Resolver

A hybrid approach: use a managed resolver service but point your own domain at it:

Pros:

• Brand-consistent URLs (resolve.yourbrand.com/01/... instead of sprouter.gs/01/...)
• Managed infrastructure
• Portability — you can move the domain to another provider

Cons:

• DNS configuration required
• Slightly more setup complexity

Sprouter supports custom resolver domains for enterprise customers.

What “GS1 Conformant” Means

GS1 maintains a conformance program for resolvers. A conformant resolver must:

• Correctly parse GS1 Digital Link URIs per the specification
• Support link type routing
• Support language-based routing
• Return appropriate HTTP headers and status codes
• Handle compressed Digital Link URIs (for DataMatrix)
• Pass GS1’s conformance test suite

This matters because non-conformant resolvers may work for basic use cases but fail in edge cases — incorrect parsing of Application Identifiers, missing support for compressed URIs, incorrect redirect behavior. POS systems and supply chain scanners rely on precise spec compliance.

Sprouter is a registered GS1 Solution Provider with a fully conformant resolver implementation.

Why You Can’t Skip the Resolver

Some brands consider encoding a direct URL in their QR codes — pointing straight to a product page without a resolver in between:

https://mybrand.com/products/olive-oil-500ml

This approach has critical problems:

1. No POS compatibility. POS scanners need to extract the GTIN from the URL structure. A resolver URL following the GS1 Digital Link spec allows this. A direct product page URL doesn’t.

2. No multi-purpose routing. Without a resolver, the code can only link to one destination. You can’t serve different content to different audiences.

3. No updateability. If you redesign your website and URLs change, every printed code is broken. A resolver decouples the printed code from the destination — you update the resolver mapping, not the packaging.

4. No analytics. A resolver logs every scan event (time, location, device, link type). Direct URLs give you standard web analytics at best.

5. No GS1 compliance. The GS1 Digital Link specification requires a conformant resolver. Direct URLs don’t qualify.

Choosing a Resolver Provider

When evaluating resolver providers, assess:

Conformance

Is the provider GS1-conformant? Have they passed the conformance test suite? A provider that claims “GS1 compatible” without conformance certification may not implement the full specification.

Supported Link Types

How many of the 55 GS1 link types are supported? At minimum, you need gs1:pip (product information) and basic device detection. Specialized needs (ePIL for pharma, recipe for food) require those specific link types.

Uptime and Performance

Your resolver must be available 24/7 with low latency worldwide. A consumer scanning a product in a store won’t wait 3 seconds for a response. Target: 99.9%+ uptime, sub-200ms global response time.

Scalability

Can the resolver handle scan spikes? If a product goes viral or a recall drives mass scanning, the resolver must not buckle.

Analytics

What scan data is captured and how is it presented? Useful metrics include scan volume, geographic distribution, device types, time-of-day patterns, and link type usage.

Integration

Does the resolver integrate with your existing systems? PIM (Product Information Management), ERP, EPCIS, and marketing platforms all benefit from resolver integration.

Getting Started

If you’re approaching the GS1 Sunrise 2027 deadline and need a resolver:

1. Assess your needs — How many products? What content types? What markets? Use our compliance checklist to start
2. Choose your approach — Managed resolver, self-hosted, or hybrid
3. Configure your products — Map GTINs to content, set up link types, configure language routing
4. Generate QR codes — Create GS1-compliant codes pointing to your resolver
5. Monitor and optimize — Track scan analytics and refine content based on consumer behavior

Sprouter provides a managed, GS1-conformant resolver with 55 link types, device-aware routing, and enterprise-grade analytics. See the full GS1 platform overview or contact our enterprise team for custom requirements.