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
  • English-First Authoring
  • Adding Languages
  • Translation Workflow
  • Automated Translation
  • Manual Translation
  • Translation Status
  • External Links
  • Content Integrity
  • Related Docs
Localisations

Multilingual Content

Was this page helpful?
Previous

Domain Architecture

Next
Built with

Global products require multilingual documentation. tieback provides a structured multilingual authoring model that lets brands manage translations for market-specific content — recycling guidance, disclaimers, and supplementary information — across all enabled languages.

English-First Authoring

All Market Pack content is authored in English (en-GB) as the primary source language. English serves as the authoritative version from which all translations are derived.

This approach ensures:

  • a single source of truth for content governance
  • consistent quality across all language versions
  • clear editorial accountability

Adding Languages

Each Market Pack can support multiple languages. To enable a language for a market:

  1. Open the Market Pack from the Localisations section.
  2. Navigate to the Languages & Formats tab.
  3. Add the desired language to the market’s enabled languages list.

Once a language is enabled, it becomes available for translation across all content within that Market Pack — including recycling guidance, disclaimers, and supplementary content.

Translation Workflow

tieback

supports two translation approaches:

Automated Translation

For rapid multilingual deployment, tieback integrates with professional-grade machine translation services. Automated translations can be generated for any enabled language with a single action, providing a strong starting point that can be refined as needed.

Manual Translation

For brands that require precise editorial control, the translation interface provides a side-by-side editing experience:

  • The source panel displays the English original as a read-only reference
  • The translation panel provides an editable field for the target language
  • Changes are saved per content entry, per language

Manual translations take precedence over automated translations and are preserved across subsequent automated translation runs.

Translation Status

Each content entry displays a clear status indicator:

StatusMeaning
Auto-translatedContent has been translated automatically and has not been manually reviewed
Not translatedNo translation exists for this language

These indicators help editorial teams quickly identify content that needs attention.

External Links

External links — such as references to local recycling authorities or regulatory bodies — are part of the translatable content model. This allows brands to provide region- and language-appropriate source links. For example, a German Market Pack might link to a German-language recycling authority page when viewed in German, and an English-language equivalent when viewed in English.

Content Integrity

The multilingual model is designed to preserve content integrity:

  • Formatting is preserved — Markdown formatting, line breaks, and list structures are maintained across translations.
  • Manual overrides are protected — automated translation runs do not overwrite manually edited translations.
  • Source content governs — the English original remains the canonical version. Translations supplement but do not replace the source.

Related Docs

  • Market Packs
  • Localisations Overview
  • Consumer Experience