Blog

The Declaration of Conformity Isn’t a Document. It’s a Test of Your Data Infrastructure.

Posted on

June 4, 2026

• 

  Danielle Goad

  Director, EMEA

Packaging PPWR Specification Management Sustainability Sustainable Packaging

With the August 12 PPWR deadline looming, one requirement is emerging as the most urgent — and most revealing — challenge for packaging teams: the Declaration of Conformity (DoC).

Here’s the part many brand owners are still processing: under Article 3 of Regulation (EU) 2025/40, if packaging or a packaged product is designed or manufactured under your name or trademark, you are legally the manufacturer. That means you issue the DoC, you maintain the technical documentation, and you are the entity authorities come to when they want proof of compliance.

One critical clarification before we go further: the DoC is not submitted to a regulator.

It is drawn up, signed, and kept on file as part of your technical documentation — available upon request to market surveillance authorities, customs officials, distributors, and customers. There is no central registry to file with, no proactive submission. The obligation is to have documentation that holds up when someone asks for it. That distinction changes how you should think about preparation: the goal isn’t to file something by August. The goal is to be audit-ready, at any time, for any packaging type you’ve placed on the EU market.

The DoC is not a form you fill out. It is a legally binding written declaration — backed by evidence — confirming that each specific packaging type placed on the EU market complies with the sustainability requirements of Articles 5–12 of PPWR. Not every article is equally operative on day one — we cover what’s required now versus what phases in through 2030 and beyond later in this post. On paper, it sounds like a reporting task. In practice, it exposes something far more fundamental: whether your organization has the packaging specification data to back up the claims you’re making.

Most don’t. Not yet.

That’s not a criticism — it’s the reality. For most organizations, specification data lives in siloed systems, spreadsheets, and across teams, making it hard to structure, standardize, and share. PPWR is forcing companies to re-think how this critical data is managed. And the DoC is where that change hits hardest, first.

What the DoC Actually Requires

The DoC is mandatory for every packaging type placed on the EU market from August 12, 2026. There is no grace period. If packaging enters the EU market after that date, it must comply.

You are responsible for the full conformity assessment under Module A (internal production control, Annex VII). That means preparing technical documentation covering design, materials, recyclability assessments, and substance test results, then drawing up and signing the EU Declaration of Conformity per Annex VIII. No third-party notified body is required, but the person who signs assumes full legal liability for accuracy. 

Among other elements, the DoC must include: 

• a unique identification number for the declaration
• the manufacturer’s name, address, and contact details, or those of any authorised representative in the EU
• a statement that the declaration is issued under the sole responsibility of the manufacturer
• identification of the packaging type covered — sufficient description to enable traceability (e.g. packaging type, dimensions, materials, key components)
• a statement of conformity confirming the packaging meets the applicable requirements of Regulation (EU) 2025/40, referencing any other Union legislation that applies
• references to the harmonised standards, common specifications, or other technical specifications used to demonstrate compliance
• where applicable, the notified body — name, address, identification number — that performed the conformity assessment intervention, with details of the certificate(s) issued including date, duration, and conditions of validity
• place and date of issue; name, position, and signature of the authorised signatory

On scope: The DoC is required per packaging type, not per supplier. If you work with one converter who produces five different packaging formats for you, that’s five separate declarations — each with its own technical documentation.

It’s worth noting that interpretation of the regulation is still evolving. Major brands are actively debating whether DoCs should be pre-generated and dated ahead of August, or made available on demand per packaging type. The regulation’s intent supports an on-demand model, but regardless of how that debate settles, the underlying need is the same: structured, traceable packaging data that can support whichever documentation approach your organization chooses.

On retention: Once a packaging type has been placed on the EU market, its DoC and technical documentation must be retained for 5 years for single-use packaging and 10 years for reusable packaging. This means you need to be able to demonstrate compliance not just at today’s snapshot, but at any point in the product’s market history. As specifications change — materials, components, suppliers — you need a record of what was in the market when. A static file cannot do this. Versioned, timestamped specification records can.

This is not a one-time exercise. As PPWR requirements scale — recyclability thresholds tighten in 2030, recycled content mandates increase through 2040 — your DoC must stay current with each substantive change to a packaging type. It is a living obligation, and it is only as credible as the data that sits beneath it.

The Real Barrier: Specification Data That Isn’t DoC-Ready

Ask most packaging teams where their specification data lives today, and the answer is some version of the same story: partly in a PLM or ERP system, partly in spreadsheets, partly in supplier emails, partly in a shared drive that nobody fully maintains. R&D, procurement, sustainability, and regulatory — all working from different versions of the same information.

That model worked when compliance was simpler. It does not work for PPWR.

To produce a credible DoC – and to be able to produce it again two years from now when an authority requests it – you need:

• A single, authoritative record of what each packaging SKU is made of — materials, components, weights, dimensions, finishes
• Recyclability and composition data traceable to a source — live, granular, and accurate at the moment you need to report it
• Supplier-confirmed data, not internally assumed data
• Version control — so you know which specification was in market at which point in time, and can demonstrate compliance at any moment

The most common failure point right now is brand teams attempting to compile DoC documentation from fragmented data. The result is a painful manual process that produces a document nobody fully trusts — and has to be rebuilt from scratch every time something changes. This is not sustainable, nor scalable.

Centralizing your packaging specification data  into one system of record – accessible across R&D, procurement, sustainability, and regulatory — is the structural fix that makes the game more manageable.

Your Suppliers Hold Data You’re Legally Responsible For

A significant share of the evidence your DoC requires doesn’t originate with your team. It originates with your packaging converters and material suppliers — composition details, substance test results for PFAS and heavy metals, recyclability evidence. And you are accountable for the accuracy of all of it.

