Skip to content
ReMake Value Retention Centre

Standards alignment

EU-aligned registry compatibility

RVRC Hub is designed for forward compatibility with emerging EU Digital Product Passport standards and registry patterns, without claiming to be an official EU registry.

ESPR Articles 13 and 14

Aligned with the EU Digital Product Passport registry direction

The Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781) establishes the Digital Product Passport framework. Article 13 provides for a digital product passport registry, and Article 14 provides for a web portal that supports discovery of passport information according to access rights and product-specific rules.

RVRC Hub follows the same architectural direction as a UK platform: centralise enough information to identify, register and discover product passports, while keeping DPP content decentralised with the economic operator or its DPP service provider.

Key alignment points

  • Registry stores metadata, not full DPP content
  • DPP content remains with the provider or economic operator
  • Discovery is governed by access rights
  • Product-specific rules can be accommodated through publication policy
  • Identifiers support GS1 Digital Link and ISO/IEC 15459 patterns

Metadata registry pattern

RVRC Hub is a registry and governed-access layer, not a DPP store

RVRC Hub implements the registry pattern. The hub holds:

  • A registry of DPP records, keyed by provider-assigned DPP identifiers
  • Search payloads with approved, indexed metadata
  • Variable manifests that describe fields and security levels without containing values
  • Owning company and provider references
  • Lifecycle and publication status

The hub does not hold:

  • DPP variable values above public level
  • Any DPP content the provider has not explicitly pushed as searchable metadata
  • Binary assets such as CAD files, simulations or video work instructions

dpp_key and UPI

RVRC Hub uses a composite primary key, with optional EU-compatible identifiers

dpp_key — the canonical identifier

RVRC Hub uses dpp_key = {provider_short_code}:{provider_dpp_id} as its canonical internal identifier. For example, m2v:dpp_abc123. This avoids cross-provider ID collisions and accommodates DPPs without GTINs.

upi — the optional EU-compatible identifier

Where a DPP has a EU-style unique product identifier (upi), it is stored as an additional indexable field. The upi does not replace dpp_key. It supports EU-style registry lookup without changing the hub's internal key semantics.

GS1 Digital Link

When a DPP has a GS1 GTIN and serial number, the GS1 Digital Link path is stored as a separate indexable field. The provider-issued resolver URL (for example https://www.made2verify.com/01/.../21/...) is also stored. DPPs without GS1 identifiers remain addressable via dpp_key alone.

EU registry compatibility metadata

Optional fields for EU-style registry interoperability

RVRC Hub supports an optional EU registry metadata profile that adds a mapping layer for metadata concepts commonly expected in registry-style systems. This does not replace the native provider specification.

Registry conceptRVRC field
Unique product identifierupi
Responsible economic operatorresponsible_economic_operator_id
Live DPP URLprovider_dpp_url
Backup DPP URLprovider_backup_url
Commodity codecommodity_code
Granularity levelgranularity_level
Deactivated stateDerived from publication/lifecycle status

Standards reference

Key standards and regulations informing RVRC Hub design

ESPR (EU 2024/1781)

In force

Hub follows the registry and web portal pattern from Articles 13 and 14.

CEN/CENELEC JTC 24

Draft standards expected end 2026

Hub borrows architectural principles: decentralise where possible, centralise where necessary; persistent unique identifiers; explicit access rights.

GS1 Digital Link / ISO 15459 / ISO 18975

Published

Hub stores GS1 Digital Link paths as indexable fields. Accepts ISO/IEC 15459 identifiers from non-GS1 issuers.

IEC 63278 / AAS

Published

AAS submodel patterns map to the provider variable manifest. AAS/ID concepts map to provider_dpp_id. Direct AAS integration is planned for Stage 2.

Battery Passport (EU 2023/1542)

In force

Battery passport schemas inform the variable classification model and access rights granularity.

Important disclaimer

RVRC Hub is not a full implementation of the future EU DPP registry. It is a UK platform aligned with the same architectural pattern. Product-specific regulatory details are expected to evolve through delegated acts, standards and implementation guidance. RVRC Hub keeps the registry contract provider-neutral and extensible.

Learn more about the architecture

Explore how RVRC Hub works end to end, or contact the team to discuss participation.

How it worksContact us