Data that arrives with a digital ID — order number, production details, anything your label printer sends — is a set of named attributes you manage, and nothing reaches the public passport unless you make it public.
Digital ID attributes work like product attributes. Each has a name, an optional category, a value type — text, number, date, boolean, country, location or file — a “show as default” toggle, and a public/private toggle. The list is searchable by name and filterable by category and by either toggle.
Values are edited per digital ID from the admin panel. The panel saves the full set, so removing an attribute there removes it from the digital ID.
One visibility rule covers every audience: admins see all attributes on a digital ID, while retailers, distributors and anyone scanning a code see only the ones marked public. Attributes are private when created, so making something public is always a deliberate step. Public attributes become available as passport page variables, so they can be placed on the consumer-facing page.
Incoming syncs and supplier pushes send attributes by name. A name that does not exist yet is created as private, so a new column appearing at the source stays off the public passport until someone decides otherwise. A sync only overwrites the attributes it mentions, so values you entered by hand stay as they are.
Values longer than 1,024 characters are not stored, and raise a data-quality issue on the integrity dashboard.
This covers digital ID attributes. Product and purchase order attributes are unchanged.
