Process
For: Anyone naming the manufacturing steps used to build a Recipe
A Process is deliberately small, a name and nothing else. It exists so a Recipe has something to string together in order, not to hold any detail about how that step is actually carried out.
What this module does
1. A Process is just a named step, nothing more
The Add Process form has exactly two fields, and that's the whole record.
Process Name: Must be unique across your company.
Process Code: Assigned automatically with a PROC prefix.
Duration, cost, instructions, sequence: None of these exist on a Process. It's purely a label you'll reuse across Recipes.
2. It only ever gets used inside a Recipe
A Process is never selected directly on a Production Order. It reaches production only through the Recipe it's part of.
Inside a Recipe: You pick one or more Processes and put them in order. That order is what defines the production sequence.
When production actually runs: The system copies just the name and code of each process onto the Production Order. It doesn't stay linked back to this master.
What actually gets tracked per run: Quantity in, quantity out, scrap, manpower, and timing are all entered on the Production Order itself, step by step, as the work happens.
Note: Because Production Orders keep their own copy of each step, editing or deleting a Process later has no effect on runs that already used it. It only changes new Recipes you build with it from that point on.
Business rules
| Topic | Rule |
|---|---|
| No subscription gate | Unlike Division, Branch, and Warehouse, creating a Process isn't limited by your plan |
| Unique name | Process names must be unique per company, checked case-insensitively |
| No active/inactive status | There's no deactivate action on a Process, only Edit and Delete |
| Deleting | Blocked only if a Recipe still includes this Process. A Production Order that already ran the process doesn't block it, because the order keeps its own copy of the step |
| No per-step data lives here | Input quantity, output quantity, scrap, manpower, and timing are all entered fresh on each Production Order, never stored on the Process itself |