Multi-kiosk distribution and waste tracking

3 kiosks, each selling about 50 menu items, supplied daily from a central kitchen.

Kiosks were supplied daily from a central kitchen, but keeping track of what each kiosk received, what its sales used up, and what was wasted needed one shared record.

The admin enters all raw ingredients, adds the kiosk branches and menu items, and builds a recipe for each item. For example, a Dubai crêpe is crêpe dough, a kunafa portion, Belgian chocolate, pistachio spread, pistachio nuts and a plate, each in its own quantity. Each day the admin records the purchase for every kiosk from the central kitchen. At the end of the day the admin enters each menu item’s sales, and the system updates each kiosk’s inventory through the recipes. Any waste is entered per ingredient.

• Running 3 kiosks with about 50 items each
• Each kiosk’s ingredient stock is updated from the day’s sales
• Daily supply from the central kitchen and waste are recorded in one place
• Stock is calculated from sales and recipes, not estimated

These results come from real use of the product.

We designed the product, planned how it is built, and developed the whole system, front end and back end.

• Admin / operations manager

• Each kiosk keeps its own stock, supplied daily from the central kitchen
• Items are sold as menu items but stock is held as raw ingredients, so recipes had to connect the two
• Waste had to be recorded against ingredients

• Add raw ingredients, kiosk branches and menu items
• Build a recipe for each menu item from ingredient quantities
• Record the daily purchase for each kiosk from the central kitchen
• Enter each menu item’s sales at the end of the day
• Kiosk inventory updates automatically through the recipes
• Enter waste per ingredient

• Angular 21 and TypeScript front end with PrimeNG and Tailwind CSS
• Firebase backend and hosting
• Recipe model linking menu items to ingredient quantities
• Separate stock for each kiosk branch