Enterprise ERP Platform

Arian System's ERP is a large-scale enterprise platform covering more than twenty business modules. Each module has its own domain, its own screens and its own backend surface, but all of them ship as one product to the same users.

My role is on the core frontend platform: the architecture, scaffolding, shared components and standards that every module is built on, plus the cross-cutting features — reporting and real-time notifications — that all modules depend on.

Growth was the problem. Every new module added surface area, and without a shared foundation each one drifted: different structure, different patterns, different components solving the same problem twice.

That drift has a cost on three axes at once — consistency for users, ramp-up time for developers, and integration effort whenever a module has to talk to the rest of the platform.

Treat the ERP as a platform, not as a collection of applications. That means the decisions a module author should not have to make — folder structure, state layer, data fetching, form handling, table and layout components — are made once, in the core, and handed to them as scaffolding.

Everything module-specific stays in the module. Everything shared moves into the platform, with a standard for how a module plugs into it.