How Blockchain Integration with SCM Solves Supply Chain Problems?
Lost cargo cannot be localized, data from suppliers and carriers do not match, audits take weeks — this is a typical enterprise scenario without blockchain. Blockchain in logistics is becoming standard, improving product tracking and data verification. Each operation (customs, warehouse, transport) is recorded in a smart contract, creating an immutable registry. In case of a dispute, it is enough to compare the on-chain hash with the actual data. According to Linux Foundation, 65% of industrial companies are exploring blockchain for supply chain. We have implemented such solutions for 15+ clients — from pharmaceuticals to automotive components. A typical request is blockchain and ERP integration with SAP or Oracle SCM. We build an Event Bridge that listens to ERP events and sends hashes to the blockchain. The result is reducing dispute resolution time from months to hours and lowering operational costs by 30–50%. One client saved €150,000 in audit fees in the first year.
What Data to Record on the Blockchain?
The first question when designing is not "which blockchain" but "exactly what needs to be verified". The correct architecture is off-chain storage, on-chain verification. Blockchain is expensive for storing data and slow for complex logic.
Data Model
Each physical object receives a digital twin — a record in a smart contract tied to a unique identifier. The identifier can be:
- QR code / RFID — for serial products. RFID is read automatically at warehouse gates, creating a transaction without human involvement.
- EPC (Electronic Product Code) — GS1 standard, compatible with most existing WMS systems.
- NFT (ERC-721) — for unique assets: batches of pharmaceuticals, expensive equipment, art objects.
The contract itself stores only hashes and metadata, not raw data:
struct ShipmentEvent { bytes32 dataHash; // keccak256 of full event data address actor; // who created the event uint64 timestamp; EventType eventType; // CREATED, DEPARTED, ARRIVED, INSPECTED, DELIVERED bytes32 locationId; // location ID from registry } Full data (temperature, weight, photos) is stored in IPFS or corporate S3; only the hash goes to the blockchain. In case of a dispute, any party can present the original data and prove its correspondence to the on-chain hash. This enables automated data verification without third-party trust.
Network Selection
For enterprise supply chain projects, three real options exist:
| Approach | Examples | When Suitable |
|---|---|---|
| Public L2 (Polygon, Arbitrum) | — | Consortium of companies without a single operator, need open verifiability |
| Private Ethereum (Hyperledger Besu, Quorum) | TradeLens (Maersk+IBM), Food Trust (Walmart+IBM) | Closed consortium, compliance requires transaction privacy |
| Hyperledger Fabric | — | Strict permissioned control, no public token |
Most enterprise clients choose Polygon PoS or a private Besu node with periodic anchoring to Ethereum mainnet. Public L2 provides open verifiability at 2–3 times lower cost than maintaining a private network.
How to Integrate Blockchain with ERP and WMS?
This is the most labor-intensive part. A typical stack: SAP S/4HANA or Oracle SCM, in-house WMS, EDI gateways with counterparties, IoT sensors (temperature, humidity).
Integration Layer
Between legacy systems and the blockchain, an Event Bridge is needed — a service that:
- Listens to events from ERP (webhook / polling via SAP BAPI / JMS queue)
- Normalizes data into a canonical format
- Signs the transaction with the participant's key
- Sends to the blockchain
- Records the transaction hash back to ERP for audit
Technically, this is a microservice on Node.js or Go with a queue (Kafka / RabbitMQ) for resilience. The blockchain transaction is asynchronous; ERP should not wait for its confirmation — a key point for operator UX. The Event Bridge reduces integration time by 70% compared to custom APIs.
SAP → BAPI Event → Kafka topic → Event Bridge → Sign & Submit → Blockchain ↓ Confirmation listener → TxHash → SAP Custom Field Participant Identity Problem
Each participant in the chain must have an on-chain identity. Two approaches:
Centralized registry — a smart contract with mapping address → ParticipantInfo. Fast, but requires trust in the registrar.
DID (Decentralized Identifiers) — W3C standard. Each participant controls their DID, verified credentials are attached as verifiable credentials. More complex to implement, but correct for inter-company scenarios.
Smart Contract: Supply Lifecycle
contract SupplyChainRegistry { mapping(bytes32 => ShipmentEvent[]) public history; mapping(bytes32 => address) public custodian; // current holder mapping(address => bool) public authorizedActors; event EventRecorded( bytes32 indexed shipmentId, EventType indexed eventType, address indexed actor, uint64 timestamp ); function recordEvent( bytes32 shipmentId, bytes32 dataHash, EventType eventType, bytes32 locationId ) external onlyAuthorized { history[shipmentId].push(ShipmentEvent({ dataHash: dataHash, actor: msg.sender, timestamp: uint64(block.timestamp), eventType: eventType, locationId: locationId })); if (eventType == EventType.DEPARTED) { custodian[shipmentId] = msg.sender; } emit EventRecorded(shipmentId, eventType, msg.sender, uint64(block.timestamp)); } } The contract is intentionally minimal. Business logic (SLA calculation, penalties, conditional payments) is implemented separately and can read event history. This simplifies contract auditing and allows changing business logic without data migration.
Conditional Payments and Escrow
For automatic payments upon delivery, the escrow pattern is used: buyer deposits payment → escrow smart contract. On EventType.DELIVERED + recipient signature → release payment to supplier. On SLA timeout → automatic penalty from escrow. For B2B fiat settlements, an off-ramp through licensed processing is needed.
How IoT Sensors Interact with the Blockchain?
Data from IoT sensors (temperature loggers, GPS trackers) cannot directly enter the blockchain — a trusted intermediary is needed. The use of data oracles solves this. Two options:
Centralized oracle — your own server signs sensor data and sends the transaction. Fast and cheap, but a single point of trust. Acceptable for internal supply chain of one company.
Chainlink Any API — decentralized oracle network. Data via HTTPS to Chainlink node operators, aggregation of multiple nodes, on-chain recording. More expensive but verifiable for external auditors. For cold chain, temperature violations automatically create an on-chain event CONDITION_BREACH and can block transfer custody. Blockchain-based verification is 100x faster than manual checks.
Implementation Stages
| Phase | Content | Duration |
|---|---|---|
| Discovery | Process mapping, data scope, network selection | 2–3 weeks |
| Smart contract development | Registry contracts, governance, tests (Foundry) | 3–4 weeks |
| Event Bridge | Integration layer with ERP/WMS, Kafka pipeline | 4–6 weeks |
| Identity setup | Onboarding participants, DID or registry | 2–3 weeks |
| Pilot | Limited launch with 2–3 participants, real shipments | 4–8 weeks |
| Production rollout | Scaling to all participants, monitoring | 4–8 weeks |
Realistic timeline from discovery to production: 6–9 months. Projects that promise “blockchain in supply chain in 3 months” are usually building a centralized database with blockchain marketing.
What’s Included in the Work
We offer turnkey implementation, including:
- Documentation: Detailed process analysis, data schema, and architecture documentation.
- Access: Provisioned blockchain network nodes, identity management system, and integration endpoints.
- Training: Operator training for 5 users on system usage and dispute resolution.
- Support: 3 months of technical support and maintenance post-launch.
Additional deliverables:
- Smart contract development and audit (formal verification)
- Event Bridge construction with integration to SAP / Oracle / 1C
- Identity management setup (DID or centralized registry)
- Pilot launch with 2–3 counterparties
To discuss your project, contact us for a preliminary audit. Ready to implement blockchain in your supply chain? We will assess your project in 2 days. Write to us.