GS1 Conformant Resolver
Resolves GS1 Digital Link URIs to product information, masterdata, EPCIS endpoints, and twelve more standard link types.
The Resolver is the platform's entry point. When someone scans a Digital Link QR on a product, the resolver returns the right URL for the purpose: the product page for a shopper, the EPCIS event history for a recycler or auditor, the recall status for a market-surveillance officer, the certification dossier for a regulator. One URL gives each audience its own answer.
OpenEPCIS implements the GS1 Conformant Resolver standard end to end, so the deployment is self-describing. It publishes a discovery document at the spec-mandated path /.well-known/gs1resolver, where the GS1 Global Office resolver and partner registries can find it and read what it offers without manual configuration.
Save a product to the resolver and a dozen standard GS1 link types are derived from its masterdata fields with no extra POST: gs1:pip, gs1:productImage, gs1:audioFile, gs1:relatedVideo, gs1:safetyInfo, gs1:certificationInfo, gs1:nutritionalInfo, gs1:instructions, gs1:recallStatus, gs1:serviceInfo, gs1:productSustainabilityInfo. The bulk endpoint handles tens of thousands of products in a single multipart CSV or JSON-LD call for first-time onboarding.
Everything else on the platform is discovered through the resolver. A scanned identifier resolves here, and the resolver points on to the masterdata record and the EPCIS endpoint that hold the rest of the information. The resolver is what makes Web Vocabulary masterdata reachable by URI and ties EPCIS events back to a product or place.
The open-source pieces in the Resolver group are libraries for URN ↔ Digital Link translation, barcode rendering and identifier validation. The full resolver service ships in the Business edition: multi-tenant, secured by Keycloak, discoverable under the conformance standard and populated automatically from masterdata.
Capabilities by edition
| Capability | OSS | Business |
|---|---|---|
| GS1 Conformant Resolver service | — | ✓ |
| Self-describing deployment (GS1 Conformant Resolver standard) | — | ✓ |
| Auto-derived linksets (a dozen GS1 link types) | — | ✓ |
| Bulk CSV / JSON-LD import | — | ✓ |
| Tenant-scoped masterdata cache | — | ✓ |
| Linkset change audit | — | ✓ |
| EPC URN ↔ Digital Link translation (library) | ✓ | ✓ |
| QR / Data Matrix / GS1-128 barcode generation (library) | ✓ | ✓ |
REST surface
| Method | Path | Auth | What it does |
|---|---|---|---|
GET | /.well-known/gs1resolver | none | Resolver discovery document |
GET | /{primary-key}/{value} (e.g. /01/04012345999990) | none / cap-token | Resolve a GS1 identifier → linkset |
GET | /{pk}/{value}/{qual}/{qv} | none / cap-token | Resolve a qualified identifier (e.g. /01/<gtin>/21/<serial>) |
POST | /organizations/{gln} | OIDC / API-key | Create / update organisation masterdata |
POST | /products/{gtin} | OIDC / API-key | Create / update product masterdata (auto-derives linksets) |
POST | /places/{location-id} | OIDC / API-key | Create / update place masterdata |
POST | /bulk/products | OIDC / API-key | Bulk CSV / JSON-LD import |
See also
- Modules → Masterdata: where the linksets the resolver returns come from.
- Architecture → GS1 conformance contract: the platform-wide rule that masterdata lives on the resolver and stays out of EPCIS events.
- Feature Matrix → Resolver.