When Does Lifecycle Data Need to Follow the Individual Product?

The threshold question: what state has to survive?

Before choosing an identity technology, ask what information must still be available when the product reaches the next lifecycle decision. Four forms of state point at four different architectures.

Individual history. Something happened to this exact unit and the next actor needs to know it. Maintenance hours, a previous repair, an incident or a lost/stolen status are examples.

Individual current condition. The unit's present state differs from other units of the same type. Battery state of health is a clear example.

Shared type or part information. The decision can be made from what the product or component is, rather than what happened to this particular unit.

Measured state. The deciding information can be observed directly at the moment of sorting, inspection or treatment.

Worked as an ordered threshold, that becomes four questions in sequence.

The sequence is deliberately asymmetric. There are several valid reasons to stay coarse, and only specific reasons to go fine. Asking "what state has to survive?" before deciding that item identity is required is ActivateDigital decision guidance, not a legal standard.

This is also different from asking whether a unique identifier can technically be attached. Technical possibility is a weak threshold. The stronger threshold is whether a decision becomes materially worse when the item's history is lost.

If you have already established that a finer operational identity is needed but are choosing between lot, serial and item, use the operational identity decision guide. This page covers the narrower lifecycle question: when the state itself needs to remain attached to one exact object.

When item-level continuity is justified

When repair information is exact-vehicle specific

EU motor-vehicle rules provide a mature example of exact-unit identification supporting repair. Regulation (EU) 2018/858 uses the Vehicle Identification Number, VIN, to retrieve vehicle repair and maintenance information, including original-equipment part and fitting information.

Not every repair needs a VIN. But in some repair decisions the exact vehicle is the right lookup key, because configuration and service information can be vehicle specific.

For the broader question of what information a repairer can actually use, including access and evidence limits, the repairer evidence page covers that answer.

When a regulated lifecycle state belongs to the individual unit

The EU Batteries Regulation gives a different kind of example. Since 18 August 2024, Article 14 of Regulation (EU) 2023/1542 requires covered batteries to contain current state-of-health and expected-lifetime data in the battery management system, with read-only access for defined purposes including residual value, remaining lifetime and further use.

That is a category-specific NOW example of lifecycle state that can vary by battery and matter to the next action. It does not bring the Battery Passport deadline forward, and it does not create a general rule for other product categories.

Battery second-life obligations also have their own passport rules and hand-offs. The battery second-life page covers those legal mechanics.

The Digital Circularity Vehicle Passport is a clear future example of law choosing item-level continuity. From 1 September 2032, each vehicle within Article 13 of Regulation (EU) 2026/1738 has its own DCVP.

That settles the granularity question for the in-scope vehicle. It does not settle the identifier or carrier. The adopted DCVP framework does not yet make the VIN the passport identifier or require a QR code. Those technical choices remain for the Article 13(6) implementation.

The Euro 7 Environmental Vehicle Passport is useful only as a separate comparison: its implementation already uses QR/VIN mechanics, but those choices cannot be imported into DCVP as if the vehicle-circularity law had already selected them.

See EU Digital Circularity Vehicle Passport (DCVP): What Changes for Cars and Vans from 2032?

When accumulated use or maintenance history changes the decision

Aviation provides a high-assurance example. EASA continuing-airworthiness guidance expects maintenance history for used serialised components and tracks life or time-controlled status. Here, the history of an individual component can determine whether it remains acceptable for continued use.

That demonstrates the feasibility and value of serial identity linked to maintenance history in a mature safety-critical sector. It does not justify aviation-grade records for ordinary consumer products.

When an individual status signal matters at acquisition

GSMA Device Check shows another form of item state. A buyer or service can query a device serial identifier such as IMEI and receive a lost or stolen status signal from the GSMA Block List.

The signal is useful because it relates to one device. It is also bounded. GSMA states that status can change and reporting can be delayed, so the check does not prove legal ownership or physical authenticity.

When item-level continuity is not necessary

Circularity does not become more credible simply because every object is serialised.

Recycler information can work at product-type level

Article 15 of the WEEE Directive requires producers to provide information needed for preparation for reuse and treatment for each type of new electrical and electronic equipment. That is an established legal model where lifecycle information can be useful without attaching a unique history to every individual item.

It does not prove type-level information is sufficient for every treatment decision. It proves that useful lifecycle information is not inherently item-level.

A sorting line can measure the material directly

The SIPTex textile sorting plant in Malmö provides an operating counterexample to item-passport lookup. IVL reported that the full-scale plant used near-infrared sensing to sort mixed textile waste by fibre composition.

The recycler's problem there is material recognition at the point of sorting. A direct measurement can answer that question without retrieving a history for one garment. The recycler evidence page goes deeper on when direct sensing is more useful than item lookup.

This does not mean item data can never help a recycler. In ActivateDigital's bounded evidence review, a generic NOW claim that high-throughput textile sorting requires item-level passport identity was not supported.

Remanufacturing can deliberately stop caring about the original item's identity

Caterpillar's remanufacturing process is another counterexample. Used cores are returned, inspected and disassembled. Caterpillar states that after disassembly the pieces lose their original identity.

