EPCIS for the Pulp and Paper Industry: An Overview

Whatever brought you to this page, the standard underneath it is EPCIS 2.0 — GS1's model for supply-chain event data — and the discipline underneath the standard is a door: epcis.dev validates each event against GS1's own schema, stamps the capturing account (capturedBy, the warrantor, kept distinct from who, the attested observer), hashes it by CBV 2.0, and appends. Everything below assumes that door.

Start with the model. An EPCIS 2.0 event answers five questions about one observed moment: what objects were seen, when, where, why (the business step and disposition, drawn from the CBV — the Core Business Vocabulary), and how (sensor data, where instruments were involved). Events are captured over one standard interface, queried over another, and identified by the CBV 2.0 §8.9 hash of their own content. That is the whole standard in one paragraph; almost everything else is vocabulary, and the CBV is that vocabulary.

Ten years of vendor XML has a path forward: EPCIS 1.1, 1.2 and 2.0 XML in, EPCIS 2.0 JSON-LD out, with a round-trip fidelity report per job so the translation is something you review rather than something you trust. That translator answers at POST /translate on this origin.

Reads are minimally scoped. You see your own scope; what is outside it is absent, not greyed out and not redacted, so there is no shape left behind to argue about. Recording an event is $0 by policy — intent, until published terms bind it — because a stream that charges per event is one you stop feeding the month the bill grows with volume.

Provenance: an aged epcis.dev page, kept at its original URL and refreshed into the current design on 15 August 2026.

Proof, not adjectives. The gateway's conformance tests pass against GS1's normative artifacts, and the calculators answer on this origin — POST /translate, /validate, /hash, no key. The dated ledger is What ships today.