Food production

Central kitchen recipe-costing system

Restaurant with a central kitchen · A recipe-costing system for a restaurant’s central kitchen. The admin enters ingredients with prices, builds reusable mixtures and recipes, and sees the net cost of every menu item. Chefs see quantities only.

Food production
Restaurant with a central kitchen
Tech Duo’s roleWe designed the product, planned how it is built, and developed the whole system, front end and back end.
Built withAngular 21, TypeScript, Node.js, Firebase, PrimeNG, Tailwind CSS
Recipe screen listing ingredients and mixtures with the net cost for the admin

Overview

More than 100 recipes in the system, helping the restaurant plan catering and control its prices.

Problem

The restaurant needed to know what each menu item really costs and keep control of its prices, while the kitchen team needed clear instructions for mixtures and recipes without seeing any cost.

Solution

The admin enters all raw ingredients with their prices, builds mixtures from those ingredients, then builds recipes from ingredients and mixtures and assigns each recipe to a menu item in a category. A recipe can combine several ingredients and several mixtures, such as a cream mixture, a crêpe mixture and a chocolate spread. Only the admin sees the net price of a recipe. The chef signs in to see how to make mixtures and recipes, with quantities only and no prices.

What improved

  • More than 100 recipes managed in one system
  • The admin sees the net price of every recipe
  • Chefs follow recipes and mixtures without seeing any price
  • Price changes flow through to every recipe automatically
  • Helps the restaurant plan catering and control its prices

These results come from real use of the product.

Tech Duo’s role

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

Users and roles

  • Admin / owner (ingredients, prices, net costs)
  • Chef (mixtures and recipes, quantities only)

Requirements and limits

  • Prices and net costs had to stay hidden from the kitchen team
  • Recipes are layered: ingredients go into mixtures, and mixtures and ingredients go into recipes
  • The chef needed full preparation detail without any pricing

What it handles

  • Add raw ingredients with prices
  • Build mixtures from ingredients
  • Build recipes from ingredients and mixtures
  • Assign each recipe to a menu item and category
  • Admin reviews each recipe’s net price
  • Chef follows mixtures and recipes by quantity
  • Update an ingredient price and every mixture and recipe using it recalculates automatically

How it is built

  • Angular 21 and TypeScript front end with PrimeNG and Tailwind CSS
  • Firebase backend and hosting
  • Role-based access: the admin sees costs, the chef sees quantities only
  • Net cost calculated from ingredient prices through mixtures into recipes

Screens from the product

Built with

Related services

Need something in this direction?

If this problem looks familiar, tell us how your operation works today. We will help you decide what to build first.

Start a project