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.
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:
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.
Navigate to Settings → Custom Fields to manage your brand’s custom field definitions.
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.
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.
Custom field values flow through to the Digital Product Passport rendering pipeline. When a passport is published:
This means custom data can be disclosed to consumers alongside standard DPP information, subject to the brand’s template configuration.
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.
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.
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.
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.
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.
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.