---
title: "ESPR Framework"
description: "Guide to the EU Ecodesign for Sustainable Products Regulation (ESPR) 2024/1781 and how OpenEPCIS supports Digital Product Passport requirements."
canonical_url: "https://openepcis.io/docs/digital-product-passport/espr-framework"
last_updated: "2026-07-02T20:31:50.035Z"
---

## Building in the Open

**OpenEPCIS shares early.** The DPP standardization landscape is rapidly evolving—multiple EU initiatives, standardization bodies, and industry pilots are converging toward common requirements. Rather than waiting for all standards to finalize, we provide:

- **Early implementation** of emerging requirements from ESPR, CIRPASS2, and CEN/CENELEC JTC 24
- **Open-source vocabulary** that evolves alongside the standards
- **Practical examples** that help the community understand how DPP data actually works
- **Bridge contexts** for interoperability with other initiatives (BatteryPass, UNTP, etc.)

This approach lets implementers start building today while standards mature. As JTC 24 finalizes its specifications, we commit to aligning OpenEPCIS accordingly.

<alert type="warning">

**Living Standard**: OpenEPCIS v0.9.5 tracks the evolving DPP landscape. We publish early to gather feedback and enable pilots. Expect updates as European standards finalize.

</alert>

## What is ESPR?

The **Ecodesign for Sustainable Products Regulation (ESPR) 2024/1781** is a cornerstone of the EU's Circular Economy Action Plan. It replaces and significantly expands the previous Ecodesign Directive 2009/125/EC.

<alert type="info">

