What Is the Passport Registry?

The passport registry is the central registry established under the ecodesign framework for digital product passports, which stores unique identifiers and associated metadata for products placed on the market, while the full passport data remain held in decentralised systems operated by economic operators. For batteries, the registry interacts with the battery passport duty in Article 77 of Regulation (EU) 2023/1542, and the operator who places a battery on the market uploads the unique identifier to the registry. The registry is therefore an index, not a database of complete passports, and that distinction governs every software design decision that touches it.

The registry model reflects a deliberate architecture choice in Regulation (EU) 2024/1781. A central index allows customs and market surveillance authorities to verify that a product has a registered passport, without centralising commercially sensitive passport data in a single store. Economic operators keep the passport data, control access under the tier rules, and remain responsible for accuracy and availability. Software that treats the registry as the passport store will misplace data, misstate responsibility and create a single point of failure that the architecture was designed to avoid.

What does the registry store?

The registry stores a record of unique identifiers linked to products placed on the market or put into service, together with associated metadata that allows the identifier to be resolved to the passport held by the operator. The registry does not store the full passport content, such as chemistry detail, carbon footprint calculations or dismantling information. Those data remain in the operator system, reached through the identifier and the access rights that apply to each tier. The registry record is therefore small, structured and verifiable, while the passport record is larger, tiered and distributed.

A registry design check should list each field stored in the registry, its source and its retention period, and should confirm that no full passport field has been copied into the registry store. A check that finds passport content in the registry store indicates a design error, not a more complete registry. The registry should be able to answer three questions only: does an identifier exist, is it unique, and where is the passport held. Any further question should be answered by the passport system, under access control.

How does the registry relate to the battery passport?

The registry relates to the battery passport through the unique identifier upload duty in Article 77, as amended to refer to the registry in Regulation (EU) 2024/1781. The operator placing a battery on the market uploads the unique identifier to the registry, and the registry returns or records a registration identifier where the implementing rules provide for one. The passport itself is created and maintained by the responsible operator, and the registry entry points to it. The two records are linked by identifier, but they are created, stored and updated by different systems with different responsibilities.

Worked check: a customs check scans a battery QR code and queries the registry. The registry confirms that the identifier is registered and points to the operator passport system. The customs check then verifies passport availability through the operator system. A registry entry without a resolvable passport, or a passport without a registry entry, each fail the combined check in a different way, and the software should report which link failed, so that the operator can correct the correct system.

Who operates the registry?

The registry is set up and maintained by the European Commission under the ecodesign framework, with the operating rules set by implementing acts. Economic operators interact with the registry through the registration process, and market surveillance and customs authorities use the registry for verification. The Commission role is registry operation and identifier integrity, not passport content responsibility. Content responsibility remains with the economic operator who places the product on the market, and that allocation should be reflected in every software contract and service agreement that touches the registry.

Software procurement should therefore distinguish registry interaction services from passport hosting services. A vendor that provides registry interaction alone does not provide passport hosting, and a vendor that provides hosting alone does not provide registry registration. A contract that merges the two services without distinguishing the responsibilities will leave a gap when a registry entry fails or a passport becomes unavailable. The contract should name each service, each responsibility and each evidence output separately.

What is the registry status as checked in October 2026?

As checked on 28 October 2026, secondary reporting indicated that the registry went into production in July 2026 under Implementing Regulation (EU) 2026/1778, with a user guide noting that registering a battery passport was not currently available because the semantic catalogue for the product group had not yet been defined. That status illustrates the registry pattern: infrastructure can be live while a product group registration route remains pending on a catalogue or delegated act. A software plan should treat registry readiness as product group specific, not as a single switch for all products.

A registry status check should be dated, sourced and product group specific. A check that states only that the registry is live, without stating whether battery registration is available, misleads a battery operator. A check that states the registry status, the catalogue status and the next expected publication, with dates, supports planning. The status in this guide is a snapshot as checked on 28 October 2026, and it should be rechecked before any registration step is taken.

How does the registry connect to customs?

The registry is interconnected with the EU Customs Single Window Certificates Exchange, so that customs authorities can verify, at the border, that a product has a registered passport before release for free circulation, where the applicable rules require that check. The interconnection is an identifier verification, not a content inspection: customs checks the registration identifier and the registry entry, while market surveillance authorities carry out the deeper conformity and passport content checks inland. The distinction keeps border checks fast and identifier based, and reserves content checks for the authorities with the relevant access rights.

Border readiness for software means that the registry entry must be created before or at placing on the market, with the identifier correctly formed and the passport resolvable at the time of the customs check. A registry entry created after the border check, or an entry with an identifier that does not resolve, will fail the verification even when the passport content is complete. The software workflow should therefore place registry upload before shipment release in the internal process, with a hold where the upload has not been confirmed.

What must not be assumed about the registry?

The registry must not be assumed to verify passport accuracy, to store passport data, to grant access to restricted tiers, or to replace market surveillance checks. The registry verifies identifier registration and linkage, and the accuracy, completeness and tier access of passport data remain the responsibility of the operator and the subject of authority checks. A software dashboard that presents a registry entry as proof of passport accuracy overstates what the registry does, and a dashboard that presents a missing registry entry as proof of a missing passport understates the distinction, because the two records can fail independently. As checked on 28 October 2026, registry rules continue to develop through implementing acts, and the registry design should be reviewed after each act. This guide gives general educational information only and is not individual legal advice. A reader with a specific battery or market decision should check the current Regulation text and any applicable delegated act, as checked on 28 October 2026, before acting.

This guide gives general educational information only and is not individual legal advice. A reader with a specific battery or market decision should check the current Regulation text and any applicable delegated act, as checked on 28 October 2026, before acting. The registry is an index that points to passports, and software should keep that pointing function separate from passport hosting.