Can a product tag carry its repair history?
The tag carries the identifier and the history lives behind it, because a history grows and a tag written once does not. The harder question is who may add to it: the passport rules restrict the right to introduce or modify data, and a tag authenticates nobody.
The tag is an anchor
A repair history is a record that grows for as long as the product exists. A tag is memory written once and read many times, so the split is the obvious one: the identifier on the tag, the record on a server reached through it.
The maintenance page makes that case for a fleet of machines, and the mechanics are identical here. What differs is the cast: a consumer product is repaired by people who do not work for the manufacturer, and sometimes by the owner.
Who is allowed to write
regulation (EU) 2024/1781 settles the shape of this for products that carry a passport. Article 11 requires that the rights to introduce, modify or update data in the passport be restricted based on the access rights specified in the delegated act for the product group, that data authentication, reliability and integrity be ensured, and that the passport be designed so that fraud is avoided.
The same article lists who must have access at all: customers, manufacturers, importers, distributors, dealers, professional repairers, independent operators, refurbishers, remanufacturers, recyclers, market surveillance and customs authorities among others, each according to their rights.
So the question of who may add a repair is answered by the act, not by the design, and the design has to make that answer enforceable. Which is a statement about accounts and credentials on the server, and not about the tag.
Who believes an entry
An entry in a history is a claim by whoever made it. A manufacturer network entry is trusted because the manufacturer controls the account; an independent repairer's entry is worth exactly what the scheme that issued their credential is worth.
A tag cannot help with any of that. Possession of a tag is not identity, which the credential page puts plainly for access systems and which holds here.
The failure that matters is the opposite of forgery: a history that only the manufacturer's own network can write is a history that stops the day the product is repaired by anyone else, and that is most products after a few years. A record with no independent entries reads as a product never repaired.
What can live on the tag itself
The identifier, and in practice nothing else. Free memory on the tag is writable by anyone with a phone, as the locking page describes, so a note written there is a convenience rather than a record, and a locked tag cannot be added to at all.
There is one honest use for it. A short offline note, a service date or a firmware version, written by a technician for the next technician, costs nothing and survives a dead network. It is not the history and should not be presented as one.
Everything with consequences attached, access rights included, belongs where it can be controlled, which the access page covers.
Frequently asked questions
Why not write the history to the tag?
It grows, and a tag written once does not. An unlocked tag is also writable by anyone with a phone, so what is there is not evidence of anything.
Who may add to a product passport?
The regulation restricts the right to introduce, modify or update data to the access rights set by the delegated act for the product group.
Can an independent repairer write to it?
That depends on the act and on how the scheme issues credentials. A history only the manufacturer can write stops at the first independent repair.
Does the tag prove who made an entry?
No. Possession of a tag is not identity, so entries are authenticated by the service behind the tag rather than by the tap.