OriginSpan

Identity and Resolution Guide

What is a product identity resolver?

A product identity resolver keeps a durable product identifier stable while directing people and systems to the right information, service, or API for their context.

Separate product identity from destination

A QR code, NFC tag, Data Matrix symbol, or typed URL can carry a product identifier, but the identifier should not be permanently coupled to one web page. A resolver acts between the identifier and the available resources so destinations can change without changing the identity printed on the product.

That separation is important because packaging can remain in market for years while manuals, warranty services, safety notices, compliance disclosures, support workflows, and commerce experiences continue to evolve.

Resolve one identity for many audiences

The same product may need to provide different resources to a consumer, retailer, technician, regulator, marketplace, or software application. Resolution rules can consider the requested link type, geography, language, lifecycle state, product granularity, channel, or authorization level before returning the appropriate destination.

Human-readable experiences

Product pages, instructions, onboarding, warranty, service, recalls, parts, and post-purchase experiences.

Machine-readable resources

Structured product data, APIs, certificates, traceability records, and links discoverable by software systems.

Lifecycle-aware routing

Different responses before sale, after registration, during service, after a recall, or at end of life.

Identity-level routing

Model, GTIN, batch, lot, component, or serialized-unit experiences using the same resolution foundation.

GS1 Digital Link provides a standards-based way to express GS1 identifiers in web URIs. A conformant resolver can interpret those identifiers and make multiple related resources discoverable instead of treating the URI as a single fixed redirect.

OriginSpan uses customer authorized GS1 identifiers and Digital Link style addresses. Standards conformance claims are communicated after the applicable specification and conformance validation is complete.

Practical distinction: a QR-code generator creates a data carrier. A product identity resolver governs what a persistent identity can deliver over time.

OriginSpan resolver capabilities

  • Durable resolver addresses connected to active product and passport information.
  • Human readable pages and machine readable structured resources.
  • QR delivery, efficient HTTP behavior, locale negotiation, and translated public content.
  • Separate public and authenticated restricted product information.
  • Activation, replacement, revocation, and history preservation.
  • Customer controlled resolver domains with an OriginSpan fallback address when included in scope.

Customer domains, standards validation, availability, and operating requirements are defined according to the engagement scope and customer identity strategy.

See OriginSpan platform capabilities for the broader identity, lifecycle, evidence, trust, and localization overview.

Requirements for durable product resolution

A resolver becomes part of the product infrastructure, so its operating requirements extend beyond creating redirects.

  • Stable company-controlled domains: product URIs should remain durable even if applications or vendors change.
  • High availability: printed identities may be scanned anywhere and cannot be patched after distribution.
  • Standards-aware parsing: identifiers, qualifiers, and supported link types must be interpreted consistently.
  • Human and machine responses: browsers and software clients need appropriate formats, headers, and discovery behavior.
  • Governed configuration: changes to links and rules need access control, validation, audit history, and rollback.
  • Privacy and security: analytics, personalization, authorization, and geographic logic should minimize unnecessary data collection.
  • Portability: identity data and mappings should be exportable so product continuity does not depend on one implementation.

A resolver within connected-product architecture

Resolution is one layer of a broader connected-product platform. It should obtain authoritative product context from ERP, PIM, PLM, quality, service, CRM, commerce, and supply-chain systems rather than becoming an isolated replacement for those systems.

  1. Identity layer: establish durable model, GTIN, batch, lot, component, or serial identities.
  2. Resolution layer: evaluate the identity, requested resource type, and applicable business rules.
  3. Data and integration layer: obtain trusted product and lifecycle information from systems of record.
  4. Experience and API layer: deliver the appropriate page, document, action, or structured response.
  5. Event and governance layer: record operational events, monitor availability, and audit configuration changes.

How to evaluate resolver platforms

When comparing a hosted QR or connected-product service, ask:

  • Does the company control the identity domain and the product URIs?
  • Can one identity expose multiple typed resources?
  • Can destinations change without reprinting packaging?
  • Does the platform support model, batch, lot, and serialized identity?
  • Can it integrate with authoritative enterprise systems?
  • Does it support both human-readable and machine-readable responses?
  • Are configuration history, export, availability, and lifecycle continuity built in?
  • Are standards-conformance claims supported by testable evidence?

Standards references

The following primary sources define the standards context for product identity resolution:

Pilot a durable identity and resolver layer.

OriginSpan is working with design partners on persistent identity, resolution, enterprise integration, and lifecycle experiences.

Talk to OriginSpan