"It's on the blockchain" is one of the most overused sentences in supply chain technology. It is often said as if it settles every argument. It doesn't, and being precise about why is what separates useful systems from expensive theatre.
What anchoring actually does
When we anchor a document, say a signed consignment note, we don't usually store the document on chain. We store its fingerprint: a cryptographic hash, a short value that changes completely if a single character of the file changes.
That fingerprint, recorded on a shared ledger, proves two things very well:
- The file is unchanged. Anyone holding the document can recompute its fingerprint and compare. If it matches, nothing has been altered since it was anchored.
- It existed at that moment. The ledger records when the fingerprint was written, so nobody can later claim the document was created afterwards.
Those are powerful guarantees. They end a whole class of disputes: "that's not the version we received", "this was edited later", "we never had that document".
What anchoring does not prove
Here is where many projects overreach. A fingerprint on a ledger does not prove:
- Who agreed to the document. A hash says nothing about consent.
- That the content is true. A signed delivery note can still describe the wrong quantity.
- That it was legally accepted. Contractual and legal effect follow their own rules.
If a system treats "anchored" as if it meant "approved" or "correct", it is quietly promising more than the technology delivers. Sooner or later that gap shows up in a dispute.
Trust still belongs to people
The part a ledger cannot do is decide who is allowed to say yes. In freight, that is a chain of real responsibilities: the carrier uploads evidence, the consignee confirms receipt, the forwarder approves, finance releases payment.
So we design those as explicit steps:
- Each step is performed by a specific, identified party.
- Each step follows that company's own signing route.
- Each step is recorded against the shipment, in order.
The ledger then does what it is good at: it makes that record of decisions tamper-evident. It doesn't replace the decisions.
Keep the states separate
One design rule has saved us a lot of confusion: never collapse different states into a single flag. "Uploaded", "reviewed", "accepted", "disputed", "anchored" and "paid" are different facts with different owners. A document can be anchored and still disputed. It can be accepted and not yet paid.
Systems that blur those states feel simpler at first and become impossible to audit later.
The honest pitch
The most credible way to talk about blockchain in logistics is also the most modest one: it gives every party the same tamper-evident history, and it makes rewriting that history visible. Everything else, consent, correctness and legal effect, still has to be designed deliberately.
That honesty is not a weakness in the pitch. It is the reason serious companies can trust it.
I'm the CTO of Konfidio, where we build TrustedTrucks: one shared record for European freight.
