News analysis · Technology & Standards
Decathlon’s encoding choice separates permanent item identity from changing product data
In an August 7 retailer interview, Decathlon describes centrally encoded serialized identifiers and a database that can change without rewriting tags. The boundary is governance, not radio range.
What the retailer says
In an August 7 interview published by the RAIN Alliance, Decathlon representative Tristan Finet describes centrally managed source-tagging. A service bureau encodes and checks tags before they go to product manufacturers. Decathlon says it writes a serialized GTIN as the item’s stable key, leaving changing details such as materials and lifecycle records in a database. The interview describes using a resolver to connect the EPC to a product-information page. Those are the retailer’s account of its architecture, not an independent audit of every supplier or site.
RFIDWire analysis
This is a useful split between identity and description. A serialized identifier should remain assigned to one item for its intended lifetime. Product composition, documentation and event history can evolve without touching the chip, provided the lookup service maintains a reliable relationship between the stable key and its records. If an operator instead encodes frequently changing attributes directly on every tag, every correction becomes a physical re-encoding project across sites and owners.
Centralized encoding reduces the number of parties allowed to issue identifiers, but it concentrates responsibility. The service bureau needs a controlled allocation process, records showing which identifiers were issued and rejected, and tests for duplicate or malformed values. Factories need a way to reconcile pre-encoded labels to the products they actually attach them to. A correct label sitting on the wrong garment still produces a plausible EPC and an incorrect item record.
A practical partner test begins at the commissioning ledger. Pick a sample of actual products from different suppliers and confirm that each EPC resolves to the intended stock item and one physical unit. Then change a database attribute that genuinely changes during a product’s life without changing the identifier. Confirm that the resolver displays the current, authorized version while retaining a history of what changed and when. Finally, simulate a missing record or unavailable resolver; the software should say the information is unavailable, not substitute a generic category page as though it were item-specific evidence.
The distinction is especially important for sustainability information. A tag that points to a record is not itself proof that the record is correct. Material claims need a responsible maintainer, provenance and an update policy; the radio carries the join key. Partners should decide what data can be public, what requires authorization and how long item-level records remain accessible after sale. Stable identity can support many uses, but it does not settle privacy or compliance questions by itself.
Questions and limits
Who owns serial-number allocation and how are rejected labels retired? How does a manufacturer confirm the label belongs on the right item? Can the lookup survive service outages or changes of data owner? Does the system show prior values when materials or product claims are corrected? What happens after returns, relabeling or a recycled product?
The interview gives an implementer’s explanation; it does not disclose measured error rates or independently establish compliance for every Digital Product Passport use case. The controls and failure tests here are RFIDWire’s analysis, not reported Decathlon results.