Electronics DPP Implementation Guide
How to assemble an Electronics Digital Product Passport against the published openepcis-dpp-ready electronics vocabulary
Overview
This guide walks through assembling an electronics DPP that uses only published vocabulary, meaning terms defined in the OpenEPCIS electronics ontology and the GS1 Web Vocabulary. It follows the canonical reference passports under extensions/eu/electronics/examples/ in the dpp-ready repository.
Conventions. In JSON-LD documents the property names are bare, because the JSON-LD context maps them to the right namespace. You write
"deviceCategory": "Smartphone", and the context resolvesdeviceCategorytoelectronics:deviceCategory. Controlled values likewise appear unprefixed once@vocabis set.
Prerequisites
- A GS1 Company Prefix and assigned GTINs for the products you'll passport.
- A resolver that can host the linkset for each Digital Link URL (see Resolver Setup).
- The electronics JSON-LD context:
https://ref.openepcis.org/extensions/eu/electronics/electronics-context.jsonld. - For battery-containing devices (smartphones, laptops, e-scooters), also the battery context. The cleanest pattern for composite products is to expose the embedded battery as its own resolvable DPP (see multi-component example).
Step 1: Identify the device
Every device gets a GS1 Digital Link URL: https://id.gs1.org/01/{GTIN}/21/{serial} for a serialised unit, or just /01/{GTIN} for SKU-level information. The same identifier becomes the id of the passport document and the epcList value in every EPCIS event.
The document carries two types, "type": ["Product", "Smartphone"], where the second one (Laptop, Display, Server, …) is drawn from electronics:DeviceCategory.
Step 2: Repairability with the French Index and the EU repairability class
The electronics vocabulary supports both repairability methods side by side.
The French Repairability Index is captured as an electronics:RepairabilityIndex block with one electronics:RepairCriterion per scored axis (Documentation, Disassembly, …). The published vocabulary defines electronics:RepairCriterionType. French regulation sets the weighting of each axis per product family, and that weighting stays outside the passport; the calculation tables and per-family weights are in the official French Repairability Index methodology.
The EU repairability class from the energy label for smartphones and tablets (Regulation (EU) 2023/1669) is captured as electronics:EURepairabilityClass with one of RepairClassA, RepairClassB, RepairClassC, RepairClassD, RepairClassE.
The replaceability of individual parts is expressed with electronics:ReplacementDifficulty (UserReplaceable, ToolRequired, ProfessionalOnly, NotReplaceable).
Step 3: Energy class and EPREL registration
electronics:EnergyEfficiency carries the labelling data. The class itself goes in electronics:EnergyEfficiencyClass (EnergyClassA … EnergyClassG), and the EU Product Registry for Energy Labelling reference goes in electronics:eprelRegistrationNumber. electronics:annualEnergyConsumption captures the declared annual figure when the regulation requires it (washing machines, dishwashers, refrigerators, TVs).
Step 4: WEEE registration (Annex III, six categories)
electronics:WEEECategory holds the controlled list of the six current categories from Annex III of the WEEE Directive 2012/19/EU:
WEEE1_TemperatureExchange: fridges, freezers, heat pumpsWEEE2_ScreensMonitors: TVs, monitors, displays > 100 cm²WEEE3_LampsWEEE4_LargeEquipment: any large appliance > 50 cmWEEE5_SmallEquipment: small appliances ≤ 50 cmWEEE6_SmallIT: small IT and telecom equipment ≤ 50 cm
The producer registration goes in electronics:weeeRegistrationNumber together with electronics:weeeRegistrationCountry. URLs of take-back and collection programs are referenced from the core DPP block dpp:EndOfLifeProgram.
Step 5: Spare-parts policy
electronics:SparePartsAvailability captures the number of years a manufacturer commits to keeping spare parts available, and electronics:SparePartsPricing captures the pricing policy. Each enumerated part is typed with electronics:ComponentType (BatteryComponent, DisplayComponent, etc.) and identified by electronics:componentPartNumber, and electronics:ReplacementDifficulty tags how hard it is to replace.
Step 6: Software support lifecycle
electronics:SoftwareSupport declares the support commitment with these fields:
electronics:firmwareVersion/electronics:osVersion: the versions currently installedelectronics:previousVersion/electronics:newVersion: used when recording an update eventelectronics:updateType: feature, security, bug fixelectronics:updateSource: provenance (OEM, OS vendor, …)
Each software update is captured as an EPCIS event that references these properties; software-update.jsonld in the reference EPCIS examples shows one.
Step 7: Component BOM
For laptops, servers and other complex devices, the component breakdown lives in electronics:ComponentBOM. Each entry is typed with electronics:ComponentType (BatteryComponent, CameraComponent, ConnectorComponent, CoolingSystemComponent, DisplayComponent, EnclosureComponent, KeyboardComponent, MemoryComponent, MicrophoneComponent, MotherboardComponent, PowerSupplyComponent, ProcessorComponent, SpeakerComponent, StorageComponent, TrackpadComponent) plus electronics:componentPartNumber and the replaceability info from Step 5.
Products that combine an electronic device with a separately regulated battery are best modelled with the multi-component pattern, in which the battery has its own GS1 Digital Link URL and its own passport. The multi-component example shows how.
Step 8: Publish the electronics linkset
The electronics passport is served from an IETF application/linkset+json document (RFC 9264), which holds one object per anchor identifier with GS1 link relations as full-IRI keys. A smartphone or laptop typically links to the consumer PIP, the EPCIS history (commissioning, repairs, software updates), the repair and service information, the carbon footprint and energy declaration, and the certification dossier:
{
"linkset": [
{
"anchor": "https://id.gs1.org/01/09521234000013/21/PHONE-2025-001",
"itemDescription": "EcoOS smartphone",
"https://ref.gs1.org/voc/defaultLink": [
{ "href": "https://dpp.example.com/electronics/09521234000013/PHONE-2025-001",
"title": "Electronics passport" }
],
"https://ref.gs1.org/voc/pip": [
{ "href": "https://dpp.example.com/electronics/09521234000013/PHONE-2025-001",
"title": "Electronics passport (consumer view)",
"type": "text/html",
"context": ["ALL"], "public": true }
],
"https://ref.gs1.org/voc/epcis": [
{ "href": "https://api.example.com/events?MATCH_anyEPC=https%3A%2F%2Fid.gs1.org%2F01%2F09521234000013%2F21%2FPHONE-2025-001",
"title": "EPCIS event history (commissioning, repair, software updates)",
"type": "application/ld+json",
"context": ["ALL"], "public": true }
],
"https://ref.gs1.org/voc/serviceInfo": [
{ "href": "https://dpp.example.com/service/09521234000013/PHONE-2025-001",
"title": "Repair information and spare-parts catalogue",
"type": "text/html",
"context": ["ALL"], "public": true }
],
"https://ref.gs1.org/voc/productSustainabilityInfo": [
{ "href": "https://dpp.example.com/sustainability/09521234000013/PHONE-2025-001",
"title": "Carbon footprint and EPREL energy declaration",
"type": "application/ld+json",
"context": ["ALL"], "public": true }
],
"https://ref.gs1.org/voc/certificationInfo": [
{ "href": "https://dpp.example.com/certs/09521234000013/PHONE-2025-001",
"title": "CE declaration, WEEE registration, conformity reports",
"type": "application/ld+json",
"context": ["business", "authority"] }
]
}
]
}
The ?linkType= parameter on a resolver URL takes the bare relation name (pip, serviceInfo, productSustainabilityInfo, …). Resolver Setup describes the hosting options.
Step 9: EPCIS events
The dpp-ready repository ships reference EPCIS events for the electronics lifecycle:
commissioning.jsonld: device commissioned, baseline metadata capturedownership-transfer.jsonld: sale or transfer to a new ownersoftware-update.jsonld: version transition recorded with previousVersion / newVersioncomponent-replacement.jsonld: repair event with the replaced ComponentType and the new partNumberweee-disposal.jsonld: end of life recorded against the WEEE category
All five follow the same EPCIS 2.0 pattern. Extension properties sit at event level outside masterDataAvailableFor, and the GS1-Extensions header declares the electronics= namespace.
Validation
A complete electronics DPP should pass three kinds of check:
- JSON-LD shape: the document normalises against the electronics context without unresolved terms or
@contextcollisions. - SHACL: the instance data satisfies the electronics shapes published with the vocabulary.
- JSON Schema: the payload validates against the electronics DPP schema, which also enforces the repairability index check (the criteria sum to the total, and the total lies between 0 and 100).
For EPREL registrations, the publishing workflow should also cross-check the published number against the EPREL Database.
Next steps
- Complete examples: links to the canonical smartphone, laptop, display and server passports
- Electronics vocabulary browser: the full ontology
- Multi-component example: products that combine an electronic device with a separately regulated battery