Completing production

Completing a factory order is where production meets stock. In one step, Villva consumes the components the order used and increments the finished goods it produced, keeping your inventory and valuation correct with no manual double-entry.

Completion and back-flush

When you complete an order with a produced quantity, Villva:

1. Consumes each component (back-flush), for every BOM component, it posts a consumption of BOM quantity × produced quantity, valued at Inventory’s moving-average cost.
2. Increments finished goods: it posts a finished-goods increase equal to the produced quantity.

Both happen through the Inventory posting service, production never writes stock directly, so Inventory stays the single source of truth.

📷 Image placeholder

Add a short recording here: completing a factory order, entering the produced quantity (and any scrap), then the component consumption and finished-goods increase appearing in Inventory.

Key guarantees:

• All or nothing. The consumption and the finished-goods increase commit together. If any part fails, none of it persists, you never get a half-posted order.
• No double-posting. Completing an order is safe to retry, a repeated completion never posts stock twice.
• Traceable. The resulting stock movement references are recorded on the order and in the audit log.
• Respects the no-negative guard. If a consumption would drive a component below zero, it’s rejected per Inventory’s rule, and the whole completion rolls back.

Partial output and scrap

Real jobs don’t always yield the full planned quantity. Villva records exactly what was made and wasted:

• Partial output: completing with produced quantity less than planned consumes for the produced quantity only and sets the order to Partially Completed. A partially completed order can take further production runs, each posting its own consumption and finished-goods increase, until it’s completed or closed.
• Over-production: producing more than planned is allowed with a warning; consumption always scales to the actual produced quantity, not the plan.
• Scrap: if you enter a scrap quantity, it posts to the Inventory Scrap category (a separate movement) and never becomes finished goods.
• Cumulative produced quantity across runs is tracked and shown.