What If the QR Code Is Damaged on a Battery

A damaged QR code breaks access to the battery passport, not the passport itself, because the record sits behind the carrier in a system, while the code is only the link that resolves to the record. The distinction matters for the remedy, because a damaged code needs the link restored, not a new record created, and a new record for the same battery would create a duplication problem that is worse than the damage. The correct remedy recovers the unique identifier from other sources, restores a carrier that resolves to the existing record, tests the restored carrier, and records the damage and the remedy with dates. A damaged code is therefore a recoverable access failure, provided that the identifier can be recovered and the record can be matched.

The scope is QR code damage for batteries within Article 77, read with Article 13 and Article 77, as checked on 28 October 2026. The guide does not state marking repair procedures for any particular battery.

How is damage to a QR code recognised?

Damage to a QR code is recognised when a scan fails, when a scan resolves to the wrong record, when the code is visibly scratched, faded, covered or missing, or when a reader reports that the code cannot be read where the battery is installed. The recognition should be recorded with the date, the reader, the scan result and the visible state of the code, because a damage report without a date and a scan result cannot be followed up. A code that fails on one device but scans on another may be a device or lighting problem rather than code damage, and the damage check should include a second device and a clean, well lit scan before the code is declared damaged. The check prevents a device problem from being treated as a carrier failure.

How is the identifier recovered when the code cannot be scanned?

The identifier is recovered from other sources, including the battery marking, the accompanying documents, the invoice or contract, the record system search by model and serial information, and the holder file, in that order, with each source checked and recorded. The recovery should be done by the record holder or by an operator who can access the record system, because a reader without system access cannot match an identifier to a record. Where the identifier cannot be recovered from any source, the battery should be held from making available until identity is resolved, because a battery without an identifier cannot be matched to a record, and handling or selling it on assumption risks a mismatch. The recovery record should state the sources checked and the source that supplied the identifier.

How is the carrier restored?

The carrier is restored by applying a new carrier that resolves to the existing record, under the existing identifier, with the restoration recorded by date, operator and test result, and with the damaged carrier retained or photographed where possible as evidence of the damage. The restoration must not create a new identifier, a new record or a new model entry, and it must be tested by scanning the restored carrier and confirming that it resolves to the correct individual record. A restoration that creates a new record breaks continuity, and a restoration that is not tested may repeat the original failure. The restored carrier should also be checked for placement and durability, so that the cause of the damage, such as a harsh environment or a hidden placement, is addressed rather than repeated.

What does a damage remedy table look like?

A damage remedy table shows the damage state, the recovery route and the remedy, so that the remedy can be chosen without creating a duplicate record. The table below uses general states.

What should be recorded about the damage?

The damage record should state the date the damage was found, the reader, the scan result, the visible state, the recovery sources checked, the identifier recovered, the restoration date and operator, and the test result for the restored carrier, so that a later reader can follow the whole episode. The record should also state the cause where it is known, such as abrasion, heat, chemical exposure or installation damage, because the cause decides whether the restored carrier needs a different placement or protection. A damage record that states only that the code was fixed, without the recovery and test detail, gives a later reader no way to judge whether the restored carrier resolves to the correct record.

How can carrier damage be prevented?

Carrier damage can be prevented by placing the carrier where it is reachable but protected, by choosing a carrier material and protection suited to the operating environment, by checking the carrier at manufacture, at handover and at collection, and by recording each check with the date. Prevention is a placement and durability decision, made at design and installation, not a repair decision made after damage, and the placement decision should be recorded with the installation file. A carrier that is checked regularly will show wear before it fails, and a carrier that is never checked will fail at the moment when the record is needed most. Regular checks are therefore a readiness practice, not an extra.

What limits apply to carrier damage readings?

The limits are that a damaged carrier does not prove a record error, and a restored carrier does not prove that the record itself is accurate. This guide gives general educational information only and is not individual legal advice. An operator with a specific damaged battery should check Article 13 and Article 77 as checked on 28 October 2026 before acting.