A blockchain supply chain system records product events, such as made, shipped, received, inspected and sold, on a ledger that the companies in the chain share. Each company can then check where a product came from without trusting one partner's database.
This guide covers the goals of these projects, the system layers, the data problem, the rules that drive traceability, and the steps and cost drivers of a build. The ledger is rarely what makes a project fail; projects fail on inaccurate data or when competing companies refuse to join.
Four goals of a blockchain supply chain project
Most projects target one of four goals, and the goal decides the data, the partners and the ledger type.
- Provenance and authenticity. The system proves the origin of luxury goods, food or minerals to consumers and brands.
- Regulatory traceability. The system shows authorities the chain of custody, for example for medicines or for food recalls.
- Automation between companies. A smart contract releases a payment or a document when a shipment reaches a milestone.
- Sustainability reporting. The system supports claims about emissions, sourcing or recycled content.
Rules that drive traceability in 2026
New rules require companies to trace products, and these rules create most of the current demand. None of the rules requires a blockchain, but each requires data that a shared ledger can help collect and verify.
| Rule | What it requires | Date |
|---|---|---|
| EU Deforestation Regulation (EUDR) | Operators must prove that cattle, cocoa, coffee, palm oil, rubber, soy and wood products did not come from land deforested after 2020, with geolocation of the plots. | From 30 December 2026 for large and medium companies, and from 30 June 2027 for micro and small companies. Regulation (EU) 2025/2650 set these dates. |
| EU Battery Regulation (EU) 2023/1542 | EV batteries, light transport batteries and industrial batteries over 2 kWh need a digital battery passport with carbon footprint, recycled content and state of health data. | From 18 February 2027 |
| EU Ecodesign Regulation (ESPR) 2024/1781 | Digital Product Passports for further product groups, such as iron and steel, textiles and tyres, set by later delegated acts. | Product by product, from about 2027 |
| US FDA Food Traceability Rule (FSMA 204) | Companies that handle foods on the FDA Food Traceability List must keep key data elements for critical tracking events and supply them within 24 hours on request. | Enforcement from 20 July 2028, after a delay from January 2026 |
| US Drug Supply Chain Security Act (DSCSA) | Electronic, interoperable tracing of prescription drug packages. | In force, with phased exemptions; see the pharma guide |
The lesson from TradeLens
Maersk and IBM built TradeLens, a shipping data platform on blockchain, and launched it in 2018. In November 2022, Maersk announced that TradeLens would close by early 2023, saying the platform had not reached the industry-wide commercial collaboration it needed. Competing carriers did not want to put their data on a platform that a rival controlled.
The software worked, and the governance failed. A supply chain network needs a neutral governance model before it needs smart contracts, and common models are a consortium of members or an independent foundation.
Architecture of a traceability system
| Layer | Role | Typical choices |
|---|---|---|
| Identification | Gives each product, batch, location and party a unique ID | GS1 identifiers (GTIN, SSCC, GLN), GS1 Digital Link QR codes, RFID and NFC tags |
| Event capture | Records what happened, where, when and why | GS1 EPCIS 2.0 events from ERP and warehouse systems, scanners and sensors |
| Off-chain storage | Holds full event data and documents | Each partner's own systems, a shared database, or IPFS for public documents |
| Ledger | Stores event hashes, ownership transfers and permissions | A permissioned network such as Hyperledger Fabric, or a public chain or consensus service for hashes |
| Applications | Recall tools, consumer check pages, partner dashboards and APIs | Web apps and connectors to ERP and logistics platforms |
GS1 EPCIS 2.0 defines a common format for supply chain events, with a REST API and JSON-LD support. Many partners' systems already produce EPCIS events, and the standard also keeps your data portable if you change the ledger later.
For anchoring hashes, Hedera's consensus service charges a fixed fee in US dollars per message, so costs are predictable. The Hedera development guide covers that option. Data that only consortium members may see usually goes on a permissioned ledger, which the guide to Hyperledger development covers.
The data problem: a ledger also stores false records
A ledger proves that a record has not changed since someone wrote it, but it cannot prove that the record was true. If a supplier scans the wrong pallet or relabels fake goods, the blockchain keeps the false record. Teams use four controls to reduce this risk:
- Tamper-evident packaging and tags that are hard to copy.
- IoT sensors with their own device identity that report temperature, location and shock, as the guide to blockchain IoT describes.
- Cross-checks between independent parties, so a shipment marked as sent must also be marked as received.
- Audits and inspections linked to contract penalties.
Some projects link a physical item to a digital token to track changes of ownership, and the guide to NFTs for physical assets explains that design.
Blockchain supply chain development steps
- Pick one product line and one question, such as "where did this batch come from?", instead of the whole supply chain.
- Map partners and data owners and record what each partner will share and with whom.
- Agree on governance. Decide who runs nodes, who admits new members and who pays.
- Standardize the data with GS1 identifiers and EPCIS events.
- Build integrations with partners' ERP and warehouse systems, usually the largest part of the work.
- Run a pilot with a few partners and measure recall time, dispute rates or how often people check provenance. A focused proof of concept is a common first step.
- Scale once partners see value without a subsidy.
Cost and timeline drivers
A small team can build a technical pilot with a few partners in a few months, if the partners can export event data. A production rollout across a supply network often takes a year or more, because each partner needs an integration, a contract and training. The main cost drivers are:
- The number of partners and the state of their ERP and warehouse systems.
- Hardware such as tags, readers and sensors, priced per item or per site.
- Ledger operating costs: node hosting for a permissioned network, or transaction fees on a public chain.
- Ongoing work after launch: partner onboarding, support, governance meetings and audits.
When a shared database is the better choice
If one company controls the supply chain, a database run by that company is simpler, as with a vertically integrated firm or a dominant buyer that can require one platform. A ledger does not help when partners refuse to share data. A consumer-facing chain adds cost without value when consumers never check provenance.
Frequently asked questions
Should supply chain data go on a public blockchain?
Commercially sensitive data should not. A common design keeps the data off the chain and writes only hashes to a public chain, so anyone can check a record without seeing its content.
Can blockchain stop counterfeit products?
Blockchain helps only with physical identifiers that are hard to copy and with checks at the point of sale, because on its own a ledger records whatever it receives.
Do all suppliers need to run a node?
No. Small suppliers usually send events through an API or web portal that a larger member or a service provider runs, and the supplier then trusts that operator.
Does the EUDR or FSMA 204 require blockchain?
No. Both rules require traceability data and set no technology, and a blockchain is one way to share and verify that data between companies.