Improving logistics with EPCIS 2.0 and the CBV

The gateway framing matters for this topic: epcis.dev accepts an event only after validating it against GS1's own schema, stamps the capturing account — capturedBy, the warrantor, kept distinct from who, the attested observer — identifies it by its CBV 2.0 hash, and appends it to a store nothing rewrites. What follows stands on those mechanics.

The concrete gain is evidentiary, not cosmetic. Events validated at capture cannot drift from the standard; the CBV §8.9 hash makes a duplicate the same event and an edit a different one; and an append-only store means the answer to a later dispute, recall or audit is a chain of records that nobody — including the operator — could rewrite. The cost that disappears is the reconciliation meeting.

Custody is structural, not promised. No service identity holds an UPDATE or DELETE grant; the write path has exactly one writer and it can only append. You can add an event; you cannot un-write one, which is what makes a later trace evidentiary rather than merely stored.

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.

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