FeelEat’s kitchen runs on one recipe system.
The kitchen portal for FeelEat’s kitchen. It covers each step from recipes, sub-recipes and prep to cooking, jar filling and labels, and records who did each step and how long it took.
The kitchen’s process, written into one system.
Every FeelEat meal starts in its kitchen. Recipes are built from sub-recipes, each with its own prep steps and quantities, and every day the kitchen has to know which dishes to cook.
In the kitchen portal, each recipe lists its sub-recipes, prep steps and quantities, and the portal shows which dishes need cooking. It records who cooked each dish and how long each step took, checks steps as they are done, tracks wastage, handles jar filling and label printing, keeps a photo of every dish and step, and reads weights from the kitchen scales.
A lot happens between recipe and jar.
Sub-recipes, quantities, cooking, filling and labels all have to line up every day.
Many steps, many hands.
The work the portal had to hold.
- Layered recipes: dishes built from sub-recipes, each with its own steps and quantities.
- Daily cooking: knowing which dishes need cooking.
- Jars and labels: every dish filled into jars and labelled.
Every step is in the portal.
We built the kitchen portal around how the kitchen works.
- Recipe structure: each dish with its sub-recipes, prep steps and quantities.
- Who and how long: who cooked each dish, and how long each step took.
- Step checks: steps validated as they are done.
- Photos: a photo of every dish and of each process step.
From recipe to labelled jar.
What the kitchen portal holds.
Recipes and sub-recipes
Dishes stored with their sub-recipes, prep steps and quantities.
Cooking list
Which dishes need cooking.
Cooking records
Who cooked each dish and how long each step took, with each step checked.
Wastage
Wastage recorded in the same system.
Jar filling and labels
Jar filling and label printing.
Photos and scales
A photo of every dish and step, and weights read from the kitchen scales.
Built around how the kitchen works.
Each feature follows a step the kitchen already takes.
Conceptualisation
Mapped the kitchen’s steps, from recipe to labelled jar.
Design
Screens for recipes, cooking, filling and labels.
Development
The recipe structure, cooking records, wastage, labels, photos and the link to the scales.
Deployment
Put into use in FeelEat’s kitchen.
Bring your version of the Unified Recipe System problem. Four hours, free, with the team that shipped this one.
Book the free workshopWhat kept us up at night.
Why a generic task app wouldn’t have worked.
Sub-recipes inside recipes
A to-do list can’t hold recipes built from sub-recipes, each with its own steps and quantities. The portal stores them the way the kitchen uses them.
Weights from the scales
The portal connects to the kitchen scales, so weights come straight from them.
Tech stack.
The backend uses NestJS on Node.js, as FeelEat’s other systems do, with MySQL and Redis.
Numbers the owners watch.
What the kitchen portal covers.
Every dish is made from the same recipe data.
A photo of each dish and of each process step.
Jars filled and labels printed from the portal.
Want numbers like these? Here is what happens after you write.
Keep exploring.
Every project here is live, paid for, and earning revenue for its owners.
Frequently asked questions
Put it in a brief. A senior engineer reads it and replies within one business day.
What is the Unified Recipe System?
It is the kitchen portal FeelEat’s kitchen runs on, built by CODT Technologies. It holds every recipe and sub-recipe with prep steps and quantities, shows which dishes need cooking, and records who cooked each dish and how long each step took.
What else does the kitchen portal handle?
Step checks, wastage, jar filling and label printing. It keeps a photo of every dish and of each process step, and it connects to the kitchen scales.
Is the kitchen portal part of FeelEat’s ERP?
Yes. It is one of the three portals CODT Technologies built for FeelEat, next to the customer portal and the supplier portal.
Have a problem worth
solving well?
Tell us about your product, your timeline and your constraints. We reply within one business day with an honest read on fit, scope and the right team.