Skip to content
  • There are no suggestions because the search field is empty.

How does prodigi.link support EU-DPP identification and resolution?

Short answer

prodigi.link is the persistent identification and resolution layer in the SyncForce architecture.

It connects a standards-based identifier to one or more digital resources without making the identifier dependent on a specific webpage or system.

For the EU-DPP, prodigi.link can resolve:

  • Product Models
  • Batches
  • Serialized Items

For commercial Sales Units, prodigi.link also supports GS1 Digital Link.

For Packaging Systems, prodigi.link supports the VTA-based 31B identifier.

The key principle is:

The identity remains stable, while the digital resources associated with that identity may change over time.

What does prodigi.link actually do?

prodigi.link does not replace the PIM and does not itself define the Product.

Its role is to resolve an identifier.

Conceptually:

Persistent identifier

↓

prodigi.link

↓

one or more digital resources

Those resources can include:

  • EU-DPP
  • Product Model information
  • Battery Information Page
  • Marketing Landing Page
  • PPWR dossier
  • Declaration of Conformity
  • instructions
  • repair information
  • recycling information

This separates the permanent identity of the object from the current destination of a web request.

Why is a resolver needed?

A physical Product can remain in use for much longer than the digital systems or commercial pages that existed when it was sold.

During the Product lifecycle:

  • a Marketing Landing Page may disappear
  • a brand website may be redesigned
  • an e-commerce platform may be replaced
  • a Product may be discontinued
  • the active PIM may change
  • regulatory information may move to a long-term archive

If a QR code points directly to one temporary webpage, that QR becomes dependent on the lifecycle of that webpage.

A resolver avoids that dependency.

The Product can continue to use the same persistent identity while prodigi.link directs the user or system to the correct current resource.

How does prodigi.link identify a Product Model for an EU-DPP?

For the VTA-based EU-DPP route, a Product Model can use:

25P + VTA Product Model ID

For example:

VTA-MPLA-PM-346UJI3NUM

The prodigi.link representation is:

https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM

This identifies the Product Model independently from any Sales Unit GTIN.

prodigi.link can then resolve that identifier to resources such as:

  • EU-DPP
  • Product Model page
  • regulated Product information
  • instructions
  • repair information

How does prodigi.link resolve a Batch-level EU-DPP?

A Batch-level EU-DPP combines the Product Model identifier with the Batch or Lot qualifier.

For example:

https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM&.1T=LOT-2028-00425

Here:

  • 25P identifies the Product Model
  • 1T identifies the Batch or Lot

Both remain within the same Data Identifier scheme.

The identifier can therefore resolve directly to the EU-DPP for that specific Batch.

How does prodigi.link resolve a Serialized Item EU-DPP?

For a contextual Serial Number:

https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM&.S=000012345

Here:

  • 25P identifies the Product Model
  • S identifies the Serial Number

If Batch information is also relevant:

https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM&.1T=LOT-2028-00425&.S=000012345

SyncForce can also create a globally unique Serialized Item identity:

https://prodigi.link/?.25S=VTA-MPLA-SN-7F4K9X2Q

In that case the VTA-SN identifies the physical item independently.

Read more: How are Product Model, Batch and Serialized Item identified for an EU-DPP?

How does prodigi.link support Sales Units?

A Sales Unit remains a commercial object identified by GTIN.

prodigi.link supports GS1 Digital Link:

https://prodigi.link/01/{GTIN}

For example:

https://prodigi.link/01/08712345678901

This route can resolve to:

  • Marketing Landing Page
  • commercial Product information
  • contained Product Models
  • packaging information
  • regulatory Product links

The Sales Unit route is therefore different from the EU-DPP Product Model route.

Can a Sales Unit include qualifiers?

Yes.

Because the Sales Unit route uses GS1 Digital Link, GS1 Application Identifiers are used consistently.

For example:

Sales Unit + Batch

/01/{GTIN}/10/{lot}

Sales Unit + CPV

/01/{GTIN}/22/{CPV}

Sales Unit + CPV + Batch

/01/{GTIN}/22/{CPV}/10/{lot}

The important rule is:

GS1 primary identifier means GS1 qualifiers.

The GS1 route and the Data Identifier route should not be mixed.

Why should the GS1 and Data Identifier routes remain separate?

Because they are different identification systems.

For example:

25P

is an ASC MH10.8.2 Data Identifier.

10

is a GS1 Application Identifier.

SyncForce therefore does not build identifiers such as:

/25P/{ProductModel}/10/{lot}

Instead, the Data Identifier route uses:

25P

with:

1T

for a Batch.

For example:

?.25P={VTA-PM}&.1T={lot}

The same principle applies to Serial Number and other qualifiers.

This keeps each identifier interpretable within its own standards-based syntax.

How does prodigi.link support Packaging Systems?

Packaging Systems have their own persistent identity.

SyncForce uses:

31B + VTA Packaging System ID

For example:

31B + VTA-MPLA-PS-T46GD61T

prodigi.link supports two equivalent representations.

Human-readable path form

https://prodigi.link/31B/VTA-MPLA-PS-T46GD61T

