NetSuite supports defining an Assembly Item, which is a build-to-stock Inventory Item, typically created using Work Orders. A Work Order specifies how many of the assembly item units should be built (that is, manufactured), and which component items Component Items will be consumed (that is, used). Note that component items Component Items are typically inventory items Inventory Items but could be assembly items Assembly Items if in a multi-level bill of material (BOM).

...

You can do build transactions directly in NetSuite, or in the ShipHawk WMS: a . A Build is a single transaction that both creates the Assembly Item and consumes the Component Items. A Build does not need to specify a Work Order, but typically does. (Note: an Un-Build or Disassembly transaction can also be initiated in NetSuite or in the ShipHawk WMS).

...

The quantity built and consumed will now be displayed on the Administration screen for the work order.

Work Order WIP (Issue/

...

Completion)

Process manufacturing requires a distinction between component issue and finished good completion for a Work In Progress (WIP) work order.

The ShipHawk WMS supports process manufacturing workflows that you might have in your ERP system (such as NetSuite) by providing a way to declare separately the consumption of raw materials and the creation of finished goods for a work order in the ShipHawk WMS.

While a Build is a single transaction that both creates the Assembly Item and consumes the Component Items, the Work Order WIP approach first defines an Issue transaction against a Work Order, and then once the manufacturing process is complete, defines a Completion transaction against the Work Order. An Issue transaction reduces component inventory during a manufacturing process and moves it to an in-process status. A Completion transaction declares the new inventory has just been created by the manufacturing process.