Sub-formulas

Your habanero sauce is built on a fermented chili mash. The mash is a recipe in its own right: it has ingredients, a method, a yield, a cost. In BatchDash you write it once as a Component formula and use it as a line inside the sauce.

Add a component line

In the recipe’s ingredient picker, components show up alongside raw ingredients, marked with a Component tag. Pick “Fermented chili mash” and give it its share like any other line: 62% of the sauce, weighed in grams on the bench. Creating a component works exactly like creating any formula, with the type set to Component; see formula basics.

Mass and cost roll up

On the scale, a component line behaves like an ingredient: 62% of a 10 kg batch is 6.2 kg of mash.

The cost is where it earns its keep. The mash line is priced from the mash’s own recipe: its ingredient costs, divided by its yield, give a cost per gram, and that rolls up into the sauce. Catch a cheaper chili price and the sauce re-costs on its own; see cost breakdown.

If the component can’t be costed yet (a missing ingredient price, or no accepted version), the parent’s cost panel says so and names the line instead of guessing.

Making components for real

A sub-formula is not just math. You can produce the mash, hold it in stock with its own average cost, and draw on it during production. That side of the story lives in made components. And when several components share one method (lacto-fermented anything), a standard process mints them all from a single template.

Loops are blocked

A formula cannot contain itself, directly or through a chain (mash inside sauce inside mash). The picker greys out any candidate that would close a loop and labels it “Already uses this formula”, so the mistake is impossible rather than merely discouraged.