The recipe that made last winter’s best batch still exists. Here.

You know the scene. The binder says 12 kg of mangoes, the costing sheet says 40%, and the batch everyone still talks about followed a correction scribbled on a printout that went through the wash. Every workshop runs on recipes. Very few could reprint the one that actually made them money.

A sauce, a serum, a spice blend: a BatchDash formula is one record holding the composition, the method, the parameters and the cost, from a 5-liter pilot to a 500-liter run. Change it and the old version keeps existing, still readable, still costed, still runnable.

01Recipes & formulas

Percentages or grams. The other side fills itself in.

Type 42% and the grams for this batch appear beside it. Weigh 5,045 g into the pot instead and the share appears. It is the same record either way, so the sheet you develop on and the sheet you produce from stop being two documents that disagree. Phases group the steps the way the work is really organized, and each step carries what belongs to it: the temperature, the hold, the pH window, the kettle it needs.

The recipe editor in BatchDash: phases, numbered steps, and each ingredient weighed in grams with its computed share beside it.
02Recipes & formulas

The formula adds itself up while you type

Beside the steps sits the recipe as a bill of materials: every ingredient once, folded together across the steps that use it, priced at the weighted average of what you actually paid. Sub-formulas open into their own lines. The batch total and the cost per liter, per kilo or per jar sit underneath, and they move the same second a delivery changes what an ingredient costs.

  • Not every line follows the batch. A stabilizer dosed at 40 g per batch stays 40 g whether you make 10 liters or 200.
  • A lid, a label or a garnish counts per portion, so it follows the number of jars rather than the mass.
  • One crust per 900 g of filling rounds up for every started slice, and that line can set the batch size, so batches come in whole quiches.
The computed formula panel in BatchDash: each ingredient once with its share and its cost, a fixed-per-batch line marked as such, and the batch cost underneath.
03Recipes & formulas

Eggs come whole. A lemon is mostly pith.

An ingredient counted in pieces carries what one piece weighs, so a recipe can ask for 2.5% egg and the sheet can ask for six of them. A piece that cannot be split says so and rounds up; a lemon that halves is allowed to be 18.5. An ingredient can also have parts, and this recipe wants the yolk and the zest. Getting them takes 6 eggs and 18.5 lemons, because a zest is 4% of a lemon. So the sheet prints the input twice: 4.19 kg goes into the bowl, 5.9 kg leaves the shelf. The second figure is the one you paid for, and a percentage column will only ever show you the first.

A recipe sheet in BatchDash: what the batch makes, its yield, what goes into the product beside what leaves the shelf, and an egg marked as whole pieces.
04Recipes & formulas

Recipes inside recipes

A mother sauce, a fermented mash, an emulsion base: real production nests one recipe inside another. In BatchDash the nested one is a sub-formula, one record used everywhere, and everything built on it stays true by construction.

  • Cost flows through. The mash re-costs after a chili delivery, and every sauce that contains it re-costs the same second.
  • A batch can draw the base from stock you already made, or make it fresh inline. The plan shows both and prices both.
  • Circular references are refused at the picker, so “the sauce contains the sauce” can never be saved at 6 pm on a Friday.
05Recipes & formulas

Then it prints as something the bench can follow

Type the batch you are making and the whole sheet recomputes: quantities, equipment, the checks. Each step lists what goes in at that moment instead of making someone read the full ingredient list and work it out. An earlier step’s result flows into the next one by name, so a mash that becomes a sauce reads as one sequence. Checks sit where they are taken, with their target beside them. Print it, or leave it open on a phone next to the scale.

The method on a recipe sheet in BatchDash: numbered phases and steps, the equipment each one needs, an earlier step’s result feeding the next, and a holding-temperature check with its target.
06Recipes & formulas

Every version still exists, and you can see what changed

Editing a recipe writes a version instead of overwriting one. The old one stays readable, still costed, still runnable, and can be locked so nobody edits history. Branch from any version to try something on a Tuesday. Score the result, write down what you thought. The comparison between two versions then reads as the development log nobody had time to keep: the shares that moved, the note added to the mango line, the yield going from 92% to 98.6%.

Two versions of a recipe compared in BatchDash: the shares that changed, the note added to the mango line, and the yield, tasting note and score recorded on the new one.

Cost your first formula this afternoon.

Open a workspace, add a few ingredients with their prices, and build one formula. You'll see where the real cost lands, per jar, per liter or per 100 g, before your next run. No demo to sit through.

BatchDash is the system batch manufacturers run on: the whole life of a recipe, from the first bench test to the costed, sealed batch.

© 2026 BatchDash