BizNavi HubSign in

Carrier

Can this carrier be used?

Check placement, linkage, persistence, accessibility, machine readability, and the physical to digital association.

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

What this checks

It treats the carrier as a link to decentralised data, not as proof of registry submission.

Who should use this screen

People placing a QR or other carrier on a product or its packaging.

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

Each property is yes, no, or unknown. A QR type in the preset is only a category.

Result

Carrier actions, an evidence gap, or review.

Limits

Carrier actions do not mean the registry accepted anything.

Limits

QR code enough?

No. A QR code alone is not a registry submission.

Link may expire?

Persistence marked no is an evidence gap.

Scan unclear?

Unknown machine readability asks for review.

Holds the product file?

No. The carrier should point at data that stays outside the registry.