Choosing a carrier that still works in five years

Six words, and why collapsing them is the expensive mistake

These get used interchangeably in proposals and they fail in different ways, at different times, under different people's control.

The first four are taken apart in detail, with what each is not, on what actually happens when somebody scans the code. Three points carry over: a carrier is not a passport, a passport is not the whole of a product record, and a code that resolves is not evidence that anything behind it is current.

Five things that have to survive, and only one is physical

Longevity gets discussed as an ink and abrasion question. It is five questions, they fail at different rates, and four of them are contractual or organisational rather than material.

The third and fourth are where most long-life programmes will fail, and they are the two that look like somebody else's problem at the point of purchase. The standard leaves continuity open and a contract has to close it, as when the link dies sets out.

The architectural consequence follows from one property of the list. Only the resolver and the destination can be changed after goods ship. So the design that survives keeps the printed part minimal and stable, holds a small durable map from identifier to link type to target, and puts everything that changes at the target address where it can be rebuilt without anybody touching the map. Putting the volatile logic into the resolver itself moves it into the layer with the longest life and the least tooling.

The three decisions in front of you

What the mark is. Four carriers circulate under one name and only three of them are machine interpretable as identity.

Where it sits. There is a measured placement constraint for retail scanning that most published commentary omits entirely.

Whether it will still be there. Nobody has established whether any digital identity carrier survives a garment's ordinary life, and that is the load bearing unknown underneath everything above.

The four things people call the code

The split is between the first three and the fourth. The first three are machine interpretable as identity: a system reading one can extract the product number and, where present, a batch or serial. The fourth is machine interpretable only as a destination. No point of sale system, no customs system and no downstream reader can get a product number out of it, because there is not one in there.

Two practitioner failure modes follow directly from that table and both are common. A brand prints a marketing address and believes it has a compliant carrier, having put no product number, batch or date structure inside it. Or a brand prints correct address syntax and never stands up anything to answer it, so every scan lands on the same destination regardless of what was asked for, which discards the reason the syntax exists. Both surface late, and the second usually surfaces when somebody in a different market asks why they get an English page.

A note on naming. The third row is commonly called a GS1 QR code, which is shorthand for what the code carries rather than a distinct symbology. It is an ordinary QR code with a particular kind of address inside it. What the identifier itself commits you to is a separate decision, set out in identifiers, and what allocating one commits you to.

Three retail 2D names that are not interchangeable

Current GS1 retail guidance names QR Code with GS1 Digital Link URI syntax, Data Matrix with GS1 Digital Link URI syntax and GS1 DataMatrix as three separate future-state 2D POS implementations. GS1 Digital Link is URI syntax, while QR Code and Data Matrix are carrier symbologies. GS1 DataMatrix is a GS1 implementation of Data Matrix, not merely another label for Data Matrix carrying a Digital Link URI (Ambition 2027 and the retail 2D transition).

For the wider choice between the carrier, identifier and syntax layers, use the 2D Product Identity Map. For the difference between a GS1 Digital Link URI and the resolver behind it, see GS1 Digital Link for Digital Product Passports.

The placement constraint nobody quotes

Testing published by GS1 found that a two dimensional symbol needs to be within fifty millimetres of the centre of the linear barcode to achieve the target retail scanning rate of forty to seventy items per minute, and that without placement rules high speed retail checkout may be unable to meet its productivity target.

That is an artwork and ergonomics constraint, and it is absent from essentially all published commentary about carriers, which treats the subject as a software question.

For apparel it lands differently than for grocery, because a swing tag and a sewn in label are not a printed pack panel and a garment does not usually cross a belt at seventy items a minute. It still matters, because it is the reason a retailer may care where your mark sits, and because it demonstrates that the transition being discussed as a data question has a physical half that gets decided by whoever lays out the label.

The related question, whether the industry target for two dimensional codes at the till is a deadline, is answered on identifiers, and the answer is that it is a target set by an organisation for itself with no published measurement of its own threshold.

Carrier choice is diverging, and it tracks product form

Across documented programmes the choice is not converging on one answer. It sorts by what the object is.

