BatchDash

Know your margin before the batch, and prove it after.

Margins rarely die in one blow. A delivery lands 8% higher, the yield slips two points, a box of jars gets pricier, and the spreadsheet keeps quoting the plate at last spring’s numbers. The morning you finally recompute it, the money has been gone for months.

BatchDash computes every cost from the prices you actually paid, and recomputes the moment any of them moves. The figure on the recipe is the figure in your accounts, every day, without anyone opening a spreadsheet.

Request accessSign in
01Costing

Built from receipts, defensible line by line

Every ingredient carries the weighted average of your real deliveries, with delivery and platform fees folded in, recomputed at every receipt. Under that figure sits the trail it came from: what each delivery cost, what each vendor quotes today and how long they take, and how far the best offer sits from what you are currently paying. Chilis at €0.014 a gram against a best offer of €0.015 means the next delivery will push the average up, and you can see it coming.

An ingredient’s price history in BatchDash: each vendor’s current offer with its lead time, the monthly unit cost climbing past the weighted average, and the gap between the best offer and what the workshop pays.
02Costing

Every figure opens into the lines under it

A recipe cost is the sum of what its lines truly cost, sub-formulas expanded, each priced from its own deliveries. A batch shows what it needed, what actually went in, and what that came to, ingredient by ingredient. A component you made last week is priced at what that batch cost, rather than re-derived from chilis bought at a different price six weeks ago. When your accountant, your bank or your co-founder asks where €4.67 a jar comes from, the answer is a click, and the answer holds.

A batch’s bill of materials in BatchDash: needed, used and cost for every ingredient, with a made component drawn from stock at what that stock cost.
03Costing

In the unit you sell, with the whole truth in it

A cost is only useful in the unit you price in. BatchDash answers per plate, per jar, per liter or per 100 g, with the parts a quick estimate always forgets:

  • The yield: a 92% batch means the jar carries the 8% that evaporated.
  • The packaging set: jar, lid and printed label join the unit cost per piece.
  • Labor at recorded minutes and each operator’s rate, when you switch the full model on. The batch above took 2 h 30 against an estimate of 1 h 01, and the cost says so.
  • Equipment amortization and overhead, spread over the batches that actually used them.
A finished batch’s cost in BatchDash: the plan’s target, yield and expected cost above, and the sealed cost split into ingredients, packaging, labor at recorded time, equipment and overhead.
04Costing

You paid for the whole lemon

Plenty of what you buy never gets into the product, and a percentage column cannot see any of it. BatchDash costs an ingredient as bought and divides by what survives, so both losses land on the figure instead of on you at the end of the quarter.

  • An ingredient with parts costs what the whole thing costs. Ask for 63 g of zest and you have paid for 18.5 lemons, and the jar carries all of them.
  • A batch that has to round up to six whole eggs is costed at six, because that is what left the fridge.
  • Yield sits in the divisor twice: once for what an ingredient loses on the board, once for what the batch loses on the heat.
05Costing

Then set the price with the cost in front of you

Each format carries a retail price, VAT included, and a wholesale price, before VAT. Under them, one sentence suggests a retail price from the true unit cost, your target margin, the fee your channel takes and your VAT rate. You still type the price; the card tells you what it should earn, and what recorded sales actually earned, both before VAT.

  • A 3% marketplace fee is taken on what the customer pays, VAT included, so the suggestion counts it that way.
  • Defaults live in your settings; any product overrides them, so jam at 5.5% VAT and soap at 20% share one workspace.
  • Planned beside realized: a jar that should have earned 45% and earned 40% says so on the page you price from.
A product’s cost, price and margin card in BatchDash: unit cost split between recipe and packaging, retail and wholesale prices, a suggested retail price, and planned beside realized margin.
06Costing

Buy in dollars, keep the books in euros

Your suppliers invoice in their currency and your accounts are in yours. Each vendor carries the currency it bills in, each order shows the rate it was booked at, and you can replace that rate with the amount your bank actually took: every line is then restated to the cent, with a row in the ledger saying what moved. Offers from three countries compare at today’s reference rate, fetched daily, so the cheapest one is the cheapest one. VAT works the same way. Say whether your business recovers it, type what the invoice printed, and the cost that reaches your average is the cost you actually bear.

07Costing

One price moves, every affected recipe follows

Book a delivery at a new price and the weighted average shifts, the mash re-costs, the three sauces on it re-cost, and the jar’s margin updates, all before you have put the invoice down. At the end of the month the reports read off the same figures: what the units you sold cost to make, which batches came in over their plan, what the shelves are worth today. That is the difference between costing as a quarterly cleanup and costing as something the system keeps true.

Cost breakdownIn the help center

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.

Request accessSign in

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