The regulation applies, the field list does not yet Textiles first Structure now, fields later

Custom digital product passport software development

The ESPR is in force, but there is not yet a single delegated act specifying which data your product passport must contain. Anyone selling you a ready-made DPP package today is selling a gamble on rules that have not yet been published. What is settled is the structure: a unique identifier, a data carrier on the product and tiered access per audience. You can build that now, and the fields will hang off it.

What is and is not settled

Regulation (EU) 2024/1781 replaced the Ecodesign Directive and extended it from energy consumption to the sustainability, repairability and circularity of almost all physical products. The regulation itself, however, sets hardly any concrete product requirements. Those come per product group, in delegated acts that the Commission publishes step by step.

The April 2025 working plan identifies the first priorities, including textiles, aluminium and tyres. As things stand, no product-specific delegated act has been adopted; the textiles act is expected at the end of this year or early next year. A transition period of at least eighteen months then applies before the requirements actually take effect.

That is the catch, and it is the reverse of what suppliers tell you. You cannot yet know the field list, so you cannot buy it either. What you can do is answer the question nobody will solve for you: at what level do you identify a product, where does the data that will go into the passport live, and who may see which part. That work is the same today, and for most companies it takes longer than eighteen months.

If you work with timber or paper, a second provenance record runs alongside the passport. See FSC and PEFC chain of custody.

How we build this

It is not the field list but the identification that is the unit here. Once it is settled what a product is and where its data comes from, every later field requirement is just a setting.

1
Choosing the identification level

Does a model get a passport, a production batch, or each individual item? That is the heaviest choice in the entire process, because it determines how many passports you manage and whether you can link them to a physical object with an app.

2
Mapping the data sources

At most companies, material composition, origin, repair information and spare parts are scattered across PLM, ERP, specification sheets and the purchasing team's mailbox. Gathering that is the real work, not displaying it.

3
Structure first, configurable fields

We build the passport as a schema that you extend yourself, with version control per schema. When the delegated act for your product group appears, you add fields instead of starting over.

4
Baseline measurement on one product group

We run one product line through the system and show what is missing. That list is usually longer than expected, and it is the reason to start now.

What the software actually does

The passport register carries everything; the data carrier and the public view follow from it. Which components you need depends on your product type and your position in the chain.

Passport register with unique identifier

A unique identifier per product, batch or item, to which everything is attached. The system ensures that an identifier stays unique and is never reused, because a passport must still point to the same object years from now.

Schema per product group, configurable

You define the fields of a passport yourself and extend them as soon as the requirements for your product group appear. Each schema is versioned, so an old passport remains readable against the schema that applied at the time.

Creating and managing the data carrier

A QR code or other data carrier that points to the passport, with a permanent web address so the link keeps working even if your system changes later. Without that separation, you end up printing codes you can no longer move.

Collecting data from suppliers

Your supplier knows the composition and origin of components, not you. A portal where they submit this per component works better than an email thread in which nobody can see what is missing.

Tiered access per audience

A consumer, a repairer, a recycler and a regulator do not see the same information. The regulation is built on this tiering, so the permissions model is not an extra but a requirement.

History kept per passport

Who changed which data, when, and on what grounds. A passport lasts as long as the product does, which can be longer than the supplier who provided the data.

Who we build for

Your position in the chain determines which part of the passport you fill in yourself. Four situations.

Manufacturers

You make the product and determine its composition, so most of the passport comes from your own systems. Your customers will start asking you for the data before the obligation takes effect, and whoever has that side in order becomes the supplier of choice.

Brand owners and retailers with their own brand

You have products manufactured and place them on the market under your own name. The obligation therefore lands with you while the data sits with your manufacturer, often outside the EU. Requesting that data is then the whole job.

Importers and distribution

You import products and are often the first to place them on the market in the Union. Your supplier does not know the regulation and has no reason to study it, so the data request has to come from your side and has to be simple. The same challenge applies to the EUDR, where you must demonstrate origin down to plot level.

Online sales

