Skip to content
Knowledge / Digital Product Passports

2D Product Identity Map: QR Code vs GS1 DataMatrix vs Data Matrix with GS1 Digital Link

Compare QR Code, GS1 DataMatrix and Data Matrix with GS1 Digital Link for a Digital Product Passport. Separate the carrier, identifier, syntax, resolver and legal requirement before choosing what to print.

Last verified
Share
LinkedIn X Email
Navigate this page

Choosing a 2D code for a Digital Product Passport is not one decision. It is at least four. You need to decide what legally identifies the product, which identifier scheme you will use, what syntax the carrier contains and which physical carrier you will print. A resolver or destination sits behind those choices and can change later. The printed mark usually cannot. The EU Ecodesign for Sustainable Products Regulation, Regulation (EU) 2024/1781, does not establish one universal rule saying every DPP must use QR Code, GS1 DataMatrix or GS1 Digital Link. It requires the passport to connect through a data carrier to a persistent unique product identifier and leaves important carrier detail to the applicable product-specific measure. EN 18220:2026 now provides a harmonised standards route for DPP data carriers, but its public scope does not turn one symbology into the universal legal answer. So start with the architecture, then choose the square.

The short answer

If you are deciding between QR Code, GS1 DataMatrix and Data Matrix with GS1 Digital Link, use this order:

  1. Check the product law first. A product-specific rule can specify a carrier, placement or granularity. Batteries are the clearest example of a regime that expressly uses QR Code. Do not generalise that choice to every DPP.
  2. Decide the identity you need to carry. A GTIN, batch number and serial number are different identity layers. The law's Unique Product Identifier is a legal role, not automatically a synonym for GTIN.
  3. Decide whether the encoded content is a GS1 element string, a GS1 Digital Link URI or another standards-compliant structure. Syntax is not the same thing as symbology.
  4. Then choose the physical carrier. QR Code, Data Matrix and GS1 DataMatrix have different operational strengths and scanner assumptions.
  5. Keep the destination changeable. If the carrier contains a web-enabled identifier, control the domain and design the routing so destinations can move without reprinting the product.

If you are only comparing the physical mark's durability, placement and print quality, use QR, Data Matrix or NFC: Choosing a Lasting Carrier. This page owns the wider product-identity decision.

The five layers people collapse into “the barcode”

Most bad barcode decisions begin with a vocabulary problem. The same word gets used for a symbol, a number, a URL and a service behind the URL.

LayerThe question it answersExampleFixed when printed?
Product identityWhich product, batch or item is this?UPI, GTIN, batch, serialUsually yes
Identifier schemeUnder whose rules is that identity allocated and managed?GS1 or another standards-compliant routeUsually yes
Encoded syntaxHow is the identifier represented inside the carrier?GS1 element string, GS1 Digital Link URIYes
Data carrierWhat physical or electronic mark is read?QR Code, Data Matrix, GS1 DataMatrix, NFCYes
Resolution/destinationWhere does a web-enabled identity lead?Direct resource or resolver-managed targetCan be changeable

A QR Code can carry an ordinary URL. It can also carry a GS1 Digital Link URI. A Data Matrix can carry a GS1 Digital Link URI. GS1 DataMatrix is a specific GS1 use of the Data Matrix symbology and is not simply another name for every Data Matrix containing GS1-related information.

That distinction is the centre of the map.

What EU DPP law actually decides

Regulation (EU) 2024/1781 sets the horizontal DPP architecture. Article 10 requires a DPP to be connected through a data carrier to a persistent unique product identifier. It also says the carrier must be physically present on the product, its packaging or accompanying documentation as specified by the applicable delegated act.

That is enough to rule out one common mistake: a passport that exists only as a page on the web is not the complete physical-to-digital architecture.

It is not enough to choose QR Code over Data Matrix.

The product-specific measure matters because the framework allows it to set details including one or more data carriers, presentation and positioning and the level at which the passport applies. The Digital Product Passport Requirements by Product Category page is therefore the legal starting point before this technical decision map.

A category rule can be more specific than the horizontal framework

Battery law is the useful warning against universalising the horizontal rule. Regulation (EU) 2023/1542 requires a QR code for batteries from 18 February 2027 under its own provisions, including access to the battery passport for covered batteries.

That tells you what the battery regime chose. It does not prove that ESPR requires QR Code for every future product group.

What EN 18220 changes, and what it does not

EN 18220:2026 is the European DPP standard on data carriers. Its reference is one of the six published in the Official Journal by Commission Implementing Decision (EU) 2026/1736.

The public BSI scope says EN 18220 covers matters including:

  • symbology characteristics;
  • format and error correction;
  • encoding methods;
  • printing and production quality;
  • durability;
  • placement;
  • machine readability;
  • quality checking;
  • links between the physical product and its digital representation.

That makes EN 18220 highly relevant to a carrier implementation.

It does not establish that every product legally needs a DPP. It also does not, from the public scope we have read, establish one universal QR-only or Data-Matrix-only rule. We have not reviewed the full licensed text and do not infer clause-level requirements from a public scope.

For the difference between a harmonised standard and product-specific legal scope, see DPP Standards and Presumption of Conformity.

What EN 18219 changes, and why it belongs before the carrier decision

EN 18219:2026 covers unique product, economic operator and facility identifiers used in DPPs. Its public scope includes global uniqueness, persistence, syntax, granularity, interoperability and openness. It accommodates product identity at model, batch or individual-item level and describes routes using issuing agencies, self-issuing systems or combinations of the two.

The important sequence is this:

identity first, carrier second.

If the product must be identified at item level, the data structure has to distinguish individual items. If the applicable product rule is model-level, serialising every physical unit may be unnecessary. Printing a sophisticated 2D carrier does not settle the granularity question.

