FMCGEnterpriseERP
Clean-architecture ERP for multi-store FMCG trading.
30%
Less manual inventory tracking
25%
Faster API response
20%
Faster data retrieval
2 + 3
Stores & warehouses
The flagship system at Cool & Cool (ABC International Ltd.) — a modern web-based ERP replacing legacy desktop workflows for FMCG trading. It unifies Purchasing, Sales, Inventory, Finance and Warehouse Management into one Clean-Architecture platform that scales with the business across multiple stores and warehouses.
A legacy desktop ERP couldn't keep pace with FMCG trading across multiple stores and warehouses. Inventory was tracked manually, data-entry errors were common, and modules for purchasing, sales and finance were siloed — making the system fragile and hard to scale.
I led the migration to a modern, web-based ERP built on ASP.NET Core with Clean Architecture and an N-Tier design. Each domain — Products, Stock, Purchasing, Sales, Finance — is a modular, independently testable slice with FluentValidation and AutoMapper. Real-time stock synchronization, caching and background jobs turn a manual, error-prone process into a reliable system of record.
Clean Architecture with clear separation between API, Application, Domain and Infrastructure layers. Data access runs through a Generic Repository + Unit of Work pattern over Entity Framework Core; SignalR pushes live stock changes to every connected client; Redis and in-memory caching front hot read paths; Hangfire handles recurring background work; and JWT with role-based access control secures multi-user workflows. Azure App Service and Blob Storage back cloud deployment.
API / Presentation
Controllers · thin, delegate only
Application
Use cases · validation · CQRS
Domain
Entities · rules · zero dependencies
↑ dependencies point inward · infrastructure plugs in from outside
Real-time stock synchronization
SignalR broadcasts inventory changes instantly across stores and warehouses — cutting manual tracking by 30%.
Modular domain design
Products, Stock, Purchasing, Sales and Finance are isolated, testable modules validated with FluentValidation.
Caching for hot paths
In-memory + Redis caching on high-traffic reads improved API response times by 25%.
Secure multi-user workflows
JWT authentication and role-based access control govern every ERP action across departments.
Background processing
Hangfire runs scheduled and long-running jobs off the request thread for a responsive UI.
Repository + Unit of Work
A generic data-access layer keeps queries consistent, transactional and unit-testable.
- Clean Architecture pays for itself the moment a second store or warehouse is added — boundaries make change cheap.
- Real-time UX (SignalR) removes an entire class of reconciliation bugs that caching alone can't solve.
- Caching is a scalpel, not a hammer: measure the hot paths first, then cache deliberately.
Related Projects
Have a system that needs to scale?
I'm open to senior .net & backend engineering roles. Let's talk about what you're building.