Modules
Seven module families that organise the OpenEPCIS platform — Resolver, Masterdata, EPCIS Events, Formats & Validation, Integration, Testdata, Platform.
1 min read
The OpenEPCIS platform is organised into seven module families. Each family has its own page describing what it does, what's non-obvious about it, and the capabilities it ships in each edition.
| # | Family | What it does |
|---|---|---|
| 1 | GS1 Conformant Resolver | The platform's front door for GS1 identifiers — a scan resolves to product information, masterdata, EPCIS endpoints, and twelve more GS1 link types. |
| 2 | GS1 Web Vocabulary & Masterdata | The descriptive layer — who makes the product, where it's made, what regulations it meets, how it's described in GS1 Web Vocabulary. |
| 3 | EPCIS Events | EPCIS 2.0 capture, query, and live (non-polling) subscriptions. |
| 4 | Formats, Validation & Identity | XML ↔ JSON-LD conversion (XSLT in OSS, SAX-streaming in Business), multi-layer validation, idempotent event hashing. |
| 5 | Integration & Gateways | The perimeter — S3-compatible and Azure Blob storage, file service, AI assistant. |
| 6 | Testdata & Developer Tooling | Synthetic event generation, reference event collection, EPCIS REST conformance test suite, replay tool, multi-language SDK examples. |
| 7 | Platform, Build & Observability | How OpenEPCIS is built (one version anchor, thirteen container images), deployed (Terraform / Helm or Ansible / Docker Compose), and observed (OpenTelemetry). |
See also
- Feature matrix — capabilities by edition, grouped by these same seven families.
- Architecture — the four cross-cutting concerns that shape every module.
- Roadmap — strategic next steps.