That is an operating model where the original item's persistent identity is not preserved through every stage of the loop. Part identity and condition inspection can be enough for parts of the decision process.

The conclusion is bounded. It does not show that every remanufacturing process can dispense with serial history. It shows that item-level continuity is not a universal precondition for remanufacturing.

Portable lifecycle history is not established yet

The evidence supports a broader direction, but not a universal present state, and the difficult step is portability across organisations rather than capture inside one.

More repair, remanufacture and ownership-transfer services can plausibly maintain item-specific records where economics justify the capture and the identity remains durable. Production ecosystems already show parts of this pattern.

A history that works inside one manufacturer's service ecosystem is not automatically portable to a second owner, independent repairer or resale platform. Cross-company continuity requires compatible identifiers, permissions, data models, entitlement rules and commercial governance.

So portable lifecycle history belongs in EMERGING or POSSIBLE unless a specific implementation is demonstrated at scale.

Resale is a good example. An identity can reduce product-recognition or service-transfer friction, but it does not solve every resale problem. The resale article separates the frictions identity can reduce from ownership, authenticity and price claims.

Keep the original passport, link the later history

One emerging way to preserve lifecycle continuity is not to keep rewriting the manufacturer's original passport.

UNTP's Linked Lifecycle Data pattern proposes leaving the original product credential intact and adding later signed credentials for events or state changes that happen after manufacture. Those later credentials can link back to the product and to earlier records, creating a chain of history without pretending that the manufacturer authored events it did not witness.

That separation is useful where an individual product is repaired, inspected, transferred, refurbished or otherwise changes state. The original product facts can remain attributable to their original issuer while later actors add their own signed records under their own responsibility.

It is an emerging protocol pattern, not an EU DPP requirement and not yet a settled production standard. The decision to use item-level identity still depends on the threshold this page sets out: whether the later state has to survive with the individual item rather than the model, batch or transaction.

For the wider protocol context, see what UNTP is and how it works.

Official EU methodology now uses the same append-preserve idea

In March 2026 the European Commission Joint Research Centre published its methodology for defining Digital Product Passport data requirements under the ESPR framework. Annex 9 describes a tightly restricted or immutable Core DPP alongside an append-only Life-cycle Log for later events such as repairs, software updates, ownership changes and refurbishment.

That strengthens the case for keeping an original product record attributable to its original issuer while adding later lifecycle history rather than silently rewriting earlier assertions. It shows that append-preserve lifecycle architecture has entered official EU methodology work, not just standards and pilot discussions.

It is still an EMERGING architecture, not a binding universal ESPR technical requirement. The JRC publication is methodology for policy and implementation work. It does not remove the threshold this page sets out: item-level history is justified only when the later decision needs state or history to remain associated with the individual object.

See the JRC methodology and Annex 9. If that retained history is later used to flag conflicting, duplicate or implausible sequences, the separate question is what product identity and event history can defensibly flag as suspicious.

What not to infer, and what the evidence supports

Four claims do not follow from the evidence.

Item identity is not a universal requirement for circularity. Repair, recycling and remanufacture have valid operating models that use coarser data or direct sensing.

Identity is not authenticity. A persistent identifier can point to the right record while the physical object still needs a separate authentication mechanism.

Identifier is not ownership. Knowing which item is being discussed does not establish legal title to it.

A portable history is not established merely because one organisation can keep a history. Interoperable transfer is a separate operating problem.

Set against the four maturity positions, that gives:

If any of this is going to be reported as a rate, the denominator decides what the number means. Choosing the denominator is its own question.

What would change this page

This answer should be revisited if:

• product-specific EU legislation introduces new lifecycle records or finer mandatory identity levels;
• repair, resale or remanufacturing standards establish repeatable cross-company history transfer;
• scaled deployments show that item-level histories materially change decisions now handled by type, part or direct sensing;
• new evidence shows that a currently item-level decision can reliably move to a coarser or measurement-led model.

Sources as at 4 September 2026.

Sources

• Regulation (EU) 2018/858 on motor-vehicle approval and repair information, consolidated 26 September 2021. Used for VIN-linked repair and maintenance information.
• GSMA Device Check FAQs. Used for serial-identifier lost/stolen status checks. The signal does not establish ownership or authenticity.
• GSMA Device Check Terms of Use. Used for the limits on the timeliness and completeness of device-status data.
• Regulation (EU) 2023/1542 concerning batteries and waste batteries, Article 14. Used for covered-battery state-of-health and lifetime data available since 18 August 2024.
  EU law
• Directive 2012/19/EU on waste electrical and electronic equipment, Article 15. Used for the product-type reuse and treatment information model.
  EU law
• IVL Swedish Environmental Research Institute, Textile waste becomes unique recycling products, 6 May 2021. Used for the SIPTex direct-sensing sorting example.
• Caterpillar, Cat Reman: The Remanufacturing Process. Used for an operating remanufacturing example where original identity is not preserved through disassembly.
• EASA, Easy Access Rules for Continuing Airworthiness, September 2025 revision. Used for serialised-component maintenance and life-status continuity in aviation.