Data Identifier query form

https://prodigi.link/?.31B=VTA-MPLA-PS-T46GD61T

Both identify the same Packaging System.

They do not create two Packaging Systems or two identities.

prodigi.link should normalize both to the same underlying identity and return the same associated resources.

Those resources can include:

  • PPWR dossier
  • Declaration of Conformity
  • recycling information
  • compliance documentation

The path form can remain the easier human-readable representation, while the query form provides the equivalent Data Identifier representation.

Can the same identifier resolve to different resources?

Yes.

That is one of the main purposes of a resolver.

A Product Model identifier may resolve to:

  • EU-DPP
  • Product Model page
  • repair information
  • instructions
  • regulatory documentation

A Packaging System identifier may resolve to:

  • PPWR dossier
  • Declaration of Conformity
  • recycling information

The identifier remains the identity of the object.

The individual resources are destinations associated with that identity.

This means:

One identifier can have multiple resources without becoming multiple identities.

Can the destination change over time?

Yes.

The persistent identifier can remain unchanged even if the destination changes.

For example, while a Product is actively marketed:

25P Product Model

↓

prodigi.link

↓

active EU-DPP service

Years later:

25P Product Model

↓

the same prodigi.link identifier

↓

long-term EU-DPP copy

The Product identifier does not have to change.

This is particularly important where regulated information must remain available after the commercial lifecycle has ended.

What is direct EU-DPP access?

Direct access means that the data carrier identifies the regulated Product itself.

For example, a QR code on a Product can encode:

https://prodigi.link/?.25P=VTA-MPLA-PM-BATTERY01

The flow is:

QR on Product

↓

Product Model identifier

↓

prodigi.link

↓

EU-DPP

No Sales Unit or Marketing Landing Page needs to sit between the Product and the EU-DPP.

For public EU-DPP information, this is the regulatory access path.

What is indirect EU-DPP access?

A Sales Unit can also provide an additional route to regulated Product information.

Consider an RC car Sales Unit containing two batteries.

The Sales Unit can use:

https://prodigi.link/01/{GTIN}

That can resolve to one Marketing Landing Page.

The page can then link to:

Battery Product Model A → EU-DPP A

and:

Battery Product Model B → EU-DPP B

This is indirect access.

It is useful for the consumer, but it does not replace a Product-level EU-DPP data carrier where the applicable regulation requires one.

Is a Marketing Landing Page the EU-DPP?

No.

A Marketing Landing Page and an EU-DPP serve different purposes.

A Marketing Landing Page can contain:

  • brand content
  • commercial information
  • consumer information
  • sustainability storytelling
  • instructions
  • links to regulated information

An EU-DPP is a regulated digital information object.

A Marketing Landing Page may display EU-DPP information or link to it, but that does not turn the Marketing Landing Page into the EU-DPP.

prodigi.link allows both use cases to coexist without confusing their identities.

How can the relationships be machine-readable?

The relationships between Sales Units, Product Models, Packaging Systems and EU-DPP resources can also be exposed through APIs or structured data such as JSON-LD.

For example:

Sales Unit

containsProduct → Product Model A

containsProduct → Product Model B

usesPackagingSystem → Packaging System C

A Product Model can expose:

hasEUDigitalProductPassport → EU-DPP

A Packaging System can expose:

hasDeclarationOfConformity → Declaration of Conformity

This allows software and AI systems to follow the same relationships that people can navigate through webpages.

What requirements apply to public EU-DPP routes?

For public EU-DPP routes, prodigi.link is part of the regulated access path.

The design therefore separates EU-DPP access from marketing functionality.

Public EU-DPP routes are designed to:

  • use secure HTTPS transport
  • work without login or registration for public information
  • work without requiring an app
  • avoid marketing tracking or profiling in the EU-DPP access path
  • support both human-readable and machine-readable representations
  • remain resolvable for the required EU-DPP lifetime

Marketing Sales Unit routes do not necessarily have the same restrictions because they serve a different purpose.

How does Perennis relate to prodigi.link?

prodigi.link provides the persistent identity and resolution layer.

Perennis provides the long-term regulatory publication and persistence layer.

Conceptually:

Product identifier

↓

prodigi.link

↓

Perennis EU-DPP

When an EU-DPP is active, prodigi.link can resolve to the appropriate current resource.

When long-term persistence becomes necessary, the same persistent identifier can continue to resolve to the preserved EU-DPP.

The identifier does not need to change simply because the hosting or lifecycle status changes.

What is the SyncForce principle behind prodigi.link?

The SyncForce Golden Hierarchy separates:

  • Product identity
  • Sales Unit identity
  • Packaging identity
  • EU-DPP identity

prodigi.link then connects those identities to the appropriate digital resources.

The key rule is:

The identifier identifies the object. The resolver finds the resources. The resource itself is not the identity.

See the full overview: How does SyncForce support the EU Digital Product Passport, EU-DPP?

In one sentence

prodigi.link gives Product Models, Batches, Serialized Items, Sales Units and Packaging Systems persistent digital identities that can continue to resolve to the right resources throughout their lifecycle.