Semifinished settings
This area defines semifinished recipes: which output products go to which storages for a reference batch and which production costs (inputs) are drawn from which storages. It is separate from warehouse products, although both use the shared ingredient catalog.
Actual production runs (consuming inputs and posting outputs) happen from kitchen screens and rely on recipes saved here.
Requires Pro and menu and product settings — the same permission bundle as catalog products and menu editing.
How to open it
Under Settings, choose Semi-finished products.
List
The grid shows image, name, unit from the saved card and an edit action. Add a semi-finished product creates a new recipe.
Name search is supported.
Recipe card
The modal title is Semi-finished product. New cards use Add; saved cards use Save changes.
Top section:
- Image
- Name (required) — duplicate names in one venue show Semi-product with this name already exists.
- Category — autocomplete from categories already used on semifinished cards.
Then two stacked blocks in on-screen order:
Output product
The Output product section describes what arrives on stock when you manufacture one reference batch:
- Pick each component from the shared ingredient catalog (typically your catalog products).
- Choose storage where those quantities land.
- Enter quantities for that batch (toggle Display packaging like other warehouse tables).
If no storage fits yet, the storage selector can open Add a storage to quickly create one.
Lines are added with Add a component and removed with the trash icon.
The first row of this section is treated as the batch scaling anchor in production logic — see Semifinished production.
Costs of production
The Costs of production section uses the same table layout for inputs that leave storage for the same reference batch (components, storages, quantities, packaging toggle, catalog add, Add a storage from the picker).
Quantities across both sections should reflect your real process so one executed batch moves stock correctly.
Saving and history
Each successful save writes a recipe snapshot with worker and timestamp for revision history.
Delete
Saved cards expose Remove using the generic product-delete confirmation wording from the product catalog.