What is BatchDash?

BatchDash is process manufacturing software: the system you run on when you make things from a formula instead of from a parts list. You buy ingredients by weight, turn them into batches, and sell what comes out by the unit. BatchDash holds that whole loop in one place, so the cost of a jar, the stock on the shelf and the trail behind a lot are one set of records rather than three spreadsheets that disagree.

It is built with people who make food, drink and cosmetics, which is where its labeling and compliance work goes deepest. The shape of the job is the same for a paint, a candle, a fertilizer or a supplement, and it fits those too.

Request access Sign in

You cannot take a sauce apart

Assembly builds a countable thing from countable parts. Four legs and a top make a table, and the table comes apart again into four legs and a top. Process manufacturing does not work like that. You measure things out, something irreversible happens to them, and what comes out is a quantity rather than a count.

That single difference is why software written for parts lists fights you the whole way. It wants units where you have percentages. It assumes what goes in comes out, so it has no idea what to do with the 800 ml that boiled away. And it has nowhere to put the batch, which is the only thing you can actually cost, check or recall.

If your product is written as a recipe and made in batches, this is built for your work, whatever you make.

One record for each thing you handle

Nothing here is a module you switch on to look busy. Each record exists because something downstream cannot be computed without it.

01What you buy

Every ingredient, what it costs, and how that changed. Vendors and their offers, purchase orders, deliveries received against them, losses. An ingredient carries a weighted average cost computed from what you actually paid, delivery fees included, and that figure is what everything downstream is priced from.

Stock Buying Sourcing

How an ingredient gets its cost

02What you make

Formulas written as percentages, with phases, steps, checkpoints and sub-formulas. Versions, so a batch from last winter still shows the recipe it came from. A week board that says what is being made when, checked against the stock it needs. Then runs: the batches themselves, planned, weighed and completed.

Recipes & formulas Planner AI

How a formula becomes a batch

03What you sell

The formats you actually ship, with their packaging counted per unit and their prices per tier. Customers and sales orders that reserve finished stock when you confirm them. A connected shop whose orders arrive the same way, and which is only ever offered stock that is genuinely free.

Sales orders Sales channels Costing

How a product is put together

04What proves it

Lot codes on what you make and on what you received. A sealed record per batch holding the recipe as executed, the quantities weighed, the checks signed and the real cost. Labels composed from the formula, declaration and all. Reports that read those sealed records rather than recomputing from current prices.

Traceability Batch records Labels

How a lot is traced both ways

What matters is what connects them

Twenty kilos of habaneros arrive against an order at €4.60 a kilo, delivery included. That moves the ingredient’s average cost, and every formula using it is repriced on the spot. A 20 L batch draws from that delivery, comes out at 19.2 L after reducing, and books 76 jars under its own lot code at €1.84 each, jar, lid and label counted in.

Sell one and the margin is measured against what that batch really cost. If something is wrong with it, the trail runs back to the farm that grew the chilies and forward to everyone who bought a jar. Every one of those steps already exists in a spreadsheet somewhere. What does not exist there is the line between them, and that line is the product.

What it does not do

Knowing where a system stops is worth more than a longer feature list.

It is not your accounting system. It knows what a batch cost and what a jar sold for. It has no general ledger and it will not file anything for you.
It is not a warehouse system. It holds lots, locations and quantities, and it will tell you what is short. It does not plan pick paths or talk to a forklift.
It is not for assembly. If your product is a list of countable parts that could be taken apart again, an MRP built for parts will serve you better than this will.
It does not decide what is safe. You set the checks and the shelf lives; it holds them, asks for them at the bench, and keeps the record that you ran them.

Where to look next

Every part of this has a page of its own. The glossary defines the vocabulary, and the help center carries the step-by-step version of all of it.

Read the glossary Open the help center