The problem: circularity is a multi-party workflow, not a single-system feature
A circular supply chain has to move a specific component from a decommissioned asset, through dismantling and processing, into a certified secondary raw material that a refiner or manufacturer will accept — and produce auditable evidence at every handover. That workflow crosses at least four organizational boundaries: the asset owner, one or more logistics providers, one or more recyclers, and the offtake party. Each of those parties has its own software, its own incentives, and its own data model. No existing enterprise software category was designed for this multi-party, neutral coordination problem. Each adjacent category solves a slice of it, then stops at the boundary of its original purpose.
Enterprise ERP and EAM systems: strong on assets, blind on recovery
Enterprise resource planning and asset management systems are excellent at tracking what an organization owns and operates. They know when a transformer was installed, when it was decommissioned, and what it cost to maintain. What they do not have is operational data from the recycler side: which dismantler actually processed the component, what mass balance came out, which fraction went to which downstream offtaker, and what compliance evidence backs each step. Bolting on a recycling module does not solve this — the data simply does not exist inside the enterprise. Without recycler-side operational reality, ERP-based circularity reporting becomes self-attested and cannot stand up to CSRD, CRMA, or Digital Product Passport audit requirements.
Material trading marketplaces: liquidity for known lots, no upstream chain
Trading marketplaces work well when both sides already know what they are exchanging: a defined lot of a defined quality, ready to ship. They create price discovery and reduce search cost. They do not, however, generate the upstream chain of custody that says where that lot came from, which recycler processed it, under which permit, with what mass balance, and what regulated material content it contains. For commodity scrap that is fine. For regulated streams — WEEE, ELV, battery materials, transformer copper recoverable as evidence under CRMA — the missing upstream layer is exactly what the buyer needs and exactly what the marketplace cannot provide. Marketplaces are also structurally biased to one side of the trade, which limits their acceptance as a neutral coordination layer.
Niche traceability and passport tools: one artifact, no workflow
A growing set of tools focus narrowly on producing a single compliance artifact — a Digital Product Passport entry, a Battery Passport, a WEEE recovery report. These tools are valuable but partial: they assume that someone, somewhere, has already orchestrated the physical workflow that produces the underlying data. In practice that orchestration is the hard part. Without a workflow engine that coordinates dismantling, logistics, processing, and material aggregation across multiple parties, the passport tool ends up being fed by manual data entry, which collapses the credibility of the artifact it generates. Compliance evidence is only as good as the physical workflow it was captured from.
Sustainability consultancies: depth without scale
Consultancies bring deep strategic and regulatory expertise. They can map a take-back program, design a compliance approach, and produce a one-off report. What they cannot do is operate the program. Each cycle of material — every shipment, every dismantling job, every aggregated lot — has to be re-coordinated, re-documented, and re-reported. Consultancy delivery is intrinsically manual and does not scale linearly with material volume. As regulatory frequency increases from annual to quarterly to continuous, the gap between consulting-led delivery and platform-led operations becomes structurally unbridgeable.
Vertical waste-management software: strong locally, no enterprise orchestration
Vertical waste-management tools — particularly the established German "Entsorger" software ecosystem — are excellent at running a single recycler's operations: weighing, invoicing, route planning, regulatory paperwork inside one operator's four walls. What they were never built to do is orchestrate a take-back program across an asset owner, multiple recyclers in different jurisdictions, and a refiner expecting aggregated, certified material. The enterprise OEM motion — the side that initiates a take-back program and demands cross-party evidence — sits outside what this software was designed for.
The neutral orchestration layer that connects all five
What circular supply chains actually need is a layer that sits between all of these systems and does the multi-party coordination none of them can do alone: intelligent R-strategy routing per component, Virtual Material Accounts that aggregate fragmented arisings into refiner-grade lots, neutral orchestration that asset owners and recyclers can both accept, and built-in EU compliance evidence captured from the physical workflow rather than reconstructed afterwards. This layer does not replace ERP, marketplaces, passport tools, consultancies, or vertical recycler software — it connects them. That is the category ContainerGrid operates in, and it is one of the reasons no incumbent in any single category has been able to address the problem end-to-end.