Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How One Buyer Used Blockchain to Trace Conflict Minerals
Transcript
- Lucas: So last year a mid-size electronics maker in Ohio found itself staring down a potential SEC investigation. The company had been filing conflict minerals disclosures based on supplier affidavits — basically Excel spreadsheets with signatures — and a routine audit revealed that one of their third-tier smelters was sourcing from a mine in the eastern Democratic Republic of Congo that had been flagged by the UN Group of Experts. Luna: That's the nightmare scenario. The company had no idea because the affidavit chain broke somewhere between tier two and tier three. Lucas: Exactly. And that's the problem with paper-based or even email-based compliance. The buyer — her name is Sarah, she's the director of global sourcing — decided to try something different. She moved the entire conflict mineral traceability pipeline onto a permissioned blockchain. Luna: Okay, I hear 'blockchain' and my brain goes to crypto volatility or Ethereum gas fees. But this is different — it's a shared ledger where every transaction is immutable and every participant has a copy. Lucas: Right. Sarah didn't use a public chain like Bitcoin. She used a private, permissioned ledger — Hyperledger Fabric — where she invited each supplier in her chain to run a node. Every time a batch of tantalum or tungsten moved from the mine to the smelter to the component manufacturer, that transfer was recorded as a transaction with a digital signature and a timestamp. Luna: And because it's permissioned, only verified participants can write to the ledger. So no anonymous bad actors slipping in fake data. Lucas: Correct. But the real innovation was how she handled tier two and tier three. Most companies only audit their direct suppliers — tier one. But conflict minerals risk lives in the smelters and mines further upstream. Sarah required each tier one supplier to onboard their own sub-suppliers onto the blockchain as a condition of doing business. If a tier two supplier refused to join the ledger, that supplier was de-sourced within 90 days. Luna: That's a strong arm. But it worked because she had leverage — the company represented about 8 percent of her top-tier supplier's revenue. Lucas: That leverage was critical. The pilot covered 47 individual nodes across six countries. The blockchain itself cost about forty thousand dollars to set up — mostly in developer time and node infrastructure. But Sarah calculated that her annual audit costs for conflict minerals were running at about three hundred and seventy thousand dollars — third-party auditors flying to smelters, reviewing paper trails, reconciling discrepancies. The blockchain reduced that to about fifty thousand dollars in year one, because auditors could verify the ledger remotely. Luna: So the ROI was there on paper. But implementation must have been messy. Lucas: It was. The biggest bottleneck wasn't technology — it was people. Many of the smelters were small operations in central Africa with limited digital infrastructure. One smelter in Rwanda had no reliable internet connection. Sarah's team had to supply a satellite terminal and train a local administrator to enter data manually. That added six weeks and about eight thousand dollars to the rollout. Luna: That's a real-world constraint you don't see in the white papers. The human cost of onboarding. Lucas: And it's why most blockchain procurement pilots fail. A 2025 study from the University of Tennessee found that over 70 percent of supply chain blockchain projects never made it past the proof of concept phase because project leads underestimated the onboarding friction. They assumed suppliers would just join because it's better. But suppliers with thin margins and older ERP systems saw it as extra work with no immediate benefit. Luna: So how did Sarah overcome that? Did she offer incentives? Lucas: She did two things. First, she tied blockchain participation directly to payment terms. Suppliers who joined the ledger and submitted clean data for six months got their net terms moved from Net 60 to Net 30. That's a real cash flow improvement for small smelters. Second, she absorbed the cost of the node software and any training. For the average tier two supplier, the total cost to participate was zero — they just had to assign one person to input data. Luna: That's a clever use of payment terms as a stick and a carrot. I've seen similar strategies in other contexts, but not tied to technology adoption. Lucas: It worked. Within eight months, 41 of the 47 suppliers were active on the ledger. The remaining six were replaced with alternative suppliers who were willing to participate. Sarah's team then used the blockchain data to run a conflict mineral report for the SEC filing. The entire process took three days instead of the usual six weeks. Luna: Three days vs six weeks — that's the kind of headline number that gets a CFO's attention. Lucas: And it's not just speed. The data integrity argument is even stronger. On a blockchain, once a transaction is recorded, it cannot be altered retroactively without the consensus of the network. So if an auditor questions a specific batch of tin from a specific mine, Sarah can prove exactly when that batch was recorded and by whom. Compare that to an affidavit that could have been filled out six months after the fact with fuzzy memory. Luna: I can see why the SEC would look more favorably on that. But does the blockchain itself ever get hacked? I mean, no system is perfect. Lucas: The risk is much lower than a centralized database, but it's not zero. The main attack vector would be a 51 percent attack — where a malicious actor controls more than half the network's computing power. But on a permissioned blockchain with only 47 known, vetted nodes, that's effectively impossible because you'd need to compromise at least 24 of those organizations. The bigger risk is a bad actor at a legitimate node entering false data at the source. Sarah addressed that by requiring dual signatures from the supplier's operations manager and a quality officer before any transaction was finalized. Luna: So you're distributing trust but not eliminating the need for human oversight at the entry point. Lucas: Exactly. Blockchain doesn't solve the 'garbage in, garbage out' problem. It just makes the garbage auditable and immutable. But for compliance purposes, that's actually a huge step forward. Because now, if a supplier knowingly enters false data, that becomes a legal liability for them, not just a compliance gap for the buyer. Luna: I want to touch on something broader. There's a lot of hype around blockchain in procurement — I've seen Gartner reports claiming it will save billions. But this case shows it only works when you have a specific, narrow problem with clear ROI. Conflict mineral traceability is almost the perfect use case. Lucas: That's right. And Sarah would be the first to admit she wouldn't use blockchain for, say, tracking office supplies. The overhead of onboarding and the computational cost don't make sense for low-risk, high-volume items. But for regulated materials — conflict minerals, conflict timber, certain pharmaceuticals — the cost of non-compliance is so high that the technology pays for itself. Luna: Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. If these conversations have moved your work forward in some small way, that's the reason we keep going ad-free. Lucas: Yeah, it's a small group that keeps the lights on. And we really appreciate it. Back to Sarah's story — she also built a dashboard for her executive team that visualized the entire supply chain in real time. So the CEO could see, on any given day, exactly which smelters had confirmed their latest batch and which were overdue. Luna: That visibility is a game changer for a board that's worried about reputational risk. I imagine it also helped during her annual budget review. Lucas: It definitely did. The project saved roughly three hundred and twenty thousand dollars in audit costs in the first year alone, and it eliminated the risk of an SEC penalty, which could have been millions. Sarah's team also found an unexpected benefit: the blockchain data helped them identify which smelters had the highest throughput, which allowed them to negotiate better pricing on raw materials. Luna: So it moved from a compliance tool to a strategic sourcing tool. That's a nice arc. Lucas: It is. And I think that's the lesson for any buyer considering blockchain. Don't start with the technology. Start with a specific, painful problem — like not knowing where your third-tier suppliers are sourcing from — and then ask whether an immutable shared ledger actually solves it better than a traditional database. Luna: Right. And if the answer is yes, then be prepared to invest in the human side of onboarding. The satellite terminals and the training and the payment term incentives are often harder than the code. Lucas: Exactly. Sarah's project is now being expanded to cover cobalt sourcing for batteries, and she's in talks with three other manufacturers to create a shared consortium blockchain. If that works, the audit cost savings could multiply because the same network serves multiple buyers. Luna: I'd love to check back in a year and see how the consortium model holds up. My guess is the coordination costs will be high, but the upside is real. Lucas: I think so too. And we'll make sure to follow up. For now, the takeaway is: blockchain in procurement isn't dead. It's just very, very specific about where it works.