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

3PL receiving ledger

One record of receiving and claims, made at the door.

A damage or shortage claim is three companies arguing over whose record is right. When each of them runs a node of the same ledger, the count, the seal number and the photo at the door are one record nobody can quietly edit. It is a narrow case, and we are clear when a database would do instead.

Start a project See the example projects

// what matters here

What is different in this industry.

One record at the door

The count, the seal number and the photos are recorded when the trailer is unloaded, with the time and the person, and every party sees the same entry.

Nodes for the parties who need them

The 3PL runs a node, and so can its larger clients and carriers. Smaller parties read through the portal without running anything.

Documents stay off the chain

Photos and documents live in storage; the ledger holds their fingerprints, so a changed file shows and the chain stays small.

When a database is enough

If your clients and carriers already accept your records, a well-audited database is cheaper. The ledger earns its cost when they do not.

// 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 receiving record

Hypothetical. Not a client, not a result.

// The problem

When a shipment arrives short or damaged, the 3PL, the client and the carrier each hold a different photo, count and timestamp, and claims drag on for months.

// What we would build

A receiving record on a private permissioned ledger that the 3PL, its larger clients and its main carriers each run a node of: counts, photos and seal numbers recorded at the door, so nobody can change the story later. If one party is trusted by all, a shared database does the same job for less, and we will say so.

// What is in it

Counts, seal numbers and photos captured at the dock and recorded on the ledger
A node for the 3PL and for each carrier or client that wants one
Carrier labels and tracking through direct carrier APIs
Claims packets exported with every record and its time
Documents held in storage, with only their fingerprints on the chain

// Stack

Next.js
Hyperledger Besu (private, permissioned)
PostgreSQL
S3-compatible storage
AWS

// estimate

Build: ≈ US$123,000 to US$188,000, delivered within 25 weeksCAD 174,600 to 267,100
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.9 to 2.9 weeks
Full build: 0.9 to 1.9 weeks
Devnet: 2.9 to 5.4 weeks
Testing and fixes: 0.4 weeks
Testnet: 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

Carrier API accounts and test keys: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 34,920 to 53,420
Discovery 2.5%: CAD 4,365.00 to 6,677.50
Architecture 6.7%: CAD 11,698.20 to 17,895.70
Design approved 2.5%: CAD 4,365.00 to 6,677.50
Core features 7.5%: CAD 13,095.00 to 20,032.50
Full build 5%: CAD 8,730 to 13,355
Devnet 20.2%: CAD 35,269.20 to 53,954.20
Testing and fixes 2.5%: CAD 4,365.00 to 6,677.50
Testnet 13.4%: CAD 23,396.40 to 35,791.40
Launch 2.5%: CAD 4,365.00 to 6,677.50
Mainnet 7.2%: CAD 12,571.20 to 19,231.20
Holdback, 30 days after launch (10%): CAD 17,460 to 26,710

Start from this example

// questions

Questions we get about this.

Do carriers have to install anything?

No. A carrier can read and add records through the portal. Running a node is optional, for parties that want their own copy.

Does this replace our WMS?

No. The WMS stays the system of work; the ledger records the receiving and shipping events that matter in a dispute.

Is there a token or a public fee?

No. It is a private, permissioned network with no token and no public transaction fees.

Back to the industry: Warehousing and 3PL 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