Recipe Cost Card Template: Fields, Sub-Recipes, and Batch Scaling

Food cost percentage is a scoreboard. The recipe cost card is the scorecard behind it — the per-dish document that tells you whether the number is telling the truth. Dubai's 8,617 restaurants and 5,240 coffee shops compete on margins where a systematic yield error on one high-volume ingredient can cost AED 2,000 a month in invisible food spend. Most kitchens get the math right but build the wrong document: no sub-recipe links, no batch version, prices nobody updates. This guide is about the template that fixes all three.

What follows is a field-by-field walkthrough of the recipe cost card template: what each column does, how sub-recipes (sauces, stocks, marinades, doughs) fit into the structure, when to use a batch card versus a portion card, and a full worked example — a shawarma plate with the garlic sauce costed as its own nested sub-recipe.

What the card actually is (not a cooking instruction)

A recipe card on a laminated sheet tells a cook how to make a dish. A recipe cost card is a financial document that tells management what the dish should cost to produce — and flags when reality drifts from that number.

The difference matters in how you design it. A cooking card optimizes for readability in a hot kitchen. A cost card optimizes for precision at every quantity: it must track what you buy (as-purchased, brutto), not just what you serve (edible portion, netto), because you pay for what you buy — including the parts you throw away in prep.

A properly built cost card answers three questions for every dish:

• How much of each ingredient must I order to produce the correct portion?
• What is the true cost of this dish, accounting for all prep losses?
• If I sell it at this price, what margin does it actually deliver?

Those three questions cannot be answered accurately by a recipe card that records only edible-portion weights and ignores what gets trimmed off, peeled away, or lost to cooking shrinkage.

The eight fields every recipe cost card needs

There is no universally standard recipe cost card format, but every template that works in a production kitchen contains at least these eight columns. Columns 1–4 define what you need; columns 5–7 calculate the cost; column 8 tracks the card's own maintenance history.

Below the ingredient rows: a Total recipe cost row (sum of all line costs), a Menu price field, and a Food cost % cell (Total ÷ Menu price × 100). Those three lines are what management reads; everything above is what makes them accurate.

Cold loss vs hot loss — costing cooked proteins correctly

Yield percentage covers cold loss: weight removed from a raw ingredient by trimming, peeling, boning, or portioning before it touches heat. But proteins also lose weight during cooking — this is hot loss, and it must be built into the AP quantity calculation for any dish where the served portion weight is specified.

The two factors compound. The formula is:

A practical example for a bone-in chicken thigh served at 130g:

• Cold yield: 78% (removing bone and excess fat)
• Hot yield: 72% (roasting at 200°C, 25 min)
• Combined: 0.78 × 0.72 = 0.562
• AP Qty = 130g ÷ 0.562 = 231g purchased weight per portion

Without hot loss, you would have calculated AP Qty at 130g ÷ 0.78 = 167g — a 38% undercount in what you actually order and pay for. This undercount shows up as mysterious variance in your actual vs theoretical food cost reports.

Sub-recipes: sauces, stocks, and marinades as nested cards

The recipe cost card breaks down when sauces, marinades, or other prepared components are entered as a single line item with an estimated cost. In a kitchen that makes its own garlic sauce, the garlic sauce appears in 12 different dishes. If you cost it differently in each dish, or just estimate "AED 0.60 per portion," two things go wrong: costs are inaccurate, and when the garlic price changes you have to find and update all 12 cards manually.

The correct structure is a sub-recipe (also called a semi-finished product or prep recipe): a cost card for the sauce or stock on its own, producing a cost per 100g or per litre. That unit cost then appears as a single line in every dish that uses it.

How to build a sub-recipe card

A sub-recipe card follows the same eight-field structure as a finished recipe card, but its output is not a selling portion — it is a batch of prepared product. The header of the sub-recipe card specifies:

• Batch yield: how much finished product the recipe produces (e.g., 2,000ml of garlic sauce)
• Batch cost: sum of all ingredient costs for that batch
• Unit cost: Batch cost ÷ Batch yield (e.g., AED 22 per litre = AED 2.20 per 100g)

In the finished recipe card, the garlic sauce line reads: "Garlic sauce (sub-recipe) — 30g — AED 2.20/100g — AED 0.66." The sub-recipe card is the source of truth; all finished recipe cards pull from it. When you change the garlic sauce formula or the price of garlic changes, you update one card and all 12 dishes recost automatically.

Common sub-recipes in UAE restaurant kitchens: garlic sauce (toum), tahini, shawarma marinade, hummus, tabbouleh base, stock (chicken, beef, fish), pizza dough, bread dough, pastry cream, tomato base.

Batch card vs portion card

Most recipe management guides describe a single recipe card per dish. In practice, a working kitchen needs two versions of the same card:

A batch card is simply the portion card multiplied by the batch size (e.g., 40 portions). They must be linked: if you update portion sizes or ingredient yields in the portion card, the batch card must reflect the change. Maintaining two separate documents that can diverge is a common source of portioning error and food cost drift.

Worked example: shawarma plate with garlic sauce sub-recipe

The following example builds two linked cards: first the garlic sauce sub-recipe, then the finished shawarma plate that references it. Dubai wholesale ingredient prices are based on Numbeo retail data (April 2026) with a 20% wholesale discount applied.

Multi-branch recipe standardization

When a restaurant group runs three or five branches in Dubai, the instinct is to give each kitchen a copy of the recipe spreadsheet. This produces three or five diverging versions within three months: one branch updates the chicken price, another does not; someone changes the marinade on branch 2 but not branch 1. By quarter-end, theoretical costs calculated from the spreadsheets and actual costs from the P&L do not agree, and no one can say which card is current.

The principle is: one recipe card, many price lists. The card's structure — ingredient specifications, EP quantities, yield percentages — is the same across branches. What changes per branch is the ingredient cost, which depends on which supplier serves that location.

This architecture means:

• A change to portion size or yield is made once and propagates to all branches immediately
• A price change at the Sharjah branch supplier does not pollute the Dubai cost card
• Management can compare theoretical food cost by branch on the same recipe structure
• Training new kitchen staff uses one source of truth, not branch-specific variants

Keeping the template current

A recipe cost card that was accurate in January is almost certainly wrong by April. Three things change without warning:

Supplier prices. UAE imports the majority of its food supply; exchange rate movements and shipping disruptions can shift wholesale prices 5–15% within a quarter. A dish costed at 29% food cost in Q1 can drift to 34% by Q3 if chicken, onion, or cooking oil prices move and no one updates the card. The only reliable solution is to link recipe costs to live invoice prices — either by manually updating on every new purchase order, or by using inventory software that does it automatically via Weighted Average Cost (WAC).

Yield percentages. A yield test run when the restaurant opened reflects the quality of the supplier at that time. If you switch chicken suppliers, or tomato quality deteriorates in summer humidity, your yield % changes. Cards that have not been yield-tested in the past six months should be treated as estimates, not actuals. Assign a "last yield test" date to each ingredient and flag any that are more than three months stale.

Sub-recipe formulas. When a chef adjusts the garlic sauce recipe — more lemon, less oil — the sub-recipe card must be updated. If it is not, every dish that references it carries a wrong cost. The practical fix: mark sub-recipe cards as requiring chef sign-off before and after any formula change, and log changes with a date.