Production: work orders, BOM and batches

Production should know what to make without anyone walking over with a slip of paper. In Sankalp the work order appears when the sales order is confirmed, and it already knows what is short.

Work orders that follow the orders

When a sales order is confirmed, Sankalp compares what the open orders need with what is on the shelf and what is already being made. Only the shortfall becomes a work order. If a second order arrives for the same product, the system shares stock between orders in the order they were invoiced and adjusts the work orders. You can also start a make-to-stock batch with no order behind it.

Check the recipe before you start

Each finished good has a BOM (bill of materials), the list of ingredients per unit. Before you launch a batch, Sankalp multiplies the recipe by the batch size and shows which raw materials are short. If something is missing you get a clear warning, and only a deliberate override lets the batch go ahead.

No recipe saved yet? Formulate it on the spot while launching the batch. It is stored for next time.

Batch records that people fill in once

A batch captures the batch number, quantity, date, shift, machine or line and operator. Ingredients are deducted from stock when the batch is launched. Partial runs are fine: make 600 now, and the remaining 400 stays open as a work order.

Rejection and rework

If part of a batch is scrapped, enter the quantity and the reason. If a batch fails, it can be reproduced from the same screen, and the order's quantity is not lost along the way. A shift performance report shows output and scrap by shift.

Straight on to QC or packing

A finished batch goes to Quality Control if you use the QC module, otherwise directly to Packing. Nobody has to remember to pass it on.