PPWR Software Compared 2026: Specialist Tool, Suite or Connected System Landscape?

Transparency up front

This comparison was produced by Central Agency for Green Commerce GmbH, the provider of SUSYCHECK. Statements about the other providers are based on publicly accessible information. The presentation of SUSYCHECK additionally draws on our internal product knowledge. The information base is therefore not fully symmetrical.

For that reason we mark capabilities that cannot be clearly substantiated publicly as such, disclose the selection criteria we used, and do not establish a ranking. The article is meant to help companies understand the types of solutions and the typical trade-offs. It replaces neither your own provider assessment nor a demonstration based on real use cases.

The real decision: specialist or suite?

PPWR software cannot sensibly be compared on capability lists alone. Many systems promise data management, supplier communication and document generation. What matters, however, is how deeply those functions are worked out for the actual PPWR process and how easily they can be used day to day.

A specialised system is built for a clearly defined use case. Data model, input forms, validation logic, roles and output documents all follow that process. This reduces configuration effort and makes the system easier to use for both internal users and suppliers. A broad compliance, ESG or product lifecycle suite, by contrast, can cover several topics and regulations in one shared environment. Its advantage lies in consolidation and reuse; in a specialised case, however, this can mean more configuration, more complex user journeys or functional compromises.

On top of that comes the reach of the data model. Some platforms manage not only packaging data but also product, supply chain, CO₂, quality, production or distribution information. That can be highly valuable across the enterprise. For a PPWR project, though, it often means that more data owners, departments and governance rules have to be involved before the process runs stably.

Why the future is connected rather than monolithic

With every new regulatory requirement, the desire for one central solution grows. At the same time, the professional differences between packaging compliance, EPR, recyclability assessment, carbon accounting, the Digital Product Passport and general product conformity keep increasing. A platform that covers everything must either be configured very broadly or will hit limits in individual specialised processes.

Our thesis is therefore: the future lies in a connected best-of-breed architecture. ERP, PIM or PLM remain the leading systems for master data. Specialised applications handle their respective domain logic and exchange results automatically via APIs. Integration is no longer an argument against specialisation – it is the precondition for using specialist depth without creating new data silos.

The data model determines the project scope

A packaging-specific data model concentrates on packaging systems, components, materials, weights, suppliers, evidence and PPWR assessments. This allows a company to start with the directly responsible areas and connect further systems step by step.

A cross-domain data model, by contrast, links packaging to products, supply chains, CO₂ data, quality information or operational processes. The supposed advantage of a shared data foundation is real. At the same time, the implementation scope grows: data ownership and definitions must be agreed across several departments, interfaces prioritised and permissions governed more comprehensively.

Large data models are not automatically inflexible. The more domains, dependencies and user groups they represent, however, the more likely longer alignment and change cycles become. Modular suites can reduce this drawback if the PPWR module is introduced on its own. The question should therefore not only be what data a platform can store in principle, but which data and departments are genuinely required for the specific PPWR start.

The Declaration of Conformity is only the result

An EU Declaration of Conformity can be produced as a PDF quickly. That does not yet establish whether the underlying packaging data is complete and current, who supplied and confirmed it, what evidence exists, which criteria were applied and who is accountable for the declaration.

That is precisely where the operational challenge of the Packaging and Packaging Waste Regulation (PPWR) lies: companies do not need another isolated document generator, but a robust evidence and process chain spanning packaging systems, components, suppliers and internal approvals.

The PPWR has been in force since 11 February 2025 and has generally applied EU-wide since 12 August 2026. Before placing packaging on the market, manufacturers must assess its conformity, draw up the technical documentation in accordance with Annex VII and issue the EU Declaration of Conformity in accordance with Article 39 and Annex VIII. Which obligations apply in a specific case depends on the role and the supply constellation.

Legal basis: Regulation (EU) 2025/40 and the European Commission overview.

Four levels of a robust PPWR solution

1. Organisation and workflow

Roles, responsibilities, processing steps, reviews and approvals are predefined. This turns PPWR compliance from an individual Excel task into a reproducible company process.

2. Data and evidence chain

