Tyre Passports — your EPREL entry + type-approval, structured
Your tyres already have EPREL registration + UNECE type-approval + published rolling-resistance class. TracePass reuses all of it and adds lifecycle, rubber sourcing, and abrasion fields for a 95-field DPP.
Our promise
Compliance-ready in 2–4 weeks, without changing your existing systems.
Who this is for
Tyre (tire) manufacturers, importers, and distributors — passenger-car (C1), van (C2), truck / bus (C3), motorcycle, bicycle, and retreaded tyres.
How TracePass helps — Tyres
Concrete things TracePass does for this category — not a list of what the regulation requires.
EPREL URL + registration number + label class pulled straight from Michelin / Continental / Bridgestone / your EPREL entry.
UNECE type-approval number as a structured field — not buried in a PDF.
Rubber-composition arrays + EUDR-ready deforestation-free declaration field.
Abrasion data structured as test-method + rate + index — matches emerging UNECE R117 tyre-wear rules.
Retreaded tyres supported with casing-origin + tread-material fields.
Built against the Tyre Labelling Regulation (Regulation (EU) 2020/740) — rolling resistance, wet grip, external rolling noise, and snow / ice grip classes all surface as structured enum fields on the published passport.
What's in the Tyres template
95 fields — The fields aren't abstract — here are the groups you'll actually work with:
- Tyre size + load / speed index
- EPREL URL + registration number
- EU tyre-label classes (rolling resistance / wet grip / noise)
- UNECE type-approval number
- Natural + synthetic rubber %
- Deforestation-free natural rubber sourcing
- Abrasion rate + method + recyclability %
- Inflation pressures + carbon footprint
Questions buyers in this category ask
Does TracePass re-enter our EPREL data?
No — reuses it. EPREL URL, registration number, and classes become structured passport fields. One source of truth.
Retreaded tyres get their own DPP. Is that supported?
Yes. Retread declarations (casing origin, tread material) are first-class fields in the template.
We produce tyres in batches. Does one passport cover a whole production run, or do we need one per tyre?
TracePass issues per-batch passports, so a single DPP covers an entire production run rather than every individual tyre. You enter the batch's rolling resistance, wet grip and other regulated values once, and the same GS1 Digital Link QR is moulded onto the sidewall of all tyres in that batch. There is no per-scan or per-SKU billing, so a batch with thousands of tyres costs the same to publish as a small one.
How does the tyre DPP relate to our existing UNECE type-approval and Reg (EU) 2020/740 labelling data?
The tyre passport sits on top of the same data you already hold for UNECE type-approval and the (EU) 2020/740 energy label, including rolling resistance and wet grip classes. TracePass lets you upload your type-approval documents and test reports, and the AI extracts the regulated fields with confidence scores and source attribution so you can see exactly where each value came from. You review and approve before publishing, so the DPP stays consistent with what you have already declared, rather than becoming a separate source of truth.
Ready to generate tyres passports?
We're onboarding design partners now. The manufacturers who land first are the ones who move before the deadline pressure — that's our speed advantage and yours.
Reviewed by Malin Ivanov, Managing Director — on