tieback
is structured as a SaaS platform for Digital Product Passport and product identity workflows. Its architecture separates identity, resolver logic, passport content, localisation, lifecycle events, and API access into clear modules — so organisations can scale from compliance preparation to high-assurance authentication without reissuing identifiers.
tieback
is designed around a set of principles that prioritise data integrity, tenant isolation, and minimal public disclosure.
Every brand operates in its own logical workspace. Data access is scoped to the brand level — users, products, identifiers, localisations, and jobs are all partitioned by brand.
All write operations go through server-side functions rather than direct table access. This ensures validation, audit logging, and access control are applied consistently regardless of the client.
Identifier changes, product updates, and administrative actions produce permanent audit records. Nothing is silently overwritten.
A brand is the primary organisational unit. Each brand has its own product catalogue, identifier space, passport templates, Market Packs, team members, and configuration. Users can belong to multiple brands with different roles.
Every product has an immutable system UUID. Mutable identifiers (SKU, GTIN, EAN, UPC) are stored as aliases with full change history. The public resolver uses a “forever valid” strategy — retired codes fall back gracefully so printed barcodes never break.
See Identifiers for details.
Product attributes are governed by a schema derived from your brand’s industry classification (NACE code). The schema defines which fields are required, their data types, and any value-set constraints. This schema drives mint readiness checks.
In addition to the standard schema, brands can define custom fields — brand-specific attributes that extend the data model for operational or compliance purposes. Custom fields are first-class data: they appear in product records, flow through to passport rendering, and participate in the three-layer data inheritance model. See Custom Fields.
Passports are composed of configurable content blocks — structured sections covering product identity, materials, sustainability, compliance, and care. Brands control which blocks and fields appear through a template configuration layer, ensuring precise control over disclosure. See Content & Templates.
Market Packs provide market-specific formatting, recycling guidance, disclaimers, and multilingual content. Each pack is linked to one or more passports and layers supplementary content on top of the base passport structure. The localisation layer supports 31 pre-configured markets with configurable locale rules, date and number formatting, and measurement systems. See Localisations Overview.
tieback
exposes a set of authenticated endpoints for programmatic access:
All API operations require authentication. The only public endpoint is the Resolver, which returns UUIDs only.
Product data is stored in a managed database with tenant-level isolation. All access is mediated through server-side functions with role-based access control.
Yes. Each brand is a fully isolated tenant with its own data, team, identifiers, localisations, and configuration.
tieback
is currently offered as a managed service. Self-hosting is not available at this time.
Market Packs provide an additive content layer that supplements the base passport with market-specific information. The base passport content and template structure remain unchanged — localisation adds recycling guidance, disclaimers, and formatting conventions for the target market.