Choosing PPWR Software Means Choosing Processes

A form is not yet an understood process

Data fields can be derived from a legal text. That alone does not produce a working packaging organisation. Who records which information? Who can actually answer it? What must the supplier provide, and what must your own company review? Which follow-up question is necessary, and which merely creates extra work?

A good provider curates this workflow: it offers well-founded standard paths, makes exceptions visible and supports the decisions along the way. It neither demands every piece of information that is theoretically available nor leaves every conceivable configuration to the customer. The relevant expertise shows in what is deliberately simplified without giving up review quality or responsibility.

The supply chain is not a contest for the most connections

One example is networking suppliers, their upstream suppliers and further tiers. Technically, an impressive network can be built. But who then resolves contradictory information? Who confirms that a piece of evidence really belongs to the component delivered? And who checks whether information from the third tier is still current?

Take a packaging supplier that buys in film, adhesive and printing inks. If all parties are connected directly to that supplier's customer, additional communication channels emerge. A question about the coating can suddenly land with the raw material provider, even though it does not know the finished packaging or how it is used. More connections have then not clarified responsibility but created new coordination effort.

The sensible starting point is usually the direct supply relationship. Article 16 PPWR obliges suppliers to provide the manufacturer with the information and documentation needed to demonstrate conformity. The manufacturer (DE: Erzeuger) remains responsible for its conformity assessment. A supplier declaration therefore does not replace a necessary review; conversely, there is no blanket obligation to manage every upstream tier yourself.

Direct contact with upstream suppliers can make sense when there are specific evidence gaps. It should, however, be a justified escalation, not an automatically inflated standard process. Before data is shared, confidentiality and usage rights must also be clarified. The GDPR concerns personal data such as contact details, not all material information across the board. Multi-tier networking is not inherently impermissible – its benefit and its permissions must be traceable.

Onboarding must turn uncertainty into a workable process

Login credentials and an import template are not onboarding. At the start, the provider must help select representative packaging, identify data sources and define the right mapping logic. Only then can you sensibly decide which suppliers should add which information.

Ask to be shown the path using one of your own packaging items: from the existing ERP extract via a missing supplier document to reviewed documentation. Ask who supports you, which decisions are made jointly and how you can tell that progress is being made. A working start reduces uncertainty. It does not shift it into a new system.

The decisive test begins after the first approval

A demo often shows a fully completed record. Day-to-day operations, by contrast, consist of follow-up questions, stand-ins and changes. So have a supplier correct a weight or replace a material. Which affected packaging items are identified? Who has to review again? What happens to documents that have already been issued?

It must be possible to set a status back to editing or review when needed without deleting the history so far. Progress reports must distinguish whether data is missing, information is unreviewed or a decision is pending. Permissions should safeguard this work, not obstruct stand-ins and collaboration so much that side lists in Excel reappear.

“Audit-ready” must also become concrete: can the company show, for an earlier state, which packaging was described, which evidence was available and on what basis the decision was made? Such a system supports an inspection. No software label, however, guarantees that every authority will accept every specific piece of evidence.

Experience must show in product decisions

SUSYCHECK comes from packaging management. Our developers bring many years of experience in software development and architecture. Our operational know-how comes from procurement, sales, general management and practical collaboration across departmental and company boundaries. This combination shapes our ambition: technically sound solutions for processes that can actually be executed.

SUSYCHECK structures packaging and component data, integrates suppliers, highlights missing information and evidence, checks for PPWR conformity and automatically generates Declarations of Conformity and technical documentation based on the captured and reviewed data. Companies therefore do not have to design and build these workflows from scratch themselves.

AI can support this. It does not, however, replace responsibility for domain rules and process decisions. Nor does a background in an ESG suite or a consultancy alone prove suitability or unsuitability. Check the result against the real workflow.

So do not compare annual licences alone. Compare the remaining effort for data collection, follow-up questions, review, changes and documentation. A lower licence fee saves nothing if your organisation has to compensate for the system's gaps on a permanent basis.

Sources

• Regulation (EU) 2025/40 (PPWR), original text – in particular Articles 15 and 16 and Annexes VII and VIII
• Regulation (EU) 2016/679 (GDPR) – in particular Articles 5 and 6 on personal data