Bistro food cost: price rotating specials, stocks, sauces, and yield
A bistro-specific method for costing short-run specials, shared preparations, yield-adjusted proteins, and mise en place used across dishes.
A bistro often earns its character from change: a soup follows the market delivery, a sauce is reused with a different protein, and a special lets the chef work through a prepared component before its approved use period ends. That flexibility makes costing easy to blur. A purchase invoice describes what arrived; it does not automatically describe the edible portion, the finished batch, or the amount used on a plate. Build the chain in the same language the kitchen uses: purchase item, prep batch, usable quantity, recipe version, menu item, and service date. If a quantity is estimated, label it as an operator assumption and leave a path to correct it.
Price the shared stock or sauce once, then allocate it
A stock or sauce can be a parent preparation consumed by several dishes. Record its ingredients, trim, water or other process inputs, finished batch weight or volume, measured losses, and the portion unit used by each receiving recipe. The allocation is not a claim that every ladle is identical forever; it is a reproducible local convention that can be tested. If a special uses a reduced sauce while a lunch dish uses it as a base, give those versions separate portion instructions. Keep the parent batch linked to the children so a changed yield can be reviewed without guessing which dishes were affected.
- Name the stock or sauce version, production date, vessel or batch reference, and the approved uses for that service.
- Record usable output after straining, reducing, or discarding rather than dividing by an unverified planned volume.
- Attach the actual portion tool or weight to each receiving dish; a ladle name alone may not define a portion.
- When a special consumes the remainder, record the transfer as a receiving line instead of deleting the parent preparation.
- Keep allergen, handling, cooling, and local food-safety decisions with the responsible kitchen process; this guide is not legal advice.
Use yield-adjusted protein cost for the plate actually served
Protein is where a bistro’s apparently simple special can hide a large conversion. Keep purchased weight, trim, raw usable weight, cooked weight when tested, portion definition, and leftover destination as separate records. The CIA reference is useful context for AP, EP, yield, and recipe calculations, but a public formula does not know your cut, trim instruction, cooking method, or supplier lot. Re-test when those conditions change. If a stock or sauce is built from trim, decide whether that trim is already charged to the parent recipe before assigning another cost to the special.
Clearly labelled illustrative operator-entered example: a changing special
Illustrative operator-entered example only. The ingredients, weights, prices, batch outputs, portions, dish names, dates, and calculations are invented teaching values. They are not supplier facts, a yield promise, a price recommendation, a demand signal, a saving, or customer evidence. Replace them with reconciled invoices and weighed kitchen records.
| Protein yield | Illustrative operator-entered calculation: 5.0 kg purchased protein − 1.1 kg trim − 0.6 kg cooking loss = 3.3 kg cooked usable output | Fictitious local test; not a universal yield |
|---|---|---|
| Shared sauce batch | Illustrative operator-entered: a batch costs €42.00 and produces 6.0 kg usable sauce; the special uses 0.18 kg | Fictitious batch and portion inputs; verify the actual parent recipe |
| Special portion | Illustrative operator-entered: 0.22 kg cooked protein plus 0.18 kg sauce and a recorded garnish portion make one dated plate version | Fictitious portion specification; not a serving recommendation |
| Allocation | Illustrative operator-entered calculation: €42.00 ÷ 6.0 kg = €7.00 per kg; 0.18 kg × €7.00 = €1.26 sauce cost | Arithmetic is illustrative and excludes any unrecorded parent cost |
| Transfer | Illustrative operator-entered: 0.9 kg sauce left after service is transferred to the approved soup recipe with a new date and batch link | Fictitious transfer status; confirm food-safety and local process |
The bridge makes the special’s version, protein yield, shared-prep allocation, and transfer visible. The operator must replace every input and decide whether the resulting plate cost is complete.
A rotating menu should be versioned like a small production release. Write the effective service date, the intended portion, the garnish, the source batches, and the ingredients that are deliberately shared. When a special is retired, do not erase its cost record: close the version and note where remaining mise en place went. This preserves a useful explanation without pretending that a single service represents every future service. The same discipline lets a chef compare a new special with a prior one without borrowing an old yield or calling a difference a saving.
- 1Freeze the special version. Name the dish, service date, protein portion, garnish, shared preparations, recipe revision, and what the calculation includes or excludes.
- 2Record purchase and yield. Link invoices or approved purchase records to weighed input, trim, edible raw output, cooked observation, and leftover destination.
- 3Cost parent preparations. Reconcile stock or sauce inputs to usable batch output, then define the measured portion consumed by each receiving dish.
- 4Trace mise en place transfers. Record source batch, quantity moved, receiving recipe, date, operator, and any approved handling or use-period decision.
- 5Review the plate decision. Compare your operator-entered cost with current menu, waste, and service records, then choose a recipe, portion, price, or retirement review without inferring demand.
FAQ
- Should the full stock batch cost be put on every dish?
- No. Reconcile the usable parent output and allocate the measured quantity used by each receiving recipe. Keep the parent batch linked so the allocation can be revised when the local yield or portion changes.
- Can a daily special use yesterday’s recipe automatically?
- It can reuse a controlled version only when the protein, portion, garnish, shared preparations, and date conditions still match. Otherwise create a new version and record the differences rather than inheriting them silently.
- Does the CIA PDF provide my bistro’s yield?
- It provides public calculation context for AP, EP, yield, and recipe costing. It does not test your cut, supplier, trim, cooking method, or kitchen. Use your own weighed record for the local factor.
- Does menu engineering prove that a special will sell?
- No. Muntin’s public material can help structure menu questions, but it is not customer research for your bistro. Use your own dated sales and waste evidence, and label interpretations as operator analysis.
- How should leftover mise en place be costed?
- Keep the source batch and remaining quantity visible, then record an authorised transfer, discard, hold, or other destination. Do not count a transfer as a saving or assume it is safe to reuse without the local food-safety decision.
Keep reading
- Seasonal menu costing: pricing a menu built on ingredients that change price every week
Costing seasonal specials when tomato, game and berry prices move weekly — re-costing cadence, trigger thresholds, and substitutions that protect margin.
- Recipe costing: know the real cost of every plate
Accurate recipe costing converts pack prices into edible yield, batch cost and a defensible plate cost, including sauces and garnish.
- Menu item profitability matrix: act on popularity and contribution margin together
Build a popularity-by-margin matrix from real sales, assign every dish to a quadrant, and apply disciplined re-engineering rules.
Browse by category
Want to review your purchasing?
Submit the details and we will confirm which invoices are useful.
Review 3 invoices free