Custom Fields
Every brand has product information that doesn’t fit neatly into a standardised schema. tieback Custom Fields let you extend the product data model with brand-specific attributes — tracked, governed, and available throughout the platform alongside your standard DPP fields.
What Custom Fields Do
Custom Fields allow you to define additional data attributes that are specific to your brand’s operational needs. These fields sit alongside the standard DPP schema fields and are treated as first-class data throughout the platform:
- Appear in Product Detail — custom fields are displayed in a dedicated section on every product record
- Included in passport content — custom field values flow through to Digital Product Passport rendering when configured
- Available at mint time — lot-level custom values can be set during minting for batch-specific overrides
- Governed by the same rules — custom fields respect the platform’s data integrity, audit, and access control policies
Who It’s For
Brand administrators who need to track product attributes beyond the standard DPP field catalogue — for example, internal reference codes, brand-specific sustainability metrics, proprietary material classifications, or operational metadata.
How It Works
Defining Custom Fields
Navigate to Settings → Custom Fields to manage your brand’s custom field definitions.
Create a field definition
Give the field a label and a unique field identifier. Choose a data type (text, number, boolean, date, or URL). Assign it to a scope — product-level or lot-level.
Scope Levels
Custom fields can be defined at two scope levels:
Product-level custom values are stored on the product record. Lot-level custom values are captured during the minting process and frozen into the mint batch data.
Data Types
Custom Fields in Passports
Custom field values flow through to the Digital Product Passport rendering pipeline. When a passport is published:
- Product-level custom values are included in the passport snapshot
- Lot-level custom values are captured at mint time and included in the batch data
- The passport template governs whether custom fields appear in the consumer-facing experience
This means custom data can be disclosed to consumers alongside standard DPP information, subject to the brand’s template configuration.
Custom Fields in Product Detail
Custom fields appear in a dedicated Custom Fields section on the Product Detail page, below the standard DPP attribute sections. Each field displays its label, current value, and data type. Values are editable inline, following the same interaction pattern as standard product attributes.
Three-Layer Data Model
Custom fields participate in tieback’s three-layer data inheritance model:
When a passport is rendered, the system resolves custom field values using this precedence hierarchy — lot overrides take priority over batch snapshots, which take priority over the product master.
Limits & Notes
- Custom field definitions are brand-scoped — each brand manages its own set of fields independently
- Field identifiers must be unique within a brand and cannot be changed after creation
- Deactivating a field hides it from new data entry but preserves existing values
- Custom field values are subject to the same audit and access control policies as standard product attributes
FAQ
Can I use custom fields for compliance data?
Yes. Custom fields support any data your brand needs to track. However, for fields that map to standardised DPP requirements, we recommend using the built-in DPP schema fields instead — these are already configured for your industry classification and support regulatory reporting.
Do custom fields appear in the consumer passport?
Custom field values are available in the passport rendering pipeline. Whether they appear in the consumer experience depends on your passport template configuration — you control which fields are disclosed.
Can I change a custom field's data type after creation?
No. Data types are fixed at creation to protect data integrity across existing product records and passport snapshots. If you need a different type, create a new field definition and migrate your data.
What happens to custom field data when I deactivate a field?
Existing values are preserved on all products and passport snapshots. The field is hidden from new data entry but remains part of the historical record.