For most brand organizations, the process for collecting and validating that data is informal: email requests, one-off calls, PDFs in someone’s inbox. This fails PPWR on two fronts.

Scale. Fifty packaging formats means fifty declarations — each with its own supporting documentation. If your suppliers submit generic certificates rather than documentation specific to each packaging type, those documents don’t meet the regulatory checklist. Most suppliers don’t yet know this, which means the burden of educating and chasing them falls on you.

Currency. PPWR requires supplier data to be current, traceable, and updateable whenever packaging changes. A static PDF is not a compliance record. Building a structured supplier data process — with clear requirements, a shared submission framework, and a feedback loop that keeps supplier data synchronized with your specification records — is what separates brand teams that will produce credible DoCs from those that will produce documents they can’t fully stand behind.

Start that process now. Not at the deadline.

A note on higher-risk sectors: Certain industries face elevated audit exposure under PPWR. Food and beverage brands are under particular scrutiny given PFAS restrictions on food-contact packaging. E-commerce packaging faces specific rules around empty space. Cosmetics and personal care brands face close attention to recyclability claims. If your portfolio touches any of these categories, on-demand DoC readiness isn’t theoretical — it’s the scenario to plan for.

What DoC-Ready Infrastructure Actually Looks Like

The brand organizations ahead of the curve are not treating the DoC as a documentation exercise. They are treating it as a data infrastructure challenge — and building accordingly.

Start with your specification data, not your compliance gap. Before you can assess DoC readiness, you need to know what packaging specification data you actually have — and where it lives. Map your portfolio against what is documented, what is current, and what is missing or unverified. This exercise alone typically surfaces significant gaps: specs that haven’t been updated in years, regional variants that were never formally documented, material data that exists in supplier files but never made it into a centralized record.

Build for the retention requirement, not just for August. Every DoC and its supporting technical documentation must be retained for 5 to 10 years after a packaging type is last placed on the EU market. That means your infrastructure must be able to answer a question asked in 2035 about what your packaging was made of in 2026. Static files and spreadsheets cannot reliably support that. Version-controlled, timestamped specification records can — and this is a legal requirement, not an operational preference.

Build for change, not just for August. PPWR will eventually score packaging on a recyclability scale from A to E — but the exact cutoffs for each grade haven’t been finalized yet. The Commission has until January 2028 to lock those in (under Article 6(4)). In the meantime, packaging teams should use established standards like EN 13430:2004 or RecyClass to assess and document recyclability — these are the accepted methods right now, and they belong in your DoC. Once the PPWR grades are official, the bar starts rising: from 2030, only grades A, B, and C can enter the EU market. By 2038, only A or B. Recycled content targets for plastics also phase in from 2030, tightening further through 2040. The infrastructure you build now needs to carry you through all of it.

Version-controlled specifications are non-negotiable. You must be able to demonstrate what packaging was in-market at any given point in time – for compliance audits, for regulatory inquiries, and for your own 5-10 year documentation record. Static files don’t support this. Dated, managed, versioned specification records do.

What’s Coming from Specright

Each of the steps above is achievable manually — but not at scale, and not sustainably.

Specright’s Specification Data Management™ (SDM) platform is purpose-built for exactly this foundation: a single system of record for every packaging SKU, with materials, components, recyclability attributes, certifications, and supplier-confirmed data held in one structured, auditable environment. Version control, supplier collaboration, and reporting that draws from one source — not a mosaic of spreadsheets assembled at deadline time.

For teams already navigating PPWR, Specright’s sustainability capabilities deliver compliance visibility today — because they’re built on the specification records that drive them. When a material changes, teams see the downstream impact immediately: which markets it affects, whether it triggers a restriction or ban, and how it shifts eco-modulation fees by country. That’s proactive compliance, not reactive reporting. For extended producer responsibility specifically, our EPR Report Generator, powered by Lorax gives brand teams real-time visibility into EPR obligations across markets — without leaving the platform.

For teams managing PFAS compliance, documentation — test results, certifications, supplier declarations — sits directly against the specification records and suppliers it belongs to, with metadata tracking expiry dates and surfacing what needs attention before it lapses. You know which specs are covered, which suppliers have outstanding documentation, and when anything is due to expire — all within the platform.

This summer, Specright is releasing dedicated Declaration of Conformity capabilities — built for brand packaging and compliance teams that need to move from scattered documentation to a structured, auditable process.

The platform generates compliant DoC documents and Annex VIII audit dossiers directly from your spec data: material composition, weights, substance test reports, and supplier documentation, all structured for PPWR under Regulation (EU) 2025/40. A per-component readiness checklist tracks what’s confirmed, what’s outstanding, and what needs attention before your deadline. And across your full portfolio, coverage monitoring surfaces gaps at the SKU level — so you know your exposure before a regulator does.

If you’re building your DoC process now and want to see how Specright can accelerate it, reach out to our team.

Key Takeaways

The DoC is not submitted — it’s required on demand. Market surveillance authorities, customs, and distributors can request your documentation at any time. Audit-readiness is a permanent state, not a one-time filing.

The DoC is a data problem before it is a documentation problem. Specification data has to exist, be current, and be traceable before you can document anything credible.

The DoC is per packaging type — not per supplier. One supplier, five formats, five declarations. SKU-level tracking is the only tracking that holds up.

Your suppliers hold data you’re accountable for. Build the structured process to collect and validate it now. Generic certificates don’t meet the regulatory checklist.

Retention matters as much as generation. DoC documentation must be held for 5–10 years. Version-controlled, timestamped specifications are a legal requirement, not a best practice. August is the start, not the finish. PPWR scales through 2040. Build the infrastructure, not just the document.