The cost of implementing a Digital Product Passport – Key factors affecting the budget

For an off-the-shelf DPP platform, a monthly SaaS subscription may start at around €100-200, while the Digital Product Passport implementation cost may start at approximately €3,500-10,000 for a simpler scope. A project that also requires a new PIM system, complex integrations or environmental assessments may need a significantly larger budget.

The final cost is shaped by the scope of data that must be prepared and maintained for the Digital Product Passport (DPP), the number of products and variants, the required identification level, and the number of source systems. Fragmented product information increases the effort required for data cleansing, mapping, integration and ongoing updates.

PIM (Product Information Management) can act as the layer that collects and structures approved data from ERP, PLM, DAM, supplier systems and other sources before preparing it for publication in the DPP. A realistic DPP budget should therefore cover the complete data architecture, integrations and ongoing maintenance processes. 

This Digital Product Passport budget guide separates expenditure into two main categories:

• CAPEX covers the initial assessment, data preparation, PIM/DPP data model, integrations, APIs, new LCA or PCF work, testing, and any required labelling or packaging changes.
• OPEX covers SaaS platform subscriptions, hosting, API maintenance, technical support, monitoring, data updates, repeated environmental calculations, and regulatory change management.

The role of LCA in the budget depends on the environmental data the organization already has. With structured and verified data, integration, mapping and preparation for DPP publication may account for a greater share of the cost. Preparing LCA from scratch, calculating a carbon footprint or developing EPDs for multiple product families can significantly increase the project budget.

What affects the cost of implementing a DPP? PIM, scale, and key budget components

The digital product passport implementation cost depends on several groups of expenditure. The most important factors are the condition of the product data, the number of source systems, the complexity of the SKU portfolio, the environmental calculations required, and the level of automation applied to data integration and updating.

Number and complexity of SKUs – Why scale multiplies every cost

The cost impact of SKU volume depends on the complexity of the portfolio, the number of variants and the way product data is organized. Two companies with 10,000 SKUs may require very different budgets. One may have a standardized catalogue, a shared data model and attribute inheritance across product families. The other may manage multiple material variants, factories, suppliers, BOM versions and separate environmental results. One publicly available estimate suggests that collecting data may take around 15-20 minutes per product record when the source information is well structured, and 30-60 minutes when it is spread across spreadsheets, email messages and supplier documentation.

Tandemite’s project experience shows that product data complexity can have a greater impact on implementation effort than the SKU count itself. A portfolio of 100,000 simple products may be easier to manage than 1,000-1,500 highly configurable products with complex variants, multiple sources and extensive approval workflows.

Licensing and software: Off-the-shelf DPP platform or custom-built solution?

For micro and small businesses, an off-the-shelf SaaS platform is usually the most accessible starting point. Publicly available DPP price lists indicate that subscriptions can begin at several dozen euros or around €100-200 per month. Simpler implementations covering data assessment, configuration and integrations may start from a few thousand euros. The DPP software implementation cost for a custom-built solution also needs to cover development, data validation, versioning, registry integration, maintenance and adaptation to regulatory changes.

When comparing platforms, organizations should consider the subscription price together with understanding PIM licensing models before you commit. Licensing restrictions can increase the later cost of configuration, integrations or custom development.

A common mistake is selecting the cheapest or free version of a platform and later building functions that are included as standard in a more suitable licence.

“When making a build-versus-buy decision, the key factors are data complexity, the number of integrations, required workflows and the scope of custom functionality. These elements show the true cost of a solution over several years, so the decision should be based on full TCO: licences, configuration, development, integrations, maintenance and future growth.”  - Maciej Pałubicki, CEO Tandemite

It is also important to verify whether the less expensive platform option supports the required data model and processes. Savings on the licence can be consumed by the cost of implementing functions already available in a higher plan or a different solution.

System integration costs: PIM, ERP, and API

