MATRIKEL

Digital Product Passport Software one scan from proof of compliance.

Matrikel is a digital product passport software solution for manufacturers and importers. Model it once, register every serial and publish a digital product passport that shows the right data to the right person, automatically. Batteries, textiles, electronics or whatever's next in the EU regulation.

One schema, any category EU registry integrated GS1 Digital Link First deadline 18 Feb 2027

Product Unit A200

SN-88213

scan
9:41
id.matrikel.eu/.../SN-88213
Battery pack

Product Unit A200

SN-88213

Active
Public Pro Reg
Material composition
Steel, composite
Carbon footprint
12 kg CO₂e
Recycled content
24%
Expected lifetime
10 years

Scan the label. The page that loads depends on who's looking.

Built against Regulation (EU) 2023/1542 Regulation (EU) 2024/1781 GS1 Digital Link

Digital Product Passport compliance is a data modelling problem wearing a legal disguise

The regulation doesn't ask for a PDF. It asks for structured, per-unit data that stays retrievable for the life of the product, that different audiences see different slices of, and that gets reported to a central EU registry the moment it's created. Most manufacturers and importers are trying to solve that with spreadsheets and a supplier email thread. That breaks down past the first product line.

Spreadsheet & email

  • Per-serial identifiers

    Manually generated, easy to duplicate

  • EU registry filing

    A separate, manual submission step

  • Access by audience

    One document, one audience

  • Supplier data collection

    Email threads, inconsistent formats

  • Retention if you stop trading

    No mechanism

Matrikel

  • Per-serial identifiers

    Issued and validated automatically per unit

  • EU registry filing

    Filed the moment a serial is registered

  • Access by audience

    Public / professional / regulator, enforced per field

  • Supplier data collection

    Scoped fill-in link per supplier, reviewed before publish

  • Retention if you stop trading

    Backup-custodian hosting for the mandatory retention period

From product model to a live Digital Product Passport in four steps

01

Model your product

Define composition, materials, origin of critical raw materials, and lifecycle CO₂ once per model, validated against the mandatory fields for your product category.

02

Register serials at scale

Upload a production batch by CSV or push it through the API. Every serial number gets its own item-level record and its own identifier.

03

Publish a tiered passport

One URL per unit. Public label view for consumers, an authenticated view for repairers and recyclers, full access for regulators.

04

Stay compliant as it evolves

Every identifier is filed with the EU registry automatically, and the passport updates over the product's life — charge cycles for a battery, wash cycles for a textile, repairs for anything.

The dashboard

Your whole catalog's Digital Product Passport compliance, in one screen

Not one passport at a time — every product model you've created, how much of its required data is actually filled in, which certificates are about to expire, and whether anyone's actually scanning what you've published.

  • Portfolio-level compliance

    See at a glance how many required fields are filled in across every product model, published and draft, instead of checking one at a time.

  • Certificates with real expiry tracking

    Upload declarations of conformity, test reports and certificates once. Matrikel flags anything expiring within 30 days before it becomes a problem at an audit.

  • Know who's actually scanning

    Every public passport view is counted, with no cookies and no personal data, so you can see whether anyone's using the QR code you printed.

app.matrikel.eu/dashboard
82%

Catalog readiness

Product models

14

11 published · 3 draft

Scans, 30 days

1,204

Needs attention

EV-75 Pack 62%

Documents expiring

ISO 14001 certificate 12 days

The same two layers, in every Digital Product Passport you build

The Battery Regulation and ESPR both structure requirements the same way, whatever the product: what it's made of, how long it lasts, how it can be repaired, and what happens to it at end of life. That's what model-level and item-level data are built to capture — batteries are simply where the legal detail is most finalized today, since Annex XIII is fixed law.

Don't see your category? Tell us what you need — the data model is designed to extend.

Two levels of data in every Digital Product Passport

Model-level data is filled in once per product model: composition, origin of materials, carbon footprint per lifecycle stage. Item-level data is per serial number: production date and site, test results, and dynamic data pushed later. The rows below mix categories on purpose — the shape doesn't change.

Model

  • Chemistry & cell composition
  • Fibre composition
  • Component bill of materials
  • Carbon footprint per lifecycle stage
  • Recycled content %

Item

  • Serial number & production batch
  • Manufacturing date & site
  • Test / conformity report reference
  • Dynamic lifecycle data
