One product identity. More ways to connect.

01

Identity is permanent; information changes

A campaign ends. Instructions change. A new language or customer service becomes relevant. Separating identity from destinations gives the architecture a way to evolve those resources without redefining the product. Keeping issued addresses reachable is an explicit compatibility requirement.

02

A shared identity, different audiences

The Resolver roadmap connects an identity to a default consumer experience and additional discoverable resources. Each resource still applies its own access rules.

• Consumers: product information and configured verification or loyalty experiences.
• Business partners: authorised traceability and EPCIS resources.
• Future services: certificates, instructions and digital product passport resources.

03

Resolver and EPCIS do different jobs

The Resolver answers where related information can be found. EPCIS represents recorded lifecycle events. A resolver can point to an authorised event resource without publishing that resource’s private contents. A simple redirect and a full standards-conformant Resolver are different levels of functionality.

04

Built around tenant ownership

AIQR’s brands and distributors already operate through tenant-specific settings, roles and modules. Resolver development must preserve those boundaries, establish domain and identifier authority, and retain existing URLs. A valid GTIN checksum does not establish brand ownership.

05

Start with a real product

Use your existing GTIN to preview a product, batch or serialized Digital Link. Add product information and a picture, then register to publish and download. Selecting rewards or tracking records intent; configured workflows require additional setup. Recognising an identifier is not proof that a physical product is genuine.