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
  • The Passport Configurator
  • Content Blocks
  • How the Configurator Works
  • Template-Governed Rendering
  • Content and Localisation
  • Template and Product Relationship
  • Content vs Presentation
  • Related Docs
Passports

Content & Templates

Was this page helpful?
Previous

Themes & Presentation

Next
Built with

Digital Product Passports in tieback separate what information is included from how it is presented. This page explains the content configuration side — how brands control which product data appears in the passport and how localised content supplements it.

The Passport Configurator

The Passport Configurator is the primary tool for managing passport content. It provides a visual, block-based editor where brands define the structure and content of their Digital Product Passports.

The Configurator is built around content blocks — modular sections of information that together form the complete passport experience. Each block represents a category of product information, and brands have full control over which blocks are included, what fields appear within them, and how they are ordered.

Content Blocks

Content blockWhat it governs
Product identityProduct name, images, key identifiers, and descriptive information
Materials & compositionRaw materials, fibre composition, recycled content, and material declarations
Provenance & manufacturingCountry of origin, manufacturing location, and supply chain information
Care & useCare instructions, repair availability, reuse guidance, and spare parts
SustainabilityEnvironmental impact data, carbon and water footprint, end-of-life guidance
Trust & complianceCertifications, compliance declarations, restricted substances, and warranty

Each block can be independently enabled or disabled. Within each block, the set of included fields is explicitly defined. Only data for included fields appears in the rendered passport — everything else is excluded, regardless of whether the underlying product record contains it.

How the Configurator Works

1

Select content blocks

Choose which categories of product information to include in your passport. Enable or disable entire blocks based on your disclosure strategy and regulatory requirements.

2

Configure fields

Within each enabled block, review and confirm which individual fields appear. Fields can be toggled on or off to match your data readiness and compliance needs.

3

Preview

See exactly how the passport will render with the current configuration — including the brand’s theme and any linked Market Pack content.

4

Publish

Finalise the configuration and make it the active governing template. Published passport snapshots retain the content structure in effect at the time of publication.

Template-Governed Rendering

The passport template governs what the consumer sees, not the raw product record.

A product record may contain extensive structured data — covering dozens of fields across multiple categories. The passport template acts as a controlled lens over that data, presenting only the fields that the brand has chosen to include.

This means:

  • Adding data to a product does not automatically expose it in the passport. The template must explicitly include the relevant fields.
  • Disabling a field in the template removes it from the passport even if the product record contains a value for that field.
  • Different templates can present different views of the same product data, supporting different disclosure strategies or regulatory contexts.

Content and Localisation

When a Market Pack is linked to a passport, localised content is layered on top of the base template configuration:

  • Base content is governed by the Passport Configurator — the fields, blocks, and structure defined here form the foundation.
  • Custom field values — any brand-specific custom fields with values set on the product are available in the content pipeline and can be included in the passport.
  • Market-specific content — such as recycling guidance, disclaimers, and supplementary information — is added by the Market Pack as a supplementary layer.
  • Language and formatting — dates, numbers, and measurement units are rendered according to the Market Pack’s locale rules.

The base template structure is never altered by localisation. Market Packs add to the passport experience; they do not modify the content blocks or field selections defined in the Configurator.

See Localisations Overview for details on how Market Packs work.

Template and Product Relationship

In the current model, a brand’s published passport template applies to all products under that brand. This provides a consistent disclosure framework across the product catalogue.

Future releases will support more granular template assignment — such as per-product or per-category templates — for brands that need different disclosure structures for different product lines.

Content vs Presentation

Templates control content — what information is included. They do not control presentation — how that information looks visually. Presentation is handled by themes, which are covered in Themes & Presentation.

This separation means:

  • a brand can update its visual presentation without changing the content structure
  • a brand can adjust its disclosure strategy without redesigning the passport layout
  • content and design decisions can be made independently

Related Docs

  • Passports Overview
  • Themes & Presentation
  • Localisations Overview
  • Publication Lifecycle
  • Brand Setup & Readiness
  • Products