LMTPASS

All articles

The battery QR code is not a QR code like any other

· 5 min read

Substrate, placement, durability, URL content: the marking that carries the passport is subject to physical constraints most projects discover at production time.

Putting a QR code on a battery sounds trivial. The constraints on that marking are not, and they are physical before they are digital.

The marking must outlive the product

The QR code must stay legible for the battery's entire service life, including at end of life — precisely when a recycler needs it most. An electric vehicle battery spends a decade exposed to temperature swings, vibration and sometimes moisture.

An inkjet-printed adhesive label does not meet that requirement. The solutions used in practice are direct laser marking, engraving, or an industrial-grade label qualified for the intended lifetime.

Placement determines usefulness

The code must be reachable without destructive disassembly. A QR code on an internal face, visible only after opening the enclosure, fails its purpose: the recycler must be able to identify the chemistry and the safe-state procedures before opening.

This is where the regulatory requirement meets operational safety. An operator who cannot read the instructions before intervening is working blind on an energetic object.

What the URL must and must not contain

The URL behind the code must be stable and durable. That rules out:

Conversely it must point directly at the passport of the specific unit, render the public circle without authentication, and stay valid even as your infrastructure evolves. An opaque, permanent identifier in the URL path is the most robust structure.

The size question

A QR code must be readable by a standard phone, held at reading distance, in a workshop lit by fluorescent tubes. That imposes a minimum size and sufficient contrast — constraints that compete with the space available on the enclosure.

Shortening the URL reduces the code's density and therefore the minimum size needed. That is a concrete argument for a short identifier rather than a descriptive URL.

What to check before production

Three simple tests, on a real unit rather than a mock-up:

  1. Phone reading at 30 cm, moderate lighting, no zoom.
  2. Reading after the accelerated ageing planned for the product.
  3. Reading by an operator who was not on the project — if they cannot find the code within thirty seconds, the placement is wrong.

Check your obligations in 30 seconds · Create a passport for free