The 58-module ERP: what 'one platform' means
Why MetalogixERP is built as one platform rather than a stack of add-ons, and how plans and gating keep it manageable.
When we tell operations leaders that MetalogixERP has 58 modules, we usually get one of two reactions. The first: "Good, no add-ons." The second, more interesting: "Isn't that bloat?"
Both miss what is different. A platform designed as one system is not the same as a stack of separate products with everything switched on. This post explains the difference and how we keep the breadth from getting in your way.
The cost of a stitched stack
A typical growing business ends up with a base system, a warehouse tool, a purchasing tool, a reporting tool and some glue between them. The cost is not only in licences. It is in the person whose week revolves around CSV exports, connector fixes and reconciling totals that should already match.
The hidden cost of separate tools is the rationing it forces inside your own company. Teams stop asking "where should this data live?" and start asking "is it worth another subscription?"
What changes with one platform
- Every record lives in one workspace, scoped to your business and covered by the same audit log.
- A module that hands data to another hands it a live link, not a file.
- Reports can reach across modules without a separate reporting tool.
Everyday workflows that cross modules
Take a wholesale reorder. It starts in Sales, draws on Inventory, moves through Warehouse and Fulfillment, and ends in Invoices and Financial, with Xero kept in step. Or a supplier return: Purchasing, Receipts, Inventory and Financial all have a part. On a stitched stack each hand-off is a place for numbers to drift. On one platform each hand-off is the same record.
Three things one platform allows
Cross-module questions
When the data lives together, a question that spans purchasing, suppliers and inventory is a single query rather than an integration project.
One audit trail
Changes in any module write to the same audit log, so "who changed what, and when" has one answer.
AI that reads the whole business
The copilot reads the same records the rest of the system writes. It works with several model providers, and an MCP server lets your own agents use the same capabilities. The agent acts as the signed-in user, inside the same tenant isolation, so it can never see what the person asking could not.
Keeping breadth from becoming bloat
- Plans gate capability on the server. Higher plans unlock more modules. Features your plan does not include stay visible but locked, with a clear way to upgrade, and your data is never deleted if you change plan.
- Modules are organised by the job you are doing, such as selling, fulfilling or closing the books, rather than by which team owns a feature.
- Enterprise can switch modules on or off per company, so each entity sees only what it uses.
In short
"One platform" is not a claim about an all-in-one box. It is a design choice: one workspace, one source of truth, one audit log and one navigation grammar across everything the business records. The 58 modules are the consequence, not the goal.