What does a plate actually cost?

A plate's true cost is the full cost of everything that goes onto it, followed all the way down through your sub-recipes, with each ingredient adjusted for the part you actually use after trim, plus packaging and prep labor. It is not the price of the ingredients multiplied by their quantities. And because vendor prices and formulas move, a plate cost is right for a day, wrong for a month unless something keeps it current. Misenlogic computes that true cost from the ground up and keeps it correct as your prices and formulas change.

Why "ingredients times quantity" is not what a plate costs

The number most operators carry in a spreadsheet is a snapshot: each ingredient's price times how much the recipe uses, summed once, on the day it was typed in. That figure is wrong in three ordinary ways.

• It ignores your sub-recipes. A dressing built on a house aioli built on a roasted-garlic paste has cost buried two and three layers down. If the roll-up stops at the top level, the plate cost is missing most of what it is made of.
• It ignores yield. You buy 40 pounds of whole tenderloin and get 31 usable after cleaning. You pay for 40, but only 31 reaches the plate, so the real cost of the usable pound is higher than the invoice price. Costing on the as-purchased price understates every dish that uses it.
• It ignores packaging and prep labor. The clamshell, the label, and the hands that portion and pack are part of what the plate costs to put in front of a customer. Left out, the margin reads better than it is.

A tool that multiplies price by quantity can be right on the day you enter it. The wound is that the number then rots quietly: a vendor raises flour, three sub-recipes and eleven menu items go underwater, and nobody re-keys 200 recipes to notice.

How Misenlogic computes a true, recursive, yield-adjusted plate cost

Misenlogic walks the full ingredient tree for every recipe and costs it from the ground up.

It follows sub-recipes as deep as they nest. A compound sauce inside a dressing inside an entree rolls all the way up. There is no level at which the cost stops accumulating, so a plate built on layered components carries every layer's real cost.

It adjusts each ingredient for edible-portion yield after trim. The cost that lands in the recipe reflects the usable portion, not the as-purchased weight. When you run a yield test the way you already trim, entering what you bought and what was usable, Misenlogic records the measured yield and folds it into that ingredient's edible-portion factor, and every recipe that uses it re-costs on the truer number.

It adds packaging and prep labor. The result is a true plate cost and a real per-unit cost, not ingredients times quantity.

Here is the shape of a single plate, with each line resolved to its cost in the recipe:

Example figures. The levain line is a sub-recipe that rolls up its own ingredients; the butter line reflects an 82% yield after trim, not the as-purchased price.

What keeps the number correct after you stop looking

Computing a true cost once is table stakes. Keeping it correct without a human re-doing the math is the point. Misenlogic maintains the loop: change a price once, and it flows to every recipe that uses that ingredient, directly or through a sub-recipe. The cost is recomputed on read, so it is fresh at view time and lands within about a minute of a change. Nothing to re-run, nothing to re-key.

Because the cost is computed from your current prices rather than stored as a stale number, opening a recipe always shows today's cost. When a vendor raises the price of one item used across dozens of recipes, every one of them reprices, and the margin on each reflects today's number, not last quarter's. Competitors store a number; Misenlogic computes it fresh.

For how one change ripples across a whole menu, see how a price change flows through every recipe.

When a cost is not real yet, Misenlogic says so

A plate cost is only as honest as the prices behind it. If an ingredient has no price, Misenlogic does not guess and it does not quietly plug in a zero. It marks the plate cost incomplete and names exactly how many ingredients are still missing a cost. "Incomplete" is a feature, not a flaw: it means a margin never reads better than it is, and you never chase a number that was never real. You always know whether you are looking at a finished cost or a partial one, and what is missing to finish it.

Catalog basis or actual basis: cost the way your kitchen buys

You can cost recipes on either of two bases, and the choice ties your plate cost to how you think about inventory.

• Catalog basis costs from your vendors' quoted prices. This is the default and the simplest to reason about.
• Actual basis costs from the weighted-average cost of the stock you have on hand, so recipe cost ties back to your inventory valuation.

Switching bases is reversible, and before you switch, Misenlogic previews the blast radius: how many recipes would lose a complete cost, and which ingredients are behind it. That preview means you change basis with your eyes open, not by trial and error. Actual basis is available as a capability and a switch you control; treat it as a way to align cost with inventory value, not as a promised savings outcome.

Every cost, versioned for audit

Every material change to a recipe snapshots its cost and price at that version, with who changed it and how the cost moved over time. So beyond today's number, you have a clear history: what changed, when, by whom, and what it did to the plate cost. When you price a menu or defend a margin, the trail is there.

Related guides

• Recipe costing and nutrition labels on one record
• How Misenlogic keeps costs current across every location
• Move your data over without losing a number

Contact us for pricing

Misenlogic keeps every recipe's cost current, so your menu is priced against today's invoices and the margins you see are the ones you earn. Tell us about your operation, and we will scope it with you.

Contact us for pricing