From raw material to retailer, every actor in your supply chain can sign a custody event. Each event is linked to the previous via a SHA-256 hash chain: tamper with the past, the future breaks. Export the whole trail as EPCIS 2.0 JSON-LD on one click.
EPCIS 2.0
Standard
ISO/IEC 19987
12
Event types
Mapped to CBV
SHA-256
Hash chain
Per-event linkage
JSON-LD
Export format
GS1 @context
A custody trail is only as strong as its weakest link. Fidaty's hash chain turns every event into a dependency on the previous one — tampering with any past record invalidates every subsequent event. Auditors, authorities and downstream partners can verify independently.
Farmers, processors, packagers, warehouses, shippers, customs agents, retailers — every actor adds an event to the certificate. Event types are standardised and mapped to the EPCIS 2.0 Core Business Vocabulary (CBV), ready for export.
harvested · processed · packed · stored · shipped · received · inspected · cleared_customs · delivered · damaged · repaired · other. Each mapped to the EPCIS bizStep and disposition URNs (urn:epcglobal:cbv:bizstep:…).
farmer · processor · packer · warehouse · shipper · customs · inspector · retailer · other. Roles drive UX colour-coding and analytics breakdowns.
Country, city, latitude/longitude. Plots on the map. Per-event audit context for authorities and downstream partners.
Every event stores (previous_hash, event_hash). The event_hash is SHA-256 over (prev_hash || payload). Rewriting a historical event forces every downstream hash to change, which is publicly detectable by any auditor.
First event anchors to a deterministic "genesis hash" derived from the certificate ID. Each subsequent event chains to the previous. Genesis-to-head hash chain is self-verifying.
The chain is rooted on the certificate, which is itself anchored on Blockchain. A forged event must alter the on-chain record — which requires breaking the blockchain.
Your logistics provider, customs agent or certification body doesn't need a Fidaty account. Generate a one-time invite link (14-day TTL), they submit their event from any browser, and it lands in the chain with their name & role.
Cryptographically random token, 14-day expiry, single-use. Email it or DM it. Partner opens the link, fills in their event (location, type, notes, evidence URLs), done.
Each event accepts a list of evidence URLs: photos, PDFs, certificates of analysis, bills of lading. Stored in the event payload, hashed into the chain, visible to auditors.
Authorities, retailers and platforms increasingly ask for EPCIS 2.0 as the canonical export format. Fidaty does the heavy lifting: the /custody page has a single "EPCIS" button that produces a valid EPCIS document with GS1 @context.
EPCISDocument, schemaVersion 2.0, eventList with eventID (urn:uuid), eventTime ISO UTC, epcList, bizStep, disposition, readPoint (geo:), bizLocation. Plus fidaty: extensions for actor + evidence.
Dedicated card in the DPP dashboard: count by event_type + bizStep + disposition, percentage of total, rolling 30-day window. Useful for circularity and sustainability reports.
Farm → processing → cold storage → distribution → retailer. Every step signs, every step traceable. FSMA-ready for the US market, EUDR-ready for commodities.
Auction house receives a collectible watch: custody chain with every inspector/shipper/customs signature. Buyer sees the full provenance before bidding.
Take-back programs: returned garment → repair partner → resale channel → next owner. Multi-cycle custody documented end-to-end.
Controlled-substance shipments: every touchpoint signs, every event hashed. Detecting diversion becomes a hash-chain integrity check.
Every service in the Fidaty platform is integrated with the rest: identity, compliance, analytics and consumer engagement flow seamlessly. No data silos, no duplicate work.
Book a demoChain of Custody is available on Advanced and Enterprise plans. Pilot on a single product line and expand across the portfolio.