The generic legal and commercial identifier question remains owned by Barcodes and Product Identifiers: What You Need. If you need the three DPP identifier classes, use Product, Operator and Facility Identifiers for a DPP.

Which option is strongest for a phone-first consumer journey?

A QR Code carrying a web URI has the simplest consumer-camera mental model because modern phones commonly recognise QR web links directly.

That does not make it the best answer for every machine or every product. A retail checkout system has different scanning behaviour from a phone camera. A small label has different geometry from a carton. A regulated product can have a product-specific carrier requirement. A manufacturer may need encoded batch or expiry data at the point of scan as well as a web destination.

The useful question is therefore not “what can a phone scan?” It is:

Which carrier and syntax work across the people and machines that must use this product, under the product rule that actually applies?

Which option is strongest for retail checkout?

For general retail, do not treat “2D capable” as a yes/no property of a scanner.

GS1's 2D retail guideline says the initial Ambition 2027 goal is for retail POS systems to be globally capable of reading and processing the GTIN from existing linear and 2D barcodes by the end of 2027. It also says not all imaging scanners will necessarily meet that goal and tells businesses to work with their POS solution provider.

During the transition, GS1 says products using retail 2D barcodes still need an accompanying linear POS barcode until 90% of POS scanning solutions are capable of using GS1-compliant POS 2D barcodes and at minimum capturing the GTIN.

That makes packaging migration a systems programme, not a print substitution.

The full transition decision belongs on Ambition 2027: What Retail's 2D Barcode Transition Means for Digital Product Passports.

Can the same code support both retail and a Digital Product Passport?

Sometimes, yes. Universally, no.

A web-enabled GS1 identity in a 2D carrier can support several downstream uses, and current EU rules in some regimes explicitly push towards a single data carrier when different Union-law information obligations meet on the same product or package.

But “one physical code” only works if all of these line up:

  • the applicable product law permits or selects the carrier;
  • the encoded syntax works for the required business systems;
  • retail scanners and host software can process what they need;
  • the identity granularity is compatible across uses;
  • packaging information and product information can remain clearly distinguishable where the law requires it;
  • the destination architecture survives change;
  • every relevant trading partner has tested the implementation.

That is a separate architecture decision. See Can One 2D Barcode Handle Checkout, Packaging Information and a Digital Product Passport?.

A practical decision sequence before artwork

Use this order before anybody places a code on packaging or a product label.

1. Establish the applicable product regime

Do not begin with a vendor technology. Begin with the law governing the product and its application date.

2. Establish passport granularity

Is the legally relevant identity at model, batch or item level? Do not create item-level complexity just because the carrier can hold it.

3. Establish the identifier scheme

Decide how the product identity will be allocated, governed and kept persistent. If GS1 is the route, identify which GTIN and Application Identifier rules apply.

4. Establish the encoded syntax

Decide whether the carrier needs a GS1 element string, GS1 Digital Link URI or another standards-compliant representation.

5. Establish the user and machine journeys

List who scans: consumer, retailer POS, warehouse, market-surveillance authority, customs, repairer or recycler. One symbol can be technically readable and operationally useless to one of them.

6. Choose the carrier against physical constraints

Size, substrate, damage, print process, contrast, placement and expected product life belong here. Use Choosing a Lasting Carrier for that decision.

7. Freeze only what has to be frozen

The carrier, identifier and encoded syntax can be difficult or impossible to change after production. Destinations and access logic should be designed to change where the architecture allows it.

Common wrong turns

“The DPP is a QR code.” No. A QR Code can be a carrier used to reach a DPP. The passport is the regulated digital information and system behind that connection.

“GS1 Digital Link is a barcode.” No. It is a URI syntax. A QR Code or Data Matrix can carry a GS1 Digital Link URI.

“GS1 DataMatrix and Data Matrix with GS1 Digital Link are the same.” No. They use the same underlying Data Matrix family but the GS1 syntax carried inside them is different.

“EN 18220 tells every company which square to print.” Not established. Its public scope covers DPP carrier requirements and implementation characteristics. Product scope and product-specific carrier detail still come from applicable law.

“If a POS scanner can image a 2D code, we can remove EAN/UPC.” No. GS1's own transition guidance requires capability across scanning and host systems and retains linear barcodes during the transition under its stated threshold.

What is established, and what is not

PropositionStatus at 3 September 2026
ESPR requires a DPP to connect through a data carrier to a persistent UPIRequired by EU framework law
Every future ESPR DPP must use QR CodeNot established
EN 18220:2026 is a harmonised DPP data-carrier standard cited in the OJEstablished
EN 18219:2026 is a harmonised DPP unique-identifier standard cited in the OJEstablished
GS1 Digital Link 1.7.0 is current GS1 URI syntaxGS1 standard
Ambition 2027 is an EU DPP legal deadlineFalse
GS1 recognises QR + Digital Link, Data Matrix + Digital Link and GS1 DataMatrix in its retail 2D transition guidanceIndustry implementation guidance
One of those three is universally best for every productNot established

What would change this answer

Recheck this page if:

  • a product-specific delegated act or regulation fixes carrier type, placement or granularity for a major category;
  • EN 18219 or EN 18220 is amended or replaced;
  • the Official Journal citation status changes;
  • GS1 changes the recognised retail POS 2D options or transition conditions;
  • GS1 Digital Link URI Syntax moves beyond version 1.7.0 in a way that affects the comparisons here.

Last verified 3 September 2026.

Keep exploring

The questions this page usually raises next.

Does this reach your products?

Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.

Worth sharing?

Help someone else make sense of product passports.

LinkedInXEmail

Sources and legal basis