01 / The dashboard problem.
The packaging-compliance software market in 2026 is full of dashboards. They show recycled content percentages by region, recyclability grade distributions, EPR cost trends. They look impressive in a board pack. They fail the moment an auditor opens a single packaging unit and asks where the recycled content figure came from.
Dashboards are downstream. They render numbers that came from somewhere else. PPWR cares about the somewhere else. The supplier batch declaration, the recycler certificate, the version of the spec that was active when the production run shipped. None of that lives in a chart.
What PPWR demands is upstream. A system of record for packaging data, where every claim links to its evidence and every version of a packaging unit is preserved. The dashboard sits on top, but it is not the thing.
02 / What a system of record looks like.
A packaging system of record is a structured database where each packaging unit (the SKU-level pack, not the master) has a single canonical record. The record carries materials with masses and percentages, components linked to suppliers, certificates and test reports tied to specific batches, and a full version history of changes with effective dates.
Around the record sits an evidence layer: PDF files (test reports, supplier declarations, EuCertPlast certificates) attached to specific lines on the record rather than dumped in a folder. A workflow layer governs who can change which fields and what triggers a new Declaration of Conformity.
From this foundation, downstream artefacts (DoCs, EPR filings, eco-modulation calculations, dashboard tiles) are deterministic exports. Change a field on the record, and every artefact derived from that field updates accordingly with a new version number.
03 / The four properties auditors check.
A PPWR-grade system of record has four properties. Each one corresponds to a question auditors ask in the first hour.
- Single source. One record per packaging unit. Not three workbooks reconciled by hand. The auditor opens the record and sees everything.
- Evidence pinned. Each material claim, recycled content figure, and recyclability grade has a document attached, not just a typed statement. The document came from a supplier or a test lab and is dated.
- Version history. Spec changes are preserved, not overwritten. The auditor can ask 'show me what this pack looked like in March 2027' and see the answer with effective dates.
- Lineage to outputs. Every figure on a Declaration of Conformity, EPR filing, or dashboard ties back to a specific record version. No orphan numbers.
04 / Where teams typically come unstuck.
Three patterns recur in failed audits. First, the spec change that was made in production but never propagated to the master, leaving the Declaration referencing an outdated material composition. Second, the supplier batch that was substituted on a production run without updating the evidence chain, so the recycled content claim is correct in aggregate but unprovable for the specific lots audited. Third, the regulatory content update (a new Design for Recycling implementing act tightening Annex II) that was acknowledged in a meeting but never re-run against the existing portfolio, leaving packs at grade A on paper but grade B against the new criteria.
All three failures share a root cause: the data lives in heads and side workbooks rather than in a system that enforces the structure. PPWR is the regulation that finally makes that distinction expensive.
05 / From spreadsheet to system, in stages.
Producers do not build the system in one go. The realistic path is staged.
Stage one: master. Get every packaging unit into a single structured table. Materials by mass. Components by supplier. No rework on the historical data; just capture the current state. Six to eight weeks for a producer with a few hundred SKUs.
Stage two: evidence. Pull supplier declarations, test reports, and certificates into the system and pin them to the records they support. This is the slowest stage because it requires supplier engagement. Three to six months.
Stage three: workflow. Add the controls that prevent regression. New SKUs cannot ship without a complete record. Spec changes trigger a new Declaration. Suppliers without current declarations are flagged. Two to four weeks of configuration if the technology supports it.
Stage four: outputs. Wire DoC generation, EPR filing exports, and reporting to the records. At this point compliance becomes a side-effect of running the system rather than a project that consumes the team every quarter.
06 / How PackR8 fits.
PackR8 is the platform built specifically for this stack. The packaging master, the evidence vault, the workflow layer, and the output generation are designed as one product rather than glued together from generic compliance software.
Onboarding follows the four-stage path above. The first concrete artefact is usually a regenerated Declaration of Conformity for a producer's top SKUs, signed within the first few weeks. From there, the platform absorbs the rest of the portfolio, supplier engagement runs in parallel, and the customer arrives at a state where PPWR readiness is the default rather than the project.
07 / Frequently asked questions.
Why isn't a dashboard enough for PPWR?
Dashboards render numbers that came from somewhere else. PPWR audits care about the somewhere else: the evidence chain, the version history, the lineage from claim to source. A chart cannot answer those questions.
How long does it take to build a packaging system of record?
The realistic path is staged: master in six to eight weeks, evidence in three to six months, workflow in two to four weeks, outputs after that. Producers can be PPWR-ready inside a year if started early.
Can existing PIM or ERP systems serve as the packaging system of record?
PIM systems hold product master data and rarely have the structured packaging composition that PPWR needs. ERP holds finished goods and supplier records but no recyclability data. Both are inputs to a packaging system of record, not the record itself.
What is the smallest first step?
Pick the top 20 SKUs by volume and capture them as structured records: materials, masses, components, suppliers. That single exercise reveals 80 percent of the gaps in the data foundation.