PPWR packaging management for your product range
The same packaging in many products. Which version is being used?
A closure is used across several product lines. The supplier updates the specification. Your team now needs to establish which products use the previous version and where to apply the change.
PakPruvo connects product versions with structured packaging data. From Professional, you can maintain components in a shared packaging library and use selected versions in products.
For companies with recurring components
The shared library is for manufacturers, own-brand suppliers and trading companies that use the same packaging parts in several products. Purchasing, product management and quality assurance can access jointly maintained data versions.
For a small range, components can also be maintained directly within products. This product-specific entry is available in all plans.
Three questions that need answering when changes occur
Which data belong to the packaging?
A product name often does not sufficiently describe the packaging. Components can have their own material data, empty weights, specification information and layer structures. This keeps it clear which part a statement refers to.
Which version is used in the product?
A product uses a particular library version. A newly published version does not automatically replace the previous version in every product. Your team can review updates and apply them selectively.
What does the change mean for the declaration?
PakPruvo can show notices about newer packaging versions and differences in selected declaration-relevant information. Your team assesses the effects and works on the declaration again if needed. Changing data does not automatically recreate an existing PDF.
Example: a closure becomes lighter
Several products use the same closure version. The supplier provides a new specification with a lower empty weight. You maintain the new packaging version and review which products it should be used for.
The new empty weight remains internal information. A weight-only change is not directly compared as an individual value in declaration-of-conformity change detection. A change in the library version used can, however, trigger a notice. Technical review remains necessary even without an automated notice.
How to apply a new packaging version
PAKPRUVO · WORKFLOW
Maintain the library version
Describe shared packaging data
Review the new version
Check changed information and documents
Determine where to apply it
Select the update for affected products
Assess the declaration
Technically review the effects
Publish the product version
Complete the intended approval process
Packaging library from Professional · No automatic adoption
A library update does not automatically apply to all products.
- Maintain packaging data: Describe components and specification information in the library.
- Review the new version: Technically check changed information and associated documents.
- Determine its use: Decide which products should receive the new version and apply updates.
- Assess the declaration: Check whether a declaration of conformity needs amendment or reissue.
- Publish the product version: Complete the intended approval process and publish the required version.
Control stored data and publication separately
PakPruvo manages product versions, library versions and issued declaration versions. These serve different purposes: they describe a product, a reusable packaging building block or an issued document.
The optional four-eyes process relates to the product version. Another authorised person reviews the submission. Publication is subject to additional technical prerequisites. Technical approval is not automatic confirmation of legal conformity.
Questions about packaging management
Can technically equivalent packaging be grouped?
From Professional, equivalence groups with a shared conformity profile can be managed. Your company assesses which packaging is technically equivalent and may be treated together.
Can we import our existing data?
Manual maintenance is possible in all plans. CSV import is available from Starter and an integration REST API from Professional. Suitable fields and workflows for importing your data are assessed against your source data.
Does the audit export contain all evidence files?
From Professional, the audit export includes structured company and product data, the change log and available issued or superseded declarations of conformity as PDFs. Internally stored specifications, test reports and supplier documents are not automatically included as files.
Do QR codes remain the same with a new product version?
A new product version has its own public code. Updates within the same product version can be published under the existing link during the contract term.
Let's discuss your recurring packaging components
Which parts do you use in several products? Who maintains their specifications? And how do you apply changes today? These questions let us work through the use of the packaging library in concrete terms.
Request a discussion about the packaging library
Further information
PakPruvo supports the organisation of your packaging data. Content review and legal assessment remain with the responsible company.