Short answerA PPWR-ready packaging data model treats packaging as its own master data entity. It links sales, grouped and transport levels to components, and records material, weight, colour, recycled content, recyclability grade, supplier and declarations per component. Specifications usually live in PLM or a packaging specification tool, volumes in ERP, and published data in PIM.
Key takeaways
- PPWR obligations attach to the packaging unit, but the evidence sits at component level, so the model needs both packaging units and components with weights and materials.
- The primary, secondary and tertiary hierarchy maps to the PPWR categories of sales, grouped and transport packaging, plus e-commerce packaging for the empty space ratio.
- For portfolios of 2,000 to 10,000 SKUs, an estimated 6 to 12 months covers hierarchy, components and supplier evidence, with supplier data collection as the critical path.
Treat packaging as a managed entity
PPWR compliance requires packaging to exist as its own master data entity, linked to products and managed independently. Most companies store packaging as free text on the product record, or as a bill of materials line with a weight and little else. That structure cannot answer per-unit questions such as which SKUs use a closure that drops a pack below grade C, or how much recycled PET a plant consumed last year. A dedicated packaging entity with components, materials and evidence makes each PPWR obligation answerable from one source.
Model the packaging hierarchy
The hierarchy maps packaging levels to the PPWR categories that trigger different obligations.
| Level | Common term | PPWR term | Typical example | Main PPWR exposure |
|---|---|---|---|---|
| Primary | Consumer unit | Sales packaging | Bottle with closure and label | Recyclability, recycled content, labelling, PFAS |
| Secondary | Case or multipack | Grouped packaging | Shrink-wrapped six-pack, display tray | Reuse targets, empty space ratio |
| Tertiary | Shipper or pallet load | Transport packaging | Pallet, stretch film, crate | Reuse targets, empty space ratio |
| Shipment | Online order box | E-commerce packaging | Mailer box with filler material | Empty space ratio |
Each level links to its children with a quantity: a pallet holds 80 cases, a case holds 6 consumer units. GS1 hierarchies built on GTINs already describe these relationships, and GDSN packaging attributes offer a ready vocabulary for materials and weights, as covered in the syndication article. Reusing that structure prevents a second, competing hierarchy.
Capture attributes at component level
Obligations attach to the packaging unit, but the evidence sits at component level, so the model needs both. A practical attribute set:
- Packaging unit: identifier, version, level, PPWR category, total weight, dimensions, empty space ratio, reusable flag, target Member States, recyclability grade with assessment method and date.
- Component: type (body, closure, label, sleeve, adhesive, coating, insert), material and polymer, weight, colour, opacity, separability, food-contact status, supplier and supplier part number.
- Material: recycled content percentage, post-consumer share, certification scheme, biobased share, compostability, substances of concern, PFAS status.
- Evidence: supplier declarations, test reports, certificates with validity dates, EU declaration of conformity, technical documentation reference.
- Market: EPR registration number per Member State, reporting material category, label artwork version.
Versioning matters as much as attributes. A packaging unit changes when any component changes, and the declaration of conformity must match the version actually placed on the market. Effective dates on every version let EPR tonnage reports reflect what shipped in each period, and retention rules must cover 5 years for single-use and 10 years for reusable packaging, as Article 15 requires.
Decide where packaging data lives
No single system type fits every company, so the decision follows where packaging is designed and who consumes the data.
| Option | Strengths | Limitations | Fits when |
|---|---|---|---|
| PLM | Specifications, BOMs, change control, supplier collaboration | Weaker downstream publishing; often limited to own-brand packaging | Packaging is engineered in-house |
| PIM | Channel syndication, completeness rules, links to SKUs | Limited change control and component structure | Packaging data mainly feeds retailers and labels |
| Packaging specification tool | Deep packaging models, supplier portals, built-in compliance calculations | One more system to integrate; overlap with PLM | Large packaging portfolios with many suppliers |
| ERP | Weights, purchasing, shipped volumes for EPR | Thin material detail and document handling | Source of tonnage, rarely the master |
The central insight is to separate the system of record for specifications from the system of distribution. A common pattern keeps packaging specifications and evidence in PLM or a specification tool, takes shipped volumes from ERP, and publishes material composition, grade and label data through PIM. The integration patterns article details the interfaces, and the PLM vendor overview lists platforms with packaging capabilities.
Plan the build in stages
A staged build delivers usable data early and limits the risk of a multi-year modelling exercise. A typical first stage covers the hierarchy and component structure for the top 20% of SKUs by volume, which often account for most EPR tonnage. The second stage adds supplier evidence and recycled content, and the third automates grade roll-ups and EPR reporting.
For a portfolio of 2,000 to 10,000 SKUs, an estimated 6 to 12 months covers the first two stages, with supplier data collection as the critical path. Governance determines whether the model stays accurate: assign packaging data ownership to a named role, define completeness rules per PPWR category, and block product release when mandatory packaging attributes are missing. Those rules turn the model into a control point instead of a reporting afterthought.
Frequently asked questions
Should packaging data live in PLM or PIM?
It depends on where packaging is designed and who uses the data. PLM or a packaging specification tool usually holds specifications, components and evidence because it manages change control. PIM usually publishes material composition, grades and label data to retailers, labels and other downstream channels.
How does the packaging hierarchy relate to GS1 standards?
GS1 packaging hierarchies use GTINs for each level, from consumer unit to case and pallet, with quantities between levels. GDSN also offers packaging attributes for materials and weights. Aligning the PPWR data model with these structures avoids duplicate hierarchies and eases data exchange with retailers.
Which packaging attributes are mandatory for PPWR?
PPWR does not publish a single attribute list. In practice, compliance requires material, weight, colour and supplier per component, plus recycled content, recyclability grade, substance status, dimensions, empty space ratio, reusable status and links to the declaration of conformity per packaging unit.