---
title: Where Do You Fill In a Digital Product Passport?
description: "No EU portal accepts DPP data. You build a DPP on a compliant platform: pick a template, fill the fields, and publish — generating a GS1 Digital Link QR code."
canonical: "https://www.tracepass.eu/resources/dove-si-compila-il-dpp"
locale: en
source: "https://www.tracepass.eu/resources/dove-si-compila-il-dpp"
---

# Where Do You Fill In a Digital Product Passport?

> No EU portal accepts DPP data. You build a DPP on a compliant platform: pick a template, fill the fields, and publish — generating a GS1 Digital Link QR code.

One of the first questions companies ask when they learn about the Digital Product Passport is: where do I actually go to fill it in? Is there a form somewhere on a government website? The short answer is no — and understanding why matters for how you plan your compliance work.

## Is there an official EU DPP portal?

No. The EU does not operate a data-entry portal where you type in your product's DPP fields. The EU DPP Registry — managed under the ESPR framework — is a registry of identifiers and economic operators. It records that a DPP exists and who is responsible for it; it does not store the DPP's field data, and you do not enter product information directly into it.

## How do you create a DPP?

You create a DPP on a compliant platform or via its API. The process has four steps regardless of which platform you use:

- Pick the category — the category determines which field template applies (battery, packaging, electronics, textiles, and so on). Each category has its own mandatory field set under the relevant regulation.
- Complete the field template — enter the required values (material composition, carbon footprint, recycled content, compliance references, and so on) and attach supporting evidence (test reports, SDS files, certificates).
- Review and approve — the platform flags missing required fields or implausible values before you publish. A human approves the final record.
- Publish — the platform registers the DPP, generates a GS1 Digital Link QR code, and makes the record accessible to authorised parties (public fields, restricted fields for inspectors, authority-access fields for regulators).

## How is the DPP published?

When you publish a DPP, the platform mints a unique identifier and a GS1 Digital Link URL. That URL is encoded into a QR code which goes on the physical product (or its packaging). Anyone who scans the QR code is resolved to the right DPP record — the public data tier is openly readable, while restricted tiers require authentication. The data itself lives on the platform, not on the QR code.

## What TracePass provides

TracePass is the platform where you complete this process. For each regulated category, it ships a pre-built field template matching the regulation's field list — you fill in the values, attach evidence, and publish. You can work through the form in the browser, or drive the whole process via the REST API. A supplier portal lets you forward specific field requests upstream to the parties that own the data, so you are not limited to what your direct supplier can provide.

## FAQ

### Is there an EU government website where I enter my DPP data?

No. The EU DPP Registry records identifiers and responsible operators — it is not a data-entry portal. You create and host DPP data on a compliant platform like TracePass, not on an EU government site.

### How do I create a Digital Product Passport?

Pick the product category on a compliant platform to load the correct field template. Complete the required fields, attach supporting evidence, and publish. Publishing registers the DPP and generates a GS1 Digital Link QR code for the physical product.

### How is a DPP published and made available?

When you publish, the platform mints a unique identifier and a GS1 Digital Link URL, encoded into a QR code for the physical product. Scanning the QR code resolves to the DPP record — public fields are openly readable; restricted and authority-access tiers require authentication.

### Can I create a DPP via API instead of a web form?

Yes. TracePass exposes a REST API so you can create, update, and publish passports programmatically. This suits high-volume workflows — for example, creating one passport per manufactured unit from your ERP or production system.