tyrepas.eu

How does the tyre size relate to the unique identification code?

Tire size and unique code are not the same

The tire size is a technical designation of a tire — for example the width, aspect ratio and rim diameter — and the unique identification code is a separate characteristic that links a specific product or product model to its digital product passport. The size indicates something about the physical properties of the tire, the code indicates which passport belongs to it. A tire with size 205/55R16 can exist in multiple versions — from different manufacturers, with different compositions or production years — and each of those versions requires its own passport. The size alone is therefore not sufficient to uniquely identify a tire; the identification code serves that purpose.

Who this is relevant for, and what it is not

This distinction is relevant for everyone involved in compiling, consulting or linking a product passport for tires: importers, wholesalers and fleet managers who purchase, register or resell tires. This concerns the question of how a tire is identified within the digital product passport system, not the question of what technical requirements apply to a tire — those are set out elsewhere and have not yet been established for tires. It also does not concern type approval or homologation numbers for tires; that existing numbering is separate from the unique identification code from the ESPR, even though both data can ultimately end up in the same passport.

When this will apply

There is no fixed date yet for when the requirements for the tire product passport — including the way the unique identification code is applied — will actually come into force. According to the European Commission's work plan for the ESPR (2025-2030), the delegated act for tires is expected in 2027; only after publication of that act will a date follow on which the obligations take effect. Until that time, there is no legal obligation to provide tires with a uniquely identified product passport. What is established, however, is the general framework from the ESPR itself: Article 12 provides that a product passport contains a unique identification code by which the product or product model can be traced. That framework will apply in future to all product groups for which a delegated act has been adopted, so tires once that act is in place.

How this will work in practice later on

Anyone now considering how to connect to the digital product passport would be wise to continue distinguishing between the data that describes the tyre and the identifier that identifies the tyre. Tyre size, load index, speed category and the like are descriptive data that will appear in the passport as part of the technical information about the product. The unique identification code is additionally the means by which that specific passport is retrieved — for example via the QR code that is affixed to or with the tyre. In practice, this means that two tyres with exactly the same size can nevertheless each have their own code and their own passport, because they are from a different manufacturer, a different production model or a different composition, for example. For those having passports compiled, it is therefore important to be clear about the level at which the code is assigned: per product model, per batch, or — as is customary for many other product groups — per model with a shared passport for identical versions. As long as the delegated act for tyres is not yet in place, that detail remains unsettled, but the starting point from Article 12 of the ESPR — that the code makes a product or product model uniquely traceable — does provide the framework within which that choice will be made. For an importer or wholesaler, this is particularly relevant when setting up their own product administration: it is worthwhile to already register tyre size and other technical characteristics separately from manufacturer or model codes, so that a later link to a unique identification code can proceed without restructuring of the organisation's own data.

Where this is based on: Article 12 of the ESPR

This relationship between descriptive data and identification follows from Article 12 of Regulation (EU) 2024/1781 (ESPR), which stipulates that the digital product passport contains a unique identification code for the product or product model. That article governs the identification element of the passport in general terms, for all product groups falling under the ESPR. The specific application for tyres — including the question of how tyre size and identification code will later be concretely presented alongside each other in the passport — follows from the delegated act that has yet to be adopted and published.

Anyone wanting to get started now would be best advised to start by separating technical tyre data (such as size) and model data in their own administration, and to follow developments around the delegated act for tyres via the official source. Once that act is published, this page will be supplemented with the concrete date and the precise requirements for the identification code for tyres.

What this is based on

The regulation itself is available on EUR-Lex. We provide references per statement; you do not have to take our word for it.

What you must do concretely

What is expected of you

Treat each tyre size as a separate product

Article 12 of the ESPR (Regulation (EU) 2024/1781) links the unique identifier to the product, not to a model name or brand name. A tyre sold in four sizes is, in practice, four different products for the digital product passport: each size receives its own identifier, and thus its own passport. For a company with 10 to 100 employees, this means that passport management scales with the number of SKUs, not with the number of models. A company carrying ten models with six sizes each manages, in practice, sixty identifiers. This requires a system that keeps the link between model and size transparent, because manual tracking quickly becomes unmanageable at these numbers. More on the structure of that code is covered in how each product receives a unique identification code.

Keep the code traceable to the correct technical data

The identifier is only useful if it actually points to the correct dataset. Tyre size, load index, speed category and tread type belong to one specific code, and a mix-up between two similar sizes results in a passport that does not match the physical product. For administration, this means that the coupling file between article code and passport data must remain current and error-free, even when a supplier adjusts a specification in the meantime.

Ensure that each size retains its own code, even when reusing data

Tyre manufacturers often work with one base recipe per tread pattern, which is then rolled out across multiple sizes. The underlying test data and material information may then be largely the same for multiple sizes. This does not change the requirement that each size receives its own identifier: it concerns the product as placed on the market, not the source of the underlying data. How that data reuse works without the identifiers themselves overlapping is covered in reuse data for other tyre sizes of the same model.

Align the code with the data carrier on the product

The identifier itself is a data point in the passport; the QR code on the tyre is the means by which that code is accessed. Both must align: the QR code on the tread or sidewall of a specific size must point to the passport of precisely that size, not to a generic passport for the entire model. This coupling is also relevant to the application method and placement on the rubber; see how the QR code is applied to the tyre.

Where things go wrong in practice

One passport for an entire product line. An importer creates one passport for a tyre model and directs each size to the same QR code, because the technical differences between sizes seem small. Upon inspection, the load index per size differs, while the passport shows only one value.

Mix-up between similar sizes in the source data. When loading manufacturer data into a spreadsheet, two rows with nearly identical size designations (for example, a difference of one digit in rim diameter) are swapped. The identifier is correct, but points to the specifications of the wrong size.

No unique code for private label variants. A distributor has the same tyre sold under its own brand name in a size different from what the manufacturer originally supplies. No new identifier is created because it is "basically the same product," while for the passport it is a different product.

Revised size specification without a new code. A manufacturer adjusts the speed category of an existing size after a new test, but the existing identifier and QR code remain unchanged. As a result, the passport temporarily shows outdated data under a code that now corresponds to a different specification.

Coupling between ERP article code and passport code becomes loose. When switching systems or migrating your inventory system, the internal article code is adjusted, but the link to the associated digital product passport identification code is not moved along. Issues regarding that link with your own system are discussed in linking the digital product passport to an ERP or inventory system.

What you can record

  • An overview per model in which each tyre size has its own row, with the associated identification code, load index, speed category and tread pattern designation next to each other.
  • An established procedure for creating a new identification code as soon as a new size, private label variant or revised specification is introduced.
  • A control step in the purchasing or import process in which the manufacturer data supplied per size is checked before it is linked to an identification code.
  • An established mapping table between the internal article code (or SKU) and the digital product passport identification code, including a note of each change in the inventory system.
  • Documentation of which underlying test data are shared between sizes and which are specific per size, so that data reuse remains traceable.
  • An archive of previous versions of the size specification, so that when an identification code is changed, it is clear which data belonged to which period.

This is not legal advice. This page provides general information about the legislation that this platform concerns. We do not know your situation. If you are in doubt about your own case, consult a lawyer or the competent supervisory authority.

Written with AI based on the sources above, checked by a human on 2026-08-22. Is something incorrect? Let us know — corrections are given priority.