The system batch manufacturers run on.

One formula holds the composition, the method, the parameters and the cost. Around it, the same system runs your purchasing, your stock and the batch itself. Every run seals what was made, what went in, and what it really cost.

  • A formula in percentages, with phases, parameters and a yield on every version.
  • Every batch prices itself from the deliveries you actually received.
  • Lot traceability and the sealed batch record cost nothing extra.
A recipe in BatchDash: version 2, accepted, its ingredients as percentages with a fermented mash among them, each line priced, and the cost of an 11.6 liter batch underneath.

A spreadsheet gets you surprisingly far. Then it doesn't.

A recipe binder and a stock sheet hold up until the versions, the prep and the production start drifting apart. The true cost of a plate or a jar is the first thing to go stale, and you tend to notice the morning the margin is already gone.

It came out right last time, but the exact version that made it is gone.

Every version is kept, and each batch records the one it ran.

Two people quote a different price for the same ingredient.

One weighted average, taken from the deliveries you booked.

Nobody can say what a plate, or a finished jar, actually costs to make.

A cost per jar, per plate or per 100 g, built from what you paid.

You find out the stock is short the morning of service, or the day of the run.

The week's plan checks itself against stock before you commit.

One recipe of smoked habanero hot sauce, followed from formula to printed label. Every screen below is the app, and every figure on it is real.

01Formulate

Weigh it. The percentages follow.

Weigh what you actually used on a bench sheet and BatchDash back-computes the percentages, checks the mass balance and reports the yield. Try a change as a new version and the old one stays intact, with the record of what moved and a tasting score to pick the winner.

A bench sheet section: ingredients weighed in grams with their back-computed shares.
A product’s cost, price and margin card: unit cost, retail and wholesale prices, the suggested price, and planned against realized margin.
02Cost

Know the cost and the margin before you commit

See what any version costs per plate, per jar or per 100 g, built from real prices. Vendor offers and weighted average cost feed in, sub-formulas expand on their own, and the full breakdown is there when finance asks where the figure came from. Change one price and every recipe that uses it re-costs. Set a retail and a wholesale price on each format and the product page suggests a price from the true unit cost, then shows the planned margin beside what sales actually earned.

03Plan

Plan the week. The plan checks itself.

Put batches, prep, packing and time off on one board. Every production day is checked against your stock and incoming orders. When something will be short, you get the last day to order it, per vendor.

The BatchDash planner: a week board with a batch per person per day, a short batch flagged, and the order-by markers on the days that need one.
04Run

The recipe sheet your line actually follows.

Type a batch size and the whole recipe rescales: the equipment to gather, the ingredients to weigh, and the method step by step. Checkpoints and tick boxes turn it into a worksheet you can print, for the kitchen or the lab.

A BatchDash recipe sheet for a hot sauce: equipment, scaled ingredients, and the method with checkpoints.
05Seal

Ask a finished batch what it did. It still knows.

A finished batch seals its record: the recipe as it ran, the weighed quantities, the steps and their parameters, the checks, the lots that went in and the lot that came out. Editing the recipe next month changes nothing about it.

A sealed batch record in BatchDash: lot code, production date, operators, yield against expected, and the cost of the batch.
06Print

A label editor that has already read your recipe.

Draw the label in the app itself: drag text, your artwork and barcodes on a millimeter canvas, and watch the finished label take shape live, filled from a real batch as you design. The ingredient declaration writes itself off the formula, descending order, allergens in bold, and the lot and dates come from the batch that prints it.

The BatchDash label editor: a hot sauce jar label on the canvas, previewed against batch RUN-000004 so it carries that batch's lot and dates, with its layers listed on the left and the selected product name showing its binding, its face and its size on the right.

Where the other options stop.

You are probably running this on a spreadsheet, or on a system built to count parts. Neither one knows what a formula is.

Hold a recipe as percentages, with phases and a yield

A spreadsheet
The formula breaks when a row moves.
An MRP built for parts
Built to count units of parts.
BatchDash
Percentages, phases and yield, on every version.

Know what a batch actually cost

A spreadsheet
True on the day you typed it.
An MRP built for parts
A standard cost you keep by hand.
BatchDash
The weighted average of what you paid.

Trace a lot forward and back

A spreadsheet
A column somebody has to remember.
An MRP built for parts
Sold as an upgrade.
BatchDash
In every batch record, both directions.

Prove a batch was made right

A spreadsheet
A photo of a sheet, in a folder.
An MRP built for parts
A work order that closes and moves on.
BatchDash
A sealed record with its checks and its lots.

Print a label with its ingredient declaration

A spreadsheet
Retyped for every product.
An MRP built for parts
Outside what it does.
BatchDash
Written from the formula, filled by the batch.

Put one recipe inside another

A spreadsheet
Copy the rows and watch them drift.
An MRP built for parts
A sub-assembly, stocked as a part.
BatchDash
A sub-formula that expands and costs itself.

Scale a batch and have everything follow

A spreadsheet
Multiply by hand and hope.
An MRP built for parts
Quantities scale. The method does not.
BatchDash
Ingredients, equipment and method, rescaled together.

Keep stock that production actually consumes

A spreadsheet
A second sheet, updated when someone remembers.
An MRP built for parts
Yes, for the parts you count.
BatchDash
A ledger every figure walks back to.

A spreadsheet cannot hold a formula. An MRP holds parts, and charges again for the lot trail. BatchDash does both, from the first trial to the printed label.

Questions we hear before the first batch.

Where do the numbers come from?
From your own deliveries. Every ingredient carries the weighted average of what you actually paid, delivery fees folded in, and every recipe cost is built from that.
Can I undo a batch?
Yes. Reverting a completed run returns the stock it consumed and removes what it booked, so a trial costs you nothing but the tasting.
Does it work for cosmetics as well as food?
Yes. The same gram-based engine costs a serum and a sauce, and a cosmetic batch writes its INCI list from what went in, with the period after opening beside its date. Cosmetics manufacturing software
I already have spreadsheets.
Good, they import. Ingredients, vendor offers, products and the lots on your shelves come in from CSV, one file each; imported rows hit stock and costs exactly like hand-typed ones. What the move looks like
Can it print my product labels?
Yes. You design a label template once, and each batch prints it filled with its lot number, dates, net quantity and the ingredient list computed from your formula. Output is a PDF sized for roll printers or label sheets, or an export bundle a label printing service accepts.
Is there a free trial?
Plans that carry one say so on their card, and you can cancel during the trial. You start on your own recipes, with your own prices.

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.