積載

Passport Profiles

A Passport Profile defines the information that a particular kind of Digital Product Passport must contain. It describes the requirements, their applicability, evidence rules and reader audiences. It does not contain a company's product data.

For example, one profile may require an individual battery's serial number, model characteristics and manufacturing information. Another profile may describe a voluntary model-level information passport. Selecting a profile does not establish that a product meets a regulation.

Profile, mapping and passport

These records answer different questions:

Record Question it answers
Passport Profile What information is required, for which subjects and dates?
Passport Category Mapping Where does that information come from in Actualog?
Digital Product Passport What is the assembled, reviewed information for this particular subject?

A profile edition records its jurisdiction, authoritative source and source edition, review date, effective date, exact subject level: Model, Batch or Item and publication release gates. Individual requirements can be Required, Conditional, Optional or Inapplicable. A requirement's own effective period can be narrower than the profile's period.

The profile's level must match the passport subject exactly. A Model profile cannot be used to publish a Batch or Item passport merely because those subjects contain model information. Requirements can use sources at different scopes without changing the identified passport subject.

For regulated products, use the level specified by the applicable law or delegated act. EU battery passports in Article 77's scope identify individual batteries; other product groups can require Model, Batch or Item level. Requirement-specific dates and conditions remain separate from the passport obligation. See the Ecodesign Regulation, Battery Regulation, and Commission FAQ.

Who maintains profiles

Application administrators manage profiles in Profiles and mappings. Company Product Editors prepare passports using available approved mappings; they do not redefine platform requirements. Product Governance Managers or Company Administrators review and publish company passport preparations within their authority.

Administrative access does not substitute for a company's declaration or publication mandate.

Working with a profile edition

  1. Open the profile list and search for an existing suitable edition before creating one.
  2. Select Create new passport profile edition and record the source, applicability and subject level.
  3. Use Add requirement to define named requirements, conditions, target units, audience and evidence criteria.
  4. Record the review decision resolving publication release gates before enabling publication.
  5. Save the draft; activate it only after its definitions and sources have been reviewed.

An activated edition is immutable. Use the existing edition's Create new passport profile edition link to prepare a successor when requirements change.

Common blockers and ongoing maintenance

An inactive profile cannot support an active mapping or passport preparation. A profile with unresolved publication gates must not be treated as ready for statutory publication. The EU battery review seed is a starting point for configuration and review, rather than a compliance certificate.

Review source editions, applicability dates and access rules before activating successors. Earlier passport publications retain their original profile edition. Do not remove a requirement simply to make one incomplete product pass validation; correct the source records or review the requirement's documented applicability.

Related topics: Passport Category Mappings, Digital Product Passports.