[{"data":1,"prerenderedAt":842},["ShallowReactive",2],{"content-ecommerce-stack-best-compliance-tool":3,"related-ecommerce-stack-best-compliance-tool":283},{"id":4,"title":5,"author":6,"body":7,"category":265,"date":266,"description":267,"draft":268,"extension":269,"locale":270,"meta":271,"navigation":272,"path":273,"readingTime":274,"seo":275,"stem":276,"tags":277,"thumbnail":257,"__hash__":282},"articles\u002Farticles\u002Fecommerce-stack-best-compliance-tool.md","Your E-Commerce Stack Is Your Best Compliance Tool — If You Wire It Correctly","PassportLab Team",{"type":8,"value":9,"toc":256},"minimark",[10,14,19,22,63,66,92,95,99,102,183,186,190,193,196,200,203,223,226,230,233,236,239],[11,12,13],"p",{},"Most e-commerce brands have more of the data required for a Digital Product Passport than they realise. The product name, SKU, materials description, country of origin, and supplier information already live somewhere in their Shopify store, WooCommerce database, or ERP system. The DPP compliance gap is not primarily a data gap — it is a wiring gap.",[15,16,18],"h2",{"id":17},"what-your-stack-already-has","What Your Stack Already Has",[11,20,21],{},"A typical mid-sized importer running Shopify or WooCommerce with a connected ERP has:",[23,24,25,33,39,45,51,57],"ul",{},[26,27,28,32],"li",{},[29,30,31],"strong",{},"Product metadata"," (title, description, SKU, variants) — Shopify\u002FWooCommerce",[26,34,35,38],{},[29,36,37],{},"Supplier information"," (manufacturer name, country of origin) — usually in the ERP or as product metafields",[26,40,41,44],{},[29,42,43],{},"Material composition"," (fabric content, component breakdown) — often in product descriptions or technical sheets, not structured data",[26,46,47,50],{},[29,48,49],{},"Product images"," — Shopify CDN \u002F WooCommerce media library",[26,52,53,56],{},[29,54,55],{},"Weight and dimensions"," — Shopify\u002FWooCommerce",[26,58,59,62],{},[29,60,61],{},"Customs classification"," (HS code) — usually in the ERP for import compliance",[11,64,65],{},"What your stack probably does not have, structured:",[23,67,68,74,80,86],{},[26,69,70,73],{},[29,71,72],{},"Carbon footprint per unit"," — requires calculation, not just storage",[26,75,76,79],{},[29,77,78],{},"Recycled material content percentages"," — must come from supplier data, often not digitised",[26,81,82,85],{},[29,83,84],{},"End-of-life instructions in machine-readable form"," — usually locked in PDF manuals",[26,87,88,91],{},[29,89,90],{},"Repair and spare parts availability"," — may be in a separate system or not tracked at all",[11,93,94],{},"The first group — data you already have — can be synced to a DPP platform automatically. The second group requires a deliberate supplier data collection exercise.",[15,96,98],{"id":97},"how-shopify-sync-works-in-practice","How Shopify Sync Works in Practice",[11,100,101],{},"PassportLab's Shopify integration pulls products via the Admin API and creates a draft DPP for each variant. The sync maps:",[103,104,105,118],"table",{},[106,107,108],"thead",{},[109,110,111,115],"tr",{},[112,113,114],"th",{},"Shopify field",[112,116,117],{},"DPP field",[119,120,121,133,141,149,159,167,175],"tbody",{},[109,122,123,127],{},[124,125,126],"td",{},"Product title",[124,128,129],{},[130,131,132],"code",{},"productName",[109,134,135,138],{},[124,136,137],{},"Product type",[124,139,140],{},"Category (with manual confirmation)",[109,142,143,146],{},[124,144,145],{},"Vendor",[124,147,148],{},"Manufacturer",[109,150,151,154],{},[124,152,153],{},"Country of origin (metafield)",[124,155,156],{},[130,157,158],{},"originCountry",[109,160,161,164],{},[124,162,163],{},"Body HTML (cleaned)",[124,165,166],{},"Materials description",[109,168,169,172],{},[124,170,171],{},"Weight",[124,173,174],{},"Physical dimensions",[109,176,177,180],{},[124,178,179],{},"Custom metafields",[124,181,182],{},"Any structured DPP field",[11,184,185],{},"The sync creates DPPs in draft status. You review and complete the missing fields — primarily the supplier-provided data — before publishing. This approach means you are not starting from a blank form; you are filling gaps in a pre-populated record.",[15,187,189],{"id":188},"the-woocommerce-path","The WooCommerce Path",[11,191,192],{},"WooCommerce integration works similarly via the REST API. Because WooCommerce product attributes are more flexible than Shopify metafields, there is more room to pre-populate DPP fields directly from product attributes if your catalogue uses consistent naming.",[11,194,195],{},"If you are importing products from a CSV or XML feed, PassportLab also supports direct CSV\u002FXML import with a field mapping UI. This is useful for brands that manage product data in a spreadsheet rather than a live e-commerce platform.",[15,197,199],{"id":198},"what-still-requires-human-input","What Still Requires Human Input",[11,201,202],{},"No integration can automate the compliance-critical fields that require supplier documentation:",[23,204,205,211,217],{},[26,206,207,210],{},[29,208,209],{},"Battery regulation fields"," (Annex XIII): carbon footprint per kWh, recycled content percentages, state of health methodology, responsible sourcing certificates",[26,212,213,216],{},[29,214,215],{},"Textile fields",": composition by fibre, chemical treatments, restricted substances",[26,218,219,222],{},[29,220,221],{},"Electronics fields",": hazardous substance declarations, repair scores, spare parts availability",[11,224,225],{},"These fields require a supplier data collection workflow. PassportLab's supplier invite feature lets you send a scoped data request directly to your supplier's contact email. They fill in a structured form — no account required — and the data flows into the DPP. This is the fastest path to getting supplier-provided fields completed without building a custom procurement integration.",[15,227,229],{"id":228},"the-integration-payoff","The Integration Payoff",[11,231,232],{},"Once your Shopify or WooCommerce catalogue is synced and your suppliers have submitted their data, generating a compliant DPP becomes a one-click operation per product variant. Updates to existing DPPs (new supplier certifications, material changes) can be pushed from your e-commerce platform via webhook without manual intervention.",[11,234,235],{},"The brands that implement this wiring before the 2027 deadline will be able to respond to new regulatory categories by running a sync and completing supplier data requests — rather than rebuilding their compliance infrastructure from scratch.",[237,238],"hr",{},[11,240,241],{},[242,243,244,245,250,251,255],"em",{},"Connect your Shopify or WooCommerce store in minutes. ",[246,247,249],"a",{"href":248},"\u002Fhow-it-works","See how the integration works"," or ",[246,252,254],{"href":253},"\u002Fdemo","book a walkthrough",".",{"title":257,"searchDepth":258,"depth":258,"links":259},"",2,[260,261,262,263,264],{"id":17,"depth":258,"text":18},{"id":97,"depth":258,"text":98},{"id":188,"depth":258,"text":189},{"id":198,"depth":258,"text":199},{"id":228,"depth":258,"text":229},"Integration","2026-03-03","Shopify, WooCommerce, and ERP data already contain most of the fields a DPP requires. The compliance gap is not data — it is the wiring between your existing stack and the regulatory output.",false,"md","en",{},true,"\u002Farticles\u002Fecommerce-stack-best-compliance-tool",7,{"title":5,"description":267},"articles\u002Fecommerce-stack-best-compliance-tool",[278,279,265,280,281],"Shopify","WooCommerce","E-Commerce","DPP","-nDYGBTyeoriIC1CcWfLmxJB6gXF3sCjlJETPeABWD8",[284,460,661],{"id":285,"title":286,"author":6,"body":287,"category":448,"date":449,"description":450,"draft":268,"extension":269,"locale":270,"meta":451,"navigation":272,"path":452,"readingTime":453,"seo":454,"stem":455,"tags":456,"thumbnail":257,"__hash__":459},"articles\u002Farticles\u002Fdeath-of-the-static-pdf.md","Death of the Static PDF: Why DPPs Cannot Be Documents",{"type":8,"value":288,"toc":441},[289,292,295,299,302,314,317,321,324,327,331,334,358,361,365,368,378,384,390,396,402,406,409,423,426,428],[11,290,291],{},"A significant fraction of the \"DPP solutions\" being marketed to brands in 2025 are, at their core, PDF generators with a QR code on top. The QR code links to a hosted PDF. The PDF contains the product data. Someone, somewhere, reads the PDF and decides whether the product is compliant.",[11,293,294],{},"This approach fails at every layer of the ESPR technical specification. Here is why, and what a DPP actually needs to be.",[15,296,298],{"id":297},"the-pdf-cannot-be-verified","The PDF Cannot Be Verified",[11,300,301],{},"ESPR requires that DPP data be cryptographically verifiable. Specifically, the data must carry a verifiable credential (W3C Verifiable Credentials 2.0) signed by the economic operator using a key registered under their legal entity identity. A customs officer or market surveillance authority must be able to verify that:",[303,304,305,308,311],"ol",{},[26,306,307],{},"The data was issued by the organisation claiming to issue it",[26,309,310],{},"The data has not been modified since issuance",[26,312,313],{},"The issuing organisation is the legitimate economic operator for this product",[11,315,316],{},"A PDF cannot carry a W3C VC. A PDF cannot be verified by an automated system. A PDF requires a human to read it, which does not scale to the volume of products crossing EU borders.",[15,318,320],{"id":319},"the-pdf-cannot-be-queried","The PDF Cannot Be Queried",[11,322,323],{},"EU customs pre-filing systems, market surveillance tools, and retail compliance platforms all query DPP data programmatically. They call a REST endpoint, receive JSON, and check specific fields against required values. A PDF has no queryable API. It cannot be integrated into import declaration systems. It cannot be cross-referenced with the EU Common Information Repository.",[11,325,326],{},"The ESPR technical specification requires that the DPP endpoint return machine-readable JSON. The GS1 Digital Link standard specifies how the URL should be structured. The CIRPASS-2 interoperability format specifies what the JSON must contain. None of these requirements can be satisfied by a PDF.",[15,328,330],{"id":329},"the-pdf-is-static-dpps-must-be-dynamic","The PDF Is Static — DPPs Must Be Dynamic",[11,332,333],{},"A DPP is not a point-in-time document. It is a living record. Under ESPR, the DPP must be updated when:",[23,335,336,343,349,352,355],{},[26,337,338,339,342],{},"The product is repaired or remanufactured (status changes to ",[130,340,341],{},"remanufactured",")",[26,344,345,346,342],{},"The product is destroyed (status changes to ",[130,347,348],{},"destroyed",[26,350,351],{},"The product model is discontinued (triggers 10-year retention clock)",[26,353,354],{},"Recycled content percentages change due to supply chain adjustments",[26,356,357],{},"A conformity certificate is renewed or revoked",[11,359,360],{},"None of these updates can be reflected in a static PDF without reissuing the entire document and invalidating all the existing QR codes in the field. A DPP must be a live data record with a stable URL that always returns current data — not a document frozen at issuance time.",[15,362,364],{"id":363},"what-a-compliant-dpp-actually-needs","What a Compliant DPP Actually Needs",[11,366,367],{},"A compliant DPP requires:",[11,369,370,373,374,377],{},[29,371,372],{},"A stable, resolvable URL"," — the GS1 Digital Link format ",[130,375,376],{},"\u002F01\u002F{gtin}\u002F21\u002F{serial}"," is the preferred form. The URL must resolve for the lifetime of the product plus 10 years after discontinuation.",[11,379,380,383],{},[29,381,382],{},"Machine-readable JSON at that URL"," — conforming to the ESPR delegated act schema for the product category. For batteries, this means Annex XIII fields. For textiles, the relevant delegated act fields.",[11,385,386,389],{},[29,387,388],{},"A W3C Verifiable Credential"," — signed by the economic operator's DID (Decentralised Identifier), using Ed25519 or similar algorithm. The credential must be verifiable against the issuer's published DID document.",[11,391,392,395],{},[29,393,394],{},"EU CIR registration"," — the product's unique identifier must be registered in the EU Common Information Repository so discovery tools can find the authoritative data endpoint.",[11,397,398,401],{},[29,399,400],{},"Selective Disclosure capability"," — some fields in the DPP are public (basic product data), others are restricted (B2B supply chain data visible only to authorised parties). SD-JWT format allows field-level access control without invalidating the credential.",[15,403,405],{"id":404},"the-time-to-switch-is-before-enforcement","The Time to Switch Is Before Enforcement",[11,407,408],{},"If your current DPP solution produces PDFs, the time to replace it is before the 2027 battery DPP deadline, not after. Migration from a PDF-based approach requires:",[303,410,411,414,417,420],{},[26,412,413],{},"Re-creating all DPP records in a compliant JSON format",[26,415,416],{},"Re-issuing cryptographic credentials for all products",[26,418,419],{},"Re-registering all products with the EU CIR",[26,421,422],{},"Re-distributing QR codes that resolve to the new endpoints (or setting up redirect infrastructure from old QR codes)",[11,424,425],{},"This is significant operational work. It is much less significant if done proactively than if triggered by a customs rejection at the border.",[237,427],{},[11,429,430],{},[242,431,432,433,250,437,255],{},"PassportLab generates cryptographically signed, W3C VC 2.0 compliant DPPs with GS1 Digital Link resolution and EU CIR registration. ",[246,434,436],{"href":435},"\u002Fdevelopers","See the technical details",[246,438,440],{"href":439},"\u002Ffree-dpp-generator","generate a compliant DPP now",{"title":257,"searchDepth":258,"depth":258,"links":442},[443,444,445,446,447],{"id":297,"depth":258,"text":298},{"id":319,"depth":258,"text":320},{"id":329,"depth":258,"text":330},{"id":363,"depth":258,"text":364},{"id":404,"depth":258,"text":405},"Technical","2026-03-09","Many brands are treating their Digital Product Passport as a sophisticated PDF. This approach is not just incomplete — it is fundamentally incompatible with how DPP verification actually works.",{},"\u002Farticles\u002Fdeath-of-the-static-pdf",6,{"title":286,"description":450},"articles\u002Fdeath-of-the-static-pdf",[281,448,457,458],"W3C VC","Cryptographic Signing","KUbA7KmThxykMVRK2Zc-EtH11Jf1ffV_Ulv6VoudELw",{"id":461,"title":462,"author":6,"body":463,"category":648,"date":649,"description":650,"draft":268,"extension":269,"locale":270,"meta":651,"navigation":272,"path":652,"readingTime":653,"seo":654,"stem":655,"tags":656,"thumbnail":257,"__hash__":660},"articles\u002Farticles\u002Fdigital-product-passport-decoded-2026.md","Digital Product Passport Decoded: The 2026 Practical Guide for Importers",{"type":8,"value":464,"toc":641},[465,468,472,475,478,481,485,488,497,503,509,515,521,525,531,537,543,549,553,556,582,585,589,592,624,627,629],[11,466,467],{},"The phrase \"Digital Product Passport\" appears in enough regulatory communications that most importers and brand managers have heard of it. Fewer have a concrete understanding of what it actually is, what it must contain, and what happens when an authority checks it at the border. This guide is the practical version.",[15,469,471],{"id":470},"what-a-dpp-is-and-is-not","What a DPP Is (and Is Not)",[11,473,474],{},"A Digital Product Passport is a structured data record attached to a physical product, accessible via a URL encoded in a QR code, barcode, or RFID tag on the product. It is not a document. It is not a certificate. It is not a PDF. It is a live API endpoint that returns machine-readable JSON.",[11,476,477],{},"When a customs officer, market surveillance authority, retailer, or consumer scans the QR code on your product, their device makes an HTTP request to a URL. That URL returns JSON data. The data is verified cryptographically. The result is either a valid, compliant DPP — or it is not.",[11,479,480],{},"The EU Ecodesign for Sustainable Products Regulation (ESPR) mandates DPPs for all product categories covered by ESPR delegated acts. The first mandates affect batteries (February 2027) and will extend to textiles, electronics, iron and steel, and other categories on a rolling schedule through 2030 and beyond.",[15,482,484],{"id":483},"the-anatomy-of-a-compliant-dpp","The Anatomy of a Compliant DPP",[11,486,487],{},"A compliant DPP has five layers:",[11,489,490,493,494,496],{},[29,491,492],{},"Layer 1: The unique identifier."," Every DPP has a unique identifier — either a GS1 GTIN\u002Fserial combination formatted as a Digital Link URL (",[130,495,376],{},") or a UUID-based identifier. The identifier is encoded in the physical label (QR code, RFID tag) and registered in the EU Common Information Repository.",[11,498,499,502],{},[29,500,501],{},"Layer 2: The data record."," The product's required fields as specified in the ESPR delegated act for its category. For batteries: carbon footprint per kWh of energy stored, recycled content by battery material, state of health, responsible sourcing documentation. For textiles: fibre composition, country of origin per manufacturing stage, care and repair instructions, recycled content. The delegated act for each category specifies exactly which fields are mandatory.",[11,504,505,508],{},[29,506,507],{},"Layer 3: The verifiable credential."," The data record is wrapped in a W3C Verifiable Credential (VC 2.0), signed by the economic operator's cryptographic key. The key is associated with the operator's legal entity identity via a DID (Decentralised Identifier). Any party can verify the credential without contacting the issuer, by resolving the DID and checking the signature.",[11,510,511,514],{},[29,512,513],{},"Layer 4: The selective disclosure layer."," Some DPP fields are public (accessible to anyone who scans the QR code). Others are restricted — visible to customs authorities but not consumers, or visible to recycling operators but not retailers. Selective Disclosure JWT (SD-JWT) format allows field-level access control without invalidating the credential.",[11,516,517,520],{},[29,518,519],{},"Layer 5: The registry registration."," The DPP identifier and the URL of the data endpoint are registered in the EU Common Information Repository. When an authority scans a product, they can look up the CIR to find the authoritative endpoint, even if the QR code resolves to a different URL.",[15,522,524],{"id":523},"who-checks-your-dpp-and-how","Who Checks Your DPP and How",[11,526,527,530],{},[29,528,529],{},"EU Customs:"," Import declarations for products covered by ESPR mandates will soon include a DPP identifier field. Customs systems will resolve the DPP at the time of import and check required fields against the declared product category. A DPP that is missing required fields, returns an error, or fails cryptographic verification will trigger a hold.",[11,532,533,536],{},[29,534,535],{},"Market Surveillance Authorities (MSAs):"," MSAs in each EU member state conduct post-market checks on products in circulation. They scan QR codes, resolve DPPs, and check compliance with the delegated act for the product category. MSA findings are shared via the ICSMS (Information and Communication System for Market Surveillance) and can result in product recalls, import bans, and financial penalties.",[11,538,539,542],{},[29,540,541],{},"Retailers:"," Large EU retailers are increasingly requiring DPP compliance as a condition of listing. This is a commercial requirement, not a regulatory one, but it has the same practical effect. Retailers running their own compliance checks resolve DPPs programmatically and reject listings where required fields are missing.",[11,544,545,548],{},[29,546,547],{},"Consumers:"," The public-facing layer of the DPP — product composition, care instructions, repairability information, end-of-life guidance — must be accessible to consumers. EU citizens have the right to request DPP data under ESPR. The QR code must resolve to a human-readable display, not just a machine-readable JSON endpoint.",[15,550,552],{"id":551},"what-happens-when-your-dpp-is-wrong","What Happens When Your DPP Is Wrong",[11,554,555],{},"Non-compliance with ESPR DPP requirements can result in:",[23,557,558,564,570,576],{},[26,559,560,563],{},[29,561,562],{},"Import rejection at customs"," — shipments held pending compliance remediation",[26,565,566,569],{},[29,567,568],{},"Market surveillance enforcement action"," — withdrawal from sale, recall obligation, financial penalties",[26,571,572,575],{},[29,573,574],{},"Retailer delisting"," — commercial consequence from buyers requiring DPP compliance",[26,577,578,581],{},[29,579,580],{},"Registry flagging"," — an invalid DPP in the EU CIR creates a permanent compliance record",[11,583,584],{},"The penalties under ESPR are set by member states but must be \"effective, proportionate, and dissuasive.\" France, Germany, and the Netherlands have indicated penalty frameworks of €10,000–€50,000 per non-compliant product category, per enforcement action.",[15,586,588],{"id":587},"getting-your-first-compliant-dpp","Getting Your First Compliant DPP",[11,590,591],{},"The fastest path to a compliant DPP for most importers:",[303,593,594,600,606,612,618],{},[26,595,596,599],{},[29,597,598],{},"Identify your first product category"," — which of your products will be subject to the earliest ESPR mandate? Batteries first, then textiles.",[26,601,602,605],{},[29,603,604],{},"Collect the required fields"," — use the relevant delegated act field list (or PassportLab's category templates) to identify what supplier data you need.",[26,607,608,611],{},[29,609,610],{},"Generate and sign the DPP"," — a compliant DPP platform creates the W3C VC, registers with the EU CIR, and generates the QR code automatically.",[26,613,614,617],{},[29,615,616],{},"Test the QR code"," — scan it with a DPP verification tool to confirm the endpoint resolves, the data is complete, and the credential verifies.",[26,619,620,623],{},[29,621,622],{},"Distribute to your supply chain"," — update your product labels with the QR code or RFID tag encoding the DPP URL.",[11,625,626],{},"The process does not require a technical team. It requires supplier data and a platform that handles the technical compliance layers.",[237,628],{},[11,630,631],{},[242,632,633,636,637,640],{},[246,634,635],{"href":439},"Generate a compliant DPP for your product now"," — no technical knowledge required. Or ",[246,638,639],{"href":253},"book a compliance walkthrough"," with the PassportLab team.",{"title":257,"searchDepth":258,"depth":258,"links":642},[643,644,645,646,647],{"id":470,"depth":258,"text":471},{"id":483,"depth":258,"text":484},{"id":523,"depth":258,"text":524},{"id":551,"depth":258,"text":552},{"id":587,"depth":258,"text":588},"Guide","2026-02-09","What a Digital Product Passport actually is, what data it must contain, who checks it, how it gets verified, and what happens if yours is wrong. Written for importers and private-label brands.",{},"\u002Farticles\u002Fdigital-product-passport-decoded-2026",12,{"title":462,"description":650},"articles\u002Fdigital-product-passport-decoded-2026",[281,657,648,658,659],"ESPR","Importers","2026","mUaQZffFcHsAx4FqzdLjOM4tenjSyrubnttkm5Z2e5U",{"id":662,"title":663,"author":6,"body":664,"category":448,"date":830,"description":831,"draft":268,"extension":269,"locale":270,"meta":832,"navigation":272,"path":833,"readingTime":834,"seo":835,"stem":836,"tags":837,"thumbnail":257,"__hash__":841},"articles\u002Farticles\u002Fdpp-when-the-server-goes-down.md","DPP When the Server Goes Down: Hosting Obligations Under ESPR",{"type":8,"value":665,"toc":824},[666,673,676,680,683,697,700,704,707,710,736,740,743,765,768,772,775,807,810,812],[11,667,668,669,672],{},"There is a clause buried in ESPR Article 9(2)(i) that most importers and brands have not fully processed yet: the obligation to guarantee DPP data availability for ",[29,670,671],{},"10 years"," after a product model is discontinued.",[11,674,675],{},"This is not a soft requirement. It is a hard legal obligation on the economic operator who places the product on the EU market. If the DPP endpoint returns a 404 five years from now — because your SaaS provider was acquired, pivoted, or went bankrupt — you are in breach. Not your provider. You.",[15,677,679],{"id":678},"what-availability-actually-means","What \"Availability\" Actually Means",[11,681,682],{},"The ESPR delegated acts are explicit about what availability means in practice. It means:",[23,684,685,688,691,694],{},[26,686,687],{},"The DPP URL must resolve and return the required data fields",[26,689,690],{},"The GS1 Digital Link resolver must point to a live endpoint",[26,692,693],{},"The EU Common Information Repository record must be active and current",[26,695,696],{},"The cryptographic credential (W3C VC 2.0) must be verifiable against the issuer's DID document",[11,698,699],{},"All four of these require active infrastructure. QR codes printed on physical products five years ago must still work. This is a fundamentally different obligation than keeping a PDF in a file drawer.",[15,701,703],{"id":702},"the-saas-vendor-risk-nobody-talks-about","The SaaS Vendor Risk Nobody Talks About",[11,705,706],{},"When you choose a DPP platform, you are not just choosing software. You are delegating a 10-year hosting obligation to a third party. That third party has its own venture capital timeline, its own acquisition risk, and its own infrastructure decisions.",[11,708,709],{},"The risk questions to ask any DPP vendor:",[303,711,712,718,724,730],{},[26,713,714,717],{},[29,715,716],{},"Where is the data hosted?"," EU-based servers are required for many product categories under GDPR and emerging ESPR data residency guidance. \"EU region\" on a US cloud provider is different from EU-controlled infrastructure.",[26,719,720,723],{},[29,721,722],{},"What is the data export policy?"," Can you export your full DPP dataset in machine-readable form at any time, without losing the cryptographic signatures? Or does export break the chain of custody?",[26,725,726,729],{},[29,727,728],{},"What happens to your DPPs if you cancel the contract?"," A 30-day notice period is not compatible with a 10-year hosting obligation. You need contractual continuity provisions.",[26,731,732,735],{},[29,733,734],{},"Is there a backup URL?"," CIRPASS-2 interoperability guidance recommends registering a backup resolution URL for every DPP. If your primary provider is unreachable, the backup must serve the same data.",[15,737,739],{"id":738},"the-espr-data-retention-model-in-practice","The ESPR Data Retention Model in Practice",[11,741,742],{},"PassportLab implements the 10-year retention model by:",[23,744,745,752,759,762],{},[26,746,747,748,751],{},"Recording the ",[130,749,750],{},"discontinuation_date"," at the product model level",[26,753,754,755,758],{},"Auto-computing ",[130,756,757],{},"retention_expires_at"," as discontinuation date + 10 years",[26,760,761],{},"Flagging products for archival review when they approach expiry, rather than silently removing them",[26,763,764],{},"Supporting backup URL registration in the CIRPASS-2 registry format so a secondary endpoint can serve data if the primary is unavailable",[11,766,767],{},"The backup URL field is not optional infrastructure — it is the difference between a compliant DPP lifecycle and an undiscoverable compliance gap five years from now.",[15,769,771],{"id":770},"what-you-should-require-in-your-dpp-contract","What You Should Require in Your DPP Contract",[11,773,774],{},"Minimum contractual protections for a 10-year hosting obligation:",[23,776,777,783,789,795,801],{},[26,778,779,782],{},[29,780,781],{},"Data portability clause:"," full export within 30 days of request, in ESPR-compliant JSON format with verifiable credentials intact",[26,784,785,788],{},[29,786,787],{},"EU data residency clause:"," explicit commitment to EU-based infrastructure for the full retention period",[26,790,791,794],{},[29,792,793],{},"Continuity clause:"," obligation to give 180 days notice before service termination, with a defined migration path",[26,796,797,800],{},[29,798,799],{},"Backup endpoint clause:"," platform provides a CIRPASS-2-compatible backup URL for each DPP",[26,802,803,806],{},[29,804,805],{},"SLA with teeth:"," uptime guarantee of at least 99.9% with financial remedy for breaches",[11,808,809],{},"If your current DPP provider cannot meet these terms, that is useful information to have before the 2027 deadline, not after.",[237,811],{},[11,813,814],{},[242,815,816,817,250,820,823],{},"PassportLab is EU-hosted (Elsdorf, Germany) with contractual data portability and CIRPASS-2 backup URL support built in. ",[246,818,819],{"href":248},"See how it works",[246,821,822],{"href":253},"book a call"," to discuss your specific hosting requirements.",{"title":257,"searchDepth":258,"depth":258,"links":825},[826,827,828,829],{"id":678,"depth":258,"text":679},{"id":702,"depth":258,"text":703},{"id":738,"depth":258,"text":739},{"id":770,"depth":258,"text":771},"2026-03-16","ESPR Article 9(2)(i) requires DPP data to remain accessible for 10 years after a product model is discontinued. What happens when your DPP provider shuts down or gets acquired?",{},"\u002Farticles\u002Fdpp-when-the-server-goes-down",8,{"title":663,"description":831},"articles\u002Fdpp-when-the-server-goes-down",[657,838,839,840],"Data Hosting","Reliability","EU Compliance","Td2sULQ72RFIK05Z28CFhdWrVN-64U_AOaiJd2xGh00",1781688237221]