Turn production intent into an executable plan.

Work orders with auto-exploded materials

Create a work order from a recipe and OakNex explodes the full bill of materials automatically — including any nested sub-recipes — into the exact quantities the batch size requires. No manual line-by-line material list, no forgetting the packaging, and no re-typing a recipe into a work order because the two live in different tools.

A work order can produce more than one output at once, and defaults to consuming materials as a single batch at completion — though you can switch a work order to consume as-you-go if your process calls for it. Either way, the explosion and the consumption both post to the same audited stock ledger.

FEFO lot assignment with manual override

Materials are assigned by first-expired-first-out by default when the work order consumes stock, so older lots move before they expire. When a specific lot needs to move instead — for example a quality hold or a customer requirement — it can be overridden manually. The consuming ledger is the same one your traceability reports read from, so a work order's material history is queryable the same way a shipment's is.

Routing, critical path & workstation capacity warnings

Attach a routing to the recipe — ordered steps with a workstation, setup and run minutes, and dependencies on the steps before them — and the work order snapshots it, computes the critical path, and warns when a workstation's committed load for a day exceeds its daily capacity. You see the bottleneck before committing the schedule, rather than after it causes a delay on the floor.

Because the routing is snapshotted onto the work order at creation and stays editable while it's planned, a schedule change doesn't mean re-explaining the whole batch — just adjusting the steps that actually moved.

Material-shortage warnings before you start

Before a work order starts, OakNex checks whether the materials it needs are actually available: insufficient on-hand quantity combined with nothing on order raises a warning directly on the work order, rather than partway through the batch. It's a non-blocking flag — you decide whether to proceed, with a substitution or a partial run if needed — backed by the same purchasing data driving your reorder suggestions, so the warning reflects what's actually inbound, not just what's on the shelf today.

Waste & yield capture at completion

Completing a work order records what you actually got, not just what the recipe predicted: variable bottle output for liquid batches, leftover liquid, bottling waste, samples and spoilage — all logged against the batch so yield is a real number, not a guess at month end.

For liquid batches specifically, cost allocates across the bottle sizes you actually filled, weighted by the litres each size produced — so a short pour into small bottles and a full run into large ones cost out correctly instead of splitting evenly by bottle count.

Kiosk (PIN) operator mode for the shop floor

Shop-floor staff don't need a full login to log consumption and output — a PIN-code kiosk mode lets an operator clock into a work order and record what happened, without handing every operator a system password.