System integrations can become one of the largest cost items, particularly in organizations using multiple source systems. A target architecture may use ERP, PLM/BOM, supplier platforms, LCA software and DAM as data sources for PIM. PIM can then publish approved product information to the DPP service and send the required identifiers and metadata to the European Commission’s DPP registry through an API. When designing this flow, it is important to define the responsibilities of each platform and understand why an ERP can't replace a PIM system, especially when the same product information must also feed e-commerce, B2B portals and other channels.

The DPP registry launched by the European Commission on 20 July 2026 supports both a user interface and an API. At larger scale, automated registration and updating should form part of the target architecture.

Integration costs depend on the number of endpoints, data formats, synchronization frequency, error handling, queues, monitoring, identifier mapping, versioning, authentication and retry logic. The technical basis became more concrete in July 2026: EN 18216:2026 covers data exchange protocols, EN 18219:2026 covers unique identifiers, EN 18220:2026 covers data carriers, EN 18221:2026 covers data storage and persistence, EN 18222:2026 covers APIs, EN 18223:2026 covers system interoperability.

Product data preparation and environmental audits (LCA, carbon footprint)

The share of LCA in the budget depends on the environmental data already available and the number of analyses that must be prepared from scratch. Where the required information already exists in ERP, PIM, the bill of materials and supplier documentation, the main effort may concentrate on mapping, integration and preparing data for publication. Collecting primary supply chain data, performing a Product Life Cycle Assessment (LCA), calculating the Product Carbon Footprint (PCF) and obtaining external verification can increase costs quickly.

Publicly available data indicates that developing an Environmental Product Declaration can cost from a few thousand to over ten thousand euros per project, depending on product complexity and the scope of the assessment. Registration and annual publication fees may also apply. The total cost for a portfolio should be calculated based on the structure of product families and opportunities to use common LCA or EPD models.

Physical labeling: QR codes/RFID and packaging adjustments

The selection of the DPP data carrier should follow the applicable delegated act and the organization’s product identification architecture. Depending on the product group and solution, the carrier may use a QR code, DataMatrix, NFC or RFID.

The cost depends on the industry, current packaging processes, the use of GTIN, batch/lot and serial numbers, and whether the identifier is printed as part of the standard packaging process or applied dynamically during production. GS1 Digital Link may support the connection between GS1 identifiers and online product information. The required identifier and data carrier will ultimately depend on the applicable delegated act.

How a PIM system reduces the cost of DPP implementation

The strongest economic case for PIM appears when it acts as a Single Source of Truth for approved product information used by the DPP and other channels. Centralization becomes particularly valuable when you consider why fragmented product data drives up DPP costs through repeated mapping, validation and updating of the same information.

ERP, PLM and LCA tools remain source systems for their respective domains. PIM connects their data to the correct SKU, variant, batch or product version, structures it and prepares it for publication. A single controlled PIM-to-DPP integration can therefore publish data originating from multiple ERP systems, supplier platforms, DAM repositories and other sources. A controlled data flow can follow this architecture:

ERP + PLM/BOM + suppliers + LCA + DAM → PIM → DPP/API + e-commerce + B2B + ESG reporting

With thousands of SKUs, workflow automation becomes increasingly important. For example:

• a supplier or BOM version change can trigger a check to confirm whether the PCF is still valid,
• an expired certificate can block publication,
• a new LCA version can replace the current record without removing its history.

This model reduces manual data entry and the risk of repeating the same work across multiple channels. ESPR requires DPP data to be accurate, complete and up to date, while access to data updates must remain controlled.

The savings generated by PIM increase with the number of data sources, variants, languages, markets, approval processes and publication channels. If a company has 100 simple products, one market and well-structured data, implementing a complex PIM solely for DPP may not be economically justified.

Why the DPP budget matters: ESPR and the cost of non-compliance

To understand why the DPP budget matters, it is important to start with the regulatory framework. ESPR, the Ecodesign for Sustainable Products Regulation, establishes the framework that will be further specified for individual product groups through delegated acts.

