Every supply chain event — shipping, receiving, transforming, inspecting — captured in the four EPCIS dimensions (What, Where, When, Why) and written natively to ATSHI Transaction Chains. The global standard for supply chain visibility, made immutable.
EPCIS (Electronic Product Code Information Services) is the GS1 standard for capturing and sharing supply chain events. It defines a universal language for answering the fundamental questions about any product in any supply chain: what happened, where, when, and why.
Version 2.0 uses JSON-LD natively — which maps directly to ATSHI's structured data schemas validated at consensus. No translation layer, no middleware, no data transformation. The standard's data model and the blockchain's data model speak the same language.
Core Business Vocabulary (CBV) 2.0 provides standardized business steps: commissioning, shipping, receiving, transforming, inspecting, destroying. Every supply chain actor uses the same vocabulary, eliminating ambiguity across organizations, industries, and borders.
On ATSHI Network, every EPCIS event becomes a transaction on the product's chain — immutable, timestamped, cryptographically signed. The event cannot be altered after the fact. The signer cannot deny having created it. The timestamp is consensus-validated, not self-reported.
Combined with GS1 Digital Link: one QR code reveals the full event history from farm to shelf. Scan a product, see every event that ever touched it — every handoff, every inspection, every transformation — verified on-chain.
Every EPCIS event answers four fundamental questions. On ATSHI, every answer is immutable.
Which products or trade items are involved. GTIN, batch/lot number, serial number. Each identifier is linked to the product's on-chain identity — a Transaction Chain that accumulates every event across the product's entire lifecycle.
Product IdentityLocation of the event. GLN (Global Location Number), geo-coordinates, facility identifier. On-chain proof of location — the event is cryptographically bound to the declared location at the moment of capture.
Location ProofPrecise timestamp of the event. Immutable, consensus-validated. No backdating, no tampering. The network agrees on the time — not the reporter. A shipping event at 14:32 UTC stays at 14:32 UTC forever.
Consensus TimestampBusiness context. Business step (shipping, receiving, transforming) and disposition (in_transit, in_progress, recalled, active). CBV 2.0 standardized vocabulary ensures every actor across the supply chain speaks the same language.
Business ContextEPCIS 2.0 defines six event types that cover every supply chain interaction. Each one becomes an on-chain transaction.
An event involving one or more physical objects. The most common event type — observation, shipping, receiving. A batch of olive oil leaves the warehouse, a pallet arrives at port, an inspector checks a shipment.
Most CommonPacking objects into a container, loading a pallet, filling a truck. Parent-child relationships recorded on-chain. Open a case and the blockchain knows exactly which items are inside.
Parent-ChildLinking physical objects to business transactions — purchase orders, invoices, delivery notes. The physical flow and the business flow are bound together on the same chain.
Business BindingRaw materials in, finished product out. Cheese production, wine blending, pharmaceutical manufacturing. Input lots and output lots linked with full ingredient traceability.
Input → OutputAssociating a sensor, certificate, or device with a product. Temperature logger attached to a shipment. Lab certificate linked to a batch. Digital twin bound to a physical asset.
Device & Cert BindingEPCIS 2.0 allows vendor extensions. ATSHI adds on-chain proof, per-field encryption, and real-time event streaming. Standard-compliant with blockchain-native capabilities layered on top.
ATSHI EnhancedTraditional EPCIS repositories store events in databases. ATSHI writes them to the blockchain. The difference is fundamental.
Every EPCIS event is a blockchain transaction. Cannot be altered after the fact. Regulators get tamper-proof supply chain evidence — not exportable reports that could have been modified.
Tamper-ProofPublic traceability data alongside encrypted business-sensitive fields (pricing, supplier identity, internal quality scores) in the same event. AES-256-GCM at the field level — not all-or-nothing.
AES-256-GCMEvents trigger instant notifications via WebSocket, MQTT, Kafka, AMQP. Partners, regulators, and consumers see updates in real-time — not on the next polling cycle.
InstantMeets EU FMD (pharma serialization), EU food safety regulations, and US FSMA 204. The audit trail regulators demand — built in, not bolted on.
EU & US ReadyPartners read events scoped to their role. A retailer sees receiving events, a regulator sees inspection events, a consumer sees the simplified journey. Same chain, different views.
Role-ScopedEPCIS 2.0 uses JSON-LD. ATSHI's data layer validates JSON-LD schemas at consensus. No translation layer, no middleware, no data loss. The standard and the chain speak the same language.
Zero Translation| Capability | Traditional EPCIS Repository | ATSHI EPCIS On-Chain |
|---|---|---|
| Storage | Centralized database | On-chain Transaction Chains (immutable) |
| Data integrity | Database admin can modify | Cryptographically sealed, consensus-validated |
| Audit trail | Application-level logs | Every event is a verifiable transaction |
| Privacy | All-or-nothing access | Per-field AES-256-GCM encryption |
| Sharing | Point-to-point EDI / API | On-chain with role-scoped access |
| Real-time | Polling or webhook | Native event streaming (WebSocket, MQTT, Kafka) |
| Regulatory proof | Exportable reports | On-chain evidence, independently verifiable |
| Downtime | Single point of failure | Distributed across network nodes |
GS1 EPCIS 2.0 on ATSHI Network — the global standard for supply chain visibility, written to an immutable ledger with per-field encryption and real-time event streaming.