From Supplier Data to Declaration of Conformity: Build a PPWR Compliance System That Scales

Here is the situation many compliance and procurement managers find themselves in right now.

You know PPWR applies to your company. You have probably started a spreadsheet. You have sent a few emails to your packaging suppliers asking for material information. And you are beginning to realize that the task in front of you is significantly larger than what a spreadsheet and an inbox can handle.

If you manage 50 SKUs, that is 50 Technical Documentation files and 50 Declarations of Conformity. If you sell across 10 EU member states, that is 10 EPR registrations with different national requirements. If you source from 20 packaging suppliers, that is 20 separate data collection exercises, each requiring substance disclosures, recycled content certificates, and full material breakdowns.

The documentation challenge is a data infrastructure challenge. And it needs to be solved before August 2026.

Why Supplier Self-Declarations Are Not Enough

The single most common misconception we encounter is that a supplier statement covers your obligation. It does not.

PPWR places the compliance burden on the manufacturer or importer placing the product on the EU market. Your supplier providing a letter saying their materials are compliant does not constitute proof under the regulation. What you need is specific, structured, third-party-backed data for each material and component.

For substance limits, you need test reports or Certificates of Analysis demonstrating that the sum of concentration levels of lead, cadmium, mercury, and hexavalent chromium does not exceed 100 mg/kg. For food-contact packaging, you need specific PFAS test results below the regulatory thresholds.

One number makes this concrete: a single PFAS analysis for one packaging type currently can cost from several hundreds euros up to €17,000. For companies with large packaging portfolios, testing every SKU is not financially viable before August 2026. That means compliance teams need a risk-based approach, starting with food-contact packaging where the deadline is hardest and the health risk is most direct, and working outward from there. Without a clear prioritization, the testing backlog alone can become a compliance failure.

For recycled content, you need audited mass balance data or certificates from recyclers showing that the content is post-consumer, collected in the EU or an equivalent system. A supplier telling you their plastic contains recycled content is not the same as providing chain-of-custody documentation.

For recyclability, you need conformity assessment results using the Design for Recycling methodology, including data on sorting compatibility and dismantling ease. From 2030, packaging must meet specific "Recyclability Quality Grades" (A, B, or C). If your documentation doesn't show the sorting compatibility and dismantling ease, it is considered non-compliant.

Worth noting: Declarations of Conformity can in some cases be aggregated across packaging types with materially identical specifications. The Technical Documentation file, however, must be product-specific. Understanding that distinction matters when you are scoping the compliance workload across a large portfolio.

For minimization, you need a written justification report explaining why the packaging weight and volume cannot be reduced further without compromising product protection, safety, or hygiene. If you have empty space in your box, you must be able to prove it is technically necessary as over-packaging is the most visible target of the PPWR.

This is the data you need. For every SKU. From every relevant supplier.

The Scale Problem

For companies with large packaging portfolios and multi-market distribution, the documentation burden is not a one-off compliance project. It is an ongoing operational function. And the underlying data problem is usually worse than people expect when they start.

One recent conversation involved a producer managing around 8,000 product lines across multiple production locations. Some sites had detailed material specifications. Others had only a basic article number and a price. Across multiple ERP systems with different data structures and varying data quality, there was no single view of what materials were in use, what the recycled content percentages were, or which packaging types had been assessed for recyclability. Getting to a position where Declarations of Conformity could be issued required building that data baseline from scratch, across systems that were never designed to hold it.

Companies that try to manage this through shared drives, email chains, and manually updated spreadsheets create three problems. 

• Version control: When a supplier updates a certificate, how do you know which SKUs are affected and whether the relevant DoC needs to be reissued? 
• Completeness: How do you confirm that every required proof point is present for every packaging type before you sign a Declaration of Conformity? 
• Audit readiness: If a market surveillance authority requests your Technical Documentation file, you usually have only 10 days to produce it. How quickly can you produce a complete, accurate package?

That is not an unusual situation. It is the normal starting point for most producing companies right now. And it is the reason that treating PPWR compliance as a document generation task misses the point. The documents are the output. The data infrastructure is the real work.

What a Collaborative Proof Platform Changes

Sunhat is built around the idea that you already do the work. You collect supplier data. You manage material specifications. You track market registrations. The gap is not effort. It is structure.

Our Collaborative Proof Platform gives your compliance, procurement, and sustainability teams a single place to collect, verify, and store every piece of proof your packaging portfolio requires. Proof AI agents run your supplier questionnaires at scale, chase missing data, and flag proof gaps before they become audit exposures. Your Proof Library keeps every Technical Documentation file organized with version control built in.

When you are ready to issue a Declaration of Conformity, the platform confirms that every required proof point is present and accounted for. Our compliance experts work directly with your team throughout. We know where the gaps typically appear and when a national authority requests documentation, you produce it in minutes, not weeks.

The CSRD Benefit You Probably Have Not Planned For

If your organization is also managing CSRD reporting, your PPWR work delivers a second return.

Packaging data collected for PPWR maps directly to ESRS E5, the circularity and waste management standard under CSRD. Transparent PPWR compliance disclosure serves as supporting evidence for E5 reporting. The material composition data, recycled content percentages, and recyclability assessments you build for PPWR become part of your sustainability disclosure infrastructure.

Build the data once. Use it for both obligations.

The Right Time to Start Is Now

The 2030 recyclability grade requirements need 12 to 24 months of preparation before the deadline. The August 2026 obligations are already active. And the suppliers you need data from have their own lead times and backlogs.

Talk to our team about your portfolio. We will map your proof gap, scope the data collection program, and show you exactly what a compliance system that scales looks like for your organization.