Multi-Component DPPs: An E-Bike Walkthrough

How a composite product references separately-passported components via standard GS1 Digital Link and EPCIS aggregation

Overview

Complex products such as e-bikes, EVs and industrial equipment are made of parts that each have their own regulatory profile. A battery falls under EU 2023/1542, an electronic motor controller under WEEE and ESPR, and a leather saddle potentially under ESPR plus EUDR. A single monolithic passport holding all of this data quickly becomes a document that serves no audience well.

The cleaner pattern makes each component an identified, resolvable product in its own right. The composite product references its components by their Digital Link URLs, and consumers, recyclers, regulators and customs officers each follow the link they care about to a focused passport.

Status of this pattern. Component linking is an active topic in CIRPASS-2 and adjacent specs, and OpenEPCIS has no canonical property like dpp:hasPart yet. The worked example below therefore expresses the parent ↔ child relationship with EPCIS Aggregation events, which are part of the published EPCIS 2.0 spec and work today without new vocabulary.

The e-bike, by regulation

ComponentPrimary regulationDPP module that fits
FrameESPR 2024/1781DPP core
Battery packEU 2023/1542Battery DPP
Motor + controllerESPR + WEEEElectronics DPP
Leather saddleESPR (+ EUDR for the leather)Textile + EUDR
TiresFuture ESPR delegated actDPP core

Each row is an independently identifiable product with its own GTIN, serial, resolver entry and passport.

Pattern: composite product references components

The composite product gets one Digital Link URL. Its passport carries a short list of component URLs, and each of them resolves on its own to a focused passport built from the matching DPP module:

An e-bike passport linking its component passportsAn e-bike passport linking its component passports

The e-bike's own JSON-LD only needs the composite-level data (brand, model, dimensions, headline circularity claims) plus the list of component URLs. Each component URL is the canonical Digital Link of that component's passport, so component data lives in exactly one place.

Expressing the composition: EPCIS AggregationEvent

EPCIS 2.0 already models "X is made of Y, Z, …" as an AggregationEvent, which consists of a parentID plus a list of childEPCs. It makes the parent ↔ child relationship machine-readable today with published vocabulary only.

{
  "@context": ["https://ref.gs1.org/standards/epcis/epcis-context.jsonld"],
  "type": "EPCISDocument",
  "schemaVersion": "2.0",
  "epcisBody": {
    "eventList": [{
      "type": "AggregationEvent",
      "eventTime": "2025-01-25T14:00:00Z",
      "eventTimeZoneOffset": "+01:00",
      "action": "ADD",
      "bizStep": "assembling",
      "disposition": "active",
      "parentID": "https://id.gs1.org/01/09521234000010/21/EBIKE-2025-001",
      "childEPCs": [
        "https://id.gs1.org/01/09521234000027/21/BAT-EBIKE-001",
        "https://id.gs1.org/01/09521234000034/21/MOTOR-001",
        "https://id.gs1.org/01/09521234000041/21/SADDLE-001",
        "https://id.gs1.org/01/09521234000058/21/FRAME-001"
      ],
      "readPoint": { "id": "https://id.gs1.org/414/9521234000010" }
    }]
  }
}

When the e-bike is later disassembled, for example because a component is replaced under warranty or a recycler strips it for materials, the inverse event has the same shape with action: "DELETE". The components outlive the parent and are simply no longer aggregated to it. The EPCIS query API returns this history per serial.

What clients see at resolution time

Each audience gets a different view of the same product. A consumer who scans the e-bike receives the composite passport with brand, model, recycling instructions and links to the component passports, and can drill into the battery for its State-of-Health or into the saddle for its material composition. An authorised recycler who scans the same e-bike with credentials receives the same composite passport plus the access-controlled fields: the full BOM, hazardous-substance disclosures and the disassembly sequence.

Scanning a component directly leads straight to its own passport. A customs officer who scans the saddle sees the leather and EUDR passport with the EUIS reference, plot-of-origin coordinates and due-diligence statement. A battery technician who scans the battery gets the battery passport with the latest SoH event from the EPCIS query, without going through the e-bike.

Component-level resolution runs on the same Digital Link primitives as single-product resolution (Accept, ?linkType=, access tier). DPP Resolution Flow shows the end-to-end picture.

What the pattern buys you

Splitting the passport along component lines brings regulatory clarity, because each component lines up with a single regulation and its regulator. Components also keep an independent lifecycle: replacing a battery publishes a new component passport and an aggregation update, and the e-bike's main passport stays as it is. Payloads match their audience, so a consumer-grade UI carries no WEEE codes to hide and a recycler API carries no marketing description to skim past. For the circular economy, recovered components keep their full history of events, certifications and hazard data when they are aggregated into a new product.

What's left to standardise

The specs still disagree on a JSON-LD predicate that says "this composite passport references these component passports". CIRPASS-2 bridges, Catena-X industry-core and sector-specific drafts each propose their own shape. Until one is agreed, the EPCIS AggregationEvent shown above is the safest published way to express the relationship, and OpenEPCIS will follow whichever CIRPASS-2 or GS1 outcome becomes the standard.

Next steps