Building a central packaging overview: step-by-step guide

TL;DR

• Define the purpose of the overview first and decide whether PPWR compliance, internal steering, or both have priority.
• Cut the scope small and start with one product group, one country, or 20 to 50 packaging items.
• Decide bindingly which packaging types are in and out of scope before you start collecting data.
• Name owners for data maintenance, release, and evidence so the overview stays current over time.
• Check early which data sources you need to connect and replace manual Excel processes with a structured solution.

1. What needs to be decided before you start?

Yes: before you start, you have to make decisions that can't be cleanly fixed later through the data model. The most common mistake is not a missing tool but a pilot that tries to cover compliance, procurement, design steering, and all countries at once. A defensible central packaging overview therefore starts with hard boundaries, not with data collection.

1. Put the purpose in writing. Decide first whether the pilot should mainly deliver PPWR and German Packaging Act (VerpackG) evidence, make packaging data visible for internal decisions, or both with equal weight. This decision determines which fields are mandatory: for compliance you need solid sources, packaging type, and material logic; for steering you also need comparability across articles, suppliers, and variants. The fact that packaging is regulated differently shows in the official split between sales, grouped, and transport packaging at the Federal Ministry for the Environment and in the definitions from the ZSVR catalogue of packaging subject to system participation.
2. Cut the scope small and check-ready. Start with one product group, one country, or one business unit and roughly 20 to 50 packaging items, so that material variety, supplier differences, and packaging types become visible without making the pilot unmanageable.
3. Explicitly include and exclude packaging types. Use the official guard rail: subject to system participation are filled sales, grouped, or transport packaging that typically becomes waste at the private end consumer, per the ZSVR. If you don't apply this logic from the start, you quickly mix in transport, export, or other packaging that is not treated the same way. Later reports and analyses then become unreliable.
4. Name a functional owner and field-level responsibilities. Assign a responsible position in packaging, regulatory, or sustainability. For each data field, define who supplies, who checks, and who releases: procurement for supplier information, product development for specifications, regulatory for plausibility checks, sustainability for assessment attributes. Without this mapping, the overview stays a list without commitment.
5. Define one request template and a maintenance cycle. Don't request data via Excel, PDF, and email in parallel; use a standardised sheet with mandatory fields, a source field, and a deadline. Every value needs a proof; no source, no released entry. Also plan a fixed update rhythm, for example quarterly or on material changes.

2. How do you structure packaging data at a glance?

The bottleneck is usually not missing weights but missing comparability: packaging data only becomes steerable when every field has the same functional meaning, regardless of whether it comes from procurement, supplier specification, or technical documentation. That is why your overview should not start as a long article list but as a small, binding master data model.

1. Define a small number of mandatory fields. Eight fields are enough to start: article, packaging type, material, weight, market country, supplier, data source, and last check status. More fields rarely improve quality at the start – they just increase the number of empty cells. The standardised master-data exchange practice described for example by GS1 Austria in its "Packaging Master Data" guideline offers useful orientation.
2. Define the allowed evidence per field. "Material: PET" without proof is just a claim. So for each field, define what counts as valid evidence: supplier specification, released purchasing specification, or technical documentation. This is not only important for internal quality; according to the FAQ on the statistical survey under VerpackG 2026, since the May 2024 amendment of §5a UStatG, manufacturers are explicitly asked for certain packaging data. Many companies only realise then that they have values but no auditable sources.
3. Build the hierarchy strictly. The defensible order is: article → packaging component → material → evidence. That avoids mixed data like "folding box 18 g" without clarity on whether the weight refers to the whole packaging, just the carton, or a country-specific variant.
4. Introduce a status logic. Four states work in practice: complete, incomplete, checked, outdated. "Complete" means: mandatory fields present. "Checked" means: evidence is on file and confirmed functionally. "Outdated" should kick in automatically when specification, supplier, or material change. This becomes more important because, per the ZSVR, the Minimum Standard for recyclable packaging is updated annually and the 2025 edition was published on 28 August 2025.
5. Separate by obligation logic, not by department. Mark each data field by whether it is needed for compliance, sustainability assessment, or internal optimisation. Material, weight, packaging type, and evidence almost always belong to the compliance layer; additional design or cost data does not necessarily. This separation prevents operational wish-list data from overloading the overview before the regulatorily relevant core data is solid.

3. How do you bring suppliers and internal teams in cleanly?

In practice, the central packaging overview rarely fails on the database but on unclear hand-offs between teams. When procurement, product development, regulatory, and sustainability have different expectations of the same number, you get follow-ups, duplicates, and releases without a single source. That is why the overview needs a clear process that doesn't only collect data but binds it into ownership. (Packaging: consumption in Germany through 2021 | Statista) (Packaging waste | German Environment Agency)

