For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Getting Started
    • Introduction
    • Getting Started
    • Tia — Operations Assistant
    • Architecture
    • Security Architecture
  • Onboarding & Plans
    • Onboarding Overview
    • Plans & Subscriptions
    • Tia Credits
  • Tenancy & Governance
    • Roles & Members
    • Audit Log
    • Notifications
    • Economic Operators
  • Authoring Studios
    • Content Studio
    • Theme Studio
    • Advanced Studio (Track B)
  • Product Module
    • Products
    • Custom Fields
    • Global Search
    • Identifiers
    • Product Import
    • Bulk Editing
    • Bulk Updates
    • Resolver & GS1 Digital Link
    • GS1 Digital Link Contract
  • Localisations
    • Overview
    • Market Packs
    • Multilingual Content
  • Domains & Custom Hostnames
    • Domain Architecture
    • Resolver Domain Flow
    • Custom Hostname Setup
    • DNS Setup Guide
    • Resolver & Passport Rendering
    • Custom Hostname Lifecycle
    • Troubleshooting
  • Passports
    • Overview
    • Passport Operations
    • Lifecycle States
    • Controlled Update & Break-Glass
    • Content & Templates
    • Themes & Presentation
    • Consumer Experience
    • Publication Lifecycle
    • Brand Setup & Readiness
    • Drafts
  • Passport Intelligence
    • Passport Intelligence
    • Intelligence Overview
    • Scan Visibility
    • Trust Signals
    • Engagement Insights
    • Investigation Timelines
    • Data & Privacy
    • Roadmap
  • Minting
    • Overview
    • Lifecycle
    • Architecture
    • Limits & Performance
    • Token Preview
    • Exports & Print Jobs
    • Carrier Output Profiles
    • Bring-Your-Own Serials
    • Security
    • FAQ
  • API Reference
    • API Credentials Guide
    • API: Credentials
    • API: Products
    • API: Identifiers
    • API: Import
    • API: Batches
    • API: Attachments
    • API: Bulk Updates
    • API: Minting
    • API: Resolver
    • API: Search
On this page
  • Why Passports Matter
  • Content, Templates, Themes, and Localisations
  • What a Passport Contains
  • How Passports Fit into tieback
  • Key Concepts
  • Template-Governed Content
  • Themed Presentation
  • Localised Content Layer
  • Published Snapshots
  • Brand-Consistent Experience
  • Assignment-Driven Delivery
  • Current Scope
  • Related Docs
Passports

Passports Overview

Was this page helpful?
Previous

Passport Operations

Next
Built with

A Digital Product Passport (DPP) is a structured, publicly accessible record that accompanies a physical product throughout its lifecycle. It presents verified product information — such as materials, origin, sustainability data, and compliance declarations — in a consistent, branded format that consumers and supply chain participants can access by scanning a product’s identifier.

tieback

provides the infrastructure to create, manage, publish, localise, and serve Digital Product Passports at scale.

Why Passports Matter

Regulatory frameworks — including the EU’s Ecodesign for Sustainable Products Regulation (ESPR) — are making Digital Product Passports a requirement for an increasing range of product categories. Beyond compliance, passports enable brands to communicate provenance, sustainability credentials, and product-specific information directly to the consumer at the point of interaction.

A well-structured passport:

  • satisfies regulatory disclosure requirements
  • builds consumer trust through transparency
  • provides a durable, scannable record tied to the physical product
  • supports supply chain visibility across the product lifecycle
  • adapts to local markets with localised content and multilingual support

Content, Templates, Themes, and Localisations

tieback

passports are built on a clear separation of concerns:

LayerWhat it controlsLearn more
ContentThe underlying product data — attributes, identifiers, and structured informationProducts
TemplatesWhich information is included in the passport — field-level control over what appearsContent & Templates
ThemesHow the passport looks — layout, typography, colour, and visual presentationThemes & Presentation
LocalisationsMarket-specific formatting, recycling guidance, disclaimers, and multilingual contentLocalisations Overview

