The short answer
Nothing is changing this year regarding a legal obligation, because the delegated act that sets out the precise requirements for the tyre passport has not yet been published. According to the work plan of the ESPR Regulation (2025-2030), that act is expected around 2027, and only then will it become clear from which date companies must actually deliver. What is changing is the extent to which software providers are preparing: standards for data exchange are becoming more concrete this year, and you will notice that in what providers offer and promise you.
For you, that mainly means this: it is a good time to have a conversation with your software provider, but not to sign a contract now as if everything is settled. A provider who says they are fully "ESPR-proof" is essentially anticipating rules that are not yet definitive. That is not necessarily a problem, but it is something to question critically.
What is concretely moving this year
The regulation itself has been in force for some time as a framework law; what is missing is the implementation specifically for tyres. In the meantime, European standardisation organisations are working on technical standards for how a digital product passport must be structured: what data format, what link with the QR code, what minimum fields. Those standards are not the same as the delegated act, but providers are already building their software on them, because no one wants customers to have to transfer everything later.
The result is that the offering from software providers is changing this year: some are adding functions for data management per tyre model, others are already offering a link with a hosting provider. For you, the question is not so much "is my provider ready yet", but "is my provider building in a way that aligns with where the standards are moving". That distinction is difficult to assess yourself without background in this matter, and that is exactly where many entrepreneurs get stuck in the conversation.
What you can settle this year
Although the final requirements are still missing, there are things you can already agree with a software provider this year without anticipating rules that still need to come. Think of agreements about who provides the source data, how long data is retained, and what happens if a standard changes after you are already connected. The latter is relevant, because a contract signed now often continues until after the expected date of entry into force.
It is wise to ask in that conversation about the origin of the data that will fill the passport, and about who is responsible if a manufacturer adjusts his data later. review the concepts and obligations by situation provides an overview of where these agreements are about in practice, regardless of which provider you choose.
Why this is different from "waiting until it happens"
Some entrepreneurs decide to leave this matter alone until the delegated act is there. That is a legitimate choice, but it has a downside: the parties that are already taking part in pilots and early connections are building up experience with the standards before they become mandatory. Those who join later may do so under time pressure, at the moment when everyone is looking for a provider at the same time.
That is not a reason to rush into a contract now, but rather to know where you stand. see in a few questions whether this is relevant for your company provides a first direction there, without you immediately being committed to anything.
What remains the same
The role distribution in the supply chain does not change as a result of these technical developments: who is the manufacturer, importer or distributor remains decisive in determining who must provide which data. The ten-year hosting period and the requirement that data is accessible via a QR code are also already established as a starting point in the framework regulation, even if the precise implementation for tyres has not yet been published. Supervisory authorities in the Netherlands and the EU do not yet have a concrete enforcement framework for tyres specifically, simply because the underlying rules do not yet exist.
If you want to know how this data is technically processed and where the information on tyrepas.eu comes from, you will find that explained on how the data is compiled into a passport. For questions not covered in this article, there is an overview of questions that other entrepreneurs asked.
Finally
This subject does not change this year in what is legally required, but in what software suppliers offer and promise you. For your own situation, and for the question of whether a specific supplier aligns with what is still to come, a lawyer or the competent supervisory authority remains the appropriate point of contact.
Would you like to see now where your company stands, without obligations? Do the free quick-scan or browse through the subjects that are relevant for your situation.