01
The dilemma
The business had outgrown its ERP years earlier and was managing the gap with effort. A rigid client-server system sat at the center of a multinational distribution operation it could no longer describe, let alone scale with.
What was breaking
- A legacy ERP that could not scale or adapt. Client-server architecture, slow to change, and increasingly a constraint on how the business could operate rather than a support for it.
- High inventory carrying costs. Poor visibility into stock across locations meant the safest decision was always to hold more, and capital sat in warehouses accordingly.
- Approvals without structure. Sales and procurement approvals had no consistent process, which meant they were slow in some places and absent in others.
- Fragmented communication. Country operations worked in parallel rather than together, with no shared catalog, pricing discipline or communication standard.
- No cross-country coordination. The group operated as several companies that happened to share a name.
The cost of standing still
In industrial distribution, margin is made in inventory turns and approval discipline. Poor stock visibility across locations ties up working capital permanently, and inconsistent approvals mean the group's commercial terms depend on which country a customer happens to buy from.
02
The idea
A like-for-like ERP replacement would have reproduced the original constraint in newer software. We treated the migration as a chance to redesign how the group operates across borders: one catalog, one pricing structure, one approval standard, and inventory visible everywhere rather than country by country. The platform choice followed the operating model, not the other way round.
The principles we worked to
- Standardize before you migrate. Catalog, pricing and approval rules agreed across countries first, the hardest part of the project, and the one that determined whether it worked.
- Inventory visibility as the commercial objective. Not an IT feature. The point of the project was releasing working capital.
- Encode approvals as process, not policy documents. Blueprints enforce the sequence; nobody has to remember it.
- Multi-currency handled natively. Rather than through the parallel spreadsheets the old system had required.
What we ruled out, and why
| Option considered | Why we did not take it |
|---|---|
| A tier-one ERP replacement | Correct on paper for a multinational, wrong on economics and timeline for a business that needed working capital released this year, not in three. |
| Upgrading the existing client-server ERP | Would have bought capability without addressing architecture, and left the group on-premise in a multi-country operation. |
| Country-by-country migration | Politically easier, but it defers the standardization that was the actual value of the project. |
03
The build
Delivered as five connected workstreams.
Procurement-to-sales process
Modules supporting the end-to-end flow from purchase through stock to customer sale, so a transaction is traceable across the whole chain rather than stitched together from separate systems.
Location-wise stock tracking with automated replenishment
Advanced tracking by location combined with replenishment logic, directly addressing the inventory carrying cost that had been the group's largest hidden expense.
Approval governance through Blueprints
Standard operating procedures and multi-stage approvals enforced by the system, applied consistently across countries.
Centralized catalog and pricing
One product catalog and one pricing strategy across the group, replacing country-level variation with deliberate structure.
Executive analytics
Management reports and dashboards giving real-time visibility across locations and currencies from a single cloud platform.
04
The impact
| Measure | Before | After |
|---|---|---|
| ERP architecture | Rigid client-server | Unified cloud platform |
| Inventory visibility | Poor, country by country | Location-wise, real time |
| Replenishment | Judgement-based | Automated logic |
| Approvals | Inconsistent by country | Blueprint-enforced, standardized |
| Product catalog and pricing | Fragmented | Centralized across the group |
| Multi-currency operation | Handled around the system | Handled natively |
| Management reporting | Compiled per country | Unified real-time dashboards |
Beyond the numbers
- Supply chain optimized and inventory control tightened. The direct route to releasing the working capital that poor visibility had been consuming.
- Approval processes and communication standardized globally. The group now operates as one business across borders.
- Infrastructure scales with the business. Multi-location and multi-currency operations handled without additional systems.
05
What comes next
The engagement continues. These are the next moves on the table.
- Supplier performance analytics built on procurement history.
- Demand forecasting feeding the replenishment logic.
- Customer self-service ordering against live stock positions.
Engagement delivered by the Ideentrix founding team. Technologies, scope and outcomes as recorded at project close, published with the client's consent.
