A supply chain is a chain of handovers between organisations that each keep their own records. A manufacturer, a carrier, a port, a warehouse and a retailer may each hold a slightly different version of what was shipped, when and in what condition. Reconciling those versions takes time, and disagreements lead to disputes, delayed payments and slow recalls. Blockchain is proposed as a way to give the participants one shared record that none of them controls alone. The technology is often described in sweeping terms, but its genuine contribution is narrow and useful. It provides an append-only log in which past entries are difficult to alter without detection, and which several parties can read and write under agreed rules.
How does a ledger keep records tamper-evident?
Each block of records contains a cryptographic hash of the block before it, so changing an old entry would change its hash and break every later link. Participants hold copies of the ledger and agree on new entries through a consensus mechanism, which means no single party can quietly rewrite history. In supply chains, most deployments use permissioned networks, such as Hyperledger Fabric, where only known organisations can take part and access to data can be restricted. That avoids the cost and openness of public networks and fits business needs for identity and confidentiality. The resulting record is tamper-evident rather than tamper-proof: alterations can be detected, but the entries themselves are only as truthful as the people or devices that submitted them.
Fewer disputes through smart contracts
Smart contracts are programs stored on the ledger that run when agreed conditions are met. In a supply chain they can encode rules such as releasing payment when a delivery is recorded as received, or flagging a shipment when a temperature reading falls outside an agreed range. Because every party sees the same record and the same rules, there is less room for argument about what happened, and settlement can be faster. This works best for events that are recorded digitally and unambiguously. Disputes that depend on judgement, such as whether goods were of acceptable quality, still need human resolution, and contracts that encode a mistaken rule will carry it out faithfully.
The limits: data about the physical world
The central weakness is often called the oracle problem. A ledger can prove that a record was written and not altered, but it cannot confirm that the pallet really contained what the record says. Accuracy depends on how data enters the system, through scanners, RFID readers, sensors and manual entry, and on the incentives of those entering it. Other challenges include keeping commercial information confidential among competitors, integrating with existing enterprise systems, agreeing on data standards and deciding who governs the network. In some cases a shared database with signed records, run by a trusted operator, solves the problem more simply, so the choice of blockchain should follow from a real lack of trust between parties.
Why it matters
Traceability matters to regulators, food and pharmaceutical safety teams and customers who want to know where products come from. A shared, tamper-evident record can make that traceability faster and more reliable, particularly when linked with good data capture at each handover. The lesson for organisations considering it is to start with a specific coordination problem, such as slow reconciliation or recall tracing, and to invest as much in data quality and governance as in the ledger itself.
A ledger can prove a record was not changed. It cannot prove the record was true when it was written.
