tyrepas.eu

What determines the cost of a software integration for the tire passport?

The price of an integration between your company software and the digital product passport for tires does not depend on a single fixed rate, but on a few concrete choices you can inquire about in advance.

What a software integration for the digital product passport for tires costs depends mainly on three things: how much product data you have already recorded in a structured way, how your current system (ERP, inventory management, webshop) can send data outward, and whether you choose a one-time integration or a continuous, automatic data submission. There is no fixed rate that applies to every company, because these three factors differ greatly from company to company.

The underlying reason is that the passport itself is not a separate product that you buy, but a dataset that must continuously match what you sell. An integration is therefore not a one-time task that you check off, but a connection that continues to work as long as your assortment changes. That determines where the money goes: not only to the technology, but also to maintaining that connection.

Where the amount comes from

A software supplier typically charges based on the time needed to unlock your data. If you already have one central place where article numbers, material data and test results come together, the integration is relatively straightforward: only an export needs to be built to the format that the passport expects. If that same data is spread across multiple systems, spreadsheets or even on paper at a supplier, then the largest part of the work is in bringing that together, not in the integration itself.

A second cost item is the number of product lines. An importer with a few tire sizes has a more manageable task than a wholesaler with hundreds of SKUs from different manufacturers. Not because the technology differs per product, but because each product number needs its own source data, and that has to come from somewhere.

A third factor is the form of the service: a one-time data submission at the start of the passport costs less than a setup where changes in your assortment flow through automatically. The latter requires a structural connection between your system and the party hosting the passport, and that work is usually charged separately, apart from the one-time setup.

What you can inquire about before you receive a price

To get a realistic picture of the costs, it helps to have a few things clear beforehand: which part of your data is already digital and structured, who within your chain is responsible for which data, and whether you fulfill the role of provider or another market participant. The latter also partly determines which data you must submit yourself and which are already provided by another party in the chain. read the concepts and roles carefully gives a first picture of that, without you needing a lawyer right away.

It is also useful to ask what happens when there are changes: a new tire size, modified material, or a correction on previously submitted data. Some suppliers charge that as a separate assignment, others include it in a fixed amount per period. Both are common practice, but it makes a difference in the final bill and in how predictable the costs are over the longer term.

Hosting, QR code and duration

In addition to the integration itself, the hosting period and the QR data carrier play a role in the total amount. The passport must remain accessible over a longer period, and that retention obligation is part of the service, not something you arrange separately later. If you want to compare that amount between providers, it is advisable to ask exactly what is included: only the one-time setup, or also the years of keeping the data available and the QR code that refers to it.

Because the exact implementation date of the obligation is not yet fixed — the delegated act within the ESPR work plan is expected around 2027, with expected practical application around 2029 — it is advisable to discuss a connection that grows as the definitive requirements become known, rather than fixing now what could still change. how those data are produced exactly shows which steps are fixed and which still depend on the final regulations.

Get a first impression yourself

Before you speak with a software provider, it is helpful to already know yourself roughly where you stand: how many product lines are involved, how your data are currently recorded, and what role you fulfil in the chain. This makes the conversation more concrete and prevents you from receiving a price based on assumptions that do not fit your situation. An overview of the expected costs therefore depends greatly on what you already have in order yourself; an overview of what a package at tyrepas.eu includes shows which components are standard included.

Do you first want to get clear for yourself where you stand before you approach a supplier? Then do the free quick-scan or read through the other topics at your leisure; see in a few questions where your company currently stands provides a first direction for that, without you committing yourself to anything immediately.

This article is general information and not legal advice.