OpenEPCIS Overview

A GS1-conformant supply-chain data platform with Resolver, Masterdata and EPCIS Events, available in open source and business editions.

5 min read

OpenEPCIS

OpenEPCIS is a GS1-conformant supply-chain data platform. It exposes a GS1 Digital Link Resolver, hosts GS1 Web Vocabulary masterdata, and lets that masterdata be driven by EPCIS Events.

Three columns: data sources (PIM at model level, ERP at item level) feed OpenEPCIS through connectors into the EPCIS 2.0 repository, which drives the EU DPP compliance engine and the GS1-conformant resolver; the outputs are GS1 Digital Link sync to id.gs1.org, the digital product passport as web view and JSON-LD, and automated compliance reporting for ESPR, Battery and PPWR.Three columns: data sources (PIM at model level, ERP at item level) feed OpenEPCIS through connectors into the EPCIS 2.0 repository, which drives the EU DPP compliance engine and the GS1-conformant resolver; the outputs are GS1 Digital Link sync to id.gs1.org, the digital product passport as web view and JSON-LD, and automated compliance reporting for ESPR, Battery and PPWR.

The diagram shows a separation of concerns. The PIM and ERP a company already runs remain the source of truth for product and item data. OpenEPCIS sits between them and the outside world. Connectors take the data in, the EPCIS 2.0 repository keeps events in JSON-LD, the compliance engine maps them onto the CEN/CENELEC EN 182xx passport standards, and the GS1-conformant resolver serves the result under a GS1 Digital Link. The output is synced to id.gs1.org, shown as a digital product passport and reported against ESPR, the Battery Regulation and PPWR.

The platform rests on three pillars.

PillarWhat it does
ResolverResolves any GS1 Digital Link URI (GTIN, GLN, SSCC, …) to product information, masterdata, EPCIS endpoints and a dozen more GS1-standard link types. The deployment is also self-describing, so a downstream registry can find it and read what it offers without manual configuration.
MasterdataStores GS1 Web Vocabulary descriptions of products, organisations and places. Masterdata reaches the platform via REST (POST /organizations, /products, /places) and is kept out of EPCIS documents.
EventsCaptures, queries and streams EPCIS 2.0 events. Identifiers are stored in GS1 Digital Link canonical form. Subscriptions match events as they are indexed, without polling.

Editions

OpenEPCIS ships in two layers.

The open source layer (github.com/openepcis) provides the standards-conformant building blocks that anyone can build on: Maven BOM, EPCIS models, format converters, validators, identifier translator (EPC URN ↔ Digital Link), barcode renderer, event hash generator and test data generator. The GS1 Conformant Resolver itself is part of the business edition only; there is no open-source resolver today.

The business edition is the multi-tenant runtime that takes the OSS stack into production. It adds an OpenSearch-backed event store with native Document-Level Security, Keycloak-based identity (OIDC + API-key), an AS2 B2B gateway, GS1 Germany Activate Plus / GEPIR integration, Azure/AWS storage backends, an AI assistant and Terraform/Ansible deployment, delivered as thirteen Quarkus container images assembled from openepcis-build/.

What sets OpenEPCIS apart

1. Tenant isolation at the data layer

Most multi-tenant systems rewrite every database query to inject a tenant filter. OpenEPCIS forwards the authenticated user's identity into the OpenSearch transport layer, and the OpenSearch Security plugin's native Document-Level Security (DLS) enforces isolation at the data layer. Even a bug in the application code cannot expose another tenant's data. See Architecture → DLS.

2. Live subscriptions without polling

EPCIS streaming subscriptions are matched the moment an event is indexed, in the same engine that holds the events, and matches are delivered immediately via webhook or WebSocket. For clients that want polling semantics, such as nightly digests or periodic compliance pulls, scheduled (cron-based) subscriptions are available alongside streaming, and clients opt into them explicitly. See Modules → EPCIS Events.

3. A real participant in the GS1 trust graph

The platform integrates fully with the "Verified by GS1" services of GS1 Germany, in both directions. Inbound, it verifies GTIN / GLN identifiers against GS1 DE's registry (Activate Plus / GEPIR) and enriches the local record with authoritative attributes. Outbound, the brand owner's masterdata held in the deployment is published back through GS1 DE and propagates up to the GS1 Global Office resolver. The customer's deployment is the source of truth, and the global GS1 network reflects its content.

4. GS1 conformance, with a self-describing deployment

A deployment is discoverable by other systems out of the box. It publishes the self-describing document the GS1 Conformant Resolver standard expects at /.well-known/gs1resolver, so the GS1 Global Office resolver and partner registries can find and validate it automatically without manual configuration. When a product, organisation or place is saved, a dozen GS1-standard link types are derived automatically from the masterdata's referenced files, among them gs1:pip, gs1:productSustainabilityInfo, gs1:recallStatus, gs1:certificationInfo, gs1:productImage, gs1:safetyInfo, gs1:instructions, gs1:serviceInfo and gs1:nutritionalInfo. Identifiers are stored as GS1 Digital Link. See Modules → Resolver.

5. Wallet-agnostic Verifiable Credentials

Every environment runs a credential service with its own did:web issuer; on epc.is it signs as did:web:id.epc.is. It signs product passports, EPCIS event attestations and organisation identity anchors as W3C Verifiable Credentials (Data Integrity ecdsa-rdfc-2019, VC-JOSE), publishes status lists for revocation, and verifies credentials at a public endpoint. Wallets request these credentials through OID4VCI, authorised by the same Keycloak realm that handles sign-in; Keycloak itself issues employee and organisation membership credentials as SD-JWT VC.

On the presentation side the service is an OID4VP verifier. A role credential presented from a wallet yields a signed access receipt that the resolver accepts for AuthorizedOnly and Restricted fields, and every grant is written to a hash-chained audit log whose seals are public. OpenEPCIS does not ship a wallet and is not tied to one.

Issuance, verification, status lists, OID4VCI, the signed trusted issuer list and the audit checkpoints are available on epc.is today. Presentation is released and not yet deployed there, and tier unlock by presentation, Keycloak person credentials on epc.is and the EUDI reference wallet test are in preparation. See Signed Passports.


Developer summary

How the modules layer

Maven/Quarkus build topology from BOM anchor to container imagesMaven/Quarkus build topology from BOM anchor to container images

The Maven BOM defines the one version that matters, and every other module inherits it.

How OSS feeds the business edition

openepcis-build/ is the assembly point and consumes the OSS modules in two ways.

  1. As Maven dependencies for the libraries (models, BOM, document-converter, dl-translator, event-hash-generator, epcis-constants, test-resources, S3 utils).
  2. As git submodules for the modules that need source-level integration (resolver, REST/SOAP Quarkus apps, AS2 gateway, document-converter-sax, keycloak-api-key).

Business-only modules live under openepcis-build/modules/openepcis-core/ and are bundled by Quarkus profiles in quarkus-dist/ into the deployable containers. The same set of OSS jars sits underneath every business container; the business modules add the multi-tenant runtime, storage backends, and operational concerns.

The GS1 conformance loop (today and tomorrow)

EPCIS capture feeding repository, query/subscriptions and resolver linksetsEPCIS capture feeding repository, query/subscriptions and resolver linksets

The resolver already contains the plumbing for event-driven masterdata sync (MasterDataDomainEvent, MasterDataSyncEventExecutor). The bridge from /capture into that domain bus closes the loop.

Last updated: