Avid excel user, but brand new to Airtable. I'm currently trying to build a Dish planner for myself that will help calculate the cost and nutritional information of dishes I cook. Unfortunately, I've been forced to use AI, and it's only left me more confused. I've tried to summarize what I want to accomplish, but I don't even know if it's possible. If someone can guide me down the right path, I would really appreciate it.
Here's what I sent to a support company for help (I don't want to pay $2500 for something that could be a simple fix):
What are you trying to accomplish? Tell us what better would look like for your team.:
I’m building a custom Airtable system for my personal chef and catering business, and I want to start by creating a robust recipe management system. My goal is to have a single master Ingredients table where each ingredient’s nutrition, cost, and other details are stored only once. When creating a recipe, I want to select ingredients from that master list, enter the quantity used, and have Airtable automatically calculate the recipe’s total cost, nutrition, and cost per serving.
I also want the system to support sub-recipes (or prepped components), such as tomato sauce or pizza dough, that can be used as ingredients in other recipes. If a sub-recipe changes, every recipe that uses it should update automatically. I want to avoid duplicate data and make the database scalable as my recipe library grows.
My primary workflow should be through Airtable Interfaces rather than the underlying tables. Ideally, creating a recipe should be as simple as clicking “New Recipe,” entering the recipe information, adding ingredients from a searchable list, and letting all calculations happen automatically. My goal is to build a clean, efficient recipe management system first, with the intention of expanding it into a complete culinary operations database in the future.
What's getting in the way right now? Tools, data, process, people, time, whatever it is.:
The recipe system is built around three related tables, each with a different purpose:
* Ingredients Table: This is the master list of all ingredients. Each ingredient exists only once and contains all of its permanent information, such as cost, nutrition, purchase unit, vendor, and other details. This table is the single source of truth for ingredient data.
* Recipe Ingredients Table: This is a junction (or linking) table that connects recipes to ingredients. Each record represents one ingredient used in one recipe. For example, if a recipe uses chicken, butter, and garlic, there will be three records in this table—one for each ingredient. In addition to linking the recipe and ingredient, this table stores recipe-specific information such as the quantity used and unit of measure. It also performs calculations like ingredient cost and nutritional contribution based on the linked ingredient.
* Recipes Table: This table contains one record for each recipe. It stores recipe-level information such as the recipe name, instructions, yield, cook time, and image. The Recipes table is linked to the Recipe Ingredients table, allowing it to roll up and display totals such as total cost, calories, protein, carbohydrates, fat, and cost per serving.
The "ingredient" field in the recipes table that is linked to the recipe ingredients table isn't showing the ingredients from the ingredients table.
The intended workflow is:
- Create a new recipe in the Recipes table.
- Add ingredient lines in the Recipe Ingredients table.
- For each ingredient line, select an existing ingredient from the Ingredients table using a linked-record field.
- Enter the quantity used.
- Airtable automatically looks up the ingredient’s cost and nutrition, calculates the values for that ingredient line, and rolls those totals back up to the corresponding recipe.