Under the EU Packaging and Packaging Waste Regulation, the compliance question is no longer only "is my packaging compliant?" It is "can I prove it, on request, years after the packaging was placed on the market?" That is what PPWR documentation requirements govern. Regulation (EU) 2025/40 requires manufacturers, importers, and their supply chains to compile a technical file and an EU Declaration of Conformity for every packaging type, and to retain that evidence for 5 or 10 years depending on packaging type. This guide explains exactly which records must be kept, by whom, for how long, and how to make them retrievable when a market surveillance authority asks.

For compliance managers, QA leads, and document control teams, PPWR documentation requirements are the audit-defense layer of the regulation. Get the substance right but the recordkeeping wrong, and you still fail an inspection.

Key Takeaways

📄 PPWR documentation requirements center on two records per packaging type: the technical documentation (Annex VII) and the EU Declaration of Conformity (Annex VIII).

⏳ Retention is 5 years for single-use packaging and 10 years for reusable packaging, measured from the date the packaging was placed on the market.

📌 Regulation (EU) 2025/40 entered into force on 11 February 2025 and applies from 12 August 2026.

🔗 Manufacturers create the records; importers must verify they exist, keep a copy of the DoC, and be able to produce the technical file on request.

⚠️ Records must be made available to market surveillance authorities upon request, so retrievability, not just retention, determines audit outcomes.

🏭 Every packaging type needs its own DoC and technical file, which turns documentation into a portfolio-scale data problem for large manufacturers.

Table of Contents

1. What PPWR Documentation Requirements Actually Cover

2. Who Must Keep What: Roles and Responsibilities

3. How Long Must PPWR Records Be Kept

4. Inside the Technical File (Annex VII)

5. Inside the Declaration of Conformity (Annex VIII)

6. Producing Records on Request: The Audit Evidence Layer

7. Where Documentation Breaks Down at Scale

8. Enforcement Exposure and Business Risk

9. Building Audit-Ready PPWR Documentation

10. How AI and Certivo Support PPWR Recordkeeping

11. FAQs

What PPWR Documentation Requirements Actually Cover

Regulation (EU) 2025/40 replaced Directive 94/62/EC and applies directly across all EU member states from 12 August 2026, following an 18-month transition after entry into force on 11 February 2025, per EUR-Lex Regulation (EU) 2025/40. Two documents sit at the core of PPWR documentation requirements for each packaging type placed on the market.

• Technical documentation drawn up in accordance with Annex VII, which evidences how the packaging meets each applicable requirement.

• EU Declaration of Conformity (DoC) issued under Article 39 and modeled on Annex VIII, in which the manufacturer formally declares conformity.

Before packaging is placed on the market, the manufacturer must carry out the conformity assessment referred to in Article 38 (or have it carried out) and then compile these records. This mirrors the evidence logic behind related documents manufacturers already handle, such as a certificate of conformance. For the full regulatory context of the framework, Certivo maintains a dedicated PPWR framework overview.

Who Must Keep What: Roles and Responsibilities

PPWR assigns documentation duties by role, and the responsibility gap between who designs packaging and who is legally accountable is where most enterprise risk sits. The table below reflects the obligations set out in Regulation (EU) 2025/40.

One provision deserves board-level attention. Under Article 21, an importer or distributor that places packaging on the market under its own name or trademark, or modifies packaging in a way that affects compliance, is treated as the manufacturer and assumes the manufacturer's full documentation obligations. That reclassification often surprises private-label and retail operators. Structuring supplier and contractor management around these role definitions is the first step toward defensible recordkeeping.

PPWR documentation requirements retention periods of five and ten years by packaging type

Click on image to view full

How Long Must PPWR Records Be Kept

Retention is the part of PPWR documentation requirements most often underestimated. The regulation ties the retention period to packaging type, not to the calendar year, and the clock starts when the packaging is placed on the market.

These periods apply to manufacturers under Article 15 and to importers under Article 18(7), which requires importers to keep the DoC at the disposal of authorities and to ensure the technical documentation can be made available for the same 5 or 10 year windows, per EUR-Lex Regulation (EU) 2025/40. For long-lived reusable systems, a decade of retrievable evidence effectively requires a centralized system rather than spreadsheets that fragment as staff and vendors change.

Inside the Technical File (Annex VII)

Annex VII does not prescribe a fixed document format, but it does specify the substantive elements the technical file must cover to demonstrate conformity with each applicable PPWR obligation. Based on Regulation (EU) 2025/40, the file should assemble the following evidence for each packaging type.

• A general description of the packaging and its intended use.

• Conceptual design and manufacturing drawings, and plans of components, parts, and layers.

• Material composition of all components.

• Descriptions and explanations needed to understand the drawings and the operation of the packaging.

• A list of harmonized standards applied in full or in part.

• Results of design calculations, examinations, and test reports.

• Qualitative assessment of recyclability, minimization, and, where applicable, reusability, in line with the relevant articles.

Because the technical file must trace back to material composition, it connects directly to substance obligations, including the PFAS restriction on food-contact packaging that applies from 12 August 2026. Manufacturers already managing PFAS across the supply chain should fold that evidence into the PPWR technical file rather than maintaining it separately. Mapping documentation to the bill of materials, an approach Certivo supports through BOM-level compliance tracking, keeps material data and packaging evidence linked at the component level.

Inside the Declaration of Conformity (Annex VIII)

