Database Reference
The Digital Product Passport model is deliberately small: a passport belongs to a Magento product and a Store View.
| Relationship | Why it matters |
|---|---|
dpp_passport belongs to one catalog_product_entity |
Connects passport content and identifiers to the product they describe. |
dpp_passport belongs to one store |
Allows passport content and publication state to vary by Store View. |
dpp_passport is unique on (product_id, store_id, batch_id, serial_number) |
A second passport for the same product, store, batch and serial updates the existing record instead of creating a duplicate. |
dpp_template (unique code) stores schema_definition |
Defines the field structure a passport template expects — the template's structure JSON and its validation schema are different artifacts. |
Passport status values are draft, active, published and archived. Draft and active are editable working states; published makes the record visible to the public/anonymous endpoints; archived retires it.
Use the passport management UI or service contracts for changes so validation and publication behavior remain intact.