Near field tags appear where the object is large, expensive and handled with a phone already in the hand. Poltrona Frau furniture, BRABUS vehicle interiors, Axopar helm fittings, a plaque on an MCM bag.

Printed codes appear where the item is cheap, printed at line speed or has to be read at a till. Woolworths fresh categories, 7-Eleven Thailand, wine e-labels under the EU regime, Fnac Darty. 7-Eleven Thailand chose Data Matrix over QR on size grounds alone, because the symbol had to fit.

Marks already present in the object get reused rather than replaced. Bvlgari reactivated an engraving first applied in 2020.

Invisible watermarks, of the kind Digimarc and Polytag work with, appear where the mark must not be seen or must survive sorting.

And Another Tomorrow ships both a near field tag and a printed code on the same label. That is a hedge against not knowing which the customer will use, it is an honest answer to a question nobody has settled, and it costs twice.

Every programme named in this section is one we observed rather than one we can cite. The pattern is what the section is for. Any single example in it could be wrong without the pattern changing.

The cost structure, where the published numbers mislead

Passive tag inlays are quoted at roughly five to fifteen US cents at high volume, and fifteen to twenty five at around a thousand units. Near field and high frequency tags run roughly ten to fifty cents. A printed code has effectively no marginal cost at all. Those ranges are market observation rather than a figure we can cite to a source: an order of magnitude, not a quotation.

Those figures describe a chip or an inlay. The decisive point is structural rather than numeric.

A printed code is a change to a printing plate. A tag is a line on the bill of materials, plus a converting step, plus the cost of applying it, and the all in cost of an applied tag in a converted label at apparel volumes is not published by anybody. The gap between the quoted number and the real number is the part of the decision that is missing, and it is missing consistently across every source we found.

For an authenticating tag, meaning one that answers a challenge rather than serving an address, no unit cost at apparel volumes exists in public at all. That is the number a brand pursuing authentication would need, and the reason it matters is on the difference between identifying a product and proving it is genuine.

The unknown that sits under all of it

Whether any digital identity carrier survives a garment's ordinary life is not established.

Domestic laundering. Alteration. A shortened hem. A resoled boot. No independent test data for consumer apparel was found in this research.

What does exist points sideways rather than at the question. Washable tags rated to around a hundred industrial cycles are a real product, sold into industrial linen, which is a different environment with a different laundry process. One tagless approach claims testing that simulates twenty years of wear, and that is vendor testimony without independent verification.

The entire long life case for a carrier assumes it is still readable years later. Repair, resale, recycling and authentication all place the moment of use somewhere well after purchase. If the carrier is gone by then, the value proposition that justified it never arrives, and nobody would find out, because nobody is measuring resolutions against units in circulation.

It is a question one properly designed study would answer, and it is the single most useful piece of work available to anybody in this category.

If the carrier has to be replaced, preserve the identity and version the binding

A carrier failing does not automatically mean the product has become a new product. If the physical item is unchanged and its identity can still be established reliably, the persistent product identifier may be able to stay the same while the damaged mark or tag is replaced.

The control is to separate three kinds of continuity.

ESPR gives useful continuity primitives. It requires the Digital Product Passport to be connected through a data carrier to a persistent unique product identifier, and it allows lifecycle rules to be set for identifiers and carriers. If a new DPP is created for a product that already has one, the new DPP must be linked to the original DPP or DPPs.

What the current horizontal framework does not provide is one universal damaged-carrier rebinding sequence for every product category. EN 18220:2026 covers DPP data carriers, including durability and the physical-to-digital link, while its public scope excludes secure elements and cryptographic security features. Nothing in the public material supports inventing one cross-category replacement protocol from that standard.

That leaves a practical architecture problem for the operator.

For a plain printed QR Code or Data Matrix, reprinting the same identifier is technically straightforward. Trust is the harder part. A copied mark can resolve perfectly while being attached to the wrong object. So the replacement process needs to govern who may reprint, why a replacement is being made and what status the old carrier should have in the operator's records.

For a secure NFC or RFID carrier, the problem is different. A new chip is normally a new security principal with its own UID, key material or certificate. The product identifier can remain continuous, but the authentication factor has changed. The system should version that binding explicitly rather than pretending the new tag is the old tag.

