Templates and JSON Schemas

Templates provide metadata, a structure description and a JSON Schema used when a passport is published.

Bundled templates

These labels and schemas are implementation starting points. They are not a legal opinion or a guarantee that the fields cover a product's obligations.

Admin template form

Open Catalog > Digital Product Passports > Templates. An administrator with template permission can edit:

• code;
• name;
• active state;
• scope text;
• structure JSON.

The form does not expose the schema definition. A newly created custom template therefore has no publishable schema unless an implementation supplies one through code or a controlled data process. Draft or Active records can still use a template without a schema, but Published records cannot.

Structure JSON is not the validation schema

The visible Structure JSON describes the template, such as sections and intended granularity. Editing it does not change the JSON Schema that validates the payload.

Referenced templates

Once passports reference a template, its code cannot be changed and the template cannot be deleted. Other metadata can still be updated. This protects existing passport references.

Safe customization process

1. Define the required data model with the responsible compliance and product teams.
2. Create and test a JSON Schema outside production.
3. Add the template metadata and schema through a reviewed deployment.
4. Validate representative valid and invalid payloads.
5. Create Draft passports and review the public JSON-LD shape.
6. Publish only after the schema and business data have been approved.