How to run production from a recipe
Go to Production, click Run production, choose a recipe and enter how many units to make. Jogan shows what will be consumed, then takes the components out of stock at their average cost and puts the finished goods in at the rolled-up cost per unit.
Production is how a recipe becomes stock. It is the step that consumes ingredients and creates finished goods, and it is what gives a made item its true cost.
Before you start
- The recipe exists. See How to set up a recipe.
- The components are in stock in enough quantity. Production refuses to consume more than you have.
Steps
- Open Production and click Run production.
- Select the Recipe.
- Enter the Quantity to produce, in units of the output item. Any amount works; the form reminds you what one batch makes and the recipe scales up or down. Under This will consume, Jogan shows each component and the amount that will leave stock, plus the projected material cost.
- Save. You will see Production complete.
What happens
- A
production_consumptionmovement takes each component out at its current average cost. - A
productionmovement puts the output into stock at total material cost ÷ quantity produced, re-averaging the finished item's cost. See How Jogan works out cost. - If the output item tracks expiry, a batch is created with an expiry date of today plus the item's shelf life, and a batch number, so the finished goods appear on the Batches page with their date. See How expiry tracking works.
- Components that track expiry are drawn from their oldest batch first.
"Insufficient stock"
Production stops if any component is short, naming the item and what is available. Stock in the missing component (a purchase) or reduce the quantity. See How to log incoming stock.
Producing at the moment of sale
If you make to order, you can skip a separate production step by ticking Auto-produce items not yet in stock on the sales form. Jogan runs the recipe for the shortfall as part of the sale. See How to record a sale.
Undoing a run
Only an Admin can delete a production run. Deleting it un-builds the run: the consumed components come back, the output leaves, its batch is removed, and any sale that had drawn from that batch is corrected. Jogan shows the full impact before you confirm. See How to fix a mistake.
Did this not answer it? Use the chat bubble in the corner and a person will reply. If you are inside your workspace, the book icon in the top bar opens a short guide for the page you are on.