Start with one product
Take a fictional example: a product in a cardboard outer box with a plastic inner pack. The customer asks which materials are used in each layer, what the parts weigh and which documents support those values. They also ask whether certain substances are present and what supports that answer.
Illustration. This is an example of a customer request, not a real customer dossier or a standard list of legal requirements. The information and evidence needed depend on the packaging, the company's role, the market and the actual request.
Start with the structure: which product, packaging unit, layer and component? Then attach each value to the right place. That helps prevent the weight of an outer box from being treated as the weight of the complete pack.
What information do you need to bring together?
| Question | Record |
|---|---|
| Which product? | Product number or SKU, description and its packaging. |
| What is the packaging made of? | Layers, components, material types and weight per part. |
| Which specific details were requested? | For example, recycled content, substances or a country-specific question, where relevant. |
| What supports the answer? | A supplier declaration, specification or test report that belongs to the packaging unit or part concerned and supports the stated value. |
| Is the information current? | Date and version of the data, together with open questions or conflicting values. |
A completed field is not yet a checked answer. Check that a document actually covers the right material and version. Ask the supplier a focused question when a value is missing or cannot be traced to its source.
From scattered files to a customer answer
LIVO PPWR helps organise information by packaging unit and component, shows what is missing and prepares a supplier request. In the supplier portal, suppliers see known information and fill in the gaps. An answer given in the portal returns as a proposal. Someone in your organisation reviews and confirms it before it enters the register. A returned request file is imported by you. Where available, LIVO shows a count and a few examples of known values the supplier changed before you confirm; after the import those changes are listed as tasks to review and, as long as the value has not been written again since, to undo.
You can save a customer's SKU selection and export its data to Excel. Evidence documents are not attached to that workbook. Gather or share them separately when the customer asks for them. LIVO does the groundwork and prepares the next steps. You review and confirm.
If a customer asks for everything within two days, that is their request, not a general PPWR deadline. First agree which information and evidence they need, for which products and in what format. Then you can see what is already available and which questions remain open.
What can you do today?
Choose one product that regularly triggers questions. Map its packaging layers and components. Put known values and their sources next to the open questions. Ask a colleague to check whether the answer is understandable to the customer. Then extend the approach to the rest of the range.
Want to see how this works with fictional product data?
Request a demoRead next: What packaging data should you request from suppliers?. Legal source: Regulation (EU) 2025/40. This page describes a practical workflow and does not assess whether a particular product meets every requirement.