BizNavi HubSign in

Registry

Registry step ready?

Check identifier, metadata, carrier, hosting, and access before treating a product as ready to register.

Saved preset fields: product_group, operator_role, carrier_type, hosting_model, access_role, eu_market

What this checks

It separates registry prerequisites from the battery passport content checker and from battery due diligence.

Who should use this screen

Operators who need a registration readiness view, not a battery due-diligence audit.

Verified dates

Regulation (EU) 2024/1781 is the ESPR basis. The EU DPP Registry is operational from 2026-07-20 and stores identifiers and metadata only. Product data stays decentralised. Certain large batteries use 2027-02-18. Other product groups stay PENDING until a delegated act sets a date.

Official sources

Regulation (EU) 2024/1781, the battery passport date encoded from Regulation (EU) 2023/1542, and the Commission ESPR working plan. Unpublished delegated acts are not treated as final.

Limitations

This is an operational screen, not a registration and not legal advice. It does not store identifiers, files, supplier names, or product data.

How to read this

Inputs

Use yes, no, or unknown. A later product group stays pending even when the boxes are complete.

Result

Ready, an evidence gap, pending, or review. Ready is not a submitted registration.

Limits

The screen does not contact the registry and does not store raw identifiers.

Limits

Already registered?

No. Ready only means the categorical prerequisites were answered yes.

Later products?

Their dates stay PENDING until an applicable delegated act sets them.

Replace the passport checker?

No. Keep that checker for battery passport content and use this screen for registry prerequisites.

Product database?

No. It stores identifiers and metadata. Product data stays decentralised.