The applicable delegated act will define, among other things, the data required for a given product group, the identification level – model, batch or individual item – the required DPP data carrier, which may, depending on the solution, be a QR code or RFID, as well as access rights, update rules and the required passport availability period. This means that the industry directly affects the implementation timeline and budget structure. The ESPR working plan 2025-2030 schedules the development of requirements for successive product groups, including iron and steel, aluminium, textiles, tyres, furniture, mattresses and ICT products.

The DPP compliance cost includes passport availability, product data quality, integration, versioning and ongoing maintenance. Article 9 of ESPR provides that once a product is covered by relevant DPP requirements, it can be placed on the EU market or put into service only when the required passport is available and its data is accurate, complete and up to date.

The economic consequences of an underfunded implementation may include additional IT work, delayed product launches, urgent supplier data collection, packaging redesign, repeated integration testing, and manual updates across thousands of records.

Since July 2026, DPP architecture has had a more concrete technical foundation. The DPP registry supports API access, while references to standards EN 18216-18223 provide a horizontal basis for identifiers, data exchange, API management, persistence and interoperability. Organizations can therefore invest part of their CAPEX in reusable architectural components while monitoring the delegated acts relevant to their industry.

How much does a DPP cost per year and per month? CAPEX vs. OPEX breakdown

For anyone asking how much a Digital Product Passport solution costs per year, the initial implementation and ongoing maintenance need to be calculated separately. CAPEX covers upfront implementation costs. OPEX covers expenditure incurred throughout the operational life of the DPP.

Micro and small businesses

Assuming up to approximately 1,000 SKUs, one main data source, an off-the-shelf SaaS platform and a limited integration scope, a model budget may include €3,500-15,000 in CAPEX and €100-700 in monthly OPEX – approximately €1,500-8,500 as the annual DPP cost. Publicly available DPP price lists suggest that subscriptions for off-the-shelf platforms may start at several dozen euros or around €100-200 per month. Simpler implementations covering assessment, configuration and integration may start at a few thousand euros. New LCA, PCF or EPD work should be budgeted separately.

Medium-sized businesses

A medium-sized business managing approximately 1,000-20,000 SKUs, PIM and ERP, several supplier data sources, automated workflows and two to five significant integrations may use the following model planning range: €25,000-120,000 in CAPEX and €700-3,500 in monthly OPEX – approximately €8,500-42,000 as the annual DPP cost (these figures exclude major recurring LCA projects, which should be budgeted separately where required). This is a model estimate derived from publicly available costs for PIM, DPP, integrations and software. It is not an official market average. Public descriptions of PIM implementations indicate that budgets can range from around €10,000 to well over €100,000, depending on project scope.

Large enterprises

Large enterprises managing 20,000-100,000+ SKUs across multiple markets and several ERP/PLM environments, PIM, DAM and LCA tools may require a significantly larger budget. A model scenario may include €120,000-500,000 or more in CAPEX and €3,500-20,000 in monthly OPEX. The total monthly cost may be higher where the organization regularly renews environmental assessments for many product families. These figures are planning scenarios rather than market benchmarks.

The question “how much?” should therefore be assessed through a complete model covering: CAPEX + OPEX + internal labour + variable environmental data costs.

Hidden costs of Digital Product Passport implementation you shouldn't overlook

The most significant hidden costs often appear outside the software invoice. They may include the time of the Product Owner and internal product experts, collecting and reconciling supplier data, cleaning legacy records, mapping units, classifications and identifiers, translations and localization, user acceptance testing, corrections after testing, employee training, cybersecurity, API monitoring, certificate updates, repeated LCA calculations after BOM changes, versioning of historical DPP records, packaging design and printing-process changes.

How to calculate and plan your DPP implementation budget step by step

Step 1: Audit your existing product data

