Labour Cost Management
Staff time is a cost — every recipe should account for it
Enter the time it takes to make each item and your staff hourly rate. MenuCost calculates the exact labour cost per recipe — so every item's total cost includes the people who made it.
WHY THIS MATTERS
Staff time is often the biggest cost in a recipe — and the most commonly ignored one
When café and bakery owners calculate recipe costs, they typically count ingredients. Sometimes packaging too. But the staff member who spent 45 minutes laminating croissant dough, or 20 minutes assembling a layered cake, or 4 minutes pulling and steaming an espresso drink — that time is a direct cost of producing that item. And most of the time, it never makes it into the recipe.
Labour is usually the second or third largest cost in a food business, after ingredients. Leaving it out doesn't reduce it — it just hides it. The money still goes out in payroll every month. But without it in your recipe cost, your margins look higher than they are, and your pricing decisions are made on incomplete information.
Example: A barista earns SAR 20 per hour. Making a specialty latte — grinding, tamping, pulling the shot, steaming milk, adding syrup — takes 6 minutes. That's SAR 2.00 in labour per cup. At 60 cups a day, that's SAR 120 a day, SAR 3,600 a month in labour cost from a single item. If that SAR 2.00 is missing from your recipe, your margin is overstated by a significant amount — and your selling price may not be covering your real costs.
Labour Cost Management puts the time cost into every recipe — so the cost you see is what it actually costs your business to make that item.
HOW IT WORKS
Five things Labour Cost Management does for you
Set your staff hourly rates once
Enter the hourly rate for each role in your kitchen — baker, barista, kitchen assistant. You set this up once. MenuCost uses these rates to calculate labour cost across all recipes that reference each role.
Enter the prep time per recipe
For each recipe, enter how many minutes it takes to make one batch — active prep, cooking, assembly, and finishing. MenuCost combines this with the hourly rate to calculate the exact labour cost per batch and per unit.
Batch size adjusts labour cost automatically
Making 24 croissants instead of 12? Change the batch size and the labour cost per unit recalculates. If prep time scales with batch size, your per-unit cost reflects that — not a flat rate applied regardless of quantity.
Labour appears as its own line in every recipe
Inside each recipe, labour is a separate cost layer — broken out clearly alongside ingredients, packaging, and overhead. You can see immediately how much of the total cost is staff time.
Update a staff rate once — all recipes adjust
If you give your baker a pay rise, update their hourly rate once. Every recipe that uses their role recalculates the labour cost automatically. Nothing falls out of sync when rates change.
REAL EXAMPLE
Labour cost broken out across a bakery's menu
A sample bakery — each item's prep time and labour cost per unit calculated automatically from the hourly rate.
The layered cake carries SAR 10.00 in labour alone — 31% of its total cost. That's visible only when labour is tracked per recipe. Without it, that cost is absorbed silently into thin margin or unnoticed losses.
WHAT YOU GET
What changes when labour is always in the cost
- A cost number that reflects what the business actually spends. When labour is included, the total cost per recipe accounts for everything — ingredients, packaging, staff time, and overhead. Nothing is hidden.
- Visibility into which items are labour-intensive. Some items take three times as long to make as others. Seeing the labour cost per recipe tells you which items demand the most from your team — and whether the selling price reflects that.
- Better decisions about your menu. A high-labour item with a thin margin is a problem that only shows up when labour is tracked. With it in the cost, you can decide whether to reprice, simplify the recipe, or discontinue the item.
- Rate changes handled automatically. When staff wages increase, update the hourly rate once and every recipe that uses that role recalculates. Your cost numbers stay current without manual work.
QUESTIONS
You can add multiple labour entries per recipe — one for each role involved. For example, a baker at SAR 20/hr for 45 minutes of prep, and a kitchen assistant at SAR 15/hr for 10 minutes of packaging. MenuCost adds all the labour entries together into the total labour cost for that recipe.
Use active hands-on time only — the minutes a staff member is actually working on the recipe. Oven time, proofing, or resting time when staff are free to work on something else should not be included, since no additional labour cost is being incurred during that period.
Yes. When you change the batch size, MenuCost recalculates labour cost per unit based on the updated batch. If doubling the batch only adds 20% more prep time — because setup time stays fixed — you can adjust the prep time entry accordingly and the per-unit labour cost will reflect the efficiency gain.
A rough estimate is better than leaving labour out entirely. Time your staff making a batch once — either yourself or by asking them. Most prep times stay consistent once you've measured them. Even a ±5 minute estimate gives you a far more accurate cost than SAR 0.00.
Yes. Inside every recipe, labour is its own line in the cost breakdown — shown alongside ingredients, packaging, and overhead. You can see exactly how much staff time costs per unit and what percentage of total cost it represents.
Cost your recipes with staff time included
Join bakeries and coffee shops who price with confidence
✓ 7 days free · ✓ Cancel anytime