Why commerce became captive

Commerce is cooperation between strangers

Commerce is a remarkable mechanism. Two organisations that have never met can agree on what is needed, establish trust, exchange something of value and build a relationship. Technology ought to make that sequence easier. Often it does: platforms can bring buyers and suppliers together, reduce errors and make transactions faster.

Yet there is a catch. Each system may work well on its own while the wider market becomes harder to navigate. Suppliers repeat information they already supplied elsewhere. Buyers adapt processes to multiple proprietary formats. Two organisations willing to transact discover they cannot connect without expensive integration work. Over time, a useful platform can become an expensive place to remain and an even more expensive place to leave.

That is captive commerce: not simply using a platform, but depending on arrangements that make choice, movement and interoperability artificially difficult.

A supplier’s ordinary Tuesday

Imagine a small engineering company that wants to supply components to three manufacturers. All three request largely overlapping evidence: company identity, banking details, insurance, qualifications and policies. The supplier must provide the same facts through three different portals, repeat similar checks and monitor three separate statuses. Next month one customer changes systems, and the supplier starts again.

The information has not become more accurate through repetition. The supplier has spent time translating facts from one system to another rather than improving its products or serving customers.

Now imagine the buyers also use separate workflows and data formats. A purchase order in one system does not map cleanly to an invoice in another. Each integration is bespoke. Costs rise not because commerce is inherently complex, but because common foundations were never agreed.

Five ways dependency appears

1. Repeated proof. Identity and qualifications are established repeatedly rather than made appropriately reusable and verifiable.

2. Proprietary formats. Data is represented in incompatible forms, so organisations must translate the same meaning over and over.

3. Controlled access. A single intermediary can decide who connects, on what terms, and what they are allowed to see.

4. Switching costs. Information, relationships and workflows cannot move easily, making a technically possible exit commercially unrealistic.

5. Network capture. The value of trading relationships becomes tied to one platform rather than portable across services.

Not every difference between systems is artificial. Security, privacy, compliance and sector-specific needs are legitimate. The challenge is to distinguish necessary rules from avoidable dependence.

A better foundation, not the end of platforms

Free Commerce does not mean all software must be free of charge. It does not mean removing intermediaries, regulations, commercial incentives or responsibility. As the manifesto puts it, freedom means being able to connect, compete, choose and leave.

The goal is for platforms to compete where competition creates value: in usability, performance, security, intelligence and service. Underneath those differentiated services, shared open standards should allow independent organisations and systems to understand one another.

This is a change in where competition happens. Instead of competing for control over the basic language of commerce, providers compete to serve participants better.

Why exit matters

Think about a road system. A haulage company should be able to choose a vehicle, a route and a logistics provider without every road belonging to the same business. Shared infrastructure and agreed rules allow competition above them.

A system is not genuinely open merely because it lets you join. It must also permit you to carry your information and relationships to another compatible system, subject to law, privacy and legitimate contractual obligations.

The defining question is simple: Could you leave without losing your ability to trade?

Try it: map one friction point

Pick a real or hypothetical commercial process. Write down: (a) the same data requested by multiple parties; (b) formats or portals that require translation; (c) who can grant or deny access; (d) what it would take to change provider; and (e) which rules are necessary and which may simply reflect technical fragmentation.

Ask what could become a shared standard. Be precise: standards should enable options, not erase useful differences.

Key terms

• Interoperability: independent systems can exchange and use information meaningfully.
• Lock-in: changing providers is sufficiently costly or difficult that choice is constrained.
• Portable trust: relevant proof about an organisation can be verified across contexts, with appropriate control and safeguards.
• Open standard: a shared specification that can be implemented on fair and accessible terms, governed transparently; assess the actual licence and governance, not the label alone.

Next

In Lesson 2 we will explore how shared standards opened communication, publishing and global trade – and what commerce can learn from those examples. Meanwhile, read the Free Commerce manifesto or explore the existing SIGNET standard.

References

• The Free Commerce manifesto, 11 October 2026.
• This lesson’s supplier illustration is explicitly hypothetical, not an empirical case study.