Recipe management is keeping one current record for each thing you make, and knowing which version of it every batch came from. A home cook has recipes. A food business has recipes that other things depend on: the cost of a unit, the ingredient list on the label, the allergens it declares, what to order for next week, and how much a batch should yield. When the recipe changes and those don't change with it, they drift apart, and the first sign can be small, like a cost sheet worked out from a recipe that has changed twice since. Managing recipes means there's one place the recipe lives, a change makes a new version with a date, and everything downstream is worked out from that version. Below is what a recipe record holds, what goes wrong without one, and a checklist.
The short version
- One record for each recipe, in one place. Not a binder, a spreadsheet and someone's memory.
- Ingredients by weight, with the yield a batch should make.
- Every change is a new version, with a date and who approved it.
- Each batch records which version it used.
- Cost, label and allergens are all read from the current version.
- A component you make in house is its own recipe.
- TaroStack keeps recipes by weight with versions and costs every batch. More below.
What a recipe record holds
| What to keep | Why | Example: a granola |
|---|---|---|
| Name and code | So everyone means the same recipe | Honey Almond granola, HA-12 |
| Version and date | So you know which recipe made which batch | Version 4, from Nov 3 |
| Yield | What one batch should make | 40 bags of 12 oz |
| Ingredients, by weight | Cups don't scale, and costs come from weights | Oats 20 lb, honey 6 lb, almonds 5 lb, oil 2 lb |
| Sub-recipes | A component made in house is its own recipe | None here. A house caramel would be one |
| Packaging | It's part of the cost and it runs out too | 40 bags, 40 labels, 4 cases |
| Method | Steps, times and temperatures | Toast 25 minutes, stir at 12, cool before bagging |
| Allergens | What's in it, and what the label must say | Tree nuts |
| Cost of a unit | From today's prices, not last year's | From the last deliveries |
| Label and claims | The ingredient list has to match this version | Checked against version 4 |
| Approved by | One person signs off a change | The owner, Nov 3 |
A layout for the record itself is in standardized recipe template. Listing a recipe as materials and quantities is a bill of materials: see bill of materials for food.
What depends on the recipe
Cost. The cost of a bag is the recipe's weights times what each ingredient cost you, plus packaging, divided by the yield. If the recipe on file is last year's, so is the cost. See batch costing example.
The label. The ingredient list is the recipe in order of weight. In the granola, version 3 had 6.5 lb of honey and version 4 has 6. That half pound doesn't change the order: honey is still ahead of the 5 lb of almonds. A cut to 4.5 lb would put almonds first of the two, and the label would be wrong. See ingredient statement example.
Allergens. They come from the ingredients, including the ones inside a sub-recipe and the ones that came in with a change of supplier. See food allergen labeling requirements.
Ordering. Next week's plan times each recipe says what to buy: see MRP spreadsheet template.
Yield. A recipe that says 40 bags and makes 37 is telling you something about the recipe, the scale or the bagging. You only see it if the 40 is written down. See batch yield formula.
Versions
The habit that separates managing recipes from having them is this: nobody edits a recipe. They make a new version. The old one stays, dated, because batches were made from it.
| Version | From | Change | Why |
|---|---|---|---|
| 3 | Aug 12 | Almonds from 4 lb to 5 lb | Customers asked |
| 4 | Nov 3 | Honey from 6.5 lb to 6 lb | Too sweet |
When a customer complains about a bag from October, the batch says version 3, and you know what was in it. A change that touches the label, the allergens or the shelf life needs its checks done before the first batch: that's what a change control log is for.
Do you need software for it?
Not at first. Twelve recipes fit in a spreadsheet with a tab each, if one person owns the file and versions are kept as dated copies. It gets hard when recipes share sub-recipes, when ingredient prices move monthly, or when more than one person can change the file. Then the cost tab is out of date the day after it's built. What to look for is in recipe costing software.
Get the checklist
Download the recipe record checklist. One sheet and a read-me: the eleven things to keep for each recipe, why each matters, and the granola as an example. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
A spreadsheet holds the recipe. It doesn't know what happened on the floor. The batch sheet on the wall is a printout of version 3. The cost tab uses an oat price from spring. And the question "what was in the bag this customer bought" needs the batch, the version it used, and the lots that went in, three things a recipe file has never held.
How TaroStack does it
TaroStack keeps the recipe and what's made from it in one place.
Recipes are by weight, with versions. A change makes a new version. The old one stays.
Sub-recipes and unit conversion: a house caramel is a recipe used inside another, and an ingredient bought by the case is used by the gram.
Every batch records the version it used and notes the ingredient lots it took, automatically.
Cost is from deliveries, freight included, so a recipe's cost moves when an ingredient's price does, and each batch shows actual cost against standard.
Allergen tracking, on Growth: a batch can't start if its label leaves out an allergen.
Recipe truth: from your own batches, whether a recipe yields what it says.
| The question | Spreadsheet | In TaroStack |
|---|---|---|
| What does a bag cost today | The price when the tab was built | From the last deliveries |
| Which version made this batch | Unknown | On the batch |
| Does the label still match | Checked by eye | The current version's ingredients and allergens |
| Does it yield 40 bags | Nobody compares | Yield against the recipe |
TaroStack doesn't write recipes, make nutrition labels or design labels. Recipes, versions, batches and costs are on every plan: Starter at $9.99 a month holds 5 recipes, Growth at $39 a month holds 50 and adds allergen tracking. The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
