What to watch for, and how to qualify vendors
Kai Rostcheck \ November 2026
When considering Extended Producer Responsibility (EPR) and/or Packaging and Packaging Waste Regulation (PPWR) software, your first questions will likely be: How will it handle our packaging data? Does it cover all of the markets we sell into? Which reports and declarations will it create?
That’s the right place to start, and it is the focus of The Packaging Software Buyers Guide and Packaging Compliance Reality Check. But as you narrow your vendor shortlist and define your requirements, there’s another important consideration: security.
Packaging compliance software often connects to other business systems and may process information that is more sensitive than it first appears. SKU-level packaging weights and units placed on the market, by country, can reveal sales volumes and market mix. Material specifications, supplier test reports, and declarations may have been shared by suppliers under confidentiality terms. And like any business system, these platforms face familiar threats such as stolen credentials, unauthorized access or changes, and ransomware.
It’s especially important to consider integrations to and from these tools and platforms. A standalone reporting tool may hold only the data you upload to it, while a platform connected to ERP, PLM, PIM, procurement systems, supplier portals, single sign-on, document repositories, or external AI services can reach much further. If that platform were compromised, the consequences would depend on the connections and privileges involved: a read-only feed carries different risks from credentials that can update specifications, supplier records, or enterprise master data. Those permissions, along with how the platform is isolated, authenticated, monitored, and recovered, belong in your risk assessment.
Software security is a broad topic. Here I focus on the two forms of security assurance you are most likely to encounter (ISO/IEC 27001 certification and SOC 2 Type II reports) and on the questions worth asking every vendor.
Two Common Forms of Security Assurance
For commercial packaging software delivered as a hosted service, ISO/IEC 27001 and SOC 2 Type II are useful starting points. Other frameworks may matter in your industry or procurement process, but these two address concerns that many buyers share: how the provider manages information security, and how specific controls operate in practice.
ISO/IEC 27001 sets requirements for an information security management system. Your PPWR workspace may hold supplier test reports, material specifications, and declarations that suppliers shared under confidentiality terms. An ISO/IEC 27001 certificate shows that a certification body examined how the provider identifies and manages information security risks within a stated scope. The question to settle is whether that scope includes the operations that host and support your PPWR workspace. Ask for the current certificate and scope statement, and have the vendor name the legal entity responsible for those operations.
SOC 2 Type II is an attestation report: an independent firm gives an opinion on the design and operating effectiveness of specified controls for a defined service over a stated period. Ask for the latest report and have your IT team check which service was examined, the period it covers, which categories beyond Security are in scope (such as Confidentiality or Processing Integrity), the controls tested (including the ability to change reporting data), and any relevant exceptions. The report tells you what the auditor examined, while an actual software demonstration will show what the product can do within your required workflow.
A parent company’s certificate or a cloud host’s report may also be relevant, but neither automatically covers the application you’re buying.
What Public Evidence Shows
As of October 29, 2026, I reviewed public evidence for 154 vendors whose current software supports packaging EPR, the EU Packaging and Packaging Waste Regulation (PPWR), or both. The sample combines the EPR and PPWR vendors in The Packaging Software Buyers Guide with additional vendors from my wider market research. The group includes dedicated platforms as well as broader software and specialist tools with narrower capabilities, such as fee estimates or declaration generation.
Of the 154 vendors:
27 (about 18%) had a public indication of ISO/IEC 27001 certification
15 (about 10%) had a public indication of a SOC 2 Type II report
8 (about 5%) had both
This evidence is primarily based on public vendor statements or third-party listings; a few rest on published certificates I could inspect. I did not inspect actual SOC 2 reports. Where the only association was to a parent company or group-level certificate, I did not count a vendor.
For the other 120 (about 78%), I found no qualifying public indication of either. Public evidence is a narrow window here: SOC 2 reports and other security documentation may be available on request, so be sure to check with the vendors you are evaluating.
Do this: Align with your IT, compliance, and risk colleagues on the evidence they need before you shortlist, so that an absent badge does not rule out a strong option and a visible badge does not replace review.
If your organization is in scope of the EU NIS2 Directive, your security team may already have a supplier assessment process that applies to this purchase. Article 21(2)(d) lists supply chain security, including the security-related aspects of relationships with direct suppliers and service providers, among the minimum cybersecurity risk-management measures.
Outside the EU, or as a practical starting point anywhere, NIST’s Quick-Start Guide for Cybersecurity Supply Chain Risk Management (SP 1305) shows how to manage cybersecurity risks from suppliers and service providers using the Cybersecurity Framework 2.0. SP 800-161 Rev. 1 offers a fuller treatment written for organizations that acquire technology products and services.
What should you ask packaging compliance software vendors?
Your follow-up questions depend on what you are buying:
| If you’re buying… | Why it matters | Ask the vendor to show you… |
|---|---|---|
| A regulatory reference or standalone calculator | Even a simple tool can end up holding confidential uploads, such as SKU-level volumes and supplier data. Teams may adopt lightweight tools without IT review, so file retention, account protection, and processing by third parties can go unchecked. | Where uploaded files are stored and for how long, how you delete them, how accounts are protected (for example, multi-factor sign-in), and whether any third party, including an AI service, processes the uploads. |
| An EPR reporting platform | A compromised or over-privileged account could change weights, material codes, or approved filings. Role-based permissions, strong sign-in, and audit logs that users cannot edit are the controls that let you prevent, detect, and reverse such changes. | Which roles can edit and approve reporting data, and whether one person can do both. Then use a test account to change an approved weight, and show the audit-log entry, who can change or delete that log, and how sign-in is protected (for example, single sign-on and multi-factor authentication). |
| A supplier-evidence or PPWR documentation workspace | Suppliers often share test reports and specifications under confidentiality terms, and a declaration depends on the evidence version it relied on. Access that continues after a supplier leaves, or evidence you can’t retrieve, weakens both. | Replace a test report and revoke a sample supplier’s access. Show what that supplier could see and retrieve the document version that supported the declaration. |
| A packaging system connected to enterprise applications | Write access to ERP, PLM, or PIM records extends the platform’s reach into enterprise master data, so an unintended update can spread beyond the packaging system. | Show which records the integration can read or write. If it can write back, show how your team would trace and correct an unintended update. |
| A service where the vendor or a partner prepares or submits reports for you | Vendor or partner staff may handle your data and, in some cases, act in registry or PRO portals on your behalf. Their access and the credentials they use become part of your risk. | Show which staff or partners can see your data and how that access is approved and removed. If they act in a registry or PRO portal on your behalf, show whose credentials are used and how they are stored. |
If a vendor uses AI to read supplier documents or classify materials, ask whether your documents are sent to third-party model providers, whether they are used to train models, and which subprocessors are involved. I look at how vendors are applying AI in more depth in AI in Packaging Compliance Software.
For your most consequential workflow, ask who is responsible for access, incident notification, and recovery, how quickly the vendor commits to notify you of an incident, and whether that commitment is in the contract. Ask when restoration was last tested, what can be restored, and what your team would need to do.
Whatever you are buying, the core questions are the same: what the vendor protects, what you can recover, and what remains your responsibility if something goes wrong.