**Official Reference**: [ESPR Regulation 2024/1781](https://eur-lex.europa.eu/eli/reg/2024/1781) - Entry into force: July 18, 2024

</alert>

### Key Objectives

1. **Improve product sustainability** - Set requirements for durability, repairability, recyclability
2. **Enable informed choices** - Provide consumers with reliable product information
3. **Create level playing field** - Harmonize requirements across the EU single market
4. **Support circular economy** - Reduce waste and promote resource efficiency
5. **Combat greenwashing** - Standardize environmental claims

### Digital Product Passport (DPP)

ESPR introduces the **Digital Product Passport** as a mandatory requirement for products covered by delegated acts. The DPP is a structured data set that:

- Provides product information throughout its lifecycle
- Is accessible via a data carrier (QR code, NFC, RFID)
- Contains both public and restricted information
- Is interoperable across the EU
- Supports market surveillance and customs

## ESPR Key Requirements

The OpenEPCIS DPP framework provides classes and properties aligned with key ESPR articles:

<table>
<thead>
  <tr>
    <th>
      ESPR Article
    </th>
    
    <th>
      Requirement
    </th>
    
    <th>
      OpenEPCIS Support
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Article 7
    </td>
    
    <td>
      Performance & Durability
    </td>
    
    <td>
      <code>
        dpp:PerformanceInfo
      </code>
      
      , <code>
        dpp:RepairabilityInfo
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Article 7
    </td>
    
    <td>
      Material Composition
    </td>
    
    <td>
      <code>
        dpp:MaterialComposition
      </code>
      
      , <code>
        dpp:RecycledContent
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Article 8
    </td>
    
    <td>
      Substances of Concern
    </td>
    
    <td>
      <code>
        dpp:SubstanceOfConcern
      </code>
      
       (SCIP aligned)
    </td>
  </tr>
  
  <tr>
    <td>
      Article 9
    </td>
    
    <td>
      Access Rights
    </td>
    
    <td>
      <code>
        dpp:AccessRights
      </code>
      
      , <code>
        dpp:AccessLevel
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Article 77
    </td>
    
    <td>
      Economic Operator Registry
    </td>
    
    <td>
      <code>
        dpp:economicOperatorId
      </code>
      
       (EOID)
    </td>
  </tr>
</tbody>
</table>

## European Standardization: CEN/CENELEC JTC 24

**CEN/CENELEC JTC 24** is the official European standardization body for Digital Product Passports under ESPR. Established in 2023, JTC 24 develops the technical standards defining how DPPs work across the EU.

### Standards Landscape

<table>
<thead>
  <tr>
    <th>
      Standard
    </th>
    
    <th>
      Focus
    </th>
    
    <th>
      Status
    </th>
    
    <th>
      OpenEPCIS Alignment
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        prEN 17957
      </strong>
    </td>
    
    <td>
      DPP data model
    </td>
    
    <td>
      In development
    </td>
    
    <td>
      Tracking via CIRPASS2 coverage
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        EN 45552
      </strong>
    </td>
    
    <td>
      Durability assessment
    </td>
    
    <td>
      Published
    </td>
    
    <td>
      <code>
        dpp:expectedLifespan
      </code>
      
      , <code>
        dpp:usageCycles
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        EN 45553
      </strong>
    </td>
    
    <td>
      Remanufacturability
    </td>
    
    <td>
      Published
    </td>
    
    <td>
      <code>
        dpp:CircularityPerformance
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        EN 45554
      </strong>
    </td>
    
    <td>
      Repairability assessment
    </td>
    
    <td>
      Published
    </td>
    
    <td>
      <code>
        dpp:RepairabilityInfo
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        EN 45555
      </strong>
    </td>
    
    <td>
      Recyclability assessment
    </td>
    
    <td>
      Published
    </td>
    
    <td>
      <code>
        dpp:recyclableContent
      </code>
    </td>
  </tr>
</tbody>
</table>

### How We Track JTC 24

1. **CIRPASS/CIRPASS2** - These EU projects feed requirements directly into JTC 24. Our [CIRPASS2 coverage](https://github.com/openepcis/openepcis-dpp-ready/blob/main/extensions/common/interop/docs/CIRPASS2_COVERAGE.md) anticipates prEN 17957 requirements.
2. **Direct ESPR alignment** - JTC 24 standards implement ESPR. Our Article 7/8/9/77 coverage means we're building toward the same target.
3. **Methodology standards** - EN 45552-45555 define *how* to measure durability, repairability, etc. Our vocabulary provides *where* to store these assessment results.

### Why Not Wait for Final Standards?

The EU Battery Regulation requires DPPs starting **February 2027**. Other product categories follow shortly after. Industry needs to:

- Build IT systems now
- Train supply chain partners
- Pilot data exchange with trading partners
- Integrate with existing GS1/EPCIS infrastructure

OpenEPCIS provides a feature-complete vocabulary (pre-release), built on stable foundations (GS1, EPCIS 2.0) that can remain valid by providing final mapping, regardless of how prEN 17957 finalizes.

## ESPR-Aligned Classes

### Performance & Durability (Article 7)

Products must provide information about their expected lifespan and performance characteristics:

```json
{
  "@type": "dpp:PerformanceInfo",
  "dpp:expectedLifespan": {
    "@type": "gs1:QuantitativeValue",
    "value": "10",
    "unitCode": "ANN"
  },
  "dpp:usageCycles": 3000,
  "dpp:performanceClass": "A"
}
```

### Repairability (Article 7)

Products must disclose repairability information including spare parts availability:

```json
{
  "@type": "dpp:RepairabilityInfo",
  "dpp:repairabilityScore": 7.5,
  "dpp:repairabilityClass": "B",
  "dpp:sparePartsAvailability": {
    "@type": "gs1:QuantitativeValue",
    "value": "10",
    "unitCode": "ANN"
  },
  "dpp:diyRepairPossible": true
}
```

### Substances of Concern (Article 8)

Products must track hazardous substances per ECHA SCIP database alignment:

```json
{
  "type": "SubstanceOfConcern",
  "name": "Lead",
  "casNumber": "7439-92-1",
  "scipId": "SCIP-12345678",
  "substanceLocation": "Battery electrodes",
  "safeUseInstructions": "Avoid contact"
}
```

### Access Control (Article 9)

ESPR defines three access levels for DPP data:

<table>
<thead>
  <tr>
    <th>
      Access Level
    </th>
    
    <th>
      Who Can Access
    </th>
    
    <th>
      Example Data
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Public
      </strong>
    </td>
    
    <td>
      All users including consumers
    </td>
    
    <td>
      Product identification, manufacturer, recycling instructions
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        AuthorizedOnly
      </strong>
    </td>
    
    <td>
      Market surveillance, customs
    </td>
    
    <td>
      Test reports, compliance docs, supply chain details
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Restricted
      </strong>
    </td>
    
    <td>
      Specific authorized parties
    </td>
    
    <td>
      Trade secrets, proprietary formulations
    </td>
  </tr>
</tbody>
</table>

```json
{
  "@type": "dpp:AccessRights",
  "dpp:accessLevel": { "@id": "dpp:Public" }
}
```

### Economic Operator Registration (Article 77)

ESPR establishes a single EU-wide registry for economic operators with the Economic Operator ID (EOID):

```json
{
  "@type": "dpp:OperatorInformation",
  "dpp:economicOperatorId": "EOID-DE-2025-123456",
  "dpp:eoriNumber": "DE123456789012345",
  "operatorRole": { "@id": "dpp:Manufacturer" },
  "partyGLN": "9521234000006"
}
```

## Priority Product Categories

ESPR establishes priority sectors for DPP implementation:

<table>
<thead>
  <tr>
    <th>
      Category
    </th>
    
    <th>
      Status
    </th>
    
    <th>
      Timeline
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Batteries
      </strong>
    </td>
    
    <td>
      Pre-release
    </td>
    
    <td>
      February 2027 (first DPPs)
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Textiles
      </strong>
    </td>
    
    <td>
      Pre-release
    </td>
    
    <td>
      2028-2030
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Electronics
      </strong>
    </td>
    
    <td>
      Pre-release
    </td>
    
    <td>
      2028-2030
    </td>
  </tr>
  
  <tr>
    <td>
      Furniture
    </td>
    
    <td>
      Future
    </td>
    
    <td>
      TBD
    </td>
  </tr>
  
  <tr>
    <td>
      Tyres
    </td>
    
    <td>
      Future
    </td>
    
    <td>
      TBD
    </td>
  </tr>
  
  <tr>
    <td>
      Construction Products
    </td>
    
    <td>
      Future
    </td>
    
    <td>
      TBD
    </td>
  </tr>
</tbody>
</table>

<alert type="success">

**Ready Now**: The [Battery DPP](/docs/digital-product-passport/battery-dpp), [Textile DPP](/docs/digital-product-passport/textile), and [Electronics DPP](/docs/digital-product-passport/electronics) modules are at v0.9.5 (pre-release, feature-complete for pilot use).

</alert>

## GS1-Extensions HTTP Header

All OpenEPCIS DPP extensions are first-class EPCIS 2.0 extensions per Section 12.3. Declare them in HTTP requests:

```http
POST /capture HTTP/1.1
Content-Type: application/ld+json
GS1-Extensions: dpp=https://ref.openepcis.io/extensions/common/core/
```

With product-specific extensions:

```http
GS1-Extensions: dpp=https://ref.openepcis.io/extensions/common/core/, battery=https://ref.openepcis.io/extensions/eu/battery/
```

## Optional: GS1 Shortcuts Context

For cleaner JSON-LD syntax with GS1 RegulationTypeCode values, include the optional shortcuts context:

**Without shortcuts** (standard GS1 syntax):

```json
"regulationType": { "@id": "gs1:RegulationTypeCode-BATTERY_DIRECTIVE" }
```

**With shortcuts** (include `gs1-shortcuts-context.jsonld`):

```json
{
  "@context": [
    "https://ref.openepcis.io/extensions/common/core/dpp-core-context.jsonld",
    "https://ref.openepcis.io/extensions/common/core/gs1-shortcuts-context.jsonld"
  ],
  "regulatoryInformation": {
    "regulationType": "BATTERY_DIRECTIVE",
    "regulatoryAct": "EU 2023/1542"
  }
}
```

Available shortcuts: `BATTERY_DIRECTIVE`, `DEFORESTATION_REGULATION`, `ROHS_DIRECTIVE`, `WEEE_DIRECTIVE`, `REACH`, `CE_MARKING`, `CE`, `E_MARK`, `ECODESIGN_DIRECTIVE`, `LVD_DIRECTIVE`, and more.

## How OpenEPCIS covers ESPR

### ESPR article coverage

<table>
<thead>
  <tr>
    <th>
      ESPR article
    </th>
    
    <th>
      OpenEPCIS implementation
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Article 7 — performance & durability
    </td>
    
    <td>
      <code>
        dpp:PerformanceInfo
      </code>
      
      , <code>
        dpp:RepairabilityInfo
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Article 8 — substances of concern
    </td>
    
    <td>
      <code>
        dpp:SubstanceOfConcern
      </code>
      
       with SCIP alignment
    </td>
  </tr>
  
  <tr>
    <td>
      Article 9 — access rights
    </td>
    
    <td>
      Three-tier <code>
        dpp:AccessLevel
      </code>
      
       enumeration
    </td>
  </tr>
  
  <tr>
    <td>
      Article 77 — Economic Operator registration
    </td>
    
    <td>
      <code>
        dpp:economicOperatorId
      </code>
      
       with role enumeration
    </td>
  </tr>
  
  <tr>
    <td>
      Circularity metrics
    </td>
    
    <td>
      <code>
        dpp:CircularityPerformance
      </code>
      
       (UNTP-aligned)
    </td>
  </tr>
  
  <tr>
    <td>
      Carbon footprint
    </td>
    
    <td>
      <code>
        dpp:EmissionsPerformance
      </code>
      
       (UNTP-aligned)
    </td>
  </tr>
</tbody>
</table>

### Built on existing infrastructure

ESPR requires "a data carrier on the product" — typically a QR code or RFID tag. OpenEPCIS uses **GS1 Digital Link**, which is already issued by GS1 member organisations and resolved by existing GS1 Digital Link resolvers. No parallel identifier scheme or new resolver infrastructure is required.

### Supply-chain traceability via EPCIS 2.0

The DPP is not only a product description — ESPR expects traceability across the lifecycle. OpenEPCIS captures lifecycle steps as EPCIS 2.0 events:

- **Commissioning** — the product comes into existence
- **Shipping** — movement between supply-chain locations
- **Transformation** — manufacturing, assembly, recycling
- **Inspection** — quality checks, certifications, State of Health

Identifiers reference the resolver; events stay lean (see the [DPP intro page](/docs/digital-product-passport) for the masterdata / events split).

### Multi-regulation overlays

Products often fall under more than one regulation. OpenEPCIS composes module contexts so a single product description can satisfy several:

<table>
<thead>
  <tr>
    <th>
      Product
    </th>
    
    <th>
      Regulations
    </th>
    
    <th>
      OpenEPCIS modules
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      EV battery
    </td>
    
    <td>
      ESPR + Battery Regulation 2023/1542
    </td>
    
    <td>
      <code>
        dpp:
      </code>
      
       + <code>
        battery:
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Smartphone
    </td>
    
    <td>
      ESPR + WEEE + RoHS
    </td>
    
    <td>
      <code>
        dpp:
      </code>
      
       + <code>
        electronics:
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Cotton shirt
    </td>
    
    <td>
      ESPR + EUDR + Sustainable Textiles
    </td>
    
    <td>
      <code>
        dpp:
      </code>
      
       + <code>
        eudr:
      </code>
      
       + <code>
        textile:
      </code>
    </td>
  </tr>
</tbody>
</table>

## OpenEPCIS DPP Modules

The OpenEPCIS DPP framework implements ESPR requirements through modular vocabularies:

### Core Module

Provides shared ESPR-aligned patterns used across all product categories:

- **Namespace**: `https://ref.openepcis.io/extensions/common/core/`
- **Browse**: [ref.openepcis.io/extensions/common/core/](https://ref.openepcis.io/extensions/common/core/)

### Product-Specific Modules

<table>
<thead>
  <tr>
    <th>
      Module
    </th>
    
    <th>
      Regulation
    </th>
    
    <th>
      Namespace
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <a href="/docs/digital-product-passport/battery-dpp">
        Battery
      </a>
    </td>
    
    <td>
      EU 2023/1542
    </td>
    
    <td>
      <code>
        https://ref.openepcis.io/extensions/eu/battery/
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/digital-product-passport/eudr">
        EUDR
      </a>
    </td>
    
    <td>
      EU 2023/1115
    </td>
    
    <td>
      <code>
        https://ref.openepcis.io/extensions/eu/eudr/
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/digital-product-passport/textile">
        Textile
      </a>
    </td>
    
    <td>
      EU Sustainable Textiles
    </td>
    
    <td>
      <code>
        https://ref.openepcis.io/extensions/eu/textile/
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/digital-product-passport/electronics">
        Electronics
      </a>
    </td>
    
    <td>
      ESPR + WEEE + French Repairability
    </td>
    
    <td>
      <code>
        https://ref.openepcis.io/extensions/eu/electronics/
      </code>
    </td>
  </tr>
</tbody>
</table>

## Implementation Timeline

<table>
<thead>
  <tr>
    <th>
      Date
    </th>
    
    <th>
      Milestone
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      July 2024
    </td>
    
    <td>
      ESPR enters into force
    </td>
  </tr>
  
  <tr>
    <td>
      February 2027
    </td>
    
    <td>
      First DPPs operational (batteries)
    </td>
  </tr>
  
  <tr>
    <td>
      2028-2030
    </td>
    
    <td>
      Textiles, electronics, furniture
    </td>
  </tr>
  
  <tr>
    <td>
      2030+
    </td>
    
    <td>
      Additional product categories
    </td>
  </tr>
</tbody>
</table>

## Resources

### OpenEPCIS Documentation

- [Battery DPP Implementation Guide](/docs/digital-product-passport/battery-dpp/implementation-guide)
- [EUDR Implementation Guide](/docs/digital-product-passport/eudr/implementation-guide)
- [Textile DPP Implementation Guide](/docs/digital-product-passport/textile/implementation-guide)
- [Electronics DPP Implementation Guide](/docs/digital-product-passport/electronics/implementation-guide)
- [OpenEPCIS DPP-Ready Repository](https://github.com/openepcis/openepcis-dpp-ready)

### Vocabulary Browsers

- [Core DPP Vocabulary](https://ref.openepcis.io/extensions/common/core/)
- [Battery Vocabulary](https://ref.openepcis.io/extensions/eu/battery/)
- [EUDR Vocabulary](https://ref.openepcis.io/extensions/eu/eudr/)
- [Textile Vocabulary](https://ref.openepcis.io/extensions/eu/textile/)
- [Electronics Vocabulary](https://ref.openepcis.io/extensions/eu/electronics/)

### External References

**EU Regulation & Standards**

- [ESPR Regulation 2024/1781](https://eur-lex.europa.eu/eli/reg/2024/1781)
- [CEN/CENELEC JTC 24](https://www.cencenelec.eu/areas-of-work/cen-cenelec-topics/sustainable-development/digital-product-passports/) - European DPP standardization
- [EN 45552-45555](https://standards.cencenelec.eu/) - Durability, repairability, recyclability methodology standards

**Industry Initiatives**

- [GS1 DPP Standards](https://ref.gs1.org/standards/dpp/)
- [CIRPASS Project](https://cirpassproject.eu/) - EU DPP pilot requirements
- [UN Transparency Protocol](https://uncefact.github.io/spec-untp/) - Global DPP interoperability

**Regulatory Databases**

- [ECHA SCIP Database](https://echa.europa.eu/scip) - Substances of Concern
- [EU EPREL](https://eprel.ec.europa.eu/) - Energy Product Registry