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
  • Operator Types
  • Master-Data Model
  • Where to Manage
  • Resolution at Mint
  • Related Docs
Tenancy & Governance

Economic Operators

Was this page helpful?
Previous

Content Studio

Next
Built with

Economic Operators are the regulated parties associated with a product — manufacturers, importers, authorised representatives, distributors, and the physical facilities where products are made or assembled. ESPR and other DPP regulations require that this information is structured, accurate, and reproducible across every passport that references it.

tieback

manages economic operators as first-class master data rather than free-text fields on individual products. This guarantees consistency across the catalogue and supports clean updates when a partner’s details change.

Operator Types

TypeRole
ManufacturerThe party that physically manufactures the product
ImporterThe party importing the product into a regulated market
Authorised RepresentativeA party formally authorised to act on the manufacturer’s behalf in a market
DistributorThe party that distributes the product into market
FacilityA physical site involved in production or assembly

Master-Data Model

Each operator is a single record that can be referenced by many products. Operator records carry:

  • Legal name, registered address, and country
  • Regulatory identifiers (e.g. EORI, VAT, EUDR ID where applicable)
  • Contact details
  • Effective dates

Editing an operator updates the master record. Future mints reference the latest values; previously issued passports retain the values that were captured at publish time as part of their immutable snapshot.

Where to Manage

  • Workspace level — Settings → Economic Operators (and from the Setup Wizard during onboarding)
  • Product level — assign operators to a product from the product detail surface
  • Tia — Tia can audit operator coverage across the catalogue and surface products missing required operator types

Resolution at Mint

When a passport is minted, the resolver:

  1. Reads the product’s assigned operators
  2. Snapshots their then-current details into the passport payload
  3. Renders the operator block according to the active theme and template

Subsequent operator edits do not retroactively change passports already in circulation. To correct historical data use Controlled Update or Break-Glass.

Related Docs

  • Products
  • Controlled Update & Break-Glass
  • Tia — AI Operations Assistant