1. Use one standard template for all suppliers. Provide a single form with mandatory fields, units, and example values so suppliers don't answer in their own format. The less free text, the less rework in the internal team.
2. Define responsibilities per team. Procurement requests data, product development checks technical plausibility, regulatory assesses regulatory classification, and sustainability evaluates the data for optimisations. Without these roles defined up front, it stays unclear who releases a deviation.
3. Tie releases to a single source. Every central value should trace back to exactly one released proof. Otherwise multiple parallel versions in email, PDF, and Excel produce the same number with three truths.
4. Treat changes as events. New materials, changed weights, or a supplier change must immediately trigger a check process. That keeps the overview current instead of being corrected only at the next annual round.
5. Document follow-ups systematically. Record which data is missing, who delivers it, and by when the release stays open. That saves time and surfaces where recurring data gaps appear in the supplier process.

4. How do you tell that your overview is actually defensible?

An overview is only defensible when it survives an external question. The decisive difference is not in the number of fields but in whether you can immediately show, for any single piece of packaging, what was captured, which source the value rests on, and who owns the statement functionally. Exactly this becomes relevant under regulatory pressure: the PPWR entered into force on 11 February 2025, and in parallel statistical state offices can request manufacturers to deliver data on specific packaging types and deadlines, per the practice description at verpackungsgesetz.com on the survey under §5a UStatG. Then it shows quickly whether the data only looks plausible internally or also holds up externally.

A practical robustness test doesn't need new methodology but four hard questions. First: can a record per packaging be exported without manually adding information from emails or supplier attachments? Second: are missing mandatory fields visible, rather than hidden in free text or collection columns? Third: is the last change traceable with date and editor? Fourth: is there a named owner per record, even when the information comes from procurement, product development, supply chain, and regulatory?

The less obvious checkpoint is evidence capability. A material value without a specification, a weight without a test record, or a recyclate share without a supplier declaration is only of limited use for documentation and later DoC preparation. This is not academic: the ZSVR Minimum Standard is updated annually and explicitly relies on actual sorting and recovery practice, not on theoretical recyclability; the German Environment Agency also notes that fees have been aligned with recyclability since 2019. Before, the file was complete enough for meetings, but not defensible enough for audits.

5. When does Excel stop being enough, and when is software worth it?

Excel doesn't break on file size but on transaction logic: as soon as packaging data is no longer just collected but continuously reconciled, released, and reused for evidence, the spreadsheet shifts from register to risk. The sensible switch point is where maintenance, version conflicts, and documentation duties grow faster than the portfolio itself. Regulation makes this more relevant, not more abstract: the PPWR entered into force on 11 February 2025, and the German Environment Agency points to a total recycling rate of 70 % for packaging by 2030. That increases the pressure to hold material decisions and evidence in a more systematic way.

For a tight pilot, Excel often suffices: few packaging items, one country, rare changes, one clearly responsible team. It gets critical when data from procurement, product development, supply chain, and regulatory flows in in parallel. Then capture is no longer the problem – the question is which version is valid, which supplier value was released, and whether a change in material or weight can be traced into reporting and documentation.

No abstract maturity level works as a decision rule – use a yes/no test: many data sources, recurring changes, lacking transparency on the current state, high evidence demand, and several teams involved. If three or more apply, a platform is usually more economical than further spreadsheet maintenance. This is especially true if you need to integrate suppliers, validate data centrally, version changes, and generate technical documentation faster. Software does not replace the data logic, but it makes it defensible and repeatable – similar to how a PIM system makes product data centrally manageable, and specialised tools, per the PPWRify feature overview, keep product and packaging data separate but linked. Excel is not a mistake; it's rarely the end model.

Conclusion

A central packaging overview only delivers real value when it is built from the start on clear boundaries, ownership, and solid evidence. Start with a small, check-ready scope and replace manual Excel processes early with a structured data foundation, so compliance, documentation, and material decisions can carry day-to-day work.

FAQ

Which data fields belong in a central packaging overview for PPWR compliance?

Beyond material, weight, and packaging type, you need fields that allow a clear regulatory categorisation – for example producer (PPWR Art. 3 No. 15), market country, units, packaging level, and evidence status. A field for the data source is particularly important so you can later trace every value back to a supplier, an internal system, or a check note. Without this traceability, the overview becomes unreliable for audits and DoC generation.

How often should a central packaging overview be updated?

The update frequency should follow product changes and regulatory deadlines, not a rigid monthly rhythm. For packaging with frequent material or supplier changes, an event-based process is sensible, where every change is released directly. As a minimum, there should be a fixed review cycle so outdated records aren't quietly reused.

How do I get packaging data from suppliers into a central overview?

The best way is a standardised data format that you provide up front – for example as a mandatory template with clear field definitions and validation rules. In addition, define which entries are contractually mandatory and which evidence must be delivered when values are missing. If suppliers vary widely, a tiered onboarding process with prioritisation by volume and risk helps.