PPWR Compliance Runs on SKU Data Nobody Wants to Collect
Every PPWR compliance vendor sells the same promise: feed us your SKU data, get back an audit-ready Declaration of Conformity in minutes. That promise is true, and it's also not the hard part.
The hard part is the feed. Recycled content percentage, material composition, recyclability grade, weight, restricted substances, for every SKU, sourced from supplier spec sheets that arrive as PDFs, an ERP item master someone half-filled in three years ago, and a spreadsheet the sustainability lead maintains alone. Selling into Spain adds two more line items per SKU: an SDDR deposit label and an IEEPNR plastic tax figure for the quarterly Form 592 filing. None of that shows up in the software comparison articles, because none of it is software's job. It's data collection, and right now most companies do it by hand, once, under deadline pressure, then again next quarter.
The compliance tool already exists. The pipeline into it doesn't.
Search "PPWR compliance software" and you get a wall of vendor comparisons, Coolset's roundup of tools for importers and distributors is a good one, all evaluating the same thing: how fast does the tool turn SKU data into a filed document. That's a real question and worth answering with real software, not a workaround.
What none of them answer is where the SKU data comes from before it reaches the tool. In practice, for most mid-size brands and distributors, it comes from:
- Supplier declarations, PDFs or emails with material composition and recycled content, one per SKU, rarely in the same format twice.
- The ERP item master, which usually has weight and maybe a material code, entered by whoever set up the SKU and never revisited.
- A sustainability spreadsheet, the closest thing to a source of truth, maintained by one person, out of date the moment a supplier changes a formulation.
- Nothing at all, for SKUs where the recycled content question has simply never been asked.
Reconciling those four sources into one row per SKU, then noticing which SKUs are missing a field, is the actual work behind every "we automated PPWR" case study. It's also exactly the shape of problem covered in automating production reporting without an MES: data that already exists, scattered across systems that don't talk to each other, needing normalization before it's useful to anything downstream.
Where an agent fits in the pipeline
The agent doesn't file anything. It sits between your systems and the compliance tool, and does the three things a person currently does under deadline pressure:
- Pull what already exists. Read the ERP item master, watch the inbox or shared folder suppliers use for spec sheets, and extract the fields, material, weight, recycled content, from whatever format they arrive in. If your ERP predates the concept of an API, that's not a blocker; see connecting a legacy ERP for the four ways in.
- Reconcile per SKU. Match supplier declarations to the right SKU, flag conflicts, when the spreadsheet says 30% recycled content and the latest supplier PDF says 22%, and build one clean row per SKU instead of three disagreeing ones.
- Surface the gaps, don't guess them. A SKU with no recycled-content figure on file gets flagged and routed to whoever owns that supplier relationship, with the specific missing field named, not a generic "data incomplete" email.
| Data point | Typical source | Cross-check | What it catches |
|---|---|---|---|
| Recycled content % | Supplier declaration (PDF/email) | Prior quarter's figure on file | Formulation changed, declaration didn't |
| Material composition | Supplier declaration or spec sheet | ERP item master material code | SKU reclassified, code never updated |
| Packaging weight | ERP item master | Supplier spec sheet | Weight entered once, packaging changed since |
| SDDR eligibility | Product category + market (Spain) | SKU sales channel | Deposit label required, never generated |
| IEEPNR plastic weight | Material composition × weight | Prior Form 592 filing | Quarter-over-quarter jump with no SKU change |
Once that feed is clean, it's a compliance tool's job to turn it into the actual filing. For a brand or distributor selling into Spain specifically, that's where a specialist like PPWRsolution earns its keep, it consolidates the Declaration of Conformity, SDDR labels and Form 592 calculation into one dashboard instead of three. What it still needs from you is the same thing every compliance tool needs: complete, correct SKU data, on time. The agent is what keeps that input clean quarter after quarter, so the ten-minute filing stays a ten-minute filing instead of a week of chasing suppliers first.
Why this has to stay a human decision at the filing step
Reading supplier data and reconciling it against your ERP is safe to run untouched, nothing leaves the building. The moment a document gets generated for submission, a Declaration of Conformity, a tax figure on Form 592, someone on your team should see it first. That's the same human-in-the-loop boundary that applies to any agentic workflow: the data gathering runs on its own, the thing with your company's name and a regulator's eyes on it gets a human sign-off before it goes anywhere. PPWRsolution's own flow works the same way, automated calculation, human review before submission, which is the right design, not a limitation.
The part that repeats: this isn't a one-time project
The August 2026 PPWR obligations weren't a single deadline to clear and forget. Suppliers change formulations, SKUs get added and discontinued, and Spain's Form 592 is a quarterly filing, not an annual one. A spreadsheet assembled once under deadline pressure is stale by the next quarter. The same self-improving capture pattern used for production data, catch the mapping drift, learn the new supplier's PDF layout, works here: the pipeline that fed this quarter's filing is the one that feeds next quarter's, with less manual chasing each time, not the same fire drill on a schedule.
If your packaging data currently lives across a few suppliers' inboxes, an ERP nobody trusts fully, and one person's spreadsheet, that's the normal starting point, not a special case. Tell us what your sources look like and we'll tell you what a clean SKU feed would take to build.
Sources: SAP, AI for PPWR compliance, Coolset, PPWR compliance tools for importers and distributors, PPWRsolution, Spanish packaging compliance.
Frequently asked questions
What data does PPWR compliance actually require per SKU?
Material composition, recycled content percentage, recyclability grade, packaging weight, and any restricted substance declarations, for every SKU sold into the EU. Selling into Spain adds SDDR deposit labeling and IEEPNR plastic tax reporting on top. Most of this data already exists somewhere in your business, split across supplier spec sheets, the ERP, and old spreadsheets, it has just never been collected in one place per SKU.
Can AI collect PPWR data automatically, or does someone still have to gather it?
An agent can pull the pieces that already exist electronically, supplier PDFs, ERP item masters, packaging spec sheets, and match them to your SKU list without anyone retyping. What it can't do is invent data nobody has measured. If a supplier has never disclosed recycled content, that gap still needs a human ask; the agent's job is finding the gap and chasing it, not guessing the number.
Does an AI agent replace PPWR compliance software like PPWRsolution?
No, and it shouldn't try to. Compliance software turns clean, complete SKU data into audit-ready Declarations of Conformity, SDDR labels and tax filings, that's a narrow, regulated job worth buying rather than building. The agent's job is upstream: getting accurate, complete SKU data out of your ERP and suppliers and into the compliance tool on schedule, instead of someone assembling a spreadsheet every quarter.
What is Spain's SDDR and Form 592, and why do they need separate handling from PPWR?
PPWR is the EU-wide packaging regulation. Spain layers two national obligations on top: SDDR, a deposit-return labeling requirement per SKU, and the IEEPNR plastic tax (filed quarterly on Form 592, currently EUR 0.45/kg on non-reusable plastic packaging). A brand selling only in Germany never touches these; a brand or importer selling into Spain inherits both, and most EU-level compliance tools don't calculate either.
How much manual work does this actually save?
The filing itself was rarely the bottleneck, tools like PPWRsolution already cut document generation to minutes. The bottleneck is upstream: someone chasing suppliers for spec sheets, reconciling three spreadsheets, and re-checking SKUs that changed since last quarter. That's the multi-day task an agent turns into a standing feed, not the ten-minute filing step.