Why We Built on IOTA — And Why GS1 Comes First

When we tell food brands that their product passports are anchored on the IOTA blockchain, we sometimes get a question that we think is a very good one:

"Why should I care about the blockchain part — and why IOTA specifically?"

It's a fair challenge. "Blockchain-verified" has become one of those phrases that gets thrown around enough to mean almost nothing. This post is our attempt to answer that question plainly, so you know exactly what we've built, why we made the choices we made, and what it actually means for your traceability.

GS1 Is the Standard. Blockchain Is the Lock.

Let's be clear about the hierarchy here.

The foundation of everything we do is GS1 Digital Link — the global standard that major retailers, the EU, and international trade bodies recognise as the legitimate framework for product identification and traceability. Major EU retailers are adopting GS1-structured data across their supply chains. That's the language of traceability.

Blockchain doesn't replace that standard. It enforces it.

When you upload your batch data to PlaybookOS — your origin, certifications, supplier details — we structure it according to GS1 standards and then anchor a cryptographic record of that data to the IOTA mainnet. That anchor is a timestamp with a fingerprint. It proves that the data existed in that exact form at that exact moment, and that it hasn't changed since.

Why IOTA? Three Reasons We Can Actually Defend.

We didn't choose IOTA because it's novel. We chose it for specific reasons that matter to the food brands we serve.

1. There are no transaction fees.

Every time you generate a product passport — every batch record, every QR code, every certification link — we anchor that data on-chain. If we had built on Ethereum, each of those anchors would carry a gas fee. At the volumes an active food brand produces, those fees would either make our pricing unworkable for SMBs, or we'd have to batch records and compromise the integrity of individual batch traceability.

IOTA's low-cost architecture means we can anchor every single record independently for a small per-transaction fee. That's not a marketing point — it's the reason our pricing remains viable for small brands.

2. IOTA is designed to connect with GS1 and EU regulatory infrastructure.

IOTA's architecture is built for interoperability with existing standards frameworks — including GS1 for supply chain and eIDAS in Europe. This isn't accidental. IOTA is being used as infrastructure for some of the most ambitious real-world trade digitalisation projects currently underway, including partnerships with the World Economic Forum and the Tony Blair Institute for Global Change on African Continental Free Trade infrastructure. The design principle is the same one we rely on: IOTA as a public, neutral ledger that connects to existing standards rather than replacing them.

3. IOTA is peer-reviewed for food traceability specifically.

When we evaluated infrastructure options, we didn't just look at what other startups were doing. Academic research assessing blockchain platforms for agricultural food supply chain applications identifies IOTA — alongside Hyperledger Fabric and Algorand — as a technically feasible and scalable solution for food traceability use cases. That's a meaningful signal. It means our choice has been scrutinised outside of marketing materials.

Why Not Ethereum or Hyperledger?

We looked at both seriously. Here's where they fall short for our use case.

Ethereum is publicly verifiable and has strong smart contract capabilities, but transaction fees make it economically difficult to anchor individual batch records at the volumes and price points relevant to EU food SMBs. It's a better fit for financial applications where high-value transactions justify the cost per record.

Hyperledger Fabric is the gold standard for enterprise consortiums — large retailers and processors who can absorb the cost of running permissioned infrastructure together. It's not publicly verifiable by default, which means a buyer scanning your QR code can't independently confirm your data without being granted access to the consortium. For the transparency use case — where a retailer buyer or auditor needs to verify data without friction — that's a meaningful limitation. And for a food brand on a €149/month SaaS plan, the infrastructure overhead of a Hyperledger deployment simply doesn't apply.

IOTA sits in a specific niche: public verifiability, no per-transaction cost, and a design philosophy oriented toward standards interoperability. That's the niche our customers occupy.

What "Verified" Actually Means — and What It Doesn't

We want to be honest about one thing that the industry often glosses over.

When we anchor your batch record, we're guaranteeing that the data you certified hasn't been altered since the moment of anchoring. We are not independently auditing whether your origin claim is true, or whether your organic certificate is valid. That's your responsibility as the producer — and it should be. The value of the system is that your certified claims are now permanent and independently verifiable, not that we've added a second layer of auditing on top of your existing certification bodies.

This is actually the honest case for traceability technology: it raises the cost of making false claims, because those claims are now permanently recorded and publicly inspectable. That's a powerful deterrent. It's not the same as a guarantee.

How to Verify Any PlaybookOS Record Yourself

Every product passport we generate includes the IOTA Tangle transaction reference for that record. You don't need an account, and you don't need to trust us. You can paste that reference into the public IOTA explorer and see the anchored data for yourself.

That's what "verified" should mean. Not a green tick we put on a page. A record you can check independently.

The Bottom Line

We built PlaybookOS on GS1 standards because that's what regulators and retailers recognise. We chose IOTA as the integrity layer because it's low-cost at scale, designed for standards interoperability, and publicly verifiable by anyone. And we're telling you all of this because we think the food brands that will build durable traceability programmes are the ones who understand what their traceability system is actually doing — not just that it has a blockchain logo on it.

If you have questions about any of this, or you want to talk through how it applies to your specific traceability situation, we're easy to reach.