Recipe costing for a small hotel restaurant

What a costed recipe actually needs

Every ingredient in the dish, the quantity used, and the unit cost of that ingredient — portioned to the actual amount used, not the price of the unit it was purchased in. A recipe that lists '100g rice' is only costable if the rice's per-gram cost is known, which means it traces back to what you paid for the sack it came from, divided down.

The conversion nobody should be doing by hand

You buy cooking oil by the case and use it by the litre; you buy rice by the sack and use it by the gram. Costing a recipe accurately means converting between a purchase unit and a stock unit correctly every time, and doing that conversion by memory or on a calculator is exactly where costing errors creep in — a recipe's true ingredient cost quietly drifts every time someone estimates rather than converts.

Costing only matters if it stays current

A recipe costed once at opening and never revisited is a snapshot of a supplier price from however long ago. Ingredient prices move, sometimes seasonally, sometimes because a supplier changed — and a menu that never re-costs its dishes is a menu that slowly loses margin on paper without anyone deciding that it should.

A recipe, costed line by line

A chicken curry for two: 300g chicken at ₱180/kg (₱54), 200ml coconut milk at ₱90/litre (₱18), rice, spices and vegetables (₱24), for a total ingredient cost of ₱96. Sold at ₱320, that is 30% food cost — squarely inside target, and now a fact rather than a guess about whether the dish is priced right.

The value is not really in that one number. It is in having gone through the exercise once, correctly, so the next time a supplier's chicken price moves, re-costing the dish is a five-minute update to one ingredient's unit cost, not a rebuild of the whole calculation from scratch.

The real payoff: recipes that draw down actual stock

A costed recipe is useful for pricing. A recipe linked to inventory — where selling the dish actually depletes the ingredients it is made from — is useful for something bigger: it is what turns 'this dish should use 150g of fish' into a checkable fact against what the store's ledger says actually left.

That link is also what makes a void correct rather than a loss: reversing a bill should put the ingredients back, not just cancel the sale, and it should reverse from the specific movements that order actually wrote — not recalculate from the recipe as it exists today, which would silently return the wrong quantities if the recipe or its ingredients changed since the order was placed.

Standardising the portion, not just the price

A recipe cost is only as accurate as the portion actually served. If the costed recipe says 150g of fish and one cook plates 180g on a generous night, the dish's real food cost drifts above the number on paper every time that happens — invisibly, because nothing about the sale looks different from the till's perspective. Standardising portions, with a scale in the kitchen for anything that matters, is what keeps the costed number and the served plate the same dish.

Seasonal swaps need a re-cost, not a shrug

Swapping an ingredient for a cheaper seasonal alternative, or the reverse when a usual ingredient goes out of season and gets pricier, changes the dish's actual cost even if the menu price and the dish's name stay identical. Treating that as worth a five-minute re-cost, rather than assuming the old number still roughly applies, is what keeps the food-cost figure honest through a full year rather than only around the season it was originally costed in.

Start with the dishes that sell the most

Costing an entire menu at once is a bigger project than most small kitchens can finish in one sitting. Start with the handful of dishes that make up most of covers sold — they are worth getting exactly right first, and the rest of the menu can follow at a slower, sustainable pace.

Costing a shared or buffet-style dish

Dishes meant for sharing, or a breakfast buffet item, do not have one obvious 'per order' quantity the way a plated main does — the honest approach is costing the batch as prepared, then dividing by however many servings it realistically produces, rather than guessing a per-portion figure from the recipe's raw ingredient list. A breakfast buffet's egg station, for instance, costs out per estimated servings from a tray, not per egg in the abstract.

What changes once every dish is costed

Once the whole menu carries a real number, the conversation about pricing changes shape entirely — a decision to raise a price, or to quietly reformulate a dish to bring its cost down, is made from a specific figure rather than a feeling that 'this one probably isn't making much.' That shift, from intuition to a number everyone can check, is the actual value of doing the costing exercise at all.

Who keeps the costs current

Recipe costing decays the same way PAR levels do if nobody owns it — set once by whoever opened the kitchen, then never revisited as staff and suppliers change. Assigning it to whoever already handles purchasing, since they are the person who actually sees prices move first, keeps the costed figures closer to what the kitchen is really paying rather than a snapshot from opening week. A short quarterly review — ten minutes checking the top-selling dishes' costs against current supplier prices — is usually enough to catch the drift before it becomes significant.