What to Prepare for a Customer PPWR Evidence Request

Build the package data set before claiming proof：A useful PPWR response connects a package to the relevant topic, date of application and evidence limits—not merely to a certificate label

A customer may ask for a PPWR declaration, compliance certificate, recyclability proof, recycled-content evidence, PFAS statement, packaging composition or technical documentation. Those labels do not necessarily mean one document. PPWR addresses substances, PFAS for food-contact packaging, recyclability, recycled content, compostability, minimisation, labelling, reuse, technical documentation, declaration of conformity and extended producer responsibility. Different packages and timing can require different records.

As of 2026-08-08, PPWR has a general application date of 2026-08-12. That does not make every 2030 target, future delegated act, implementing act or customer format an obligation that can already be concluded as current. First create a traceable structure for package hierarchy, material, use, destination and available evidence, then compare the customer request with the currently applicable provision.

Bottom line first

Ask the customer to identify the PPWR article or topic, package scope, destination market, delivery date and document format; “PPWR certificate” is usually not specific enough.
One PPWR certificate, a single heavy-metal report or a generic supplier statement does not by itself cover substances, PFAS, recyclability, recycled content, minimisation, labelling, reuse and document duties.
Start with packaging SKUs and hierarchy. Separate sales, grouped and transport packaging, then map material weight, polymer type, supplier and use.
Supplier information, calculation, testing, design records, conformity assessment, technical documentation and a declaration of conformity answer different questions and are not interchangeable.
As of 2026-08-08, manage the 2026-08-12 general application date, future 2030 requirements and future delegated or implementing measures in separate fields; do not treat future measures as already current.
Respond first with supported scope and evidence gaps, then assign the required supplier data, calculation, testing, design review or traceability work.

Information needed before deciding

Packaging SKU list: identify every sales unit, part number, revision, product relationship and destination market instead of aggregating only by product name.
Packaging hierarchy: identify sales, grouped and transport packaging and state whether the company or another party places each level on the market.
Material composition and weight: list material, weight, multilayer structure, components, coatings, inks, adhesives and separability for each level.
Plastic type: retain polymer type, resin grade, recycled-content source and percentage information, including multilayer or barrier structures.
Supplier and upstream data: retain dated supplier declarations and specifications from packaging, material, printing, adhesive, recycled-content and food-contact suppliers.
Food contact and PFAS: identify food-contact use, contact surface, material and PFAS information. A generic package statement cannot replace an assessment of the actual use.
Dimensions and empty-space data: retain length, width, height, volume, product dimensions, empty space, fill and grouping information for minimisation or customer questions.
Artwork and labelling: retain current artwork, labels, material codes, recycling information and market versions linked to the packaging SKU.
Reuse status: record whether reuse is designed, the relevant system, available cycle information and evidence gaps rather than assuming a one-way use model.
Existing reports and declarations: log test reports, supplier statements, technical specifications and calculations with their sample, date, scope and limits.
Current applicability: identify whether each customer question concerns a current provision, a future 2030 requirement, a future delegated or implementing measure, or a customer condition.
Product-file ownership: assign data owner, version control, change notification, review date and authority to release a customer response so records do not remain scattered between functions.

Practical decision flow

Confirm the PPWR topic and customer delivery scope

Ask the customer or commercial owner to identify the article, topic, package type, market, deadline and format. Separate legal requirement, customer contract term and internal objective. Do not let “certificate” become an unscoped task name.

Build the packaging SKU and hierarchy map

Separate sales, grouped and transport packaging, and link each to product, component, material, weight, supplier, manufacturing location and destination. This is the foundation for determining whether a declaration, calculation or report actually maps to the package.

Inventory material, design and supply-chain data

Collect composition, weight, polymer, recycled content, food contact, PFAS, dimensions, empty space, artwork, labels, reuse status, reports, declarations and specifications. Retain source, version and scope for every item.

Assign evidence to the right PPWR question

Separate substances and PFAS, recyclability, recycled content, compostability, minimisation, labelling, reuse, technical documentation, declaration of conformity and EPR. Do not extend one record beyond the topic it actually addresses.

Identify current duties, future requirements and evidence gaps

Check the legal status as of 2026-08-08, including the general application date and conditions of individual provisions. Mark 2030 targets, future delegated or implementing measures and customer-specific terms as future or to-be-confirmed items rather than current conclusions.

Give a scoped response and strengthening plan

State what data is prepared, which topics it supports, which supplier information, calculation, design record, test or document is missing, and when it will be reviewed. Do not use a generic certificate to fill an evidence gap.

What different evidence can support

Evidence	What it can support	Important limitation
Supplier information and material declaration	A supply-chain statement about material, weight, recycled content, food contact, substances or another stated scope for packaging or material.	It must map to packaging SKU, material version, definition and date. It cannot by itself prove design, recyclability, empty space, reuse or every PPWR topic.
Calculation and mass-balance record	A weight, proportion, space or other result calculated from stated inputs, assumptions, package construction and version.	Its quality depends on the source data and method. If material, weight, system boundary or legal methodology changes, the conclusion may need updating.
Test or analytical evidence	Results for a stated sample, method, analyte or performance item.	Testing does not by itself cover untested packages, different materials, unlisted topics, design records or conformity documentation. Match method and reporting limit to the customer question.
Design record and artwork	How package dimensions, empty space, construction, separable components, labels and design decisions map to a specific SKU.	Design data does not supply substance concentration, supplier composition or legal applicability on its own. Cross-check it with material data and the market version actually supplied.
Conformity assessment or internal review record	That the company checked stated provisions, packages, records and date, and recorded its assumptions and gaps.	Review quality depends on its scope and source data. It cannot turn missing material, testing or supply-chain information into a fact.
Technical documentation and declaration of conformity	That the company has organised technical evidence for a defined package or product and issued a scope-specific declaration.	Documentation and declarations need traceable evidence and should be revisited when applicability, package, supplier or law changes. They are not stand-alone universal certificates.