Packaging is built up from components. Master data, material information, weights, supplier declarations, specifications and test reports must be linked in a structured way, versioned and attributed to their source.

3. Assessment and required action

The data is assessed against the applicable criteria. Missing information or evidence must surface as gaps and trigger follow-up actions, rather than silently counting as fulfilled.

4. Communicating conformity

From the assessed data, the role-appropriate outputs are produced: the EU Declaration of Conformity, the technical documentation and – in OEM, private-label and supplier constellations – a customer data sheet.

What “automated data flow” really means

A form or supplier questionnaire initially digitises only the data entry. A genuinely end-to-end data flow goes further: data is taken over from internal systems via API or CSV, suppliers enter missing information directly and reusably, components are assigned to packaging systems, criteria are checked rule-based, and the required documents are generated from that same data foundation.

Even a largely automated process stays controlled: suppliers are accountable for their information; the obligated economic operator reviews, approves and signs. Software structures and assesses – it takes over neither certification nor the legal responsibility of the declaring party.

Six clearly distinguishable solution categories

The providers start from different professional worlds. The primary assignment below deliberately simplifies; individual solutions may include capabilities from adjacent categories.

10 providers at a glance

This overview is not a ranking. It shows which functional focus each provider approaches PPWR from, and which typical trade-off follows from it.

Process matrix: how far does the data flow reach?

The matrix describes publicly identifiable capabilities as of the review date. “Not clearly stated” does not mean “not available”; it only means that the capability was not substantiated concretely enough on the pages reviewed.

The providers individually

SUSYCHECK – specialised PPWR compliance

SUSYCHECK is the specialised PPWR compliance and packaging management system from Central Agency for Green Commerce GmbH. It covers not only document output but the full operational process: roles, packaging systems, components, suppliers, evidence, assessment, approval and communication.

Data can be taken over via API or CSV from ERP, PIM and other internal structures. Suppliers can be invited specifically and provide missing information and documents themselves in a guided portal. Components and evidence maintained once can be reused across several packaging systems. On that structured basis, SUSYCHECK assesses the applicable criteria rule-based and surfaces gaps and required actions.

From the approved data, the EU Declaration of Conformity, the technical documentation and the customer data sheet are generated automatically. Especially for third-party brand manufacturers, OEMs and suppliers, the customer data sheet closes the communication gap towards the European brand owner or retail partner. As soon as additional PPWR requirements are specified by robust legal provisions, data fields, criteria and documentation logic are extended along the PPWR roadmap.

The advantage of specialisation lies in the preconfigured process guidance and the continuity of the data flow. SUSYCHECK does not, however, replace EPR systems, laboratory testing or leading master data systems. Those functions are brought in via partners or interfaces where required.

Source: SUSYCHECK – provider information

Recyda – recyclability and EPR

Recyda positions itself as a platform for packaging data, international recyclability assessment, EPR and PPWR preparation. Publicly described are structured data workflows, automatic assessments against national and international standards, and EPR fee calculations.

The advantage lies in connecting packaging sustainability, recyclability and cross-country EPR compliance. DoCs and technical documentation are also mentioned. Companies should check in their own use case how far the solution covers the PPWR-specific accountability, approval and communication process.

Source: Recyda – provider information

Packa – packaging documentation

Packa bundles specifications, packaging data, supplier documents, procurement, recyclability, EPR fees and CO₂ information. Technical data can be taken over from various file formats and ERP exports, and extracted from documents with AI support.

Its strength lies in broad operational packaging documentation and in connecting procurement, engineering, suppliers and sustainability. Anyone primarily looking for a preconfigured PPWR compliance process should examine assessment logic, approvals and role-appropriate documents using a real packaging system.

Source: Packa – provider information

Narravero – multi-regulation and DPP

Narravero connects PPWR documentation with the perspective of the Digital Product Passport. Packaging data, the Declaration of Conformity, evidence and change states are maintained in a digital packaging file.

Narravero explicitly states that product and packaging data sit in the same data model. That creates synergies for PPWR and DPP, but potentially extends the implementation scope to product data owners. Further advantages cited are technical documentation, version control and REST and SAP connections. What should be examined is how deeply the supplier process and rule-based PPWR assessment are preconfigured for the specific use case.

