Work-order scrap captured on the production floor
Scrap was being recorded on paper and keyed in days later, so costed BOMs never matched what the floor actually consumed.
Scrap variance by routing step
Captured at the operation · posted nightlyWhat was broken
Scrap was being recorded on paper and keyed in days later, so costed BOMs never matched what the floor actually consumed.
What runs now
We added scrap capture to the work-order flow itself, with a reason code list the supervisors helped write. Variance now posts the same shift it happens.
- Scrap recorded at the work order
- Reason codes owned by production
- Costed BOM reconciles to actual consumption
- Variance visible the same shift
One flow, end to end.
The path a record takes once this is running. Every step is logged, so when something stops you can see where.
Recorded in a demo NetSuite account.
Sample data throughout. The screens are the kind we build and leave running for clients.
We added scrap capture to the work-order flow itself, with a reason code list the supervisors helped write. Variance now posts the same shift it happens.
Considering NetSuite, or already living with it?
Tell us what is not working. If it is a half-hour fix we will tell you that, and you can decide whether to pay anyone at all.