{"id":6512,"date":"2026-10-28T23:14:46","date_gmt":"2026-10-28T20:14:46","guid":{"rendered":"https:\/\/aesinn.com\/?page_id=6512"},"modified":"2026-10-28T23:14:46","modified_gmt":"2026-10-28T20:14:46","slug":"dpp-hazirlik-kontrol-listesi-en-standartlarina-gore-uretici-kararlari","status":"publish","type":"page","link":"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/dpp-hazirlik-kontrol-listesi-en-standartlarina-gore-uretici-kararlari\/","title":{"rendered":"DPP Preparation Checklist: Manufacturer Decisions According to Eight EN Standards"},"content":{"rendered":"<p class=\"wp-block-paragraph\">This checklist, the concluding article in our DPP Standards Guide series, compiles the decision points derived from eight European standards (EN 18239, clause 0.1) for digital product passports (DPPs) into a single list for a manufacturer exporting to the EU. The standard and clause on which each item is based are given in parentheses; a link to the relevant article in the series is provided for details.<\/p>\n\n\n\n<div class=\"aes-standart-durumu\" style=\"border-left:4px solid #1F4E79;background:#f3f6fa;padding:14px 18px;margin:18px 0 22px 0;font-size:15px;line-height:1.6;color:#222;\"><strong>Official status of the standard<\/strong><ul style=\"margin:8px 0 6px 18px;padding:0;\"><li>EN 18216, 18219, 18220, 18221, 18222 and 18223 (May 2026): Published in the Official Journal of the EU. <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/TR\/TXT\/?uri=CELEX:32026D1736\">(EU) 2026\/1736<\/a> It was referred to as a standard harmonized with Commission Implementing Decision No. 14 (July 14, 2026).<\/li><li>EN 18239 and EN 18246 (September 2026): published. As of the end of October 2026, there is no reference to them in the Official Journal of the EU; therefore, they do not yet provide a presumption of conformity.<\/li><\/ul><span style=\"font-size:13px;color:#555;\">Source: CEN\/CENELEC publication information and the Official Journal of the European Union (EUR-Lex), checked 28 October 2026.<\/span><\/div>\n\n\n\n<div class=\"aes-ortak-notu\" style=\"border-left:4px solid #CE1A1A;background:#f6f6f6;padding:14px 18px;margin:18px 0 22px 0;font-size:15px;line-height:1.6;color:#222;\"><strong>Service note:<\/strong> AES Innovation carries out the EU compliance work described on this page (PPWR, digital product passport, CBAM, etc.) in collaboration with expert solution partners; it does not provide these services directly. These activities are outside the scope of our accreditation (AB-0631-M).<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">What do standards regulate, and what do they not regulate?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These standards establish the technical framework of the passport: identity (EN 18219), data carrier (EN 18220), protocol and format (EN 18216), storage and archiving (EN 18221), API (EN 18222), data structure (EN 18223), access and security (EN 18239), integrity and signature (EN 18246). None of them specify which product data the passport will carry; this comes from the product group-specific regulation (EN 18223, clause 4.1.2.1).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Non-standard general information: These regulations are delegated acts to be issued on a product group basis under the ESPR. For product-specific data... <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/tekstil-sektorunde-dijital-urun-pasaportu-dpp-espr-veri-gereklilikleri-ve-hazirlik\/\">textile<\/a>, <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/celik-sektorunde-dijital-urun-pasaportu-dpp-espr-kapsaminda-karbon-geri-donusum-ve-izlenebilirlik-verisi\/\">steel<\/a> And <a href=\"https:\/\/aesinn.com\/en\/batarya-pasaportu-nedir-ab-batarya-tuzugu\/\">battery<\/a> You can browse our pages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The official situation is briefly as follows: EN 18216, 18219, 18220, 18221, 18222 and 18223 are referenced as harmonized standards with Commission Implementing Decision (EU) 2026\/1736 (14 July 2026); there is no reference for EN 18239 and EN 18246 as of the end of October 2026, and the presumption of conformity has not yet arisen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Product side: identity and carrier<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Decisions on identity and granularity<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Follow the product group classification to determine whether it requires model, batch, or individual product level (EN 18219, clause 4.4.3, Annex A.1).<\/li>\n\n\n\n<li>If the choice is yours, evaluate the unique level in products that have been repaired, have updated software, are undergoing maintenance, or are susceptible to counterfeiting (EN 18219, Annex A.5).<\/li>\n\n\n\n<li>Determine the level before placing it on the market; if it changes afterwards, do not change the old identity, link the new identity to the old one (EN 18219, clause 4.4.2, Annex A.6).<\/li>\n\n\n\n<li>Choose one of five product schemes; GTIN is not mandatory, but you can use your existing GTIN within the defined schemes (EN 18219, clause 5.1, 4.5.2).<\/li>\n\n\n\n<li>Set up batch and serial numbers using ISO\/IEC 646 characters; \u00e7, \u011f, \u0131, \u0130, \u00f6, \u015f and \u00fc are excluded from this set (EN 18219, clause 4.3.2).<\/li>\n\n\n\n<li>Do not transfer the given identity to another product; the identity must remain accessible even if the company ceases operations (EN 18219, clauses 4.1.2, 4.2.2).<\/li>\n\n\n\n<li>If the regulations require it, define your economic operator and facility identity (EN 18219, clause 6.1); make the decision early, as the operator identity is also mentioned in the heading fields of EN 18223 and the two standards do not completely overlap here (EN 18223, Table 1).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Detail: <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18219-dpp-benzersiz-tanimlayici-urun-operator-tesis-kimligi\/\">our unique descriptive text<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Carrier on the product<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Choose a carrier from QR code, Data Matrix, HF RFID, NFC and RAIN RFID; the product group regulation determines which one is mandatory (EN 18220, clause 6, 4.2).<\/li>\n\n\n\n<li>Each individual product must have at least one carrier on its packaging or documentation; this information must be accessible to the consumer without registration or special procedures (EN 18220, clauses 5.1, 5.3.4).<\/li>\n\n\n\n<li>Choose the placement; for long-lasting products, consider branding on the product or a permanent label, as the link between the product and its identity is broken once the packaging is discarded (EN 18220, clauses 4.3.1, 5.4.1, 5.4.3).<\/li>\n\n\n\n<li>Encode the product ID to the carrier in accordance with the syntax of the identification scheme (in most applications within a DPP address) (EN 18220, clause 5.2.1); a smaller code is obtained with the same X value as the address shortens (ISO\/IEC 18004, Table 7).<\/li>\n\n\n\n<li>You determine the module width (X) and error correction level according to the target reading environment; the standard does not provide a numerical lower limit (EN 18220, clause 5.5.2; ISO\/IEC 18004, Table 8).<\/li>\n\n\n\n<li>Leave at least 4X unmarked silent zones on all four edges of the QR code (ISO\/IEC 18004, clause 5.3.8).<\/li>\n\n\n\n<li>Have the print quality measured using the ISO\/IEC 15415 method and a compliant verifier; you will then set the acceptance rating (EN 18220, clauses 5.6.2, 5.6.3).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Detail: <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18220-iso-iec-18004-dpp-qr-kod-veri-tasiyici-secimi-baski-kalitesi\/\">our data carrier article<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Data side: hosting, serving, and API.<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">3. Data storage, archiving, and backup.<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Decide whether you will store the passport yourself or provide it to the main DPP service provider; the architecture is decentralized (EN 18221, clause 1, 3.3.1, 4.1).<\/li>\n\n\n\n<li>It should be possible to generate JSON and HTML representations from the stored data; in our assessment, therefore, simply storing the passport as a PDF is insufficient (EN 18221, clause 4.1).<\/li>\n\n\n\n<li>Archive every change from the first one onwards; the archive is kept with you or the main provider and, if applicable, the backup provider for the lifetime of the DPP, and the version from a specific date can be restored to the authorized user (EN 18221, clause 4.2).<\/li>\n\n\n\n<li>If your product line requires backup copies, specify the backup provider and replication frequency; the standard mentions the maximum recovery point target (RPO, maximum acceptable data loss window) only as an example (EN 18221, clauses 4.3, 4.5).<\/li>\n\n\n\n<li>Include in the written plan how general access from backup will be enabled when the operator is inactive; the standard does not define the process (EN 18221, clause 4.3).<\/li>\n\n\n\n<li>Keep additional documents such as manuals and certificates available for download online for the entire lifespan of the DPP (EN 18221, clause 4.4).<\/li>\n\n\n\n<li>Plan the storage time not by number, but by referring to the DPP (Durable Lifespan) in the product regulation (EN 18221, clause 3.4).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Detail: <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18221-dpp-veri-saklama-arsiv-yedek-kalicilik\/\">our article on data storage and archiving<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Presentation, API and data structure.<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The passport must be presented over HTTPS: minimum TLS 1.2 (TLS 1.3 strongly recommended) and minimum HTTP\/2 (EN 18216, clause 4).<\/li>\n\n\n\n<li>Provide JSON for machine viewing and HTML for human viewing that complies with EN 301549 accessibility requirements; XML and JSON-LD are optional (EN 18216, clause 5).<\/li>\n\n\n\n<li>Passport ID reading, product ID reading, and batch ID verification methods must be operational on the part of the system that creates them and, if applicable, in backup form (EN 18222, clause 4.1).<\/li>\n\n\n\n<li>If you are authorizing service providers, dealers, or recyclers to update on a site-by-site basis, a partial update method becomes mandatory (EN 18222, clauses 4.1, 4.7).<\/li>\n\n\n\n<li>Extract the ERP\/PLM equivalents of header fields such as passport ID, product ID, granularity, and UTC-based last update time (EN 18223, clause 4.1.2.1, Table 1).<\/li>\n\n\n\n<li>Plan how to link data points to definitions in a dictionary repository and how to define your own non-regulatory fields (EN 18223, clause 4.3).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Detail: <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/dpp-yazilimi-secimi-en-18216-en-18222-en-18223-protokol-api\/\">Our article on protocols, APIs, and interoperability.<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Trust side: access and signature<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">EN 18239 and EN 18246 are not yet referenced; however, adding the role, authority, and record structure afterwards is more expensive than establishing it from the beginning (non-standard general assessment).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. Access rights and commercial confidentiality<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Label any information likely to appear in the passport as \u201cpublic,\u201d \u201ccontrolled,\u201d or \u201coutside of the DPP\u201d (EN 18239, clauses 3.1, 6.2).<\/li>\n\n\n\n<li>Do not place publicly available data behind the terms of login, membership or account (EN 18239, clause 5.2(2), 6.1).<\/li>\n\n\n\n<li>Define access rights at the data element level, not at the document or page level (EN 18239, clause 5.2(10)).<\/li>\n\n\n\n<li>The product regulation determines which role will see which controlled data; in our interpretation, it is not possible to withhold data that the regulation has opened to a role on the grounds of &quot;trade secret&quot; (EN 18239, clause 5.2(6), 5.2(7)).<\/li>\n\n\n\n<li>Specify additional roles such as dealer or authorized service and the authentication method for them (EN 18239, clause 5.2(7), 5.2(9)).<\/li>\n\n\n\n<li>Do not restrict access solely on the grounds of location; establish the limit against data scraping without compromising legal information obligations (EN 18239, clauses 5.2(3), 5.2(11), 5.2(15)).<\/li>\n\n\n\n<li>Document the access and modification log, the granting and revocation process, and the access revocation policy in writing (EN 18239, clauses 5.2(16), 5.2(17), 6.3).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Detail: <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18239-dpp-erisim-haklari-ticari-gizlilik\/\">Our article on access rights and commercial privacy.<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. Signature and trace of alteration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ensure data integrity and origin through a mechanism independent of the communication channel; the site&#039;s use of HTTPS alone is not sufficient (EN 18246, clause 4.1).<\/li>\n\n\n\n<li>Choose your signature technology: digital signature, corporate seal, electronic authentication of attributes (EAA), or signed data structure (EN 18246, clause 4.7, Annex A.3).<\/li>\n\n\n\n<li>Every actor that will write data to the passport (including your suppliers if they will write directly to the passport) must prove ownership of the digital certificate and be identifiable by a globally unique identifier (EN 18246, clauses 4.2, 4.7).<\/li>\n\n\n\n<li>Every creation, modification, and deletion must be recorded in a way that the person making it cannot deny; regulatory significant changes are recorded in accordance with EN 18221 (EN 18246, clause 4.7, 5.3.2).<\/li>\n\n\n\n<li>Keep the verification free and unrestricted for the verifier (EN 18246, clause 4.7).<\/li>\n\n\n\n<li>Do not use external analytical tools on the publicly accessible passport page, and do not request personal data or device permissions from the user (EN 18246, clauses 5.1.3, 5.1.6).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Detail: <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18246-dpp-veri-imza-butunluk-degisiklik-izi\/\">Our signature, integrity, and trace of alteration text<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7. Supplier and contract<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Standards don&#039;t impose contractual requirements; however, most of the above points are available to the software provider or printing company. A practical approach is to list these points by item number in the tender specifications and obtain written responses.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Software and DPP service provider<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>TLS and HTTP versions, JSON and accessible HTML support (EN 18216, clauses 4, 5).<\/li>\n\n\n\n<li>Mandatory readout methods must operate on both the primary and backup sides, and REST paths must be provided as per the standard (EN 18222, clauses 4.1, 8.2).<\/li>\n\n\n\n<li>Archiving of changes (also on the backup provider if available), maximum RPO (Replication Requirement Point) that you will define for replication frequency, general access from backup when the operator is inactive (EN 18221, clauses 4.2, 4.3, 4.5).<\/li>\n\n\n\n<li>Avoiding dependence on the supplier regarding identity verification (EN 18219, clause 4.6.2).<\/li>\n\n\n\n<li>Authorization at the data element level, protected access log and emergency cancellation; writing cybersecurity measures into the contract is at the recommendation level (EN 18239, clauses 5.2(10), 5.2(16), 5.2(19), 6.5.2).<\/li>\n\n\n\n<li>\u201cClaims such as &quot;EN 18223 certified&quot; are not based on any specific tests; the standard (EN 18223) does not contain any conformity testing or certification clauses.<\/li>\n\n\n\n<li>Non-standard but necessary: the country where the data is hosted, delivery of all versions upon provider change, and the authentication method.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Printing and packaging supplier<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The DPP address will be encoded according to the QR code and identification scheme compliant with ISO\/IEC 18004:2024 (EN 18220, clause 6.2.3, 5.2.1).<\/li>\n\n\n\n<li>Your specified X value, error correction level, and 4X silent zone (EN 18220, clause 5.5.2; ISO\/IEC 18004, clause 5.3.8).<\/li>\n\n\n\n<li>ISO\/IEC 15415:2024 quality method, verifier in accordance with ISO\/IEC 15426-2:2023 and your acceptance note (EN 18220, clauses 5.6.2, 5.6.3).<\/li>\n\n\n\n<li>Non-standard but necessary: sample approval before mass production, sampling per batch, and appropriate durability tests for the product.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Decisions you need to make as a producer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cThe &quot;Who provides&quot; column is our suggestion; the standards do not assign tasks internally within the company.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Decision<\/th><th>Who gives it?<\/th><th>Standard<\/th><\/tr><\/thead><tbody><tr><td>Model, batch, or individual product level<\/td><td>Production and quality<\/td><td>EN 18219, clause 4.4.2<\/td><\/tr><tr><td>Identity scheme and serial number structure<\/td><td>IT and quality<\/td><td>EN 18219, clause 5.1, 4.3.2<\/td><\/tr><tr><td>Operator and facility ID<\/td><td>BT<\/td><td>EN 18219, clause 6.1<\/td><\/tr><tr><td>Type and placement of carrier<\/td><td>Production and quality<\/td><td>EN 18220, clause 6, 5.4.1<\/td><\/tr><tr><td>X value, error correction, acceptance grade<\/td><td>Quality and purchasing<\/td><td>EN 18220, clauses 5.5.2, 5.6.2<\/td><\/tr><tr><td>Self-hosting or a service provider?<\/td><td>IT and procurement<\/td><td>EN 18221, clauses 3.3.1, 4.1<\/td><\/tr><tr><td>Backup provider and maximum RPO<\/td><td>IT and procurement<\/td><td>EN 18221, clauses 4.3, 4.5<\/td><\/tr><tr><td>Third parties&#039; authority to update<\/td><td>Quality and IT<\/td><td>EN 18222, clauses 4.1, 4.7<\/td><\/tr><tr><td>Data element access layer and additional roles<\/td><td>Quality and IT<\/td><td>EN 18239, clause 5.2(7), 5.2(10)<\/td><\/tr><tr><td>Signature technology and certificate provider.<\/td><td>BT<\/td><td>EN 18246, clause 4.7<\/td><\/tr><tr><td>Security clauses to be included in the contract<\/td><td>Procurement and IT<\/td><td>EN 18239, clause 6.5.2<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Common mistakes<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cDPP is a QR code.\u201d Identification is a string of characters; the QR code is just one of several carriers (EN 18219, clause 4.5.2; EN 18220, clause 6).<\/li>\n\n\n\n<li>\u201c&quot;Uploading the passport as a PDF is sufficient.&quot; The required formats are JSON and accessible HTML; PDFs can only be linked as associated resources (EN 18216, clause 5; EN 18223, clause 4.1.2.7).<\/li>\n\n\n\n<li>\u201cThe current version is sufficient; older versions can be deleted.\u201d All changes are archived except those explicitly exempted by the product guidelines (EN 18221, clause 4.2).<\/li>\n\n\n\n<li>\u201cAll data in the DPP is publicly accessible.\u201d Public and controlled data are separated (EN 18239, clauses 3.1, 6.2).<\/li>\n\n\n\n<li>\u201cSigned data is accurate data.\u201d The signature indicates the source of the data and that it has not been altered, but not the accuracy of the content (EN 18246, Annex A.3).<\/li>\n\n\n\n<li>\u201cISO\/IEC 27001 certification is required.\u201d It is mentioned in the standard only at the suggestion and option level (EN 18239, clause 5.2(21), 6.5.5).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">First steps for preparation<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>First, monitor your product lines for ESPR regulations; granularity, carrier, DPP lifetime, and rollers are expected to come from there. For the framework... <a href=\"https:\/\/aesinn.com\/en\/espr-ve-dijital-urun-pasaportu-dpp-ihracatci-ureticiler-icin-kapsamli-rehber\/\">Our ESPR and DPP guide<\/a> Look.<\/li>\n\n\n\n<li>Inventory your existing code and product master data; scan for Turkish characters and codes that may conflict during conversion.<\/li>\n\n\n\n<li>Decide on the identity schema and granularity before carrier and API design; both depend on this decision.<\/li>\n\n\n\n<li>Next, map each data element that will enter the passport into a single table according to its access layer and source (who is generating it, who will sign it).<\/li>\n\n\n\n<li>Have your hosting provider&#039;s TLS and HTTP support checked, then make your hosting decision.<\/li>\n\n\n\n<li>Send the questions from this list, item by item, in writing to prospective providers.<\/li>\n\n\n\n<li>Perform a pilot test on a package and a label, measure them with a validator, and write the X value and acceptance score in the specification according to the result.<\/li>\n\n\n\n<li>Finally, document the activity termination scenario, the access revocation policy, and the rights management process in writing.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Information Note<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">AES&#039;s T\u00dcRKAK 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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Related Services and Content<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18219-dpp-benzersiz-tanimlayici-urun-operator-tesis-kimligi\/\">Unique Identifier in DPP: Product, Operator and Facility according to EN 18219<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18220-iso-iec-18004-dpp-qr-kod-veri-tasiyici-secimi-baski-kalitesi\/\">QR Code and Data Carrier for DPP: EN 18220 and ISO\/IEC 18004 Guidelines<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18239-dpp-erisim-haklari-ticari-gizlilik\/\">Who Sees What in DPP? Access Rights and Commercial Privacy with EN 18239<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18246-dpp-veri-imza-butunluk-degisiklik-izi\/\">Trusting DPP Data: Signature, Integrity, and Change Trace with EN 18246<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18221-dpp-veri-saklama-arsiv-yedek-kalicilik\/\">Where and for how long is DPP data stored? Archiving and backup according to EN 18221.<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/dpp-yazilimi-secimi-en-18216-en-18222-en-18223-protokol-api\/\">When Choosing DPP Software: Protocol and API according to EN 18216, 18222 and 18223.<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/dijital-urun-pasaportu-teknik-altyapisi-en-standartlari-veri-tasiyici-ve-ab-kayit-sistemi\/\">Digital Product Passport Technical Infrastructure: EN Standards, Data Carrier and EU Registration System<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/espr-ve-dijital-urun-pasaportu-dpp-ihracatci-ureticiler-icin-kapsamli-rehber\/\">ESPR and Digital Product Passport (DPP): A Comprehensive Guide for Exporting Manufacturers<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/\">Digital Product Passport (DPP) Services<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does this list also include data requirements specific to my product?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. These standards regulate the technical infrastructure; which product data is included in the passport comes from the product group-specific regulation (EN 18223, clause 4.1.2.1).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which standards provide a presumption of conformity?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">EN 18216, 18219, 18220, 18221, 18222 and 18223 were referenced in the Official Journal of the European Union by Commission Implementing Decision (EU) 2026\/1736 (14 July 2026); they provide a presumption of conformity with the relevant requirements of the ESPR to the extent covered by the standards. EN 18239 and EN 18246 were published in September 2026; as of the end of October 2026 there is no reference, and the presumption of conformity has not yet arisen.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which decision should I make first?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The level determines the identity and granularity. It remains constant after market release (EN 18219, clause 4.4.2) and also defines the header area and API queries (EN 18223, clause 4.1.2.2; EN 18222, clause 4.3).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I leave everything to a DPP service provider?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can have the work done, but the decisions remain yours. You are responsible for identity records as the economic operator (EN 18219, clause 4.2.1); you or the service provider working on your behalf keeps the passport (EN 18221, clause 4.1).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is a backup service provider mandatory for every product?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The standard itself does not mandate this; it states that a backup copy may be required (EN 18221, clause 4.3). Which products require it depends on the ESPR and product group regulations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I verify my supplier&#039;s claim of &quot;compliance with standards&quot;?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Examine the claim point by point: TLS and HTTP versions (EN 18216, clause 4), mandatory read methods (EN 18222, clause 4.1), archiving and backup (EN 18221, clauses 4.2, 4.3). EN 18223 does not contain any testing or certification clauses.<\/p>","protected":false},"excerpt":{"rendered":"<p>DPP Standartlar\u0131 Rehberi serisinin kapan\u0131\u015f yaz\u0131s\u0131: sekiz EN standard\u0131ndan \u00e7\u0131kan karar noktalar\u0131 ve yap\u0131lacaklar, madde numaralar\u0131yla tek bir kontrol listesinde. Kimlikten ta\u015f\u0131y\u0131c\u0131ya, ar\u015fivden imzaya ve tedarik\u00e7i s\u00f6zle\u015fmesine kadar.<\/p>","protected":false},"author":1,"featured_media":6511,"parent":4959,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kadence_starter_templates_imported_post":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","slim_seo":{"title":"DPP Preparation Checklist: According to EN Standards","description":"The decisions stemming from eight DPP standards are listed in a single list: identity, data carrier, hosting and archiving, API, access rights, signature, and supplier agreement."},"_pplb_hide_from_list":false,"footnotes":""},"class_list":["post-6512","page","type-page","status-publish","has-post-thumbnail","hentry"],"acf":[],"taxonomy_info":[],"featured_image_src_large":["https:\/\/aesinn.com\/wp-content\/uploads\/dpp-kontrol-aes-kart-1024x1024.png",1024,1024,true],"author_info":{"display_name":"Emre Metin","author_link":"https:\/\/aesinn.com\/en\/author\/yonetim\/"},"comment_info":"","_hostinger_reach_plugin_has_subscription_block":false,"_hostinger_reach_plugin_is_elementor":false,"_links":{"self":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/6512","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/comments?post=6512"}],"version-history":[{"count":1,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/6512\/revisions"}],"predecessor-version":[{"id":6515,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/6512\/revisions\/6515"}],"up":[{"embeddable":true,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/4959"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/media\/6511"}],"wp:attachment":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/media?parent=6512"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}