Common mistakes

Mistake：Sending the customer one generic certificate labelled PPWR.

**Risk：**The customer, auditor or internal team cannot see which package, topic, period or evidence base it covers.

**Better approach：**Define the request first, then provide a package-SKU-mapped, topic-specific and evidence-traceable data set with stated limits.

Mistake：Treating a single heavy-metal or material report as complete PPWR proof.

**Risk：**Substances, PFAS, recyclability, recycled content, minimisation, labelling, reuse and document duties are improperly collapsed into one result.

**Better approach：**Assign the required data and available evidence to each PPWR topic, and identify what remains uncovered.

Mistake：Inventorying only sales packaging and omitting grouped or transport packaging.

**Risk：**A packaging level actually placed on the market or requested by the customer is absent from the product file.

**Better approach：**Create a full hierarchy and market-responsibility map, with separate material and weight data for every level.

Mistake：Treating recycled-content percentage, recyclability and PFAS as one type of test.

**Risk：**Different source data, calculations, design features and legal conditions are mixed into one unsupported file.

**Better approach：**Manage supplier data, calculation, testing, design record, assessment, technical documentation and declaration as distinct evidence types.

Mistake：Writing a 2030 target or future measure as a current due obligation on 2026-08-08.

**Risk：**The customer response can overstate timing and legal status.

**Better approach：**Separate applicable provisions, future dates, unadopted delegated or implementing measures and customer conditions in the response.

Mistake：Ignoring food-contact status and package use.

**Risk：**PFAS or food-contact-related evidence may be applied to the wrong package or omit the actually relevant scope.

**Better approach：**Flag food-contact use, contact surface and actual material at SKU level, then request supplier data accordingly.

Company action checklist

Create a PPWR customer-request register with the customer article, topic, package scope, market, deadline and document format.
Maintain a master file for sales, grouped and transport packaging SKUs and hierarchy, linked to product revision and market.
For every packaging SKU, collect composition, weight, polymer type, supplier, recycled content, food-contact status, PFAS, dimensions, empty space, artwork, labels and reuse information.
Tag every supplier statement, specification, calculation, report and design record with its version, sample, scope, data owner and limitation.
Use a PPWR topic matrix for substances, PFAS, recyclability, recycled content, compostability, minimisation, labelling, reuse, technical documentation, declaration of conformity and EPR.
Manage current applicability as of 2026-08-08, the 2026-08-12 general application date, 2030 requirements and future measures separately.
Assign owner and due date for each gap: supplier follow-up, calculation, design review, targeted testing, traceability or legal review.
Respond with a scoped statement of supported topics, assumptions, unresolved items and the next strengthening step.

Manager summary

A PPWR response should rest on a traceable package data set, not a search for one document that covers every topic. Leadership needs governance for SKU, hierarchy, material, weight, supplier, use and version data, then must allocate that evidence to the relevant PPWR topic and application date. Future 2030 requirements, later measures and evidence gaps should be disclosed and managed through an owned strengthening plan rather than presented as completed conclusions.

Frequently asked questions

Can we answer a customer PPWR certificate request with a company declaration?

First identify the customer’s article, package scope and topic. A company declaration may be part of the delivery, but it needs a package-SKU, material, evidence and applicability basis, with a clear statement of what it covers and does not cover.

Is one packaging heavy-metal report sufficient for PPWR?

Usually not. PPWR topics need different records. One report answers only its sample, method and analytes; it does not itself cover PFAS, recyclability, recycled content, minimisation, labelling, reuse, technical documentation or a declaration of conformity.

Was PPWR generally applicable on 2026-08-08?

Its general application date is 2026-08-12. The actual answer still depends on the individual provision, transitional arrangements, product, package and market. Keep future dates and unadopted measures separate from a current obligation.

Do all packaging levels need the same PPWR data?

Do not assume so. Sales, grouped and transport packaging can have different roles, materials, uses, market placement and customer requirements. Build the hierarchy first, then determine the data and evidence needed for each level.

Can a general product PFAS statement be reused for PPWR packaging?

Underlying material information may be useful, but food-contact use, the actual packaging material, customer definition and PPWR conditions need separate confirmation. Do not extend an unscoped statement to every package.

Can technical documentation and a declaration of conformity be completed before all data is available?

You can establish the record structure and gap list, but should not write missing material, calculation or assessment results as evidenced facts. Identify the source, version, scope, limitation and update work in the file.

Official legislation and reference material

Regulation (EU) 2025/40 on packaging and packaging waste (PPWR)

EUR-Lex / European Union

Legal status: Binding EU regulation. It entered into force in 2025 and is generally applicable from 12 August 2026, with provisions that have their own dates and transitional rules.
Last checked: 2026-08-08
Publication / update date: 2025-01-22 (Official Journal publication)
Used for: PPWR scope, substance requirements, PFAS for food-contact packaging, recyclability, recycled content, compostability, minimisation, labelling, reuse, technical documentation, declaration of conformity and application dates.

Packaging waste

European Commission — Environment

Legal status: Official European Commission policy and implementation information; use the regulation text for the binding legal requirement.
Last checked: 2026-08-08
Publication / update date: Publication/update date not stated on the linked official page; checked 2026-08-08.
Used for: Implementation context and the need to follow future Commission measures and guidance without treating future measures as already applicable.

Regulation (EC) No 1935/2004 on materials and articles intended to come into contact with food