An Environmental Product Declaration (EPD) is a specific type of environmental declaration. They are used to quantify environmental information about a product’s life cycle. EPDs are increasingly appearing in procurement documents and supplier questionnaires. For suppliers, they are often part of the environmental disclosure infrastructure expected by international customers and export markets.
At the same time, EPDs are often misunderstood. They are sometimes treated as eco-labels or marketing tools, or even proof of regulatory compliance – in fact, they are none of these. When used correctly, they support informed decision-making and reduce the risk of greenwashing in complex supply chains. Understanding what EPDs can (and cannot) do is essential for manufacturers deciding how to invest in them.
An EPD is a Type III environmental declaration under the ISO 14025 system. It is used to report quantified, third-party verified product environmental impacts in a transparent way. An EPD is based on an ISO-compliant life cycle assessment (LCA).
Several features distinguish EPDs from other forms of environmental communication:
EPDs do not demonstrate regulatory compliance or certify environmental preference. Instead, they provide transparent and credible environmental disclosure.
EPDs are never developed in isolation. Each one must follow a Product Category Rule (PCR). In turn, each PCR defines how products within a specific category are assessed and reported.
A PCR specifies, among other things:
This is why EPDs are only meaningfully comparable when they are based on the same PCR. Nevertheless, comparisons must be made carefully. PCRs deliberately allow flexibility to reflect real-world differences in geography, energy supply, manufacturing technology, and data sources. Therefore, two EPDs may both be fully compliant and transparent, yet still reflect different underlying conditions.
Like EPDs, PCR framework is laid out by ISO 14025. Governance is often done by program operators or industry technical committees. Suppliers do not usually write PCRs themselves, though they must work within them.
Many PCRs are sector-specific and aligned with regional standards. For example, EN 15804 (+A2) plays a significant and influential role in the global construction sector. Understanding which PCR applies to your product (and what requirements it contains) is an important early step in any EPD project.
An EPD is derived from a life cycle assessment (LCA), but it is not the LCA itself. Instead, it is a standardised, externally verified summary of LCA results. Further, it is specially prepared for disclosure and reuse.
This distinction is significant in practice, as EPDs are frequently used as inputs to higher-level assessments. In these contexts, EPDs are valuable precisely because the underlying data has been independently verified. Well-crafted EPDs also document any assumptions and limitations clearly. Another benefit is a set of standardized impact categories throughout the PCR.
Many EPDs report results using a declared unit rather than a performance-based functional unit. This helps to reduce assumptions while improving verification and comparability. Long-term performance, on the other hand, is typically considered at the project or system level.
The ISO 14025 standard was designed to address credibility at scale. A single EPD can involve complex modelling and thousands of data points, allocation choices, and many assumptions. Without clear governance, two documents could appear comparable while being incompatible in their methods. For this reason, ISO 14025 requires both independent third-party verification and registration with a program operator.
Verification covers the underlying LCA and the EPD itself. This includes reviewing several aspects:
The result is a verification statement, often included directly in the published EPD.
A program operator (PO) provides the governance framework for an EPD program. While a PO does not calculate impacts itself, it is responsible for developing or adopting PCRs. They will also maintain rules for EPD format and content, before registering and publishing them. POs also approve and oversee verifiers, as well as helping with reviewing verification outcomes. When an EPD needs to be updated or withdrawn, or its validity period otherwise changes, it is the PO’s job to manage these tasks.
Importantly, an EPD that is not registered with a program operator is not valid under ISO 14025, regardless of how thorough it might appear.
Used correctly, EPDs provide risk reduction, auditability, and traceability. Used incorrectly, they can create a false sense of certainty or misleading comparisons. Recognising both the utility and the limits of an EPD is essential to using it effectively.
For Canadian suppliers, EPDs are best understood as a type of environmental disclosure infrastructure. They help bridge detailed technical analysis and credible external reporting, particularly when export markets or complex supply chains are involved. Developing your EPD requires careful interpretation of standards: selecting the appropriate PCR and collecting ample data are critical steps in ensuring a positive response from external verifiers and POs. A well-crafted EPD positions you to respond confidently to evolving disclosure expectations related to your product on the global stage.
An Environmental Product Declaration (EPD) is a fact sheet about a product’s environmental impacts. It shows measured data, not opinions or claims, and the numbers are checked by an independent third party. Think of it as a standardized way to say “here is the data” rather than “this is good” (or bad).
No. An EPD does not say a product is “green,” better than others, or compliant with regulations. It only shows verified environmental data so others can make their own decisions.
Enviropass summarizes the expectations as:
Supply chain mapping (beyond just Tier 1, prioritizing high-impact stages like wet processing/dyeing/finishing)
Public reporting on key environmental impact areas
A documented due diligence policy with accountability
Remediation thinking (not only disclosure)
Enviropass helps manufacturers and brands deliver credible Environmental Product Declarations (EPDs) by turning life-cycle data collection and reporting into a clear, evidence-based workflow. We support teams in defining product scope and PCR alignment, gathering defensible supplier and process data (materials, energy, transport, packaging), and standardizing inputs so results are consistent, comparable, and verification-ready. We also strengthen readiness for customer and bid requirements by building controlled EPD data files, setting update triggers for design or supplier changes, and translating LCA results into clear environmental indicators that stakeholders can trust.