The plate cost is real. So is the prep list.

Food cost lives in a spreadsheet nobody has opened since the menu changed. The mother sauces are in one binder, prep lives in someone’s head, and the Sunday order rides on memory and a walk to the cold room.

BatchDash runs the same engine for a kitchen: recipes with sub-recipes, a cost per portion built from your delivery prices, a prep board checked against stock, and orders grouped by supplier with their lead times honored.

01Kitchens & caterers

What costing software does for a kitchen

It prices a dish from your own delivery notes and keeps that figure current as the invoices move. Prep sheets come out sized to the service, the week is checked against what is actually in the walk-in, and the margin on a menu stops being an annual exercise.

02Kitchens & caterers

Cost per portion, from your own invoices

A menu item is a recipe with a portion size, so every dish carries its own cost: the weighted average of what you actually paid, delivery fees folded in, sub-recipes expanded, the minutes recorded on the batch, the overhead your kitchen carries. Beside it sits the price you charge and the margin between them, what you planned against what the dish has really been selling for. It moves the day the mozzarella does.

A menu item’s cost card in BatchDash: five euros a portion against a €12.50 menu price, with the planned and realized margin side by side.
03Kitchens & caterers

The prep sheet for one service

Ask the recipe for forty portions and it prints forty portions: 7.4 kg of rice, 1.09 L of oil, 23 eggs, rounded to what a kitchen actually weighs. The steps are in order with the equipment each one needs and the holding temperature the pass has to keep. Two lines ask for a part rather than the whole thing, the yolk and the zest, and the sheet says both what leaves the crate and what ends up in the dish.

The rice bowl’s prep sheet in BatchDash at 16 kg: the ingredients in kitchen quantities including 23 eggs, the two phases with their equipment, and the 63 °C holding checkpoint.
04Kitchens & caterers

Prep, service and days off on one board

Base sauces, mise en place, packing for an event and somebody’s Tuesday off all sit on the same week, per person. Each row shows the hours planned against that person’s capacity and what those hours cost. A batch that will run short of an ingredient says so before the day does, and the days carrying a delivery or an order-by deadline are marked.

The BatchDash week board: a batch per person per day, one flagged short and one unverified, time off beside them, and the hours and cost each person is carrying.
05Kitchens & caterers

The order writes itself, and you argue with it

The list comes from the week you planned and the levels you set, grouped the way you actually order:

  • Per supplier, with pack sizes and minimums honored, so the quantity offered is one you can order.
  • Order-by dates walked back from each supplier’s lead time. A missed one reads in red.
  • Every line says why it is there. One click writes a draft order per supplier; a person reviews and sends, and nothing is emailed by the system.
The Buying screen in BatchDash: what to order grouped by supplier, each card with its order-by date, its total, and the lines behind it.
06Kitchens & caterers

And the walk-in stops being a guess

Every delivery, every batch and every count writes one line in a ledger you can read, so a number on screen walks back to the invoice behind it. Count a shelf on a phone and the difference is booked with its value and the person who counted. Losses take a reason, so the end of the month can tell a cold-room failure from a portion that was too generous.

07Kitchens & caterers

What is in the dish, in writing

Allergens are read off the ingredients rather than remembered, at any depth, so a sauce carrying butter puts milk on the dish without anyone typing it. A batch’s declaration prints in the language the menu is in. When a supplier substitution changes an ingredient, the dishes using it change with it.

Questions we hear before the first batch.

How is a plate cost computed?
From the weighted average cost of each ingredient, at the quantity the recipe uses, with yield taken into account. Trim and cooking loss are inside the figure, so it is a cost per portion served.
Can I print prep sheets for a service?
A recipe sheet scales to the number of covers and prints with its steps, its checkpoints and its quantities. Per-line scale rules decide what grows with the batch and what stays fixed.
What happens when a supplier raises a price?
The delivery moves the average cost, every dish using that ingredient is recosted, and the margin report shows which ones moved. Nothing is retyped.
Can the team use it without training?
A cook opens a run sheet and works down it. Roles decide who can change a formula and who can only run 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