Completing a run

Complete closes the batch and moves stock. Until now the run was a working document; completion turns it into inventory and a sealed record.

The completion dialog

Complete this batch asks for:

1. Observed output: what the batch actually made, in the unit you choose.
2. Lot code and Expiry: the identity the output carries into stock.
3. Operators: who made the batch. Pick from the roster, add someone new, or use Add yourself as an operator. See operators.
4. Finished-product check: pass or fail, with an optional note.
5. Packaging to consume, for packaged formats. A format set to “fill some, keep the rest as bulk” asks how many jars you filled; the remainder books as bulk component stock.

What completion does

• Ingredients are consumed from stock at their weighted average cost, so the batch cost reflects what you actually paid for what went in. A test run consumes stock only if you ticked Consume stock when completed when planning it.
• The output is booked. A component recipe books into made-component stock at the batch’s real cost; a product recipe books sellable units into the chosen format (see sellable products).
• The batch record shows the yield: observed output against expected input.
• Depending on your release setting, the output is on hand right away, or held until its finished-product check passes.

When component stock runs short

If the batch needs more of a made component than you have on hand, your organization’s Short component stock setting decides what happens: Warn, allow override (complete anyway and let stock go negative), Block, or Take what’s there. Configure it in organization settings.

Reverting and abandoning

• Revert completion reopens a completed run so you can adjust it. Stock it consumed returns to inventory and its booked output comes back out. Handy when a batch was closed with a typo in the output.
• Abandon closes a run without output, at any point before completion. If it had consumed stock, that stock is returned.