CirculeID

Platform

One record. Five regulations. Every party that has to read it.

CirculeID assembles a product record from the systems you already run, proves where each claim came from, and resolves it to whoever is asking — a consumer with a phone, a recycler at an intake line, or a market surveillance authority.

Book a demoRead the documentation
Identity
GS1 Digital Link
Events
EPCIS 2.0
Claims
W3C VC 2.0
Digital Product Passport
VERIFIED

GS1 Digital Link

id.circuleid.com/01/09506000134352

Product
Merino Crew Knit
GTIN
09506000134352
Material composition
82% RWS merino · 18% recycled PA
Carbon footprint
14.2 kg CO₂e · ISO 14067
Recycled content
18.4% by mass
End-of-life route
Take-back · fibre-to-fibre
did:web:circuleid.com · EcoDesignCredential · ES256

Illustrative passport record. Field coverage follows the ESPR delegated act for the product group.

Definition

What does a Digital Product Passport platform do?

A Digital Product Passport platform assembles product data from existing systems, issues each product a resolvable identity and a data carrier, attaches signed claims and supply chain events to it, applies role-based access to the result, and reports the same record into the format each regulation requires.

The hard parts are the last two. Assembling data is an integration problem; proving who asserted each figure and releasing the right slice to the right party is what the ESPR actually asks for, and what separates a passport from a product page.

How it works

From your systems to a scannable product

Four stages. The platform's job is to make the first one small and the last three automatic.
  1. 01

    Connect and map

    ERP, PLM and carbon accounting data maps onto a CIRPASS-aligned model. The gap report names the fields your product group still needs.

  2. 02

    Collect signed evidence

    Suppliers assert composition, certifications and footprint under their own keys, so every claim carries its author and its date.

  3. 03

    Issue the passport

    The product receives a GS1 Digital Link identity and a carrier payload. The record resolves from that identifier for the life of the product.

  4. 04

    Serve and report

    Each caller gets the tier their credentials allow, and the same record is projected into the form each regulation asks for.

Platform · 01

Core capabilities

What the platform issues, proves and tracks.

Platform · 02

Infrastructure

The layer your systems integrate with.

Platform · 03

Analytics

What the passport data tells you once it exists.

Architecture

Six layers, none of them ours

CirculeID implements published standards rather than inventing a proprietary model. That is what makes the passport portable: if you leave, the data still resolves, still verifies, and still means the same thing.
The standards we implement

  1. Regulatory reporting

    ESPR · Battery Regulation · CSRD · EUDR · PPWR

    Each regulation is a projection of the record below it, not a separate dataset to collect.

  2. Passport data model

    CIRPASS · CEN-CENELEC JTC 24

    The field definitions the delegated acts are converging on, so a new requirement is a mapping rather than a rebuild.

  3. Verifiable claims

    W3C Verifiable Credentials 2.0

    Recycled content, chain of custody and conformity signed by the party asserting them. Verifiable without trusting CirculeID.

  4. Supply chain events

    GS1 EPCIS 2.0

    What happened, to which object, where, when and why — the interoperable event vocabulary the industry already uses.

  5. Issuer identity

    W3C Decentralized Identifiers

    Each issuing party has a resolvable identity, so a signature can be checked years after the product was made.

  6. Product identity and carrier

    GS1 Digital Link

    A QR code, NFC tag or RFID that resolves to the passport — one identifier that works in retail, logistics and the web.

Answers

Frequently asked questions

Is CirculeID a replacement for our ERP or PLM?

No. It sits above them. Your ERP holds transactions, your PLM holds specifications and your carbon accounting system holds footprint calculations. CirculeID assembles a passport as a view over those systems, so the product record is one more consumer of data you already maintain rather than a second place to key it.

What exactly does the platform produce?

A resolvable Digital Product Passport: a GS1 Digital Link identifier, a data carrier payload to print or encode, a role-scoped record behind that identifier, EPCIS 2.0 events describing what happened to the product, and W3C Verifiable Credentials carrying the claims that have to be provable.

How long does an implementation take?

Issuing a first passport takes days. Getting a product group to a state where every required field has an attributable source usually takes a quarter or more, because the constraint is supplier engagement rather than software. Programmes that plan around the supplier timeline hit their delegated act dates; programmes that plan around the software do not.

What happens when a delegated act changes the required fields?

Passport data is stored against a CIRPASS-aligned model rather than a regulatory form, so a new or amended requirement becomes a mapping change. CirculeID tracks delegated acts as they are adopted and reports which of your products fall in scope and which fields are not yet covered.

Can we host passports on our own domain?

Yes. The GS1 Digital Link identifier can resolve under your own domain, which matters because the passport is a long-lived public artefact carrying your brand. It also means the identifier does not become a dependency on a vendor’s hostname that would be painful to change later.

Next step

See it against your own product data

One product group, one export from your PLM. We will show you the passport it produces and exactly which fields are still missing.

Book a demoRead the docs

Index

Related reading