Source: Narravero – provider information

CONSUST – multi-regulation and ESG

With its PPWR module, CONSUST starts with determining roles and obligations. A decision tree classifies the role as manufacturer, producer, importer or distributor and derives the resulting tasks. Also cited are supplier questionnaires, AI-supported document processing, technical documentation and multilingual Declarations of Conformity.

Embedding in a broader ESG and compliance environment can bundle CSRD, CO₂, supply chain, risk and PPWR requirements, among others. According to the provider, the PPWR module can also be used on its own, which means the entire data landscape does not automatically have to be introduced. Compared with a specialist tool, it is worth checking whether questionnaires and document processing carry through into an end-to-end, reusable data flow all the way to assessment and approval.

Source: CONSUST – provider information

osapiens – cross-cutting product compliance

osapiens positions PPWR within a comprehensive product compliance platform. Rule sets together with product, component, supplier and evidence data are connected in shared processes. The Supplier Portal supports requests, reminders and missing evidence.

The publicly presented platform portfolio extends further, from supplier intelligence, carbon management and reporting through to audit, quality, distribution, and maintenance and repair. Its strength lies in governance and data reuse across numerous functions. At the same time, this is the broadest data and organisational model in this comparison. Companies should examine which departments are genuinely required for a PPWR start, and what configuration effort packaging-specific structures, assessment logic and output documents require.

Source: osapiens – provider information

Tanso – PPWR within an ESG suite

Tanso offers a PPWR module within its sustainability and supply chain platform. Cited are central packaging data management, ERP import, a supplier portal, automated reminders and checking against PPWR requirements.

Alongside PPWR, Tanso offers modules for corporate and product carbon footprint, CSRD, VSME and CBAM. DoCs in accordance with Annex VIII, technical documentation, versioning and an audit trail are part of the public PPWR capability description. The modular suite approach is attractive if these data worlds are to be connected. For a focused start, it should be clarified which additional data and departments the PPWR module actually presupposes.

Source: Tanso – provider information

Simvia – industry-specific compliance

Simvia pursues an industry-specific approach for food and beverage. PPWR is connected with product compliance, supply chain, specifications, laboratory analyses and ERP integrations.

The data model thereby connects several functional dimensions of the food & beverage value chain. For companies in that industry this can be a clear advantage, but it may require the involvement of several specialist functions. Outside the target industry, an industry-agnostic PPWR or product compliance solution may be a better fit.

Source: Simvia – provider information

Interzero – tool, consulting and testing

Interzero combines digital tools with consulting and circular economy expertise. Check for Recycling supports the assessment of packaging, the classification of recyclability and the creation of technical evidence. Laboratory services such as NIR analyses are offered in addition.

The combined approach is strong where external technical expertise is needed. For cost and process comparison, it should be clearly separated which steps are delivered as a scalable software workflow and which as a consulting or laboratory service.

Source: Interzero – provider information

Landbell / SimpliDoC – tool and consulting

Landbell comes from EPR compliance and combines PPWR workshops, consulting and digital tools. SimpliDoC guides users through creating Declarations of Conformity, supports evidence collection and manages DoCs as well as technical documentation.

The advantage lies in connecting document creation, EPR expertise and consulting. Companies with complex packaging structures should examine how far reusable components, supplier data, rule-based assessment and automated data flows go beyond DoC creation.

Source: Landbell / SimpliDoC – provider information

Where SUSYCHECK differentiates functionally

SUSYCHECK is not different because the platform likewise offers a portal or a Declaration of Conformity. The difference lies in linking the process steps end to end:

• COMPLY: assess PPWR criteria rule-based, surface data and evidence gaps, and document the status per packaging.
• MANAGE: organise packaging systems, reusable components, suppliers, responsibilities, evidence and approvals in a predefined workflow.
• COMMUNICATE: generate the EU Declaration of Conformity, the technical documentation and the customer data sheet automatically from the same approved data foundation.

With internal systems connected and suppliers actively involved, this produces a largely automated data flow from source to output document. Manual review and approval decisions are deliberately retained. This combination of specialisation, user guidance, assessment and communication is the core value of SUSYCHECK.

