Implementation Guide
Step-by-step guide for implementing a GS1-native Battery Digital Product Passport with OpenEPCIS extensions
Masterdata and events. masterDataAvailableFor is a GS1 Web Vocabulary term and needs no gs1: prefix. It carries lot- or serial-level masterdata alongside an event: production batch, declaration references, incident records, regulatory citations. GTIN-level masterdata such as the product name or generic specifications belongs on the resolver, where it is POSTed once via POST /products/{gtin}, and must not be repeated in events. Extension vocabularies (battery:, eudr:, textile:, electronics:) keep their prefix and are declared in the document's @context.
Disclaimer: This guide is not official GS1 guidance. It follows official GS1 standards and best practices:
- GS1 Digital Link: resolvable URIs as identifiers
- EPCIS 2.0: event-based traceability
- GS1 Web Vocabulary: linked data terms
- CBV 2.0: bizStep and disposition values
Parties and locations are identified by GLN, products by GTIN plus serial number, and regulatory data uses the regulatoryInformation pattern from GS1 EUDR. Feedback is welcome.
Prerequisites
Before implementing the Battery DPP, ensure you have:
- GS1 Company Prefix (for GTIN assignment)
- GLN for your organization and facilities
- EPCIS 2.0 capable repository
- GS1 Digital Link resolver (or access to Verified by GS1)
Step 1: Assign GS1 Identifiers
Product Identification
- Assign GTIN to your battery product type:
GTIN: 09521234000013 - Assign Serial Numbers to individual units:
Serial: BAT2024-001 Full Digital Link: https://id.gs1.org/01/09521234000013/21/BAT2024-001
Organization Identification
- GLN for manufacturer:
Manufacturer GLN: 9521234000006 URI: https://id.gs1.org/417/9521234000006 - GLN for production facility:
Facility GLN: 9521234000013 URI: https://id.gs1.org/414/9521234000013
Device Identification
- GIAI for measurement devices (BMS, test equipment):
BMS GIAI: 9521987BMS-001 URI: https://id.gs1.org/8004/9521987BMS-001
Step 2: Create Product Master Data
Static battery information goes into a JSON-LD product master file:
{
"@context": [
{
"gs1": "https://ref.gs1.org/voc/"
},
{
"battery": "https://ref.openepcis.org/extensions/eu/battery/"
}
],
"@id": "https://id.gs1.org/01/09521234000013/21/BAT2024-001",
"@type": ["gs1:Product"],
"gtin": "09521234000013",
"serialNumber": "BAT2024-001",
"manufacturer": {
"@id": "https://id.gs1.org/417/9521234000006",
"@type": "gs1:Organization",
"organizationName": "Your Company Name",
"gln": "9521234000006"
},
"batteryCategory": { "@id": "battery:IndustrialBattery" },
"battery:technicalSpecifications": {
"@type": "battery:TechnicalSpecification",
"battery:ratedCapacity": {
"@type": "gs1:QuantitativeValue",
"value": "280",
"unitCode": "AH"
},
"battery:ratedEnergy": {
"@type": "gs1:QuantitativeValue",
"value": "14.3",
"unitCode": "KWH"
}
}
}
Required Fields per EU Battery Regulation
The EU Battery Regulation requires the following fields in the product master data.
| Field | Property | Required |
|---|---|---|
| Unique Identifier | @id | Yes |
| Manufacturer | gs1:manufacturer | Yes |
| Production Date | gs1:productionDate | Yes |
| Production Place | gs1:placeOfProductProvenance | Yes |
| Battery Category | batteryCategory | Yes |
| Battery Weight | gs1:netWeight | Yes |
| Rated Capacity | battery:ratedCapacity | Yes |
| Rated Energy | battery:ratedEnergy | Yes |
| Material Composition | battery:materialComposition | Yes |
| Hazardous Substances | battery:hazardousSubstances | Yes |
| Recycled Content | battery:recycledContent | Yes |
Step 3: Publish the battery linkset
The battery passport is exposed as an IETF application/linkset+json document (RFC 9264). The document holds one object per anchor identifier, with GS1 link relations as full-IRI keys and link descriptors as their values. A serialised battery typically links at least to the consumer Product Information Page, the EPCIS event history, the compliance certificates and the EU Battery Regulation conformity declaration:
{
"linkset": [
{
"anchor": "https://id.gs1.org/01/09521234000013/21/BAT2024-001",
"itemDescription": "EcoCell IM-500 industrial battery module",
"https://ref.gs1.org/voc/defaultLink": [
{ "href": "https://dpp.example.com/battery/09521234000013/BAT2024-001",
"title": "Battery passport" }
],
"https://ref.gs1.org/voc/pip": [
{ "href": "https://dpp.example.com/battery/09521234000013/BAT2024-001",
"title": "Battery 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%2FBAT2024-001",
"title": "EPCIS event history (SoH, shipping, recycling)",
"type": "application/ld+json",
"context": ["ALL"], "public": true }
],
"https://ref.gs1.org/voc/certificationInfo": [
{ "href": "https://dpp.example.com/certs/09521234000013/BAT2024-001",
"title": "EU Battery Regulation conformity & test reports",
"type": "application/ld+json",
"context": ["business", "authority"] }
],
"https://ref.gs1.org/voc/productSustainabilityInfo": [
{ "href": "https://dpp.example.com/sustainability/09521234000013/BAT2024-001",
"title": "Carbon footprint and recycled-content declaration",
"type": "application/ld+json",
"context": ["ALL"], "public": true }
]
}
]
}
The ?linkType= query parameter on the resolver URL takes the bare relation name (pip, epcis, certificationInfo, productSustainabilityInfo). Resolver Setup describes the hosting options.
Step 4: Integrate EPCIS Event Capture
Commissioning Event
The commissioning event records the creation of the battery. Following GS1 Germany EUDR Guideline V1.11, the event carries its product master data in masterDataAvailableFor and does not use ILMD for it:
{
"@context": [
"https://ref.gs1.org/standards/epcis/epcis-context.jsonld",
{ "battery": "https://ref.openepcis.org/extensions/eu/battery/", "gs1": "https://ref.gs1.org/voc/" }
],
"type": "EPCISDocument",
"schemaVersion": "2.0",
"epcisBody": {
"eventList": [{
"type": "ObjectEvent",
"eventID": "urn:uuid:YOUR-UUID-HERE",
"eventTime": "2024-03-15T14:30:00.000Z",
"eventTimeZoneOffset": "+01:00",
"epcList": ["https://id.gs1.org/01/09521234000013/21/BAT2024-001"],
"action": "ADD",
"bizStep": "commissioning",
"disposition": "active",
"readPoint": { "id": "https://id.gs1.org/414/9521234000013" },
"sensorElementList": [{
"sensorMetadata": {
"deviceID": "https://id.gs1.org/8004/9521234EOL-TEST-001"
},
"sensorReport": [
{ "type": "battery:stateOfHealth", "value": 100, "uom": "P1" },
{ "type": "battery:stateOfCharge", "value": 50, "uom": "P1" },
{ "type": "battery:cycleCount", "value": 0 }
]
}],
"masterDataAvailableFor": [{
"id": "https://id.gs1.org/01/09521234000013/21/BAT2024-001",
"battery:initialCapacity": { "value": "280", "unitCode": "AH" },
"lotNumber": "BATCH-2024-03-A"
}]
}]
}
}
Integration with BMS
The Battery Management System (BMS) can emit EPCIS events directly. The following function converts a BMS reading into a State of Health event:
// Example: BMS to EPCIS event conversion
function createSoHEvent(battery, bmsData) {
return {
"@type": "ObjectEvent",
"@id": `urn:uuid:${generateUUID()}`,
"eventTime": new Date().toISOString(),
"epcList": [{
"@id": battery.digitalLinkUri,
"masterDataAvailableFor": { "@id": battery.digitalLinkUri }
}],
"action": "OBSERVE",
"bizStep": "inspecting",
"sensorElementList": [{
"sensorMetadata": {
"deviceID": battery.bmsUri,
"time": new Date().toISOString()
},
"sensorReport": [
{ "type": "battery:stateOfHealth", "value": bmsData.soh, "uom": "P1" },
{ "type": "battery:stateOfCharge", "value": bmsData.soc, "uom": "P1" },
{ "type": "battery:cycleCount", "value": bmsData.cycles },
{ "type": "battery:internalResistance", "value": bmsData.resistance, "uom": "OHM" }
]
}]
};
}
Step 5: Handle Ownership Transfers
When ownership of a battery changes, an observation event records the previous and the new owning party together with the business transaction behind the transfer:
{
"@context": "https://ref.gs1.org/standards/epcis/epcis-context.jsonld",
"@type": "ObjectEvent",
"action": "OBSERVE",
"bizStep": "accepting",
"disposition": "in_transit",
"sourceList": [
{
"@type": "source",
"type": "owning_party",
"source": "https://id.gs1.org/417/9521234000006"
}
],
"destinationList": [
{
"@type": "destination",
"type": "owning_party",
"destination": "https://id.gs1.org/417/9521987000001"
}
],
"bizTransactionList": [
{
"@type": "bizTransaction",
"type": "po",
"bizTransaction": "https://buyer.example.com/orders/PO-2024-0089"
}
]
}
Step 6: Record Negative Events
Accidents, damage and safety incidents are recorded as negative events. The incident data, such as the incident ID and the recommended action, travels in masterDataAvailableFor:
{
"@context": [
"https://ref.openepcis.org/extensions/eu/battery/battery-context.jsonld",
"https://ref.gs1.org/standards/epcis/epcis-context.jsonld"
],
"type": "ObjectEvent",
"action": "OBSERVE",
"bizStep": "inspecting",
"disposition": "damaged",
"epcList": [
"https://id.gs1.org/01/09521234000013/21/BAT2024-001"
],
"battery:incidentSeverity": "Minor",
"sensorElementList": [
{
"sensorReport": [
{
"type": "battery:stateOfHealth",
"value": 93.8,
"uom": "P1"
}
]
}
],
"masterDataAvailableFor": [
{
"id": "https://id.gs1.org/01/09521234000013/21/BAT2024-001",
"battery:incidentId": "INC-2025-00023",
"battery:recommendedAction": "Continue monitoring. Schedule follow-up in 30 days."
}
],
"bizTransactionList": [
{
"type": "urn:epcglobal:cbv:btt:cert",
"bizTransaction": "https://example.com/incidents/INC-2025-00023.pdf"
}
]
}
Validation
Before publishing, check that each JSON-LD document normalises against the EPCIS and battery contexts. Each EPCIS event needs a unique event @id (UUID), correct bizStep and disposition values from the CBV, masterDataAvailableFor on its EPCs and UN/CEFACT Rec 20 unit codes.
Next steps
- Event Types: every EPCIS event type used by the Battery DPP
- Complete Examples: end-to-end commissioning, shipment and recycling flows
- Battery vocabulary browser: the live ontology