Replacing a Manual Canteen Ledger With Real-Time Inventory

A multi-school canteen operation came to me with a problem that had nothing to do with software originally: each school's canteen was tracking menus, ingredients, and purchase orders independently, on paper or in disconnected spreadsheets. That caused inventory mismanagement, inconsistent meal planning, and inefficient procurement across the group.

The constraint that shaped everything: multi-tenancy

This wasn't one canteen, it was several, each needing its own data, staff, and permissions, while still rolling up into a shared dashboard for oversight. That meant the architecture had to handle multi-tenant data isolation correctly from the start, not as an afterthought bolted onto a single-school system later.

What the system does

• Multi-tenant architecture so each school's data stays properly isolated
• Menu management with dynamic recipe creation
• Ingredient inventory tracking tied directly to those recipes
• Automated purchase order generation based on real stock levels, not manual reordering
• A centralized dashboard for cross-school analytics and summaries
• Role-based access separating school admins from canteen staff

Impact

Canteen operations efficiency improved by 65% through centralized menu, inventory, and procurement management, replacing what had been independent, manual tracking at every location.

What I'd flag for anyone building something similar

Multi-tenant systems demand strong data isolation and structure from day one, retrofitting it later is far more painful than designing for it upfront. And inventory tracking is only as good as how tightly it's tied to what's actually being planned and sold, disconnected inventory and menu systems just recreate the same reconciliation problem you were trying to eliminate.