The Blockchain Shipping Myth: Why Maersk Abandoned TradeLens for Standard APIs

The illusion of the trustless supply chain

For five years, enterprise consultants pitched blockchain as the ultimate savior of the global supply chain and logistics industry, targeting everyone from maritime shippers to local factories and agricultural exporters. The pitch was logical: shipping a container from Shenzhen to Rotterdam requires coordinating dozens of entities - freight forwarders, customs agents, port authorities, and trucking companies or local retail distributors. If they all shared a decentralized, immutable ledger, the paperwork bottlenecks would vanish.

This vision peaked with TradeLens, a joint venture between IBM and Maersk built on Hyperledger Fabric. It was an engineering marvel and a commercial catastrophe. In late 2022, Maersk abruptly shut it down.

The failure of TradeLens was not a technical failure. It was an architectural misdiagnosis of a political problem. Engineers attempted to use a blockchain to enforce trust in an ecosystem that structurally refuses to cooperate.

Why private blockchains fail in logistics

A blockchain solves the problem of reaching consensus without a trusted central authority. In a public network like Ethereum, this is achieved via economic incentives (gas fees and block rewards).

But enterprise logistics networks (like TradeLens) are private, permissioned blockchains. There are no economic incentives for running a node. The authority is centralized within a consortium. In the case of TradeLens, the consortium was dominated by Maersk.

Why would Maersk’s direct competitors - Hapag-Lloyd or MSC - voluntarily push their highly proprietary shipping data into a shared database effectively controlled by their biggest rival? They wouldn’t. The platform architecture failed because a blockchain does not magically remove the commercial conflict of interest. If competitors don’t trust you, changing the underlying database from PostgreSQL to Hyperledger will not change their minds.

EDI and APIs: The boring, functional reality

Instead of forcing a global, synchronized ledger, successful logistics platforms rely on point-to-point integration. The industry continues to run heavily on EDI (Electronic Data Interchange) - a standard from the 1970s - and modern REST APIs.

While EDI is clunky, it respects the political boundaries of the supply chain. When a port authority updates a container’s status via an API webhook, they retain complete sovereignty over their internal database. They expose only the data they are contractually obligated to share, exactly when they want to share it.

// The boring reality of supply chain tracking
// A simple REST webhook is far more viable than a blockchain transaction
{
  "event": "container_gated_in",
  "containerId": "MSKU1234567",
  "location": "NLRTM",
  "timestamp": "2026-03-05T08:30:00Z",
  "sourceSystem": "Rotterdam_Port_Authority_ERP"
}

The true use case for Web3 in B2B

If private enterprise blockchains are dead ends, does Web3 have any place in B2B SaaS? Yes, but only when you rely on public, permissionless networks (like Ethereum or Polygon) as a neutral settlement layer.

If a supply chain company wants to tokenize a Bill of Lading (a legal document representing ownership of goods) so it can be instantly transferred and used as collateral for a loan, they must use a public blockchain. Banks will not trust a private token issued on Maersk’s servers, but they will trust a standard ERC-721 token on a globally verified network.

Stop trying to use blockchain as a highly inefficient cloud database. Use it exclusively as a neutral court of law for digital assets.