Yüklənir

Digital Product Passports

A Digital Product Passport, or DPP, presents reviewed information about an identified product subject through a stable access link. A Passport Profile determines the subject level, applicable information and permitted readers. A category mapping assembles that information from approved Actualog sources.

A physical item and its information

A Product describes a reusable model or concrete variant. A Product Release preserves one approved technical definition. A Product Instance identifies one actual item with its issuer and serial. The passport is the reviewed information published about the selected subject; creating a passport does not create the physical item.

Passport level Identified subject
Model An approved Product Release.
Batch An exact Production Batch and its matching release.
Item An exact Product Instance and its applicable provenance.

The selected profile requires one exact level. For example, two sensors can share one model definition while having different batches, serials and inspection results. An Item passport reads its own instance's information, whereas a Model passport does not expose an arbitrary item's serial or measurements.

EU battery passports concern individual batteries in the scope of Article 77 and include model information. Other product groups follow their applicable rules; the platform's three levels do not imply a universal legal obligation for every product. See the Battery Regulation and Ecodesign Regulation.

What the passport contains

The preparation records the administering and responsible companies, exact subject, profile/mapping editions, applicability date and change reason. Assembled fields expose their source lineage. Missing, incompatible or conflicting information appears as readiness issues.

Model facts come from the approved release. Batch facts describe that batch and its actual factory. Individual observations describe that instance. Evidence, composition, operators and declarations are included where applicable requirements call for them; creating every supporting entity is not a universal passport prerequisite.

Who creates and publishes it

Product Editors prepare drafts within their authorized company scope. Product Governance Managers and Company Administrators exercise the relevant review/publication responsibilities. A delegated partner needs an accepted operational mandate for the action and resource. Restricted source access is checked independently.

Preparation, review, approval and publication are separate decisions. Publication preserves the exact approved snapshot as a Passport Publication Version. Later source edits do not rewrite that version.

Where to work

Open Logistic → Product Passport to search and filter existing passports by category, product, batch, instance or state. Its creation action opens the company's product selection workspace: choose an associated Manufacturer/Brand Owner product-level category, browse Published concrete products with Product Overview's attribute filters, and select the products to prepare.

The preparation screen shows existing releases and batches, the batch's actual factory and individual registration where needed. Continue from the source matching the profile's required Model, Batch or Item level. Preview applicable requirements before review and publication.

Published passports have a stable link and QR code. Public readers receive permitted public fields and documents. Authorized reading requires the relevant access; ordinary company membership does not establish statutory regulatory-reader authority.

A passport's QR code opens its stable access link. The reader identifies the exact Model, Batch or Item level, stable passport identifier, publication version/date and responsible organization. This organization holds the recorded passport responsibility; its employees' preparation and approval actions do not replace that legal/business role.

The main content groups the approved, audience-permitted publication fields into model specifications, batch/manufacturing facts, individual-item information and supporting records where present. The category mapping determines what is included. The reader does not load every live Product attribute or reconstruct historical manufacturing data. Optional publication traceability shows requirement/source references and the snapshot checksum.

An explicitly authorized restricted reader can also see Prepared by, Approved by and Published by for the selected version. These are different recorded actions. Submitting a draft for review does not itself identify an actual reviewer. Preparation receipts are retained for new publications; an older missing receipt remains unavailable rather than being guessed from today's draft, owner or publisher.

Company and user display names are resolved from their current identities, while the publication retains the responsible company and available actor references. The published technical values stay unchanged. Public readers do not receive personnel names/identifiers or restricted fields/documents. Signing in alone does not grant restricted access.

Independent outcomes

Readiness, local publication, external registration and continuity are separate outcomes. Local publication is not a registry acknowledgment or compliance certificate. Unsupported official submission or verification contracts remain explicit blockers.

A DPP can be created without a sales catalog. Catalog Publishing can use shared records without creating a passport.

Related topics: Creating Digital Product Passports, Passport Profiles, Product Instances, Passport Publication Versions.