Field Category Level Example value
Chemistry & cell composition Batteries Model NMC 811
Fibre composition Textiles Model 60% cotton, 40% recycled polyester
Component bill of materials Electronics Model 34 components, 6 flagged substances
Carbon footprint per lifecycle stage Any category Model 38 kg CO₂e, manufacturing stage
Recycled content % Any category Model 16–24%, depending on category
Serial number & production batch Any category Item SN-88213, batch 2026-07-B
Manufacturing date & site Any category Item 12 Jul 2026, plant reference
Test / conformity report reference Any category Item IEC 62619 (batteries) · EN ISO 13934 (textiles)
Dynamic lifecycle data Any category Item State of health, repair log, resale event

Field set shown is illustrative. Production schemas are validated against Annex XIII of Regulation (EU) 2023/1542 for batteries, and against each category's own delegated act as ESPR brings it into scope.

Every passport gets a real URL, built on the GS1 Digital Link standard — so any GS1-compliant scanner can resolve it, not just ours:

matrikel.eu

Host

/
01

AI 01

/
{gtin}

GTIN — product model

/
21

AI 21

/
{serial}

Serial number — this unit

The same data is available over the API, for teams who want to pull it into their own systems instead of clicking through ours:

GET /api/v1/product_models/:gtin
$ curl https://matrikel.eu/api/v1/product_models/04012345678901 \
  -H "Authorization: Bearer $MATRIKEL_API_KEY"

200 OK
{
  "gtin": "04012345678901",
  "category": "batteries",
  "status": "published",
  "passport_url": "https://matrikel.eu/01/04012345678901/21/SN-88213"
}

Illustrative request/response. Requires a bearer token, issued from your dashboard.

What each side of the desk gets from your Digital Product Passport

For manufacturers

  • Model your product once against the fields your category requires
  • Register a production batch by CSV or API in minutes
  • Generate print-ready QR / GS1 Digital Link codes per unit
  • Push lifecycle updates from your BMS, test systems, or service records after sale

For importers

  • Send your overseas manufacturer a scoped fill-in link, not a spreadsheet
  • Review and approve supplier-submitted data before it goes live
  • Keep one system of record even when suppliers change
  • Stay covered by backup-custodian hosting if a supplier stops trading

For compliance teams

  • One tiered viewer enforces public / professional / regulator access per field
  • Every identifier is filed with the EU registry automatically
  • Full audit trail and versioning on every model and item record
  • Export the exact data set an auditor or market surveillance authority asks for

Digital Product Passports are a legal record. We treat the hosting like one.

The regulation expects a passport to outlive the company that created it. That shapes how we build: data stays in the EU, every read and write is attributable, and access is enforced at the field level so a public viewer can never see what a regulator sees — or the other way around.

Talk to us about security & procurement questions

EU-hosted data

Passport data is stored and processed in the EU, separate from the central registry.

Role-based access

Public, professional and regulator tiers are enforced server-side, per field.

Full audit trail

Every model and item change is timestamped, attributed and versioned.

Retention by design

Backup-custodian hosting keeps passports live for the mandatory retention period.

Get your first Digital Product Passport live before the deadline

Tell us what you sell and where. We'll show you what your passport would look like.

Request a demo

Digital Product Passport questions we get from manufacturers and importers

What exactly is a Digital Product Passport?

A structured, machine-readable record tied to a specific product unit — typically via a QR code or NFC tag — that covers composition, origin, carbon footprint, repair and recycling information. It's a requirement of Regulation (EU) 2023/1542 (the Battery Regulation) and, over time, Regulation (EU) 2024/1781 (ESPR).

Which product categories does Matrikel support today?

Batteries first, because the deadline (18 February 2027 for industrial and EV batteries over 2 kWh) and the Annex XIII data schema are already fixed. Textiles are next. Every category shares the same underlying model-and-serial data structure, so we extend into new categories rather than rebuilding.

Where does the actual passport data live?

With you, or with us as your hosting provider — not with the EU. The central EU registry only stores the unique identifiers, so customs and market surveillance authorities can confirm a passport exists and resolve it. The regulation is explicit that the registry is not where the data lives.

What happens to our passports if we stop trading?

The regulation requires a back-up hosting arrangement so passports remain accessible for the mandatory retention period regardless of what happens to the original manufacturer. That continuity is a built-in part of what we offer, not an add-on.

How does the EU registry integration work?

When you decide to register a serial number in Matrikel, we generate a unique identifier, issue the QR code, and file that unique identifier with the central EU registry automatically. You don't have to file it seperately.

We import from manufacturers who won't fill in a compliance form. Now what?

That's the case we hear most often. The supplier fill-in portal lets you send your manufacturer a plain link scoped to just the fields you need from them, in their language, without giving them access to your dashboard.

Let's look at your Digital Product Passport

Tell us what you sell, roughly how many SKUs, and where you're importing from. We'll reply with what your first passport would need.

Request a demo

Prefer email? hello@matrikel.eu