The DPP compliance score

The screen scores each product model from 0 to 100 on its readiness for the European digital product passport, and states what is missing. You first see the brand average and the list of models, then open a model for its detailed sheet.

#What the screen shows

In list view: two tiles for product models and average score, then the score by model card. Each model is a clickable row: its name, its identifier, its playbook key where there is one, a progress bar and the score as a percentage. The ordering runs from the lowest score to the highest, and the colour code is fixed: green from 80, amber from 50, red below.

In detail view:

• The overall score in large type, a playbook selector, the history as a curve, and one bar per dimension: product identity, materials, suppliers, lifecycle, compliance, substances, publication and proof.
• Unit level evidence: the number of units and four percentages, published passport, verifiable credential (VC), hash, IPFS anchoring.
• The playbook checklist, a green tick or an amber exclamation mark per item, and its type: component, event or passport field.
• The regulatory deadlines, an in force, expected or watch badge, and the number of days left.
• The European DPP registry card: connector state, identifier field, detail of the record.
• Missing items and recommendations, replaced by a green box when both are empty.

#What you can do here

• Open a model to read its sheet, and refresh the list.
• Pick a vertical playbook or leave automatic detection, then save. The button stays disabled while the chosen value is the one already in place. The choice is stored on the product model.
• Click recompute now: the score is recalculated and a history point recorded. A drop of more than 5 points since the previous point raises an alert. History holds 90 points by default, 365 at most.
• Download the evidence pack as PDF, at brand level from the list or at model level from its sheet.
• Enter a unit serial number, ask for a preview of its record in the European registry, then trigger the send. The button reads "Register" when the connector is active and "Dry-run" otherwise. Opening another model resets that panel.

#What governs access

The tab sits behind the DPP workspace profile guard, which excludes the basic brand profile. The PDF evidence export and the registry connector both depend on the dpp plan option, checked brand by brand, including on the brand level export.

Actually sending to the registry depends on two server settings: without them, the call stays a preview. The connector state announces a go live on 19 July 2026. The preview and send buttons stay disabled while the identifier field is empty.

#What the screen refuses

• Beyond 2000 models in the catalogue, the aggregate summary is refused: the message invites you to filter by brand or to look model by model.
• A model outside the brand scope: "Product model not found".
• A unit with no public serial number, or a platform whose application URL is not configured, is refused. The GTIN itself stays optional.
• Registering a unit of another brand: "You can only register products of your own brand".
• On failure: the evidence pack could not be generated, the playbook could not be saved, or the score could not be recalculated.