Step by step
Set up a recipe or parts list
Say what one batch of a product takes, how many it makes, how many come out good, and its labour and overheads. Kila works out the standard cost each order is measured against.
A recipe, or a parts list for things you assemble, says what one batch of a product takes and makes. Kila uses it to reserve and issue the materials for each order, to expect a yield, and to work out a standard cost per unit that every finished batch is measured against.
Open Recipes and tap Edit
On Production orders, open the Recipes tab. Each product shows its Batch, Yield, Materials a unit, Standard cost and Price. Tap Edit on the product. For a product without a recipe, tap Add a recipe and type “the product to make: name or SKU”.
Say what a batch makes
Kila opens the recipe: “The materials for one batch, what a batch makes and how many come out good.” In A batch makes, type how many units one batch gives, such as 1,000 pouches. Keeps for is the shelf life in days, which dates each finished batch.
Steps 2 to 4 on one screen. Set the good output
Good output is the share of a batch you expect to come out good, as a percentage: “The rest is expected scrap.” Each order’s yield is compared with it.
List the materials for one batch
Under Materials for one batch, each material has its quantity for the whole batch. Add one with Add a material: name, SKU or scan, and remove one with the bin.
Give the labour and overheads a unit
Labour a unit and Overheads a unit are what each unit carries for the people and the running costs, in shillings, when your business costs them as rates on the recipe. See Choose how labour and overheads are costed.
Steps 5 to 7 on one screen. Leave the standard cost to Kila, or set it
Standard cost a unit is what one unit should cost. “Left empty, Kila works it out” from the materials, labour and overheads over the good output. Type a figure only if you want to hold the business to a set standard.
Say what changed, then tap Save recipe
Under What changed, write why, such as a new supplier. Tap Save recipe. Each save is a new version, and Kila says so, such as Version 4 of Mala 500ml pouch’s recipe is in force. Orders keep the version they were planned on.
The same form has more for those who need it: Track batches of this product (“Each production order puts its output into stock as a numbered batch with its use-by date.”), By-products and co-products of one batch (“Crumbs, bran, offcuts: each goes into stock at its share of the batch’s cost (90% at most between them).”), and the Routing: “The steps on lines and machines, with minutes a unit; used when labour or overheads are costed by time.”
Your change waits for approval
Link to this section: Your change waits for approvalWhen the business has Recipe changes wait for approval on, a change by someone who may not approve recipe versions, such as the QA officer, does not take effect at once:
The recipe shows change to approve. Someone allowed to approve recipe versions, such as the plant manager, opens Versions: “A changed recipe waits for approval; orders keep the version they were planned on.” The change is Waiting for approval, with Approve and Reject. Approve from dates it ahead (“Empty: at once.”), and Reject asks why, which is kept on the version.
An order still uses the old recipe
Link to this section: An order still uses the old recipe“Orders keep the version they were planned on.” The order’s heading names it, such as recipe version 1. Orders planned after a change is in force use the new version.
Needs a manager
Recipes are kept by the plant manager and the QA officer. The owner switches Recipe changes wait for approval on or off in the production settings; with it on, only someone allowed to approve recipe versions puts a change in force.
- Plan a production order: the recipe at work.
- Choose how labour and overheads are costed: rates, time, or the month’s expenses.
- Read production results: cost a unit against the standard.
Next: plan an order from the recipe: Plan a production order.