Industry Guide 📅 September 5, 2026 ⏱ 12 min read

RFID for Tyre Manufacturing and the EU Tyre Digital Product Passport

Truck tyres moving through a fixed UHF RFID read portal on a plant dispatch line, with a handheld reader in use at an inspection bench alongside

A tyre is one of the few mass-produced items that already carries an RFID tag because the industry put one there years before any regulator asked. The tag went in for warranty, recall traceability and retreading, at volume, for years. The EU Digital Product Passport arrived afterwards and found the carrier already fitted.

That changes the buying question. For most ESPR product groups the argument is still whether a printed code or a chip should carry the passport link. For tyres, GS1 and the RAIN Alliance have published a joint DPP statement in which the RAIN Alliance calls RAIN “a well-positioned data carrier solution for DPPs”, and in which Michelin’s pilot section specifies SGTIN-96 encoding for tyre applications in that project. So the open question for a plant, a retreader, a fleet or a distributor is the read side: where the portals go, what a handheld must do in a fitment bay, and how a read event reaches the system that will own the passport record. We build the UHF readers behind those read points, so that is where this guide stays.

Why tyres went to RFID before the regulation asked

Five manufacturers — Michelin, Bridgestone, Continental, Goodyear and Pirelli — founded the Global Data Service Organization for Tires and Automotive Components in early 2022 to standardise how tyre data is exchanged, according to RFID Journal’s account of the sector. Direct competitors agreed a shared identifier layer three years before the ESPR working plan named tyres at all.

The carrier was standardised earlier still. RFID Journal reports that the international standard for coding RFID tyre tags, published in 2019, set out general requirements and a data structure for electronic tyre identification, and that one supplier, Hana RFID, has provided over 250 million tyre tags to date, with tags able to sustain the one million kilometre life of some commercial tyres.

Four commercial drivers came first, and they still pay for the read points.

Warranty and claims. A serialised casing settles which line and which week built it, straight off the tag on a road-filmed sidewall.
Recall traceability. A serial scoped to a curing press and a shift turns a model-wide recall into a batch-level one.
Retreading eligibility. A casing is worth retreading when its history is known, and the tag is the one thing that stays with it through its first life.
Fleet management. Wheel-position association, rotation records and removal reasons all rest on the tyre identifying itself at fitment.

The regulatory clock

Tyres are a named priority product group in the Ecodesign for Sustainable Products and Energy Labelling Working Plan 2025–2030, COM(2025) 187 final, adopted 16 April 2025. The plan ranks tyres third in the Commission’s JRC prioritisation, sizes the EU market at EUR 45 billion on 2021 figures, and gives an indicative adoption date of 2027 for the delegated act, citing potential to improve recyclability and recycled content and to reduce end-of-life waste risk.

The second date comes from the ESPR itself. Article 4(4) of Regulation (EU) 2024/1781 sets the date of application of a delegated act at no earlier than 18 months from entry into force, except in duly justified cases. An indicative 2027 adoption plus that minimum transition is what puts practical tyre compliance around 2029 — arithmetic on an indicative year, so treat it as a planning horizon rather than a fixed date.

The scaffolding underneath is further along than the product rule. CEN and CENELEC report that CEN-CLC/JTC 24 has delivered eight European standards for the DPP system: EN 18216 (data exchange), EN 18219 (unique identifiers), EN 18220 (data carriers), EN 18221 (storage and persistence), EN 18222 (APIs), EN 18223 (interoperability), EN 18239 (access rights and security) and EN 18246 (data authentication). Six of the eight are already cited in the Official Journal.

Fixed today: tyres are in scope, the framework is in force, the horizontal standards exist. Indicative today: the 2027 year and the exact fields. That is still enough to specify serialisation and read infrastructure now, because both are decided by your process.

Michelin, CIRPASS-2 and why the reference pilot chose RFID

Michelin coordinates the tyre DPP pilot inside CIRPASS-2, the EU-funded project running DPP demonstrators across priority sectors. CIRPASS-2’s pilot page describes a team of seven stakeholders in three countries; the GS1 and RAIN Alliance statement describes the same pilot as bringing together 12 companies and associations. The partner list is the more useful detail: retreaders, recyclers, a collector, a sorting machinery maker, a transport operator, a tyre services chain, plus GDSO and GS1.

The approach is stated in one line on that page, as a tyre DPP built on “RFID – ISO Standard for electronic tyre ID and GDSO: tyre industry dataspace”. The stated objectives are more sustainable tyre design, easier access to tyre information for retreading and recycling, and new end-of-life valorisation channels.

That last objective is why an embedded carrier won. The passport has to be readable at the moment of the decision, and the decisions that matter most — retread or recycle, recycle or recover — come at the end of a life spent abraded, kerbed, hot, wet and covered in road film. A moulded DOT code survives that and identifies the mould and the week. A serialised identity, machine-read at line speed, is what the embedded tag adds on top: a carrier still present, and still readable, when the sorting line needs it.

