Blockchain does not create a common language
Participants name the same object differently, maintain separate codes for locations, batches and operations, and record events at different levels of detail. Writing these messages to an immutable chain preserves the disagreement rather than resolving it.
Start with a shared vocabulary: tracked objects, identifiers for products, batches, logistic units, sites and parties, allowed business steps and mandatory fields for each event.
EPCIS describes the business event
GS1 EPCIS answers what, when, where, why and how something happened. It represents observation, aggregation into cases or containers, transformation of materials, custody transfer and related business context. EPCIS 2.0 adds JSON/JSON-LD, REST interfaces, sensor data and certification information.
It can therefore form the boundary between operational systems and a ledger. WMS, MES, TMS, ERP and IoT gateways create standardized events; blockchain attests the order and authorship of events that multiple organizations must verify.
Not every event belongs onchain
High-frequency telemetry, commercial documents and personal data should remain outside the ledger. Store the event identifier, hash of the exact payload, source signature, timestamp and agreed state onchain.
Sensor evidence also needs a protected device-to-gateway path: equipment identity, trusted time, range validation, offline buffering and replay protection. A hash cannot prove that a faulty sensor measured the correct temperature.
Bind certificates to objects and revisions
Origin, quality, calibration and sustainability certificates can change or be revoked. Keep the document in a controlled archive and reference its stable identifier, revision, issuer, validity interval and cryptographic digest in the event.
A verifier needs the certificate state at the time of the event, not merely proof that a document once existed. Corrections create a new revision or revocation record while preserving earlier evidence for audit.
Input quality matters more than immutability
Validate mandatory fields, allowed transitions, duplicates, time, signatures and sender authority before committing an event. Suspicious messages enter quarantine and cannot change batch state until reviewed.
Manual input needs dual confirmation and rationale. Integrations need schema contracts, a test environment, reference-data versions and observability. Every partner should pass compatibility tests before joining production.
Build the pilot around an investigation
Select one product flow and an expensive failure point: acceptance, cold-chain excursion, component origin or custody transfer. Prepare a discrepancy scenario and test whether the team can reconstruct object movement, the source of every fact and the certificate valid at that time.
Measure event completeness, publishing latency, quarantine rate, lot-isolation time, manual partner requests and investigation duration. Value appears when standardized evidence removes operational work, not simply when a diagram gains a blockchain component.