How Companies Can Prepare Their PPWR Structure Today for 2028 and 2030

Summary

• The PPWR applies in stages: general application from 12 August 2026, further obligations follow with later deadlines.
• A future-proof structure rests on granular packaging data: article, components, materials, weights, functions, evidence, versions, and responsibilities.
• What is critical is not only data collection, but reusing the same data for conformity assessment, technical documentation, labelling, and later reports.
• Anyone who sets up supplier integration, data model, and release processes cleanly now will significantly reduce rework, Excel effort, and compliance risk.

Why isn't a 2026 focus enough?

Many companies are currently working toward an obvious milestone: the general application of the PPWR from 12 August 2026 (Verpackungsgesetz.com on the PPWR). That makes sense but is too short as a target. The regulation does not take effect in a single step but through several deadlines and downstream requirements. For companies, this means the structure built today has to do more than support a first piece of evidence.

Later obligations cover labelling, compostability for certain packaging, and requirements on recyclability, recyclate shares, and reusability. On top of that, open detailed provisions from implementing and delegated acts will follow, for example on the granularity of register and reporting data (ZSVR on national implementation of the PPWR). That is why a purely deadline-driven solution is risky: it only reflects what is reliably known today and breaks later under additional data fields, new evidence, or changed assessment logic.

This shows up quickly in practice. Anyone who captures packaging only as an SKU with total weight can hardly answer later questions on components, material combinations, separability, or recyclate shares cleanly. Anyone who collects supplier data only as PDF cannot efficiently review, compare, or transfer it into technical documentation. And anyone who organises releases only by email loses traceability with every design change.

The better perspective is therefore: not "How do we get to 2026?" but "Which structure also carries us through 2028 and 2030?" That is not an abstract architecture concern but a cost and risk question.

Which data structure companies should build now

A defensible PPWR structure begins with the data model. What matters is that packaging is captured not just as a final object but as a composed unit. For most companies, a structure with at least four levels makes sense: packaging unit, component, material, and evidence.

At the packaging-unit level you have product reference, market, intended use, and packaging type. At component level it is about bottle, cap, label, tray, film, adhesive, inlay, or shipping carton. At material level, materials, material shares, weights, and where relevant layers or composites are captured. The evidence level links this data to specifications, supplier declarations, test reports, conformity assessments, and technical documentation. The ZSVR explicitly points to standardised and digitally processable data capture in its discussion draft on technical documentation (glass example).

Versioning matters as well. Packaging changes constantly: new suppliers, modified material recipes, weight optimisations, changed labels, or different barriers. If these changes are not versioned, it is hard to prove later which configuration was placed on the market at which point in time. This traceability is central, especially for conformity assessments under the relevant PPWR articles.

At minimum, these fields should already be available in structured form today:

1. Packaging ID and product/SKU reference
2. Market/country and role of the entity placing on market
3. Component list with individual weights
4. Material categories and material shares
5. Supplier, plant, specification version
6. Evidence and validity period
7. Release status and responsibilities
8. Change history with versions

It sounds like a lot of work, but it is much cheaper than later data migrations. Anyone who sets up this structure now can usually add later fields rather than rebuild the system.

Concrete roadmap: 90 days, 2026, 2028, 2030

To turn the target picture into a workable programme, a simple staging by phase, priority, and maturity helps. In the first 90 days, companies should not launch a full project but lay the foundation: select the top 100 packagings by revenue, volume, or risk; agree on a unified data model; appoint owners; and roll out a supplier template with mandatory fields. For a first pilot, three to five core roles are often enough: packaging, procurement, regulatory/compliance, sustainability, and data/IT coordination. Small portfolios can often handle this part-time; with high SKU counts or many suppliers, a dedicated project setup is needed.

By 2026, the foundation should be in place: a central packaging register, versioned evidence, defined release before placing on market, and structured supplier data at least for critical and high-volume packaging. By 2028, the structure must carry additional attributes for labelling, separability, compostability, and physical packaging properties cleanly. Typical data fields then depend on packaging type, for example: for a bottle, material, weight, recyclate share, label area; for a shipping carton, inner dimensions, outer dimensions, void space, material grade; for flexible packaging, layer structure, barrier, composite type, and separation guidance. By 2030, the same data should support defensible assessments of recyclability, recyclate shares, and reusability.