Cite it accurately in a tender. The regulation sets the data obligation and leaves the carrier to the delegated act and the CEN standards; the tyre industry chose RFID on its own reasoning and got there first, already standardised and in volume.

The encoding the reference pilot has already settled

The GS1 and RAIN Alliance joint DPP statement, published in September 2025, records the RAIN Alliance’s position that RAIN is “a well-positioned data carrier solution for DPPs” and, in its Michelin section, states that for tyre applications in the project the unique item identifier shall be coded using SGTIN-96 per the GS1 EPC Tag Data Standard. That is unusually prescriptive this early, and it gives your project a defensible default to specify against rather than an open question.

SGTIN-96 is a serialised GTIN written as a 96-bit EPC into the EPC bank of a Gen2 tag. Per the GS1 standard those bits divide into an 8-bit header, a 3-bit filter value, 47 bits carrying partition, GS1 Company Prefix and item reference, and a 38-bit serial with a range of 0 to 274,877,906,943. The same identifier maps to the GS1 Digital Link form https://id.gs1.org/01/{gtin}/21/{serial}, which is what turns a tag read into a passport lookup.

Release 2.3 of the EPC Tag Data Standard, ratified October 2025, matters here. It adds twelve ‘++’ schemes, SGTIN++ among them, encoding a custom domain name losslessly after the serial so an EPC translates back to a GS1 Digital Link URI on the brand owner’s own domain — the difference between a tag that yields a number and a tag that yields a resolvable address. Contributors to the joint statement also describe dual-frequency HF plus UHF parts, pairing B2B reading with smartphone interaction where the passport has a consumer-facing side.

Encoding sits upstream of every read point, so the line needs a verification read after cure proving the tag survived and that its EPC matches the record you will publish — a pass or fail gate with a defined route for each outcome.

Read points across a tyre’s life

A tyre is read more times, by more parties, than almost anything else carrying an EPC. Each of those moments has its own right answer: a fixed portal for some, a handheld for others.

Stage	What the read must establish	Hardware
Curing exit / finishing	Tag survived cure; EPC matches the production record	Fixed reader, singulated presentation
Sorting and palletising	Which casings went onto which pallet or stack	Fixed reader or handheld
Shipping portal	Load matches the despatch note before the door closes	Fixed multi-port portal, 4–8 antennas
Warehouse racking	Stock position and cycle count	Handheld
Retread inbound	Casing identity and first-life history before inspection	Handheld at the inspection bench
Retread process stages	Stage completion through buffing and recapping	Fixed readers at stage boundaries
Retread outbound	Eligibility record and new-life data for the passport	Fixed portal or handheld
Fitment and removal	Wheel-position association, removal reason	Handheld with SDK access to the fleet app

The rule: a fixed portal where the item is moving anyway and hands are already full; a handheld where the person deciding is already touching the tyre; and let the next read downstream stand on its own where it already tells you the same thing. If the plant already runs stage-level tracking, curing and finishing reads belong in that WIP tracking model, and the dispatch portal with your outbound supply-chain scanning and pallet-level records.

What makes a tyre a demanding RF target

Construction

Carbon black loading, steel belting and rubber mass all absorb and detune. Tag position inside the tyre is the tyre maker’s decision, made for durability and balance, so you design the read point around a tag whose position and orientation are already fixed.

Metal environment

Steel-belted casings in steel racking produce reflections and nulls that move as rack contents change. A portal tuned against an empty rack behaves differently against a full one, so tune it against both.

Stacked versus singulated

A tyre presented one at a time on a conveyor is a straightforward read. A stacked or bundled load asks more of the read point: tags in the middle sit behind several layers of steel-belted rubber, and read rate falls with stack depth rather than distance. To inventory a stack, plan to break it, to give it an aggregated tag of its own, or to sweep it with a handheld.

Testing

Set the acceptance criterion from a survey with your own casings, racking and conveyor speed before the layout is committed, and sample the worst case you will ever run: fullest rack, deepest stack, wettest casing, fastest belt.

Hardware for a tyre read point

Fixed readers. Plant and dispatch portals want a multi-port reader driving four or more antennas, so one unit covers both sides of an opening and geometry can change on the same hardware. Specify circular polarisation where tag orientation varies, and calculate dwell from the actual conveyor or forklift speed.

Handhelds. Fitment bays, retread inspection, rack counting and audits all want a handheld talking to your application rather than a vendor utility, so ask for SDK access up front. We ship SDKs for Android, Windows and Flutter, which drop straight into fleet and workshop apps.

Filtering at the reader. A portal that reports every tag it hears will report the racking behind it. Handle it on the reader: EPC prefix and filter-value screening, RSSI thresholds, and a session and dwell policy that reports a load once.