A controlled replacement sequence

A defensible generic pattern is:

1. Recover the product identity from trustworthy remaining evidence. Use the old carrier where possible, or another controlled identity path designed for the product.
2. Authorise the replacement actor. A repairer, reseller or service centre should not gain rebinding authority merely because it can print or programme a carrier.
3. Record why the carrier is changing and the old state. Capture the reason, time and whether the previous carrier is damaged, lost, removed or potentially compromised.
4. Provision the replacement carrier for the same product identity. If the product itself has not changed, avoid creating a new product identity simply because the physical mark failed. If a genuinely new DPP is created, preserve the required linkage to the earlier DPP.
5. Register any new authentication factor as new. For secure tags, map the new UID, key or certificate to the continuing product identity. Do not clone the old factor conceptually in the audit trail.
6. Supersede or decommission the old carrier or factor where the architecture supports it. A plain printed mark cannot be remotely destroyed, but the backend can record that it is no longer the current authorised carrier and use duplicate or anomaly controls where appropriate.
7. Verify the new binding and retain the replacement record. Confirm that the new carrier resolves or authenticates as intended, and keep the actor, time, reason, old state, new state and evidence needed to explain the change later.

This is composable design guidance, not a horizontal DPP mandate.

There is a useful deployed precedent in another regulated sector. EU pharmaceutical safety-feature rules require controlled verification when safety features are removed or replaced, including authenticating the old identifier, decommissioning what is replaced, creating an equivalent identifier and retaining traceability. The European medicines verification system shows that a verify, retire, reissue and record pattern can operate at production scale. It is a sector-specific precedent, not a rule that ESPR automatically imports into textiles, furniture, electronics or other DPP categories.

There is also a hard stop. If the old carrier is completely lost and there is no trustworthy secondary evidence tying the digital identity to the physical item, a high-assurance system should not guess. The item may be impossible to rebind at the required assurance level. That is a physical-binding problem, not a resolver problem.

For the distinction between a reachable identifier and an authenticated physical object, see identity, authentication and ownership. If the carrier still identifies the right product but the resolver or destination has failed, that is the separate continuity problem covered by when the link dies. And if the replacement needs to preserve history for one individual item, the granularity decision belongs with when lifecycle data needs item-level identity.

Whether one carrier can do two jobs

One carrier may not be able to do two jobs, and there is a live regulatory precedent for that rather than a theory.

In the one European regime that already places mandatory product information behind a code, mandatory information must not be served alongside sales or marketing content, and data about the people viewing the e-label may not be stored. So a producer cannot host the compliance information on their own marketing site.

That regime is wine. It is not clothing, and the ecodesign framework carries no equivalent prohibition for textiles. A textile business reading it as a rule that binds them has read it wrongly, and the constraint on what may be measured at a carrier is taken apart, with the scope guard intact, on what a scan actually tells you.

What it demonstrates is narrower and more useful than a prohibition. An industry body argues, in published material, that a single code can serve regulatory information and marketing content at once. A European legislator, handed the same question in one sector, decided it could not. That is a live disagreement between advocacy and an instrument. Know about it before somebody commits a label design to the single code position.

When one carrier is a legal question, not a design preference

PPWR, the Toy Safety Regulation and the 2026 Detergents Regulation contain circumstances where one data carrier is used for information required under overlapping Union law, and whether it can also be the retail checkout carrier depends on identity, syntax and POS capability (the packaging rule, the cross-regime decision).

What this page does not decide

It does not recommend a symbology. The right answer depends on where the item is scanned, by whom and with what, and the four row table above is the decision rather than a preference. A published European standard now covers symbology, encoding, print and production quality, durability and placement, and it excludes secure elements and cryptographic features by its own scope. What it takes in and what it leaves out is on what the six published standards cover.

It does not carry a readiness percentage for two dimensional scanning at retail. The threshold is published, the measurement of it is not, and quoting a vendor's figure would be repeating something with no survey instrument behind it.

It carries no cost for an applied tag, and no cost at all for an authenticating one, because neither is published.