The DoC is a signed statement by the manufacturer that the packaging conforms with the applicable requirements of Regulation (EU) 2025/40. Annex VIII sets out the mandatory elements, which typically include a unique identification of the packaging type, the name and address of the responsible operator, an explicit reference to Regulation (EU) 2025/40, the object of the declaration, and the place, date, and signature of issue.

Two practical points matter for document control teams:

• One DoC per packaging type. A single blanket declaration across a portfolio does not satisfy the requirement.

• The DoC is event-driven, not annual. It remains valid until the packaging changes. If design, material composition, or supplier changes in a way that affects compliance, the conformity process must be repeated and the DoC reissued.

Note that PPWR does not use CE marking for packaging, because CE marks would be confused with product-level conformity. The DoC, backed by the technical file, is the conformity evidence.

Producing Records on Request: The Audit Evidence Layer

Retention alone is not the test. Both the DoC and the technical documentation must be made available to national market surveillance authorities upon request. According to European Commission guidance issued in 2026, the technical documentation should be made fully available within a short defined window of a request, so operators should confirm the applicable timeframe with the relevant authority and plan for rapid retrieval rather than reconstruction.

For a manufacturer with hundreds or thousands of packaging variants, "on request" reframes the problem. The challenge is not whether the evidence exists somewhere but whether the specific, correct version can be located, exported, and delivered quickly. This is a data and evidence architecture problem, and it is why audit readiness across frameworks depends on time-stamped, retrievable records rather than folders of static PDFs.

PPWR documentation requirements workflow from conformity assessment to audit response

Click on image to view full

Where Documentation Breaks Down at Scale

For a $10B manufacturer, PPWR documentation requirements expose predictable failure points that manual processes cannot absorb.

⚠️ Version control. When packaging changes, the old DoC must be superseded and the new evidence linked to the correct production window. Point-in-time accuracy is easy to lose in shared drives.

⚠️ Supplier evidence gaps. Material composition, recycled content data, and test reports originate upstream. Collecting them under Article 16 across many suppliers is the largest recurring burden.

⚠️ Portfolio scale. One DoC and one technical file per packaging type multiplies quickly across SKUs, regions, and reusable systems retained for a decade.

⚠️ Cross-framework overlap. Substance data feeds PPWR, PFAS restrictions, and EPR obligations at once, so duplicated or inconsistent records create contradictory audit trails.

Consolidating this into a centralized materials and environmental compliance system replaces fragmented recordkeeping with a single source of truth, and automated supplier documentation collection reduces the manual effort of chasing upstream evidence.

Enforcement Exposure and Business Risk

PPWR is enforced by member state market surveillance authorities, and consequences fall into four categories that leadership should weigh together.

The strategic point for the CFO and board is that documentation gaps convert a compliant product into a non-compliant market position. Packaging that meets every substantive requirement can still be blocked or penalized if the evidence cannot be produced on time.

Building Audit-Ready PPWR Documentation

A defensible program treats records as living evidence, not as a filing task completed once. The following steps align with PPWR documentation requirements and with standard document-control discipline.

1. Inventory packaging types. Establish a definitive list of every packaging type placed on the EU market and classify each as single-use or reusable to set the correct retention clock.

2. Assign roles. Confirm manufacturer, importer, and distributor status per Articles 15, 18, and 19, and flag any Article 21 reclassification for private-label lines.

3. Collect supplier evidence. Request material composition, recycled content, and test data under Article 16 through a standardized, repeatable process.

4. Compile the technical file per Annex VII and link it to the bill of materials for each packaging type.

5. Issue and control the DoC per Annex VIII, one per packaging type, with a reissue trigger on any material or design change.

6. Set retention and retrieval rules. Store records with time stamps and version history for the full 5 or 10 year window, and test how fast a specific file can be produced.

7. Rehearse the audit response. Simulate a market surveillance request to confirm the correct version is retrievable within the expected timeframe.

How AI and Certivo Support PPWR Recordkeeping

Manual, spreadsheet-based recordkeeping cannot sustain PPWR documentation requirements across a large portfolio for up to a decade. This is where a compliance system of record changes the operating model.

Certivo functions as a centralized compliance data backbone that links each packaging type to its technical file, DoC, and underlying supplier evidence at the BOM level. CORA-powered regulatory intelligence supports the workflow in three practical ways relevant to documentation and audit readiness:

• AI document parsing and certificate validation. CORA can read supplier declarations, test reports, and certificates, extract the relevant data, and flag missing or inconsistent evidence before it reaches an auditor.

• Automated supplier data collection. Supplier portals gather the Article 16 information manufacturers depend on, reducing email chasing and standardizing formats.

• Continuous, retrievable evidence. Time-stamped, version-controlled records support fast retrieval when authorities or customers request proof, shifting teams from reactive reconstruction toward continuous readiness.

The same evidence structure also supports adjacent obligations, including Digital Product Passport readiness and ESG and sustainability data collection, so PPWR documentation becomes reusable rather than siloed. Certivo does not make a company audit-proof; it reduces compliance surprises, improves evidence retrieval, and shortens response time.

Keep PPWR Documentation Audit-Ready

If your team is preparing packaging records for the 2026 deadline, a structured review of your current documentation and retention posture is the fastest way to find gaps before an authority does. Request a compliance review to assess how your PPWR technical files, Declarations of Conformity, and supplier evidence hold up under an audit request.