A product passport touches your product information: the same data, a different presentation, a different audience. If your range runs through an integrated PIM or webshop system, the passport layer is an addition to it, not a second administration.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Everything the delegated acts will prescribe should be configurable and stored per version. Anything hard-coded will have to be rebuilt as soon as your product group is up.

Node.js / Python / .NET PostgreSQL Passport register with unique identification Schema management per product group and version Data carrier with permanent web address Public view separated from management Permissions model per audience Supplier portal Integration with PLM, ERP or PIM Alerts for missing data Export for supervision and audit Version history per passport Audit logging Hosting in the EU

Why Appfront

We don't sell a list of fields that doesn't exist yet

There is no delegated act yet. We build the structure and leave the fields open, and we tell you which part of your investment only pays off once your product group is up.

Identification is the decision that matters

Model, batch or individual item determines the scale of your entire passport administration. We put that choice first rather than letting it follow from a choice of package.

The data sits with your supplier

You cannot fill a passport with what you don't know. We build the supply side through integrations and a portal, and make visible what is missing.

Eighteen months is shorter than it seems

After the act for your product group is published, a transition period of at least eighteen months applies. For most companies, collecting supply chain data takes longer.

Security and privacy

A product passport is partly public, which makes the security question unusual: it is not about shielding data but about showing exactly enough. The regulation assumes tiered access, where a consumer sees less than a recycler and a regulator sees more than both. We build those tiers as a permissions model rather than as separate views, because two views of the same data drift apart over time.

The confidential side sits with your suppliers. Material composition and origin are close to their formulations and their purchasing position, and they will only supply them if they know who sees them. In the portal, a supplier therefore sees only their own components. On the retention side, a passport lasts as long as the product does, so history and schema versions must remain readable long after the source has gone. How we handle security ourselves is set out in our information security policy; reports from outside go through our CVD policy.

Frequently asked questions about the ESPR and the product passport

That differs per product group, and for no group is it final yet. The ESPR works through delegated acts; only once one has been published for your product group does a transition period of at least eighteen months start. Textiles are first in line and are expected around the turn of the year, which brings the obligation there towards 2028. Check the status for your own product group, as it may come later or earlier.

You can buy a system, but nobody can tell you which fields it needs to contain, because those have not yet been set. What is known is the structure: unique identification, a data carrier and tiered access. Anyone who promises you a fully populated passport today is filling it with an assumption. We build the structure and keep the fields configurable.

That depends on your product group and is determined in the delegated act. The difference is huge: a passport per model is a handful of records, whereas a passport per item means millions and calls for a completely different system. Because the choice carries so much weight, we put it first and build so that you can refine it later without starting over.

A PIM describes a product in order to sell it; a passport describes it so that it can be repaired, reused and recycled, and it is also aimed at parties who are not customers. The data partly overlaps. We therefore integrate with what you already have instead of setting up a second product administration.

For importers this is the hardest part, because your supplier has no obligation and no interest. What works is making the request as small as possible, in their language, with a portal that shows what is still missing. What does not work is a spreadsheet with two hundred fields. Start early, too, because the first round rarely yields usable answers.

The data overlaps; the approach does not. The PPWR covers packaging and its recyclability, producer responsibility covers weight per category, and the passport covers the product itself. What pays off is collecting the article data once and using it for all three.

They have to keep working. A passport lasts as long as the product, and for furniture, machinery or building materials that is longer than the time you keep the model in your range. That is why we build the data carrier with a permanent web address and keep the schema a passport was drawn up with, so that an old passport remains readable.

That depends on the identification level, the number of product groups and whether the supplier portal needs to be included. The register with the schema structure is usually quick to put to use and delivers the most value, because it gets the inventory under way; the portal and integrations cost more. We give a substantiated estimate after the discovery phase.

Preparing for the product passport?

Take one product and try to write down what it consists of, per component and per origin. Wherever you end up having to make phone calls is where the work lies, and that work does not depend on the list of fields that is still to come. We build this as a standalone application and as part of a broader project involving custom software.

Edit content