Ten selection criteria that actually decide

1. Architecture decision. Should PPWR be operated as a specialised process or integrated as a module into a suite? Alongside functional breadth and user guidance, assess which data models, data owners and departments must necessarily be involved for a productive start.
2. Process instead of PDF. Does the system steer roles, data requirements, approvals, changes and open items – or does it essentially produce a document from the answers entered?
3. Packaging systems and components. Can packaging be built from several components and supply configurations? Can identical components and evidence be reused across products?
4. Supplier integration. Can suppliers be invited specifically, provide data and evidence directly, confirm their information and use the same components for several customers or systems?
5. Rule-based assessment. Which criteria are actually assessed automatically? How do gaps appear, and how does the system distinguish between not applicable, not available and not evidenced?
6. Evidence and change chain. Is it traceable which data and records a result came from, who supplied or approved them, and which version applied at which point in time?
7. Role-appropriate communication. Alongside the DoC and technical documentation, are customer data sheets produced for OEM, private-label and supplier constellations?
8. PPWR roadmap. How does the provider translate new, legally robust requirements on recyclability, recycled content, labelling, minimisation or reuse into data fields, rules and documents?
9. Integration and automation. Can ERP, PIM, PLM and further specialist applications be connected via API? Examine the real data flow – not merely the existence of an interface on a data sheet.
10. Total effort. Compare licence, implementation, data migration, supplier activation, interfaces and ongoing internal effort. A broad system is not automatically more economical; a specialist tool is not automatically easier to integrate.

What public provider information often leaves open

From input to output

A supplier portal, a questionnaire and an API say little about whether data flows through to assessment and document generation without a break. Ask for a complete case to be demonstrated: internal import, supplier response, component usage, gap check, approval and updated documents.

Implementation and operating effort

It is rarely explained publicly who structures Excel, ERP or specification data, how components are mapped, and when the first robust assessments are available. A pilot with representative packaging systems and real suppliers is more informative than a standard demo.

Software, consulting, testing and responsibility

Data structuring, rule-based assessment, legal advice, laboratory testing and certification are different services. Companies should delineate service and liability cleanly. Legal responsibility for the Declaration of Conformity remains with the obligated economic operator in each case.

Price and total cost of ownership

On top of licence costs there may be implementation, configuration, migration, interfaces, consulting, internal maintenance effort and ongoing additional costs. What matters is not the price per document, but the effort required for a durably robust evidence chain across the entire portfolio.

Frequently asked questions

Is a specialist tool inherently better than a suite?

No. A specialist tool typically offers more depth, faster usability and clearer user guidance within the defined process. A suite can bundle governance, data reuse and several regulations. What decides it is your target picture, your existing system landscape and real use cases.

Does a specialist tool create another data silo?

Not necessarily. With API connections, the specialist system can take over master data from ERP or PIM and return status and documents. Specialisation and integration are not opposites.

Can PPWR software certify packaging?

No. Software can collect data, apply rules, surface gaps and generate documents. External testing or certification remain separate services; the obligated economic operator is accountable for the declaration.

Why should suppliers enter data themselves?

Much technical information and evidence originates with the supplier. Direct entry and confirmation create a traceable source, reduce transfer errors and support the evidence chain. The inviting company remains responsible for its own review.

What does “growing with the PPWR roadmap” mean?

Further requirements are being specified through delegated or implementing acts. A future-proof system extends the corresponding data requirements, assessment criteria and documentation logic as soon as robust legal provisions exist.

Is a DoC solution enough?

With a small, stable portfolio, guided document creation may suffice. With more components, suppliers, changes and customer requests, the upstream data, assessment and approval process becomes the decisive factor.

Conclusion: specialisation is not the opposite of integration

The PPWR turns packaging compliance into a continuous organisational task. A good solution has to obtain data and evidence along the supply chain, assess packaging, steer responsibilities and changes traceably, and communicate the results to customers and authorities.

Broad suites can bundle several requirements in one platform. Specialised systems can cover a specific process more deeply, more quickly and more usably. The most viable architecture probably combines both: leading enterprise systems, specialised domain applications and automated interfaces.