Semifinished production
This article covers running a saved recipe: consuming inputs from the storages defined in the recipe and posting outputs to the right storages. You maintain recipes under Semifinished settings and start production from the Kitchen screen.
Contents:
- What it is for
- Prerequisites
- How to run a batch
- How batch size is calculated
- Storages, stock, and logs
- Catalog price for the first output row
- Common issues
- Related articles
What it is for
- Instead of editing stock lines one by one, one flow applies the whole recipe scaled to the batch you enter.
- It fits day-to-day kitchen work next to the live order queue on the Kitchen screen.
Prerequisites
- At least one saved semifinished recipe — otherwise the launch button is hidden (no recipes).
- Recipes are edited under Settings → Semi-finished products; that requires Pro and Menu and product settings, same as Semifinished settings.
- The Kitchen screen itself requires Plus and the Kitchen screen permission.
- Production also needs Make semifinished products — without it the button stays disabled.
- Enough stock for the scaled recipe on each storage line (same rules as other stock deductions).
How to run a batch
- Open the Kitchen screen from the main app menu.
- In the header, click Make semifinished product (primary button on the right). If the button is missing or disabled, see Common issues.
- In Select semi-finished product, search or browse categories and pick a recipe card.
- A form opens titled Prepare semifinished product with two sections matching the recipe:
- Output product — how much of each output line is posted for this batch;
- Costs of production — how much of each input is deducted.
- Enter the batch using the quantity in the first row of Output product, or edit any other line — the rest rescale to match the recipe ratios (details below).
- Confirm with Make semifinished product. On success you should see something like Semi-finished product has been prepared, and the dialog closes.
To pick another recipe, click the read-only recipe name field (dropdown affordance) — the form clears and selection opens again.
How batch size is calculated
The recipe defines quantities for one reference batch. In production, scaling is anchored to the first row of Output product in the saved card:
- The first output row’s quantity is the batch multiplier versus that reference recipe.
- Other output rows and cost rows are derived by applying those ratios to the batch; values are rounded to whole units where the UI does.
If you edit a non-first output row or any Costs of production row, the app backsolves the batch size so that row matches the recipe proportions.
Storages, stock, and logs
Every storage that appears in either outputs or inputs participates:
- Increases residues for output lines on that storage.
- Decreases residues for input lines on that storage.
If outputs and inputs sit on different storages, each storage is updated according to the recipe.
Operations are reflected in per-storage logs for semifinished production (including the recipe name).
Catalog price for the first output row
If the first row of Output product points to a catalog product, its purchase price may be recalculated after the batch: it reflects an estimated unit cost from the sum of component costs for the batch relative to that output quantity. The previous price is kept in the product’s previous-price field.
Additional output rows do not get this automatic catalog price update.
Common issues
- No “Make semifinished product” button — there are no saved semifinished recipes, or you are not on the kitchen screen.
- Button disabled — the worker lacks Make semifinished products; update Workers and access.
- Submit stays disabled — quantity is zero or empty.
- Insufficient stock — check Storages and on-hand quantities per recipe line.