Challenge
Bread yield was known only from what the head baker said, reseller debts were in the cashier's notebook, and unit costs were calculated quarterly, after the fact, in Excel.
Management system · manufacturing · food industry
Halyk Nan: a management system for a bakery plant
Mixing, inventory, shipments to dozens of resellers and their debts lived in notebooks and Excel, and unit costs were known once a quarter. Now it all runs in one system.
- 34 modules
- 11 roles
- PWA for resellers
- Telegram bot
34modules — from mixing plan to P&L
11roles with precise permissions
30dough batches per shift in the system
What we built
- Mixing planrecipes, mixing and proofing times, yield, rejects, day and night shifts.
- Inventory & purchasingraw materials, finished goods, shelving and spare parts for the chief mechanic.
- Shipmentsa resellers × bread types matrix, two delivery runs, personal price lists and bonuses.
- Financecash desk, cash flow, P&L, daily unit costs, reseller and supplier debts.
- Payrolltimesheets and pay calculated from actual shifts.
- PWA & botresellers place orders from their phones, and every evening a Telegram bot sends each of them a personal debt statement.
Result
The system runs live production in two shops. Unit costs are calculated daily, and the cashier no longer phones debtors — the bot does it.
Technology
- NestJS
- PostgreSQL
- React
- TypeScript
- Ant Design
- PWA
- Telegram Bot API
What it looks like
Have a similar task?
Tell us what you need to automate or build. We will show similar solutions and estimate the timeline on the first call.