The boundary of this market
Software, data networks, intelligence services, and maintained operating platforms used to forecast demand; balance supply, capacity, inventory, service, and cost; design networks; monitor suppliers, orders, shipments, facilities, and disruptions; coordinate exceptions; test scenarios; and support accountable response and recovery decisions across physical supply chains.
The maintained market is organized around operating role, documented capability, authority context, and the buyer decision each record can support. It is not a popularity list, paid marketplace, or claim that a single product category can own every part of the workflow.
What is outside the boundary
- generic ERP, CRM, BI, or data platforms without maintained supply-chain planning, visibility, risk, or orchestration positioning
- freight marketplaces or carriers listed solely because they execute transportation
- consultancies without a maintained software, data, intelligence, or managed operating product
- single sensors or trackers without a maintained data and workflow layer
- news aggregators without an enterprise identity, exposure, alert, or decision product
- certification databases listed solely because they hold a certificate
- pages that provide business-specific legal, customs, sanctions, safety, continuity, or engineering conclusions
How the market divides
Integrated Business Planning And Scenario Platform
9 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Demand Inventory And Replenishment Planning Platform
7 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Supply-Chain Design And Optimization Platform
1 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Logistics Visibility And Control-Tower Platform
7 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Multi-Enterprise Network And Orchestration Platform
6 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Supplier And Geopolitical Risk Intelligence Platform
5 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Shipment Condition And Cargo-Risk Platform
3 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Supply-Chain Mapping And Due-Diligence Platform
2 maintained organizations begin with this operating model. Their dossiers preserve adjacent capability, fit conditions, and evidence limits so the primary classification does not erase meaningful differences.
Why the architecture matters
Buyers often compare organizations that participate in the same broad outcome but own different stages, data, authority, or accountability. A platform, data provider, network, service organization, content provider, and integration layer may all appear in one workflow without being substitutes. The market map makes those relationships visible.
The durable evaluation question is not which organization has the longest feature list. It is which operating model fits the buyer's governed work, which dependencies it introduces, what evidence it preserves, how change propagates, and whether the organization can exit or replace the system without losing the decision record.
How to use this publication
- Use categories and the market map to define the operating role.
- Use capability pages to define workflows and evidence requirements.
- Use authority and risk-domain records to establish scope and questions requiring qualified judgment.
- Use organization dossiers and comparisons to build a research list.
- Use guides and tools to create a repeatable evaluation record.