--- title: How does EU-DPP information remain available after a Product is discontinued? description: Learn how SyncForce, prodigi.link and Perennis keep EU-DPP information accessible beyond the commercial lifecycle of a Product, even after websites, Sales Units or systems change. --- [Skip to content](https://support.syncforce.com/knowledge/how-does-eu-dpp-information-remain-available-after-a-product-is-discontinued#main-content) [![Syncforce\_logo\_tagline](https://support.syncforce.com/hs-fs/hubfs/Syncforce_logo_tagline.webp?width=480&height=72&name=Syncforce_logo_tagline.webp)](https://www.syncforce.com/) Open main navigation Close main navigation Hello. How can we help you? - There are no suggestions because the search field is empty. 1. [Home](https://support.syncforce.com/knowledge?hsLang=en) 2. [Industry & Regulatory Knowledge](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en) 3. [EU Digital Product Passport - DPP](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#eu-digital-product-passport-dpp) # How does EU-DPP information remain available after a Product is discontinued? #### Short answer The regulatory lifetime of Product information can be much longer than the commercial lifetime of the Sales Unit. A Product may remain in use after: - the Sales Unit has been discontinued - the e-commerce page has disappeared - the manufacturer's website has changed - the active PIM system has been replaced - the original marketing campaign has ended SyncForce therefore separates three responsibilities: **SyncForce Circular PIM** creates and governs Product and compliance information ↓ **prodigi.link** maintains persistent identity and resolution ↓ **Perennis** publishes and preserves regulated EU-DPP information for the required period This allows the Product identifier to remain persistent even when the systems and webpages behind it change. --- #### Why can the EU-DPP outlive the Sales Unit? A Sales Unit has a commercial lifecycle. It is introduced, sold in one or more markets and eventually discontinued. The physical Product can have a very different lifecycle. Examples include: - laptop - battery - appliance - power tool - electronic equipment These Products may remain in use for many years after the original Sales Unit is no longer sold. Consumers, repairers, recyclers and authorities may still need access to regulated information during that period. The EU-DPP therefore cannot depend solely on the continued existence of the original commercial Product page. --- #### Why is a normal Product webpage not enough? A conventional Product webpage usually exists for commercial reasons. It may disappear when: - the Product is discontinued - the website is redesigned - the brand changes CMS - the company moves to another e-commerce platform - URLs are restructured - a campaign ends That lifecycle is not suitable as the only mechanism for long-term regulatory access. For EU-DPP, SyncForce therefore separates: **persistent Product identity** from: **the digital resource currently serving the Product information** The identity can remain unchanged while the destination changes. --- #### What role does SyncForce Circular PIM have? SyncForce Circular PIM is the operational system where the Product and compliance information is created and governed. This can include: - Product Model information - specifications - composition - regulatory information - Economic Operators - Facilities - technical documentation - evidence - approvals - audit history - EU-DPP data During the active lifecycle, SyncForce manages the information from which the EU-DPP is created. SyncForce is therefore primarily the **information management and governance layer**. --- #### What role does prodigi.link have? prodigi.link provides persistent identity and resolution. For example, a Product Model may have: `https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM` That identifier can remain unchanged throughout the Product lifecycle. Initially it may resolve to an active EU-DPP publication. Later it may resolve to a preserved copy of the same EU-DPP. Conceptually: **Product Model identifier** ↓ **prodigi.link** ↓ current EU-DPP resource and later: **same Product Model identifier** ↓ **prodigi.link** ↓ long-term EU-DPP resource The identifier does not need to change when the hosting destination changes. **Read more:** [*How does prodigi.link support EU-DPP identification and resolution?*](https://support.syncforce.com/knowledge/how-does-prodigi.link-support-eu-dpp-identification-and-resolution?hsLang=en) --- #### What role does Perennis have? Perennis provides the long-term regulatory publication and persistence layer. Its purpose is different from a PIM or commercial website. Perennis is designed to keep regulated Product information available after the active commercial lifecycle has ended. This means that a Product can remain digitally accessible even if: - it is no longer sold - its Sales Unit is inactive - its Marketing Landing Page has been removed - the manufacturer's main systems have changed Perennis therefore addresses the **regulatory information lifecycle**, not just the commercial Product lifecycle. --- #### Why separate Perennis from SyncForce? The separation creates a cleaner continuity model. SyncForce is an operational business system. It changes as manufacturers: - introduce Products - update data - change Packaging - manage markets - maintain compliance - discontinue Sales Units Long-term regulatory preservation has a different objective. It should remain available even if the active operational environment changes. The architecture therefore separates: **operational information management** from: **long-term regulatory publication and preservation** --- #### What happens when a Product is discontinued? Discontinuing the commercial Product does not automatically mean deleting its EU-DPP. A simplified lifecycle can look like this: Active Product **SyncForce** Product and compliance data actively maintained ↓ **Perennis** current EU-DPP published ↓ **prodigi.link** resolves the persistent Product identifier to that EU-DPP Discontinued Product The Sales Unit is no longer actively marketed. The Product identifier remains unchanged. ↓ **Perennis** continues to make the required regulatory information available ↓ **prodigi.link** continues resolving the same Product identifier The commercial lifecycle ends. The regulatory information lifecycle continues where required. --- #### What happens if the manufacturer's website disappears? The EU-DPP should not depend on the manufacturer's current corporate website URL. For example, this would create unnecessary dependency: `manufacturer.com/products/old-product/passport` If that website disappears or is rebuilt, the link may fail. With the SyncForce architecture, the physical Product carries a persistent identity such as: `https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM` prodigi.link can continue resolving that identity independently from the manufacturer's current website structure. --- #### What happens if the manufacturer changes PIM? The same principle applies. The Product identity should not depend on which PIM system happens to be active today. A company might use SyncForce during the original Product lifecycle and later change systems. The persistent Product identifier can remain the same. The preserved EU-DPP can remain available through Perennis. This reduces dependency between: **Product lifetime** and: **software platform lifetime** --- #### Does the Product identifier change when the EU-DPP moves? No. This is one of the core architectural principles. The identifier identifies the Product. It does not identify one particular server, database or webpage. For example: `?.25P=VTA-MPLA-PM-346UJI3NUM` continues to identify the same Product Model regardless of which compliant digital resource currently provides the EU-DPP. The resolver determines the appropriate resource. --- #### Does the EU-DPP ID change? The EU-DPP itself also has its own persistent identifier. SyncForce uses a UUID for the EU-DPP ID. For example: `urn:uuid:3f2b8c1e-6a4d-4e2b-9c7a-1d5e8f0a2b34` This is separate from the Product identifier. The EU-DPP ID remains associated with that passport while the passport may have multiple versions over time. **Read more:** [*Which identifiers are used in an EU-DPP?*](https://support.syncforce.com/knowledge/which-identifiers-are-used-in-an-eu-dpp?hsLang=en) --- #### What happens when the EU-DPP is updated? An EU-DPP is not necessarily static. Information may change because of: - corrections - new regulatory information - updated technical documentation - new evidence - lifecycle events The passport can therefore have multiple versions. Conceptually: **EU-DPP ID** ↓ Version 1 ↓ Version 2 ↓ Version 3 The passport identity remains stable while its content evolves. Long-term preservation needs to consider both the current version and the required historical information. --- #### What are the main and back-up DPP service providers? The EU-DPP architecture also distinguishes between the main DPP service provider and the back-up DPP service provider. In the SyncForce architecture: **Perennis** is the main DPP service provider and: **SyncForce** acts as the back-up DPP service provider. The purpose is to avoid making the regulated Product information dependent on one publication environment. --- #### What does the back-up provider preserve? The back-up arrangement is intended to support continuity of the EU-DPP. This includes preserving the required EU-DPP information independently from the main publication provider. The architecture must therefore avoid a situation where both the primary and back-up copy depend on exactly the same infrastructure or continuity mechanism. The objective is genuine regulatory continuity rather than merely another URL pointing to the same underlying system. --- #### What happens if the Economic Operator is no longer active? This is one of the scenarios long-term persistence needs to address. The physical Product may continue to exist even if the Economic Operator: - stops selling the Product - exits a market - restructures - becomes inactive The EU-DPP architecture therefore needs to preserve access to required Product information independently from the ongoing commercial activity of the original Economic Operator. The persistent Product identity remains the entry point. prodigi.link can continue directing users and systems to the appropriate preserved resource. --- #### How does EN 18221 relate to this? EN 18221 addresses data storage, archiving and persistence within the European EU-DPP infrastructure. It is therefore particularly relevant to the role played by Perennis and the back-up provider. The broader EU-DPP standards architecture separates: - identification - data carriers - exchange - APIs - interoperability - access control - integrity - long-term persistence Long-term persistence is therefore not an optional website feature. It is a distinct architectural concern. **Read more:** [*Which European standards define the EU-DPP architecture?*](https://support.syncforce.com/knowledge/which-european-standards-define-the-eu-dpp-architecture?hsLang=en) --- #### Does Perennis replace prodigi.link? No. They perform different functions. prodigi.link Answers: **Where can I find the current resources associated with this persistent identity?** Perennis Answers: **How do we keep the regulated information available for the required period?** The architecture therefore remains: **persistent Product identity** ↓ **prodigi.link** ↓ **Perennis or another appropriate current resource** --- #### Does Perennis replace SyncForce Circular PIM? No. Again, the roles are different. SyncForce Circular PIM Manages and governs: - Product information - Packaging information - regulatory data - evidence - workflows - approvals - lifecycle relationships Perennis Publishes and preserves: - regulated EU-DPP information - required historical information - long-term accessible regulatory resources SyncForce manages the operational truth. Perennis provides the long-term regulatory publication layer. --- #### How does this fit into the SyncForce Golden Hierarchy? The SyncForce Golden Hierarchy separates both **business objects** and **lifecycles**. For example: **Product Model** has its own Product lifecycle **Sales Unit** has its own commercial lifecycle **Packaging System** has its own compliance lifecycle **EU-DPP** has its own regulatory information lifecycle These lifecycles overlap, but they are not identical. That is why the architecture does not make long-term EU-DPP availability dependent on the continued existence of the Sales Unit or commercial webpage. --- #### What is the complete lifecycle architecture? The simplest representation is: **SyncForce Circular PIM** creates and governs Product and compliance information ↓ **prodigi.link** provides persistent identity and resolution ↓ **Perennis** publishes and preserves EU-DPP information for the required period This division allows each component to solve a different problem. **SyncForce:** What is the Product and what information applies to it? **prodigi.link:** What persistent identity is being requested and where should it resolve? **Perennis:** How does the regulated information remain available beyond the active commercial lifecycle? --- #### Why does this matter for manufacturers? Without this separation, long-lived Products can become dependent on short-lived digital infrastructure. A manufacturer could otherwise face situations where: - QR codes on Products no longer work - discontinued Product pages disappear - migrations break old links - regulatory information is lost with a legacy system - consumers and authorities cannot reach required information Persistent identification combined with independent regulatory preservation reduces that risk. **See the full overview:** [*How does SyncForce support the EU Digital Product Passport, EU-DPP?*](https://support.syncforce.com/knowledge/how-does-syncforce-support-the-eu-digital-product-passport?hsLang=en) #### In one sentence **SyncForce governs the Product information, prodigi.link keeps the Product identity persistently resolvable, and Perennis keeps the regulated EU-DPP information available beyond the commercial lifecycle of the Product.** ### Links you can activate now This is **Article 8 of 8**, so the original EU-DPP knowledge cluster is now complete. You can now activate the previously mentioned link **“How does EU-DPP information remain available after a Product is discontinued?”** on: - **How does SyncForce support the EU Digital Product Passport, EU-DPP?** - **Which European standards define the EU-DPP architecture?** - **How does prodigi.link support EU-DPP identification and resolution?**, especially in its Perennis section. On this new page, you can already activate links to: - *How does prodigi.link support EU-DPP identification and resolution?* - *Which identifiers are used in an EU-DPP?* - *Which European standards define the EU-DPP architecture?* - the main EU-DPP pillar page. ### Your complete 8-article cluster 1. **How does SyncForce support the EU Digital Product Passport, EU-DPP?** 2. **Why is a GTIN not necessarily the Product Model identifier for an EU-DPP?** 3. **How are Product Model, Batch and Serialized Item identified for an EU-DPP?** 4. **How does prodigi.link support EU-DPP identification and resolution?** 5. **How are the Economic Operator and Facility identified in an EU-DPP?** 6. **Which identifiers are used in an EU-DPP?** 7. **Which European standards define the EU-DPP architecture?** 8. **How does EU-DPP information remain available after a Product is discontinued?** - [Industry & Regulatory Knowledge](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#main-content) - [Product Portfolio](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#product-portfolio) - [Packaging & PPWR](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#packaging-ppwr) - [EU Digital Product Passport - DPP](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#eu-digital-product-passport-dpp) - [GS1 & GDSN](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#gs1-gdsn) - [Food & Label Information](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#food-label-information) - [EPR & Sustainability Data](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#epr-sustainability-data) - [Product Identification & GTIN](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#product-identification-gtin) - [PIM & Data Architecture](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#pim-data-architecture) - [Product Data Management](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#main-content) - [Packaging Data Management](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#packaging-data-management) - [Product data imports](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#product-data-imports) - [PDM setup and config](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#pdm-setup-and-config) - [Digital Asset Management](https://support.syncforce.com/knowledge/digital-asset-management?hsLang=en#main-content) - [FileConvert](https://support.syncforce.com/knowledge/digital-asset-management?hsLang=en#fileconvert) - [Project Portfolio Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#main-content) - [Team & Planning](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#team-planning) - [Proofing & Approval](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#proofing-approval) - [Budget & Spend Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#budget-spend-management) - [Resource Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#resource-management) - [To Do (task & actions)](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#to-do-task-actions) - [Project definition](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#project-definition) - [Product Catalog](https://support.syncforce.com/knowledge/product-catalog?hsLang=en) - [Media Library](https://support.syncforce.com/knowledge/media-library?hsLang=en) - [Product Data Syndication](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#main-content) - [GS1-GDSN](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#gs1-gdsn) - [DataPorts](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#dataports) - [PS in Foodservice](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#ps-in-foodservice) - [REST API](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#rest-api) - [Document Automation](https://support.syncforce.com/knowledge/document-automation?hsLang=en) - [Exports & reports](https://support.syncforce.com/knowledge/exports-reports?hsLang=en) - [Business Network Management](https://support.syncforce.com/knowledge/business-network-management?hsLang=en#main-content) - [Single Sign-On](https://support.syncforce.com/knowledge/business-network-management?hsLang=en#single-sign-on) - [Services & Support](https://support.syncforce.com/knowledge/services-support?hsLang=en) - [Partner Support](https://support.syncforce.com/knowledge/partner-support?hsLang=en) - [General setup](https://support.syncforce.com/knowledge/general-setup?hsLang=en) - [Campaign management](https://support.syncforce.com/knowledge/campaign-management?hsLang=en) - [General](https://support.syncforce.com/knowledge/general?hsLang=en) [![Chill listening crop-3](https://support.syncforce.com/hs-fs/hubfs/SyncForce_plus_1024-2.png?width=105&height=24&name=SyncForce_plus_1024-2.png "Chill listening crop-3")](https://www.syncforce.com/) Copyright © 2026, SyncForce