labs@atheron:~/industries/food-beverage/blockchains$ launch chain --validators

Food cold chain

A private ledger shared by packer, carrier and retailer.

Cold-chain disputes are about trust between companies: whose logger, whose timestamps, whose photos. A private ledger fits when packer, carrier and retailer all write to the record and none should be able to rewrite it. If one of them already runs a system the others trust, a database does the job.

Start a project See the example projects

// what matters here

What is different in this industry.

Readings recorded as they happen

Logger readings and door events are written to the ledger when they reach a gateway, not uploaded after the load is in dispute.

Every party sees the same alarm

A temperature excursion is flagged to the packer, the carrier and the retailer at once, while there is still time to act on the load.

Acceptance at the dock, on the record

The receiver accepts or rejects the load in the app with photos, and that decision joins the same record.

No crypto, no tokens

A permissioned chain among known companies has no token, no public fees and no exposure of your volumes to outsiders.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appBlockchain

Shared cold-chain ledger

Hypothetical. Not a client, not a result.

// The problem

When a load of produce or seafood arrives warm, the packer, the carrier and the retailer each hold their own temperature data, and the claim turns into an argument over whose logger to believe.

// What we would build

A private permissioned ledger where packer, carrier and retailer each run a node, recording trailer and pallet logger readings, door openings and hand-offs as they happen, so a disputed load is settled from one record nobody could change after the fact. If the others already trust a database run by one of them, that is cheaper, and we will say so.

// What is in it

Temperature loggers on pallets and trailers read at each hand-off
Readings and door events recorded on the ledger as they arrive
Temperature excursions flagged to every party at once
Acceptance or rejection at the dock recorded with photos
Claims file for a load, exported with its full history

// Stack

Hyperledger Fabric (private, permissioned)
Node.js
Next.js
Bluetooth temperature loggers
PostgreSQL
AWS

// estimate

Build: ≈ US$113,000 to US$172,000, delivered within 27 weeksCAD 160,500 to 245,500
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Architecture: 0.4 weeks
Design approved: 2.9 to 4.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.9 weeks
Devnet: 2.9 to 4.9 weeks
Testing and fixes: 0.4 weeks
Testnet: 2.9 to 3.4 weeks
Mock recall passed: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Mainnet: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Sensor delivery: 2 to 6 weeks

How it is paid

Deposit 20%: CAD 32,100 to 49,100
Discovery 2.2%: CAD 3,531 to 5,401
Architecture 5.9%: CAD 9,469.50 to 14,484.50
Design approved 2.2%: CAD 3,531 to 5,401
Core features 6.6%: CAD 10,593 to 16,203
Full build 4.4%: CAD 7,062 to 10,802
Devnet 17.7%: CAD 28,408.50 to 43,453.50
Testing and fixes 2.2%: CAD 3,531 to 5,401
Testnet 11.8%: CAD 18,939 to 28,969
Mock recall passed 8.7%: CAD 13,963.50 to 21,358.50
Launch 2.2%: CAD 3,531 to 5,401
Mainnet 6.1%: CAD 9,790.50 to 14,975.50
Holdback, 30 days after launch (10%): CAD 16,050 to 24,550

Start from this example

// questions

Questions we get about this.

Which temperature loggers can feed the ledger?

Most Bluetooth and cellular loggers with an export or an API. We prefer the ones your carriers already use and check each model before quoting.

What if a carrier will not run a node?

A carrier can write through a hosted node or the app instead. Its records are still signed, but it relies on the host for its copy, and we explain that trade-off to everyone.

Does the ledger replace our own food safety records?

No. It holds the shared record of the shipment. Your own food safety records stay in your own systems.

Back to the industry: Food and beverage About the service: Private and public blockchains

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call