What makes an ERP composable?
Gartner defines composable ERP as a platform where business capabilities are delivered as modular, interchangeable components that can be assembled, reassembled, and extended without rebuilding the core. It is the enterprise software equivalent of LEGO bricks vs a solid plastic toy.
The three pillars of composable architecture are: modular design (independent components), open integration (API-first), and flexible orchestration (combine components to create new workflows). Not every platform that claims to be composable meets all three.
1. Teamnet
Composability score: 9/10. Teamnet is purpose-built as a composable platform. Every module is an independent app on a shared database. Custom apps are first-class citizens, built with the same framework as core modules. API-first architecture means every function is an endpoint.
Unique strengths: single-database composability (modules compose without integration), native IoT/hardware integration, unlimited users, built-in AI layer. Strongest for manufacturing, operations, and hardware-connected workflows.
2. SAP Business Technology Platform (BTP)
Composability score: 7/10. SAP's composable strategy centres on BTP as the integration and extension layer for S/4HANA. BTP offers integration suite, app development (CAP framework), AI (Joule), and data analytics. Extensions can be built without modifying core S/4HANA code.
Limitations: BTP is an add-on to a monolithic core, not composable from the ground up. Separate licensing, separate infrastructure, and significant SAP expertise required. Best for organisations already invested in the SAP ecosystem.
3. Oracle Cloud ERP
Composability score: 6/10. Oracle has moved to a cloud-native, microservices-based architecture for its ERP suite. Modules can be adopted incrementally, and Oracle's Integration Cloud provides API connectivity. OCI (Oracle Cloud Infrastructure) enables custom extensions.
Limitations: Oracle's modules are tightly coupled within the Oracle ecosystem. While you can adopt modules incrementally, replacing an Oracle module with a non-Oracle component is complex. Integration with non-Oracle systems requires significant middleware.
4. Acumatica
Composability score: 7/10. Acumatica was designed from inception as a cloud ERP with a platform-first approach. Open APIs, customisation framework, and ISV marketplace. Unique consumption-based pricing (no per-user fees) aligns with composable principles.
Limitations: Limited manufacturing depth (no MES, no IoT), primarily focused on distribution, retail, and construction industries. Smaller ecosystem than SAP or Oracle. Best for mid-market distribution and project-based businesses.
5. Unit4
Composability score: 6/10. Unit4 has embraced composable architecture for its People Experience suite targeting services industries. Modular deployment, API-first design, and micro-services architecture. Strong in HR, financials, and project management.
Limitations: No manufacturing or supply chain modules. Exclusively focused on people-centric industries (professional services, education, non-profit). Not suitable for manufacturing or operations-heavy businesses.
How to evaluate composability
When assessing any platform's composability claims, ask these five questions:
- Can I deploy one module without deploying all? True composability means incremental adoption.
- Can I update one module without updating the rest? Independent upgrade cycles are essential.
- Can I build custom apps using the same framework? Custom apps should be first-class citizens.
- Is every function available via API? API-first means any component can be replaced or extended.
- Can I combine components from different vendors? True openness means no vendor lock-in.
Composable is not a checkbox feature. It is an architecture decision that determines how fast you can evolve your operations for the next decade.