This separation means brands can:

  • adjust what information is disclosed without redesigning the visual experience
  • change the visual presentation without altering the content structure
  • add market-specific content without modifying the base passport
  • satisfy different regulatory requirements through template and localisation configuration
  • maintain a consistent, premium consumer experience through curated themes

What a Passport Contains

Each passport is composed of content blocks — structured sections of information that together form the complete passport experience. Blocks cover topics such as:

Block typePurpose
Product identityProduct name, brand, images, and key identifiers
Materials & compositionRaw materials, components, and material declarations
SustainabilityEnvironmental impact data, certifications, and circularity information
ComplianceRegulatory declarations, conformity marks, and applicable standards
Care & usageInstructions for use, maintenance, and end-of-life handling
Supply chainOrigin, manufacturing location, and chain-of-custody data

The specific blocks and fields available depend on the product’s industry classification, the brand’s template configuration, and the applicable regulatory requirements.

When a Market Pack is linked, the passport is supplemented with market-specific content — recycling guidance, disclaimers, and locale-aware formatting — layered on top of the base content blocks.

How Passports Fit into tieback

Passports build on the existing product and identity infrastructure:

  1. Products — the structured catalogue record, including schema-driven attributes and identifiers. See Products.
  2. Identifiers — SKU, GTIN, EAN, and UPC codes that uniquely identify the product. See Identifiers.
  3. Resolver — the permanent scan URL that maps a physical identifier to a product record. See Resolver & GS1 Digital Link.
  4. Localisations — market-specific content and formatting that supplements the passport for each target market. See Localisations Overview.
  5. Minting — the process that creates verifiable passport tokens tied to production batches. See Minting Overview.

Passports sit at the presentation layer: they take the product data, apply the template’s content governance, merge any linked Market Pack content, and render the result through the brand’s assigned theme into a public, consumer-facing experience.

Key Concepts

Template-Governed Content

The passport template determines which product data is included in the passport. Even if a product record contains extensive information, only the fields permitted by the active template appear in the rendered passport. This gives brands precise control over disclosure. See Content & Templates.

Themed Presentation

Curated themes control the visual presentation of the passport — layout, typography, colour application, and responsive behaviour. Themes are professionally designed and maintained to ensure enterprise-grade visual quality. See Themes & Presentation.

Localised Content Layer

When a Market Pack is linked to a passport, the rendered experience includes market-specific supplementary content — such as recycling guidance for the target market, local disclaimers, and locale-appropriate date and number formatting. This content is additive: it enhances the passport without altering the base content structure. See Market Packs.

Published Snapshots

When a passport is published, tieback captures an immutable snapshot of the content as it exists at the point of publication. This snapshot is what the public sees. Changes to the underlying product data do not automatically update the published passport — a new version must be published explicitly. This protects the integrity of the public record.

Brand-Consistent Experience

Passports are rendered with the brand’s visual identity — including logo, colours, and domain — so that the consumer experience is consistent with the brand’s other digital touchpoints.

Assignment-Driven Delivery

Brands control which passport version is served for each product. Assignments determine the relationship between a published passport version and the products or batches it applies to. This gives brands precise control over what the public sees, and when.

Current Scope

Passports in tieback currently support:

  • configurable content templates with field-level control
  • curated theme-based visual presentation
  • market-specific localisation through Market Packs
  • multilingual content with automated and manual translation
  • publication with immutable version snapshots
  • branded consumer-facing rendering
  • mobile-first responsive presentation
  • integration with the resolver for scan-based access
  • custom domain support for passport URLs

Some related capabilities — such as consumer action workflows, digital wallet integration, and per-product theme assignment — are planned for future releases and are not part of the current live feature set.

Related Docs

  • Content & Templates
  • Themes & Presentation
  • Localisations Overview
  • Market Packs
  • Products
  • Identifiers
  • Resolver & GS1 Digital Link
  • Minting Overview
  • Consumer Experience
  • Publication Lifecycle
  • Brand Setup & Readiness