SmartPack 360 is the most complete project I have built: a working ERP for horticultural warehouses that combines operations, quality, traceability, HR and BI. It is not a toy demo: it runs locally with a backend, API and dashboard, and it is designed to be shown in an operations or quality interview.
An ERP, not an app
The first thing I learned is that an ERP is not an application: it is domains, roles and processes designed before the code. Receiving, packing, stock, shipping, invoicing, quality, HR... each module has its rules and its users.
Building it phase by phase
- Phase 1: core and masters, with JWT and 6 roles.
- Phases 2-4: receiving, traceability, packing, stock, sales, shipping and invoicing.
- Phases 5-6: quality (non-conformities, corrective actions, audits, FMEA, HACCP) and HR.
- Phases 7-9: KPIs, BI dashboard, AI assistant and automations.
Quality and traceability you can prove
The heart of the ERP is traceability from field to cold room to customer, with reverse recall: given a lot, I know its origin, remaining stock and every customer it reached. On quality, I manage non-conformities, corrective actions, audits, FMEA risks and HACCP, focused on complying with standards such as IFS or BRCGS.
BI and AI over real data
The BI dashboard brings together 14 KPIs with trends and Excel export, and the AI assistant answers 16 intents over real data offline, using a rules engine plus safe SQL. No smoke: data that comes from the ERP itself.
An ERP is not technology: it is understanding a business and organising it so others can manage it better.
SmartPack 360 is not deployed yet, but it runs fully on localhost with demo data and over 100 green tests. It is my strongest card to show how I think about operations, quality and product.