What to do before the artwork goes out

Decide which of the four you are printing, in writing. Most of the failure modes in this territory are somebody assuming they were printing the third row and shipping the fourth.

Check what comes back before the print run, not after. Ask for a well formed address naming an identifier your service does not hold and confirm it answers as not found, with a not found status code rather than a branded page served as a success. The full set of checks worth running against whoever answers your codes is on what actually happens when somebody scans the code.

Settle placement with whoever lays out the label, not with whoever is building the data.

Get the destination's ownership in writing. Who owns the domain the redirect points at, and what happens to it if the supplier stops trading, is the cheapest thing to settle now and the most expensive to discover later.

Treat carrier survival as an open risk and write it down as one. If your programme's value arrives years after purchase, it depends on an assumption nobody has tested. What keeps the address answering after the company behind it changes is on when the link dies.

The cheapest of those checks is the encoded data itself. You can produce the encoded structure and read it back before the artwork is committed to a printer.

What would close these gaps

Independent durability testing of any carrier type through normal domestic laundering and alteration in apparel. That closes the largest gap here.

A published all in cost for an applied tag at apparel volumes, from anybody, with the volume stated.

Any published measurement of the two dimensional scanning installed base at retail, by the body that set the threshold or by anybody else with a survey instrument.

Sources

Two classes of material on this page are not carried by any source below. The unit-cost ranges for tag inlays, and the named deployment examples, come from market observation made for this page and no authoritative source was found that carries either. They are kept because the shape of the cost structure and the direction of the divergence are the point, and they should be read as indicative rather than as cited. Everything the page says about law, standards and what a carrier can and cannot do is carried by the sources listed here.

• GS1 2D Barcodes at Retail Point-of-Sale Implementation Guideline 1.1.0
  Standards bodyRelevant provisions reviewed

  The three future-state 2D implementations named separately, and the placement finding: a two dimensional symbol within fifty millimetres of the centre of the linear barcode for the target rate of forty to seventy items a minute. Both quoted from this document rather than from commentary about it.

• GS1 Digital Link Standard: URI Syntax 1.7.0
  Standards bodyRelevant provisions reviewed

  That Digital Link is URI syntax and not a symbology, which is the distinction the four row table turns on.

• GS1 General Specifications 26.0
  Standards bodyRelevant provisions reviewed

  That GS1 DataMatrix is a GS1 implementation of Data Matrix rather than another name for Data Matrix carrying a Digital Link URI, and the symbol and print quality requirements behind the artwork question.

• GS1 conformant resolver standard, at the reference site
  Standards bodyRelevant provisions reviewed

  That the standard specifies no continuity or retirement procedure for a resolver. The absence is the claim, and it is read off the standard's own scope rather than inferred.

• Ecodesign for Sustainable Products Regulation (EU) 2024/1781, consolidated text
  EU lawRelevant provisions reviewed

  That the framework requires a data carrier linked to a unique product identifier where a product act applies, and that it carries no prohibition of the kind the wine regime carries. The second is an absence, and it is stated as one.

• Regulation (EU) 2021/2117, electronic labelling of wine
  EU lawRelevant provisions reviewed

  The one European regime that already places mandatory product information behind a code, and the two conditions on it: mandatory information kept apart from sales and marketing content, and no user data collected or tracked. Read for what it decides in its own sector and for nothing beyond it.

• Regulation (EU) 2025/40 on packaging and packaging waste
  EU lawRelevant provisions reviewed

  One of the three regimes where one data carrier can serve information required under overlapping Union law while the information stays distinguishable.

• Regulation (EU) 2025/2509 on the safety of toys
  EU lawRelevant provisions reviewed

  The second of those three regimes.

• Regulation (EU) 2026/405 on detergents and surfactants
  EU lawRelevant provisions reviewed

  The third.

• BS EN 18220:2026, Digital product passport - Data carriers, public scope
  Standards bodyPublished abstract read, full text behind a purchase

  That a published European standard now covers symbology, encoding, print and production quality, durability and placement, and that it excludes secure elements and cryptographic features. Taken from the standard's public scope statement. The full normative text has not been read and this page states no requirement from inside it.