Restaurant inventory, recipes and dish costing
6 min read ·
A dish can look profitable on paper while oversized portions, waste and changing purchase prices consume its margin. Useful costing starts with consistent ingredient names and units, followed by a practical standard recipe and reliable stock counts. Recording a supplier’s invoice total is only the beginning: you also need to know what was bought, used and left on hand.
Standardise ingredients and measurement units
Give each ingredient a clear identity and a base unit such as kilograms, litres or pieces. When purchasing a carton containing several packs, document its conversion into the unit used by the recipe. Confusing a carton price with a kilogram price produces misleading dish costs even when every supplier invoice has been entered correctly.
Distinguish purchased quantity from usable quantity when trimming, preparation or cleaning causes a loss. The weight of vegetables before preparation may not equal what reaches the dishes. Measure actual kitchen yield rather than borrowing a general percentage, and assign responsibility for reviewing conversions whenever a supplier changes the pack size or product specification.
Write a standard recipe and cost it
Theoretical recipe cost is the sum of each ingredient quantity multiplied by its unit cost after converting measurements consistently. If a recipe uses 0.2 kilograms of an ingredient costing SAR 30 per kilogram, that ingredient contributes SAR 6. Include minor ingredients and packaging where relevant, but do not confuse material cost alone with the dish’s complete operating cost.
ORO’s recipe editor lets you link a menu item to inventory ingredients, quantities and units. Use those links as a shared recipe reference for the kitchen and management, checking availability under your plan. A saved recipe does not, by itself, establish every actual consumption movement: review physical counts, inventory movements and the recording process used by your restaurant.
Distinguish recipe cost from period COGS
Theoretical cost answers what a dish should cost at its specified quantities. Period cost of goods sold requires a review of stock movements. A simplified starting point is opening inventory plus purchases minus closing inventory, with returns, transfers and other uses treated consistently. Ask your accountant to define the appropriate valuation and classification basis.
Record waste when it happens, including the ingredient, quantity and reason. Separate spoilage from staff meals, testing and authorised hospitality. Compare expected and actual use without assuming every difference is waste or theft. A wrong unit, an outdated recipe, an inaccurate count or an unrecorded transfer between locations can also explain a discrepancy.
Compare suppliers on a consistent basis
Do not select a supplier from the pack price alone. Compare usable-unit cost, quality, delivery reliability and receiving conditions, using consistent VAT treatment. A cheaper pack may contain less product or produce more preparation loss. Keep the latest purchase reference and understand the reason for a cost change before altering menu prices.
ORO’s supplier tools include purchase history with details such as ordered quantity, received quantity and unit cost, depending on your plan. Review that evidence alongside stock counts and purchase orders rather than relying on memory. Start with ingredients that matter most to your costs, then expand the review and assign an owner to each unexplained difference or recipe change.
Frequently asked questions
Is recipe cost the same as COGS?
No. A recipe is a standard estimate for a dish, while period COGS depends on inventory movements, valuation and relevant accounting treatment.
How should carton purchases be handled?
Define the carton contents and conversion to the base unit, then use that conversion consistently in receiving, costing and recipes.
Is inventory available on every plan?
Inventory and supplier functionality can depend on your plan. Review the pricing page and included features before choosing your workflow.