Food and labor costs
Restaurant food cost: recipes, invoices and better decisions
A useful food-cost report connects the supplier’s pack to the portion you actually serve. Start with receiving and recipe quantities, then distinguish a calculated dish cost from stock on the shelf and profit in the business.
Which food-cost question are you trying to answer?
Recipe cost asks what a defined portion should cost at the ingredient prices being used. Theoretical period usage combines those recipes with the dishes sold. Purchases show what arrived or was invoiced during a period. These are different measures: receiving a case today does not mean its contents were all consumed today.
Actual inventory-based food usage generally starts with opening stock, adds purchases and subtracts closing stock, with the appropriate adjustments for transfers and credits. Comparing that result with recipe-based usage helps locate a difference; it does not explain the cause by itself. A missing count, an unrecorded staff meal, an inaccurate portion and spoilage can produce different operational problems behind a similar number.
Choose a consistent period and sales basis before comparing percentages. Keep sales tax separate from the selling price used in a dish-cost calculation. Ask your accountant which adjustments belong in your period report, and label reports so a manager cannot mistake purchase share for counted cost of goods sold.
Worked example: turn a supplier pack into a portion cost
Consider a hypothetical case of tomatoes: 10 pounds cost $18, and trimming leaves 9 pounds usable. The usable cost is $18 ÷ 9 = $2 per pound. A four-ounce usable portion is one quarter of a pound, so its tomato cost is $0.50. Dividing by the purchased weight without accounting for yield would report $0.45 instead.
Suppose the complete recipe costs $4.20 and sells for $14 before tax. Its recipe food-cost percentage is $4.20 ÷ $14 × 100 = 30%. The remaining $9.80 has to cover whatever costs are excluded from that recipe calculation. It is not the restaurant’s net profit.
If the tomato case rises to $21.60 and yield stays the same, the tomato portion costs $0.60. With everything else unchanged, the dish costs $4.30. At an illustrative 30% food-cost target, the unrounded selling-price calculation is $4.30 ÷ 0.30 = about $14.33 before tax. That is a review prompt, not an instruction to raise the menu price: portion consistency, supplier quality, guest expectations and the full business economics still matter.
- Confirm the supplier pack size and purchase unit.
- Measure usable yield rather than guessing it indefinitely.
- Use the recipe’s actual portion unit.
- Keep the selling price and tax basis consistent.
- Label which costs the calculation includes.
Build a recipe tree that another cook can check
Start with ingredients, then preparations, then menu dishes. A dressing can be one reusable preparation with its own batch yield; a salad uses a measured portion of that dressing. When the oil cost changes, you want to see the dishes that depend on the preparation without rebuilding every recipe.
Write the quantity and unit for each connection. “One sauce” is ambiguous unless the portion is defined. Separate substitutions, optional extras and packaging from the standard plated dish where they change cost. Cost a takeaway version as well as the dine-in version if their contents differ.
In Jooule, approved recipe versions can connect ingredients, shared preparations, mapped modifiers and supported packaging. Missing prices or unmapped choices remain visible as gaps. An AI recipe draft, when the service is enabled, is a starting point for a cook to correct; it is not evidence of how your kitchen portions food.
A photographed invoice still needs a receiving decision
A document can say three cases while the driver delivered two. It can also show a credit, a changed pack size or a total that includes tax. Have the receiver compare extracted lines with what actually arrived. Keep the original document available when someone later questions a price.
Jooule can prepare lines from a photo or PDF when document reading is configured. The manager reviews supplier matches, quantities and prices before confirming receipt. Delivery notes, later invoices and credits have their own matching workflow, so the same delivery should not become two purchases merely because it generated two documents.
Make exceptions part of the routine: partial delivery, unreadable line, duplicate upload, unfamiliar supplier description and an invoice covering several deliveries. Assign an owner to unresolved lines rather than quietly accepting them to clear a queue.
Review changes in the order you can act on them
Begin with missing data, then inspect price changes and affected recipes. An expensive ingredient used in one rarely sold dish may deserve less attention than a smaller increase across a busy part of the menu. Use recorded sales to understand exposure, while remembering that last week’s mix is not a guarantee of next week’s demand.
For each issue, choose an action and an owner: verify the invoice, remeasure a portion, adjust the recipe, discuss supply terms or preview a menu price. Check a replacement ingredient for quality and relevant dietary information before adopting it. A cheaper pack is not automatically a cheaper usable portion.
Jooule connects a physical stock count with confirmed receipts, recipe use when dishes reach the kitchen, recorded preparation batches and waste. The resulting balance is an estimate anchored to the last count. An ingredient never counted remains unknown. Review missing recipe mappings and record waste rather than interpreting seven burger sales as proof that exactly three portions of tomatoes remain.
With suitable recorded history, Jooule flags ingredients that may not last the rest of service using comparable weekdays. It does not automatically stop selling dishes from that estimate. When two full counts bound the reporting period and the cost data supports it, compare actual food cost with recipe-based cost and investigate the gap. Keep count times, receipt quantities and recipe coverage visible during that review.
Bring these six tests to a food-cost software demo
Bring a real, permitted invoice and two recipes: one simple dish and one that uses a shared preparation. Ask the demonstrator to follow the data instead of presenting only the final dashboard. Separate capabilities available for your restaurant from examples that need another module or service.
- Change the supplier pack size and show the resulting unit cost.
- Correct a short delivery and explain what is posted.
- Upload a duplicate and match a later invoice to its delivery.
- Change an ingredient price and identify the affected dishes.
- Leave one price or modifier mapping missing and show the report’s uncertainty.
- Run a stock count, record waste and explain actual-versus-recipe cost between two full counts, separately from business net profit.
