Tokopedia and Shopee are platforms you join. ION is a rail you connect to. That one difference decides who your buyers can reach, who owns the catalogue, and who writes the rules.
A marketplace bundles every role — storefront, search, catalogue, payments, logistics, sellers — inside a single company. ION unbundles those roles into participants who never share an owner, only a protocol. The boundary stops being a company and becomes a network.
The deepest difference isn't features — it's where the seams are. A marketplace has no seams: one owner runs the app, the search, the payments, and the logistics desk. ION cuts the same stack into roles that different organisations fill and the Beckn protocol stitches back together.
Because the seams are explicit, you can swap one side without rebuilding the other: a new buyer app reaches every existing provider, and a new provider is visible to every existing buyer app — no point-to-point integration in between.
On a marketplace, the platform is the boundary. A seller on Tokopedia reaches Tokopedia's buyers and no one else; to reach Shopee's buyers they open a second account and re-key the same catalogue, prices, and stock into a second silo.
On ION, the network is the boundary. A provider publishes its catalogue once to the Catalogue Service; from that moment any BAP on the network can discover and sell it. Reach is a property of joining the network, not of joining one company's app.
For the buyer the mirror image holds: one buyer app, many providers. The consumer searches a single storefront and can transact with any registered provider on the network — which is the whole point of the architecture.
A marketplace sets its own terms and can change them unilaterally — fees, ranking, eligibility, deplatforming — through a private terms of service. ION moves the rules out of one company's hands and into a file that a council ratifies.
ion.yaml + ION Council
The shift is from trust the owner to read the file.
See governance and the network profile for how the
Council, ion.yaml, and the two registries fit together.
The common mistake is to picture ION as another app competing with Tokopedia and Shopee for the same screen. It isn't. ION is the rail underneath — and the existing marketplaces are among the buyer apps that can ride it.
/search, /select, /init, /confirm — and consume the /on_* callbacks.So the question stops being "ION or Shopee" and becomes "which roles do you want to play on the network" — a buyer app, a provider platform, or both. The marketplace is one possible participant; ION is the field they all stand on.
The same eight questions, answered by a walled marketplace and by the ION network.
ion.yaml, ratified by the ION CouncilWant the mechanics behind the right-hand column? Walk the trade × logistics transaction end to end, or start from the network architecture.