Supply Chain Traceability Ledger
Agricultural supply chain consortium
Blockchain traceability from farm to retail — QR and RFID custody, smart-contract settlement, offline-first for producers in the field.
Producers tag crops and record harvest data on site; every custody event is written immutably on-chain. Distributors verify shipments in transit, retailers confirm origin, and smart contracts settle payment without the delays and disputes of manual reconciliation. Built offline-first, because the people entering the most important data have the least reliable connectivity.
Outcomes
- Farm-to-retail custody on an immutable ledger
- Smart-contract settlement replacing manual reconciliation
- Offline-first capture with biometric-secured accounts
Stack
- React Native
- Solidity
- ethers.js
- Redux Toolkit
- Stripe
- Secure Store
Engagement
Client named under NDA. Several engagements are active public-sector contracts, so we describe the mechanism rather than the customer.
Source, references and a walkthrough can be arranged for serious evaluation.
A produce consortium where nobody disputed the facts so much as the record of them. Farmers said they delivered a quantity; distributors recorded a different one; retailers could not verify origin at all. Payment followed reconciliation, so a disagreement about a harvest in March could still be unpaid in June.
The people entering the most consequential data — producers, at the point of harvest — had the least reliable connectivity, the least powerful devices and the least patience for software. Any design that assumed a live connection at the moment of capture would have recorded nothing.
- 01
A ledger because the parties disagree, not because it is a ledger
Distributed consensus is the wrong tool for most problems and we say so. It earned its place here for one specific reason: several independent parties needed a shared history that none of them could quietly revise. That is the narrow case where the overhead is worth paying.
- 02
Offline-first capture, deferred settlement
Harvest events are recorded locally, signed on the device, and queued. They reach the chain when connectivity allows. Producers are never blocked by a network they do not control, and the ordering guarantees survive the delay.
- 03
Physical tags as the bridge
QR and RFID tags tie a cryptographic record to a physical crate. Without that bridge, an immutable ledger only proves that somebody typed something — the tag is what makes the entry mean anything about the world.
The technical dossier for this engagement
This page describes the shape of the work. The dossier describes how it was actually built — and goes to a named person at a named institution rather than onto a public URL.
- System architecture, including the integration boundaries and why they were drawn there
- The data model for the records the system is accountable for
- Security posture: authentication, authorisation, audit trail and key handling
- Deployment topology, failover behaviour and what happens during an outage
- The measured before-and-after, where the client has cleared it for release
- Named CVs for the engineers who did the work
Sent under a mutual NDA. Client names and locations are redacted unless that client has given written consent, which some have and some have not. Prepared individually — expect it within two working days, not instantly.
Next project
Institutional Records Platform
Start here
Bring us the problem
nobody has solved.
A 30-minute technical briefing. We will tell you what we would build, roughly what it costs, and honestly whether we are the right people for it.