Map your SKUs and product families, BOMs, suppliers, certificates, PIM, ERP, PLM and DAM systems, LCA sources, and existing APIs. For each required field, record the source system, data owner, completeness, format and update frequency. This audit shows what to calculate in the budget and which capabilities already exist.

Step 2: Add up your upfront costs (CAPEX)

CAPEX should include pre-implementation analysis, regulatory requirements analysis, data-model design, PIM/DPP configuration, migration and data cleansing, integrations, LCA/PCF work, identifiers and data carriers, packaging changes, testing, and training.

Step 3: Add up your ongoing costs (OPEX)

The OPEX model should cover 12 months of licensing or SaaS platform fees, hosting, API maintenance, integration monitoring, SLA and technical support, product data updates, onboarding of new SKUs, repeated environmental calculations, certificate and EPD renewals. Maintenance is a continuing component of EU compliance because DPP data must remain current throughout the required availability period.

Step 4: Add a 15–20% budget reserve

A 15-20% reserve is a project-planning recommendation, not an ESPR requirement. The reserve can cover unexpected data gaps, additional mappings, API changes, regression testing, and requirements discovered during the pilot.

Practical formula:

First-year budget = CAPEX + 12 × monthly OPEX + variable LCA/EPD costs + 15-20% reserve

Sample DPP implementation budget structure

The table below summarizes the main cost components (budget structure) for three implementation scenarios. All figures are net model estimates for planning purposes. They are not a Tandemite price list or an official market average. In this table, “medium-sized business” refers to the scale of the DPP project, assessed through SKU volume, integrations and data complexity, rather than the formal EU definition of an SME.

* LCA, PCF or EPD work may add little to the DPP project budget where the organization already has current, usable and verified results. It can become one of the largest cost items when environmental assessments must be prepared from scratch for many product families. Publicly available data indicates that environmental documentation such as LCA, PCF and EPD may represent a significant share of the budget. Off-the-shelf DPP platforms may start from a few dozen euros or around €100-200 per month, while simpler implementation services may start from a few thousand euros. PIM projects can range from around €10,000 to well over €100,000, depending on scope and complexity. The upper ranges in the table are architectural estimates for large organizations rather than prices published by one provider.

A representative product family with a well-understood BOM, available supplier data and at least some existing environmental information is usually the strongest pilot candidate. The pilot should test the full flow: source systems → LCA/PCF → PIM → validation → DPP → registry/API → data carrier. In a medium-sized or large organization, preparing PIM, the data architecture and integrations may take several months. The pilot plan should therefore include time for data assessment, modeling, integration, testing and preparation for scaling.

Why partnering with an implementation partner like Tandemite can be cheaper than going it alone

An implementation partner can reduce the total project cost by limiting the scope of corrections and architecture redesign later in the programme. The most expensive changes often result from decisions made before development begins, including: an unsuitable product data model, unclear data ownership, unnecessary point-to-point integrations, and unsuitable technology choices.

A practical example is selecting a platform version based only on the licence price. A lower-cost option may lack functions required for workflows, integrations or product data modeling. Building these functions later through custom development can consume the original licence saving. This is why solutions should be compared through multi-year TCO covering licences, configuration, development, integrations, maintenance and future growth.

It is also worth reviewing common PIM implementation pitfalls that can blow your budget before platform or architecture limitations begin generating additional work.

An experienced partner can help determine which data should come from ERP, PIM, PLM, DAM and LCA systems, and which information should be maintained in the DPP publication layer. Identifying these responsibilities early reduces the risk of rebuilding integrations, mappings and processes.

Therefore, before development begins, it is worth clearly defining the role of the technology partner in a PIM project: the organization is responsible, among other things, for data owners and source systems, while the implementation partner is responsible for the data model, architecture, configuration, APIs, workflows and automation. 

For a larger product data ecosystem, review the 8 factors to consider when hiring a PIM development company, including experience in ERP integration, product data modeling and multi-system environments.