Product passports
The brand's product passports, their version history, the comparison of two versions, the JSON export and the creation form.
This is where product passports are written and published. A passport exists as numbered versions: as long as a version has never been published it stays an editable draft, once published it is sealed and any correction becomes the next version.

#What the screen shows
- A product passports header, a subtitle about passport management with version history, a new passport button and three tiles: total passports, published, drafts.
- A filter field for a product ID or name, followed by the number of results as soon as it is filled.
- One card per passport: the model or product name followed by the version, a published or draft badge, the first 16 characters of the hash, what it is attached to, the creation date and the notes. Four buttons: edit or new version, versions, DPP export, and a show data button that turns into hide.
- A history window: a table of version, hash, status and date, two lists for version A and version B, a compare button.
- A comparison window split into additions, removals, changes with the before value and the after value, and unchanged entries.
#What you can do here
- Filter the list as you type, over the passports already loaded, by passport identifier, product name, model name or product identifier.
- Open a passport history, pick two versions and run the comparison.
- Download the DPP export as indented JSON:
dpp-product-<id>.jsonfor a unit passport,dpp-model-<id>.jsonfor a model passport. - Expand a card to read the raw data.
- Create a passport attached to a product model or to a single unit, apply a DPP template to pre-fill it, tick the publish immediately box.
- Edit a draft in place, or create the next version of a published passport.
Publishing a version unpublishes the other published versions of the same scope, which go back to being visible to the brand only.
#What governs access
The screen depends on the dpp option of your plan, which creation and update also check on the server side. The tab sits behind the DPP workspace profile guard, and the DPP passports entry in the side menu is hidden for the basic brand profile.
The list asks for 100 passports at once, newest first. Saving a creation stays disabled until a product model or a product identifier is provided, and compare until both versions are chosen. The form switches on its own between editing in place and creating a new version, depending on whether the open version is sealed.
#What the screen refuses
- Without the DPP option, the page still shows but greyed out and not clickable, under a panel announcing the locked feature and inviting you to upgrade the plan.
- Editing the content of a published version is refused: it is sealed, a corrected version has to be published instead.
- Creating a passport with neither a product model nor a product: "product_model_id or product_id is required".
- Creating a passport on a product with no brand: "This product has no brand; the passport cannot be scoped".
- Creating a passport on a brand outside your scope:
Accès interdit à cette marque. - On failure, a red banner shows a loading error or a creation error.
Was this page helpful?
Your answer opens a pre-filled email in your mail app, addressed to contact@sealtrust.io. You read it over before sending it.