Each piece of information in a digital product passport (DPP) is linked to an identifier; EN 18219 regulates how these unique identifiers are established. This article examines the types of identifiers, the selection of model, batch or individual product, the place and persistence of the GTIN, from the perspective of a manufacturer exporting to the EU. This article is part of our DPP Standards Guide series.
- EN 18219:2026 (unique identifiers) was published in May 2026; in the Official Journal of the EU. (EU) 2026/1736 It was referred to as a standard harmonized with Commission Implementing Decision No. 14 (July 14, 2026).
What does the standard regulate, and what does it not regulate?
EN 18219 regulates three types of identifiers used in DPPs: unique product identifier, unique economic operator identifier, and unique facility identifier (EN 18219, clause 1). The product identifier is a character string and also provides the web link to the passport (clause 3.1.25). The standard expects six characteristics from these identifiers: global uniqueness, persistence, a specific syntax, the correct level of detail, interoperability, and clarity (clauses 1, clause 4).
Which data fields should be included in a passport is not the subject of this standard; this will be determined by industry-specific studies (Introduction 0.1). Technical requirements for QR codes or RFID tags. our data carrier article This is the subject of EN 18219, which requires that the identifier be readable from a carrier as defined in EN 18220 (clause 4.5.2). Access rights, data storage, and interfaces are the subject of other standards in the series (Introduction 0.1). For product-specific data requirements... textile, steel And battery You can check out our articles.
The level of detail required is determined not by the standard, but by the legislation applicable to the product group; the standard only provides guidance where the legislation leaves a choice (clause 4.4.3, Annex A.1). The presumption of conformity is limited to the clauses matched with the ESPR provisions in Annex ZA and the scope of the standard; other EU legislation may also apply to your product (Annex ZA).
Is it a model, a batch, or a unique product?
Product identification is given at one of three granularity levels: model, lot, or individual product (clause 1, clause 4.4). A model refers to units sharing the same technical specifications and model code; a lot refers to a group within a model that you have separated based on common characteristics; and an individual product refers to a single unit of that model (clauses 3.1.11, 3.1.1, 3.1.9). The identification must not conflict with any other identification, at least at the most granularity level in which it is used (clause 4.4.2).
For informational purposes, Appendix A generally finds the model level suitable for most products. The batch level becomes meaningful when you need to track a cluster produced in the same location with similar characteristics; the single level becomes meaningful when detailed information on a product basis is required (Appendix A.4). Appendix A.5 lists nine situations in which the single identity is suggested; the main ones are:
- Products that are repaired, refurbished, or upgraded by replacing parts,
- Products with updatable embedded software,
- Products subject to regular maintenance, inspection or regulatory control,
- Products for which usage data such as operating hours and wear and tear must be recorded,
- Products with a high risk of counterfeiting.
If the legislation gives you a choice, you can select a more refined level than necessary (Article 4.4.3). Although passports are currently only required at the model level, a refined level may be appropriate if future use at the batch or unit level is expected (Annex A.3). A single identity document can also carry model, batch, and serial information together in a hierarchical structure (Article 4.4.3).
Could this decision be changed later?
The level of detail is locked at the moment the product is placed on the market or put into service (clause 4.4.2). If a finer level is subsequently needed and the existing identity cannot meet this requirement, you do not replace the old identity; you issue a new or expanded identity and link it to the old one for traceability (clause 4.4.2, Appendix A.6).
Five product schemes and GTIN questions
Each product identity must be based on one of the five identification schemes defined in the standard (clause 5.1). The schemes are based on the issuing agency, are self-issuing, or combine both (clause 1). In the first case, the company code is obtained and the numbers are generated within the band allocated to you (Table B.4); in the second case, you create the identity yourself without an external authority (clause 3.1.20).
| Schema | How it works | Point to note |
|---|---|---|
| Scheme 1: Web-compatible GS1 or ASC MH10 ID (clause 5.2) | The company code received from the issuing organization is embedded in the identification URL as a path or query. | The query format is defined only with ASC MH10 Data Descriptors (clause 5.2.2). |
| Diagram 2: Identification Link (item 5.3) | You create your own identity through your own web domain. | Uniqueness is based on your domain name (Table B.1) |
| Scheme 3: Decentralized identifier, DID (item 5.4) | You generate it yourself with W3C DID; it supports cryptographic verification. | An analytical infrastructure is required (Table B.8). |
| Scheme 4: RFID or 2D code-based (clause 5.5) | Issuing organization based; RAIN is built on RFID or 2D symbols. | Smartphone access is configured via a second data carrier (Table B.9); web compatibility is not clear in this scheme (Table B.7). |
| Scheme 5: DOI (item 5.6) | The prefix DOI comes from the organization; the suffix forms you or the organization (Table B.22) | The identification begins with doi.org; it declares that it belongs to a specific model, batch, or individual product (clause 5.6.2). |
GTIN is not mandatory. Where GS1 is explicitly included in the mandatory elements of schemes are the path format of scheme 1 (GS1 Digital Link) and the RFID arm of scheme 4 (clauses 5.2.2, 5.5.2). If you use GTIN, you don't have to omit it: the standard requires that the numbering systems at hand be usable within the defined schemes wherever possible (clause 4.5.2) and, in its example, places the GTIN directly in a URL (Table B.11).
The standard does not regulate this; in practice, the GS1 company prefix required for GTIN is obtained in Türkiye through GS1 Türkiye.
How does an ID URL look and what are the Turkish character traps?
For the product ID to work with web systems, it must either be a URL itself or the URL must be accessible via a transformation described by the chosen scheme (clause 4.3.2). A structure similar to the GS1 example of the standard is: https://yourdomain.com/01/{GTIN}/10/{batch}/21/{serial}. Here, 01 is the GTIN, 10 is the batch number, and 21 is the serial number, which are application identifiers (Table B.11).
A consumer wishing to access the publicly accessible portion of their passport cannot be required to provide membership, a DPP-specific application, or user information (clause 4.6.2). The identity document must be encoded in a format readable by both professional readers and smartphones, and shared with retailers and online marketplaces for consumer access (clause 4.5.2). For the exporter, this often means adding a new field to the product master data going to the customer.
Turkish characters in serial and batch numbers: ç, ğ, ı, İ, ö, ş, ü
The characters in the ID must be selected from ISO/IEC 646 (7-bit base character set); when used as a URI, characters other than those considered unreserved by RFC 3986 are written using percentage encoding (clause 4.3.2). These seven Turkish-specific characters are outside of ISO/IEC 646. A batch code like ’GÖK-A’ would result in a character string that is difficult to read and enter manually in the address.
Our recommendation (not a rule, but an inference from article 4.3.2) is to establish batch and serial numbers from the outset using only the letters AZ and numbers. When converting old codes, two codes such as ’GÖK“ and ”GOK“ may correspond to the same thing; this violates the prohibition against one identity representing two objects (article 4.1.2).
The standard doesn't regulate this, but it's a common error in practice: software configured for Turkish language support might convert the letter 'I' to 'ı' and 'i' to 'İ' during case conversion. Use a uniform font size in your code and don't allow case conversion between systems.
Persistence: What happens if your company closes?
Permanence means that the identity, once given, does not change throughout the product's lifecycle and always represents the same product (clause 4.2.2). In principle, the identity continues to represent the same object even if the company's status, ownership, or location changes, or if a merger, acquisition, or division occurs (clause 4.2.1). Transferring a given identity to another product at a later date is prohibited (clause 4.1.2).
Even if your company goes bankrupt, is liquidated, or ceases operations, your identity must remain accessible (clause 4.2.2). According to the standard's note, the EU DPP registration system provides minimum protection for products on the EU market; however, the system's operation is not defined in the standard. No specific duration of protection is given; the expected duration or the duration required by relevant legislation is taken as the basis (clause 4.2.2). The storage of the passport data itself... our data storage article That is the subject.
Maintaining and securing identity records is your responsibility as the economic operator; you can handle this yourself or outsource it to a DPP service provider (clause 4.2.1). Identity should not create vendor lock-in (clause 4.6.2). Since uniqueness in Scheme 2 is based on your domain name (Table B.1), continuous domain name renewal becomes important for longevity (this is our inference, not an explicit rule).
Economic operator and facility identity
Company and facility identifications are mandatory where required by relevant legislation; in that case, they must meet the requirements in Article 4 and be based on one of four schemes (Article 6.1). The economic operator is the manufacturer, authorized representative, importer, distributor, seller, or order fulfillment service provider who places the product on the market (Article 3.1.5).
| Choice | Examples | For the operator | For the facility |
|---|---|---|---|
| Schematics registered in ISO/IEC 6523 (clause 6.2) | GLN (ICD 0088), DUNS (ICD 0060), LEI (ICD 0199), EU VAT number (ICD 0223) (Table C.10) | Yes (Table C.1) | Yes (Table C.1) |
| GS1 or ASC MH10 identifiers (clause 6.3) | GS1 AI 417 for the legal entity, AI 414 for the physical location (Table C.11) | Yes (Table C.1) | Yes (Table C.1) |
| DID and verifiable identity information (clause 6.4) | When an authorized company registry provides identification information, the DID is converted into an operator ID (clause 6.4.1). | Yes (Table C.1) | Yes (Table C.1) |
| DOI (clause 6.5) | Prefix obtained from DOI organization | Yes (Table C.1) | It's unclear: Table C.1 says "no," while clause 6.5 also mentions the facility. |
The list in Table C.10 is illustrative and not exhaustive. It does not mention standard Turkish tax numbers, MERSİS numbers, or EORI numbers; it is unclear today whether these will be accepted as operator identifiers in DPP. If you are a GS1 member, GLN is one of the readily available options for both the company and the facility (Tables C.10, C.11).
Decisions you need to make as a producer
- Level of detail: What does the product group rule require, and which of your products fall under the categories in Annex A.5? The level is fixed after placing on the market (clause 4.4.2).
- Scheme: If you are using GTIN, use scheme 1 or scheme 4; if you want your own domain-based identity, use scheme 2; if you want a DID-based decentralized structure, use scheme 3; if you prefer DOI infrastructure, use scheme 5 (item 5). Digital signature is not specific to scheme 3 (Table B.3).
- Analysis: Accessing the passport online requires a registered domain name; will this domain name be included in the ID card itself, or will it be found using an analysis service (Table B.4)?
- Serial number design: Sequential numbers are predictable; the standard recommends masking the model and serial number with a random sequence for the Identification Link (clause 5.3.3).
- Retention responsibilities: Will the records be kept internally or with a service provider (clause 4.2.1)? A standard contract does not impose this; it is practical to include the conditions of continuity and non-dependency (clauses 4.2.2, 4.6.2) in the contract.
- Operator and facility identification: Which existing number will you use if the legislation requires it (clause 6.1)?
First steps for preparation
- Follow the ESPR regulations for your product groups; the requirements regarding the level of detail are expected to come from there. For the general framework... Our ESPR and DPP guide Look.
- Inventory your existing codes: GTIN, model code, batch and serial number formats, company identifiers such as GLN or DUNS.
- Scan the batch and serial numbers for Turkish character, space, and font size discrepancies; verify that the codes do not conflict during conversion.
- Plan the data carrier on which the identity will be printed or written simultaneously; details included. in our data carrier article.
- Clarify which master data field you will use to communicate the product ID to your buyers and marketplaces in the EU.
Information Note
This content is for informational purposes only and does not replace the standard text; in practice, the current and complete text of the standard should be used. AES is not an approved or certification body; it does not issue, verify, or certify Digital Product Passport documents, and does not offer any passport software or Registration System services.
AES's TÜRKAK accreditation covers only the periodic inspection of electrical installations (AB-0631-M). The above information does not constitute a binding legal or technical opinion; each specific case should be evaluated within its own context.
Related Services and Content
- QR Code and Data Carrier for DPP: EN 18220 and ISO/IEC 18004 Guidelines
- Who Sees What in DPP? Access Rights and Commercial Privacy with EN 18239
- Trusting DPP Data: Signature, Integrity, and Change Trace with EN 18246
- Where and for how long is DPP data stored? Archiving and backup according to EN 18221.
- When Choosing DPP Software: Protocol and API according to EN 18216, 18222 and 18223.
- DPP Preparation Checklist: Manufacturer Decisions According to Eight EN Standards
- Digital Product Passport Technical Infrastructure: EN Standards, Data Carrier and EU Registration System
- ESPR and Digital Product Passport (DPP): A Comprehensive Guide for Exporting Manufacturers
- Digital Product Passport (DPP) Services
Frequently Asked Questions
Do I need to use GTIN?
No. EN 18219 recognizes five product schemes, and GS1 is only included in some of them (clause 5). You can retain the GTIN in your barcodes; the standard requires that existing numbering systems be used within the defined schemes wherever possible (clause 4.5.2).
Can I start at the model level and then move on to the serial number?
Yes, but not by changing the existing identity. The level of detail of the identity must remain constant after market launch (clause 4.4.2). If the existing identity cannot meet the finer level, you issue a new or expanded identity and link it to the old one (clause 4.4.2, Appendix A.6).
Our batch and serial numbers contain Turkish characters. Will this be a problem?
The characters in the identifier should be selected from the ISO/IEC 646 set; when the identifier is used as a URI, those characters not considered unseparated by RFC 3986 should be percentage-encoded (clause 4.3.2). The Turkish letters ç, ğ, ı, İ, ö, ş, and ü are excluded from this set. We recommend creating the new codes using only the letters AZ and numbers, and checking that two old codes do not correspond to the same meaning during conversion.
What happens to the identities if our company closes or we change our DPP service provider?
Even if your company goes bankrupt, is liquidated, or ceases operations, the identity must remain accessible (clause 4.2.2); the identity should also not create dependency on the supplier (clause 4.6.2). You, as the economic operator, are responsible for the identity records; you may outsource this to a service provider (clause 4.2.1).
Does the consumer have to download an app or register to view the consumer passport?
No. Access to publicly available information does not require registration, DPP-specific software, or user information (clause 4.6.2). The goal is for the identity to work automatically with major operating systems and browsers on current phones (clause 4.5.3).
Do we need separate IDs for our company and factory?
Yes, if the relevant legislation requires it; in that case, one of the four schemes in the standard is used (clause 6.1). Existing identities such as GLN, DUNS, and LEI are cited as examples (Table C.10). The Turkish tax number and MERSİS are not mentioned in the standard; it is unclear whether they will be accepted.