For prioritisation: large companies start across portfolio and country, smaller ones first with the most regulatorily critical packaging. Measurable next steps are simple: 1) appoint owners, 2) define mandatory fields, 3) select a pilot portfolio, 4) start the supplier query, 5) make the release rule binding.

Which processes will actually carry through 2028 and 2030

Data alone does not solve the problem. Companies need processes that control changes and make evidence reliably available. Three processes matter most: data intake, release, and monitoring.

Data intake should not rely on manual one-off queries. Suppliers already have much of the required data but often in different formats and with different quality. So standardised data requirements are needed: clear mandatory fields, defined material categories, fixed units, document uploads, and plausibility checks. Otherwise you get what already burdens many teams today: Excel lists, follow-up queries, media breaks, and missing comparability.

The release process has to bring packaging, procurement, sustainability, and regulatory together. Packaging should only be released internally once the relevant data is complete, the evidence is in place, and the conformity review is documented. This prevents design decisions from later having to be "patched" for regulatory reasons.

Monitoring is the third building block. The PPWR will not stay static during implementation; national transposition and secondary law continue to evolve. So companies should not only manage packaging but also rule states. In practice: which assessment applied when? Which packaging is affected by which deadline? Where is evidence missing? Which suppliers have outdated specifications?

A good target picture is a system that can answer three questions immediately for every packaging: what is built in? Is the current evidence sufficient? What changes at the next deadline? This transparency decides whether 2028 and 2030 stay manageable or whether hectic special projects become necessary.

Which requirements for 2028 and 2030 must be designed in today

Not every detailed requirement is finalised in operational terms yet. Still, it is clear in which direction the structure has to hold up. For 2028, labelling obligations and requirements on certain compostable packaging are particularly relevant. For 2030, recyclability, minimum recyclate shares, and reusability move further to the foreground.

On top of that come concrete design and optimisation requirements. One often discussed point is the cap on void space in grouped, transport, and e-commerce packaging at a maximum of 50 percent. Rising data and evidence requirements in e-commerce are also expected or described.

What does this mean for today's structure? First, it has to be able to capture physical packaging attributes, not only material and weight. That includes volume, dimensions, fill level, separability, closures, label shares, and where relevant reuse cycles. Second, it has to link labelling information to the packaging, for instance which consumer or disposal information is used on which variant. Third, it has to store recyclate data verifiably, ideally with origin, type of evidence, and validity.

A common mistake is to tackle these topics only when the respective deadline draws closer. By then, historical data is missing, suppliers have to deliver under time pressure, and packaging development runs past the regulatory requirements. Better to provision the data fields now, even if they are not fully populated for every packaging at the start. An empty but defined structure is more valuable than a system that does not know these fields at all.

How companies should set up implementation organisationally

PPWR preparation rarely fails on technical knowledge alone. More often it fails on responsibilities. Packaging data sits distributed across procurement, development, quality management, sustainability, regulatory, and external suppliers. If nobody owns the structure, no defensible data basis is built.

It makes sense to have a clear owner for the packaging data model, usually a joint role between packaging and regulatory or sustainability. Procurement should ensure suppliers reliably deliver the required data and evidence. Product management and development must report changes early, not only after production release. The executive board, in turn, should treat the PPWR not as an isolated environmental topic but as a market-access and steering topic – because non-compliance can lead to sanctions and market-access restrictions.

In practice, a simple operating model helps:

• One central packaging register in the company instead of distributed files
• Binding supplier requirements with standardised templates or portals
• Release rules before placing on market
• Regular gap analyses against upcoming deadlines
• Documentation available quickly, not only in an audit case

The last point is underrated. Technical documentation and conformity evidence scale manually only to a limited extent. The larger the portfolio, the faster Excel becomes a risk: unclear versions, missing attachments, no history, no analytical use. Anyone who works digitally and in a structured way today creates not only compliance certainty but also better decisions on material choice, supplier selection, and packaging optimisation.

Conclusion

Anyone who aims their PPWR structure only at 2026 today will very likely do double work later. What carries through is an architecture that captures packaging granularly, integrates supplier data in a standardised way, versions changes, and makes the same data basis usable for conformity assessment, technical documentation, labelling, and later requirements. That reduces effort and risk for 2028 and 2030.