A recipe for a Shopify product is a bill of materials with a cook's details: ingredients by weight, a yield, any sub-recipes (a dough, a sauce, a filling), and the packaging per unit. Shopify stores none of it. Food and drink makers keep recipes in a spreadsheet for costing, or in an app that also uses them to take ingredients off stock when a batch is made. The parts that make a recipe useful for inventory are the yield, the units, and the waste.
The short version
- Shopify has no recipes, ingredients or batches.
- A recipe for inventory needs: ingredients and quantities, the yield, units of measure, waste, and packaging per unit.
- Sub-recipes (dough, sauce) let one change update every product that uses them.
- Cost per unit = recipe cost ÷ actual yield, not planned yield.
- Version recipes. A changed recipe changes cost and labels.
A recipe built for inventory
A made-up bakery, Kalihi Valley Bakehouse, sells banana bread loaves on Shopify.
Sub-recipe: banana batter (makes 12 kg)
| Ingredient | Quantity |
|---|---|
| Ripe bananas | 4.5 kg |
| Flour | 3.2 kg |
| Sugar | 2.0 kg |
| Butter | 1.4 kg |
| Eggs | 24 |
| Baking soda, salt, vanilla | 0.12 kg |
Product: banana bread loaf
| Component | Per loaf |
|---|---|
| Banana batter | 600 g |
| Macadamia nuts | 40 g |
| Loaf liner | 1 |
| Bag and label | 1 |
One batch of batter makes 20 loaves on paper; with 2% lost in the pans, 19 or 20 in practice. That actual number is the one to cost with. Shopify bill of materials covers the general idea.
Units: bought one way, used another
Flour comes in 50 lb bags, the recipe uses grams. Eggs come by the case of 15 dozen, the recipe uses each. Write the conversion once in the recipe system, so stock is counted in the unit you buy and used in the unit you cook.
Allergens and labels come from the recipe
The recipe is where the label's ingredient list and allergens come from. Wheat, eggs, milk (butter) and tree nuts (macadamia) are all in the loaf above. When a recipe changes, the label changes too. Shopify allergen information covers showing them on the product page.
Scaling a recipe
A recipe written for one pot needs scaling for a bigger batch. Multiply every ingredient by the same factor, then check the ones that don't scale evenly: leaveners, salt and spices often need adjusting, and cooking or cooling times change with volume. Write the scaled version down as its own recipe with its own yield, rather than multiplying in your head on a busy morning.
Versioning
Keep the old version when you change a recipe: a new flour, a different nut, less sugar. Batches made under the old recipe used old ingredients, and a recall or a label question needs to know which.
Where this stops working
A recipe in a spreadsheet costs the product but doesn't move stock. After each bake someone has to subtract bananas, flour and butter and add loaves to Shopify, and by Friday the sheet and the pantry disagree. Shopify raw materials inventory and recipe costing template for Google Sheets cover the spreadsheet route and where it breaks.
How TaroStack does it
TaroStack for Shopify runs inside your Shopify admin and keeps versioned recipes with sub-recipes, unit conversion and scrap. It shows what you could make right now from what's on the shelf. A batch takes its ingredients off stock by recipe, records which lots it used, costs itself from what it actually used, and adds the finished loaves to your Shopify location. Free for 14 days.
