Blockchain Project

Supply Chain Traceability System

A blockchain provenance platform that tracks a product from origin to retail with QR-based consumer verification.

Advanced8–10 weeksCSE · IT · MCABlockchainFull Stack Development

Project overview

Each participant in a supply chain — producer, processor, distributor, retailer — records a custody event against a product batch on-chain. A consumer scans the QR code on the package and sees the complete verified journey with timestamps.

The project is convincing because provenance is exactly the case where a shared ledger between mutually distrusting parties beats one company's private database.

Problem statement

Provenance claims on food and medicine packaging cannot be checked by the buyer. Each company keeps its own records, and in a contamination or counterfeiting incident nobody can reconstruct the chain quickly.

Proposed solution

Register batches on-chain at origin and append a custody event at each handover, with participant roles enforced by the contract. Keep certificates and images off-chain in IPFS with only their hashes recorded, and expose the assembled history through a public QR-linked page.

Key features

  • Role-based participant registration for each supply chain stage
  • Batch creation at origin with product and quantity metadata
  • Custody transfer events with actor, timestamp and location
  • Temperature and condition logging for cold chain segments
  • QR code per batch linking to a public traceability page
  • Certificate and image storage on IPFS with on-chain hashes
  • Recall workflow that flags an affected batch across all holders

Technology stack

Contracts

SolidityHardhatOpenZeppelin AccessControlEvents for indexing

Network

Polygon AmoySepolia testnetGanache

Client

Reactethers.jsQR generation and scanning

Off-chain

IPFS via PinataNode.js event indexerPostgreSQL

System architecture

The flow below is what goes into your architecture diagram and the corresponding chapter of the report.

  1. Producer creates a batch, generating a unique on-chain identifier
  2. Each handover calls a transfer function that verifies the caller's role
  3. Events emitted per transfer are indexed off-chain for fast queries
  4. Documents and images are pinned to IPFS with hashes stored on-chain
  5. Consumer scans the QR code and loads the assembled history
  6. Recall function marks a batch and surfaces every downstream holder

Expected output

  • Deployed contract with role-based access control
  • Participant dashboards for each supply chain stage
  • Public traceability page reachable by QR scan
  • Gas cost analysis per event type

Suitable branches, difficulty and duration

Suitable branches

Difficulty level

Advanced. Needs a team with prior experience in this domain and a schedule with slack for the hard parts.

Development duration

8–10 weeks including documentation, tested and ready to demonstrate. Milestones are planned around your review dates.

Documentation, review, demo and viva support

Documentation support

Abstract, problem statement, literature survey guidance, system architecture, ER and UML diagrams, module descriptions, test cases and screenshots — prepared in your department format.

Project review support

Delivery is split across your review calendar so review one has a design and plan, review two has working modules, and the final review has the integrated, tested system.

Demo support

A rehearsed demo path, seeded sample data, a reset script, and a recorded walkthrough kept as a backup in case something fails in the review room.

Viva preparation

A written question bank for this domain, a code walkthrough session, and practice at explaining each module in your own words — because the examiner will ask you.

Customisation options

Colleges reject duplicate topics, so most projects are adjusted before we start. These are the usual directions for this one.

  • Scope to a single commodity such as milk, rice or pharmaceuticals
  • Add IoT temperature sensors writing directly to the chain for cold chain proof
  • Add automated payment release on delivery confirmation
  • Add a carbon footprint estimate accumulated across the journey
Talk to CodeLab69

Enquire about the Supply Chain Traceability System project

Send your branch, college and first review date. You will get confirmation of scope, what the customisation would look like, and a delivery plan mapped to your reviews.