Environment. State the IP rating, the operating temperature range for a floor near a curing area, and the duty cycle the reader must sustain. Specify the reader for the floor it will actually stand on: the press line, not the office.

Band and conformity. Match the band to the destination. Identium UHF reader models carry WPC ETA and BIS registration for India’s de-licensed UHF band, and we configure FCC-band 902–928 MHz and ETSI-band 865–868 MHz variants per order for export. Name the required documents in the purchase order so they arrive with the goods.

For an Indian tyre exporter specifically

For an Indian tyre plant this obligation arrives through a customer rather than a domestic rule, and the mechanism decides what your contract will say.

Under Article 29(2) of the ESPR, an importer must ensure, before placing a covered product on the EU market, that a digital product passport is available under Article 9 and the applicable delegated act. Article 34 goes further: an importer or distributor is considered the manufacturer where it sells under its own name or trademark. Between them, whoever places a tyre on the EU market answers for the passport — which is how the requirement travels upstream into a supply contract with a plant outside the Union.

The useful preparation is the part that takes longest and holds good whatever the final field list says.

Decide who allocates the GTIN and serial, and where that is recorded, before the first tag is encoded.
Put in a post-cure verification read, with a retained per-casing record tying the EPC to production.
Define a handover export of the per-tyre data you hold, so that when the act fixes the fields you are mapping an existing record.
Settle reader band variants for every site that will read your tyres, with conformity documents named in the order.

The identifier and standards detail sits on our Digital Product Passport hub; the export side of the hardware question is on our RFID manufacturer and exporter page.

A specification you can hand a supplier

Carrier and encoding. SGTIN-96 in the EPC bank, GTIN and serial allocation owner named, verification method stated, and the defined action for a casing that fails verification.
Read points and throughput. Each point with peak items per hour, presentation (singulated or stacked) and the speed it must work at.
Acceptance criterion. A first-pass read rate at a stated speed and presentation, on your own casings, witnessed on site. Survey before the purchase order; acceptance test inside it.
Hardware envelope. Port count and antenna geometry per portal, polarisation, IP rating, temperature range, duty cycle, and the band variant and conformity documents per destination site.
Integration and recovery. Which system receives the read event, in what format, and the recovery path for any tyre that still needs accounting for — diverted, re-presented, flagged for a handheld sweep, or reconciled at the next downstream read.

That last clause is the one that repays writing down, and the one experienced buyers put in first. Write the recovery path into the specification and every tyre stays accounted for. The installations that work already know what happens next.

Frequently asked questions

Do tyres need a Digital Product Passport in the EU?

Tyres are a named priority product group in the Commission’s Ecodesign working plan 2025–2030, COM(2025) 187 final, adopted 16 April 2025, with an indicative 2027 date for the delegated act, which is what will set the passport obligation itself.

What RFID standard is used for tyres?

RFID Journal reports that the international standard for coding RFID tyre tags was published in 2019, setting out general requirements and the data structure for electronic tyre identification. Alongside it, the Global Data Service Organization for Tires and Automotive Components — founded in early 2022 by Michelin, Bridgestone, Continental, Goodyear and Pirelli — provides the industry dataspace.

Which EPC encoding is specified for tyre RFID tags?

SGTIN-96. The GS1 and RAIN Alliance joint DPP statement records that, for tyre applications in the Michelin pilot project, the unique item identifier is coded using SGTIN-96 per the GS1 EPC Tag Data Standard: a serialised GTIN in 96 bits, with a 38-bit serial field, mapping to a GS1 Digital Link URI.

When does the EU tyre Digital Product Passport come into force?

The working plan gives an indicative 2027 adoption for the tyre delegated act, and Article 4(4) of Regulation (EU) 2024/1781 sets the date of application at no earlier than 18 months from entry into force. That points to practical compliance around 2029, with the 2027 year still indicative.

Can RFID tags survive inside a tyre for its whole life?

RFID Journal reports tags that can sustain up to the one million kilometre life of some commercial tyres, and over 250 million tyre tags supplied by a single vendor to date. Survivability follows from the tag construction and from where the tyre maker embeds it.

How do you read RFID tags on stacked tyres?

Read rate on a stack falls with depth rather than distance, because each casing shields the ones behind it. The workable options are to break the stack, to give it an aggregated tag of its own, or to sweep it with a handheld.

What RFID hardware does a tyre plant need for a DPP read point?

A multi-port fixed UHF reader with four or more antennas for curing exit, sorting and dispatch; handhelds with SDK access for retread inspection, rack counting and fitment; on-reader filtering so a portal reports the load and not the racking; and a band variant per site — FCC 902–928 MHz, ETSI 865–868 MHz, or 865–868 MHz for India.