# How to create an assembly build or work order in NetSuite > Source: https://netray.co/erp-help/netsuite-how-to-assembly-build-work-order > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer For simple manufacturing with no routing or WIP tracking, use Transactions > Manufacturing > Build Assemblies (or Enter Assembly Build), select the assembly item, quantity, and location, and NetSuite consumes the BOM components and receives the finished item in one transaction. For multi-step production needing routing, WIP accounting or partial completions, create a Work Order (Transactions > Manufacturing > Work Orders) and process it through Work Order Completion, which requires the Advanced Manufacturing feature (SuiteSuccess Manufacturing or WMS add-on) or the Manufacturing bundle. ## Kind how-to ## System netsuite ## Erp Oracle NetSuite ## Module Manufacturing / Assembly Items ## Query how to create an assembly build or work order in NetSuite ## Alternate Queries - netsuite assembly build vs work order difference - netsuite build assembly item bom - netsuite work order completion - netsuite assembly item components not available ## Applies To NetSuite all current versions. Assembly Build available in standard NetSuite with the Assembly Items feature enabled. Work Orders with routing/WIP require the Manufacturing Work Orders feature (Advanced Manufacturing/CloudSuite Manufacturing edition or the Manufacturing SuiteApp). ## Steps ### Build an assembly item (simple, single-step) **Items:** Enable Assembly Items: Setup > Company > Enable Features > Items & Inventory > Assembly Items. Create the assembly item (Lists > Accounting > Items > New > Assembly/Bill of Materials) and define its BOM in the Components subtab, or via a separate BOM record if using the BOM feature. Go to Transactions > Manufacturing > Build Assemblies, select the assembly item, entity/location, and the quantity to build. NetSuite checks component availability against on-hand quantity at that location; components below the required quantity are flagged before the build can be saved. Save the Assembly Build - this consumes the component inventory and receives the built quantity of the assembly item into stock in one transaction, posting the inventory and COGS/WIP accounts per the item's accounting setup. For work orders instead: Transactions > Manufacturing > Work Orders > New, select the assembly item and quantity, and NetSuite generates the planned component requirements from the BOM/routing. Issue components to the work order (Transactions > Manufacturing > Issue Component, or via Work Order Pick/Ship if using warehouse management), then complete via Work Order Completion for full or partial quantities. Review WIP and variance postings on the work order's related records once completed - routing operations and labor/overhead absorb into WIP before the completion transaction relieves it. ## Sections ### Assembly Build versus Work Order - when each applies **Body:** Assembly Build is a single-transaction consume-and-receive: it does not track work-in-process as a separate inventory state, has no routing/operations, and completes in one step. It suits simple kitting or light assembly where the shop floor time between component issue and finished-goods receipt is not meaningful to track separately. Work Orders exist specifically to model that in-between state: components can be issued to WIP before the assembly is finished, routing operations with labor and machine time can be recorded, and partial completions post partial finished quantity while leaving the remainder open. This is the closer match to how a real production floor with multiple operations actually runs, and is what most manufacturers using NetSuite for production, not just light assembly, end up needing. ### Component availability and backordering an assembly build **Body:** An Assembly Build checks each component's available quantity at the transaction's location before allowing save. If a component is short, NetSuite will not silently negative-stock it under standard settings - the build either fails validation or (if negative inventory is allowed on that item/location) posts with a negative on-hand balance that needs correcting. For components sourced from a different location than the build, a transfer order or bin/location adjustment has to happen first; Assembly Build does not automatically pull inventory across locations. Work Orders handle multi-location sourcing more gracefully through supply planning/MRP if that module is in use. ### BOM structure and item costing implications **Body:** The assembly item's cost is derived from either the standard cost of components rolled up at build time, or a manually maintained standard cost, depending on the costing method configured (Average, FIFO, Standard). Standard costing on assemblies requires periodic cost rollups to keep the standard current as component costs change - see the related cost rollup how-to for that process on non-NetSuite ERPs; in NetSuite this is the Item Cost record and the standard cost version fields on the assembly item. Phantom components (sub-assemblies that exist only for BOM structuring, never separately stocked) are modeled by marking a sub-assembly item as Phantom on its record so the build explodes straight through to its own components rather than requiring a separate build step. ### Work order completion and variance **Body:** Work Order Completion posts the finished assembly quantity to inventory and relieves WIP for the components and operations consumed. Any difference between the standard cost absorbed and actual costs incurred (component substitutions, extra labor time) posts to a manufacturing variance account, which should be reviewed periodically rather than left to accumulate silently in WIP. ## Pitfalls - Using Assembly Build for multi-step production that actually needs WIP tracking, losing visibility into work in progress between operations. - Component shortages at the build location when the required inventory exists at a different location or bin - Assembly Build does not auto-transfer. - Standard-cost assemblies drifting out of date because the cost rollup was never re-run after component cost changes. - Forgetting to mark true structural-only sub-assemblies as Phantom, forcing unnecessary intermediate build transactions. - Partial work order completions left open indefinitely, distorting WIP balances on the balance sheet. - Negative inventory allowed on a component item masking a real supply shortfall during assembly builds. ## Ai Angle ERPray can check real-time component availability and flag which line on a planned assembly build or work order will fail before the build is even opened, by querying current on-hand and open supply for each BOM component. For recurring standard-cost drift questions, it can compare the item's standard cost record against the latest component costs and point out which assemblies are due for a rollup. ## Faq ### Does NetSuite Assembly Build support multi-level BOMs? **Answer:** Yes, but a standard Assembly Build only explodes one level unless sub-assemblies are marked Phantom (which explodes through automatically) or are pre-built as their own assembly items first. ### Can I do a partial work order completion in NetSuite? **Answer:** Yes. Work Order Completion allows entering less than the full planned quantity, posting that portion to finished goods and leaving the remaining quantity open on the work order for a later completion. ### Why does my Assembly Build fail with a component availability error? **Answer:** The build's location does not have enough on-hand quantity of one or more BOM components. Check Inventory > Item Availability for that item/location, or transfer stock in before retrying the build. ### What feature do I need for NetSuite Work Orders with routing? **Answer:** Routing, operations and WIP-stage work orders require the Manufacturing Work Orders / Advanced Manufacturing feature, typically part of NetSuite's manufacturing edition or the Manufacturing SuiteApp, beyond the base Assembly Items feature. ## Search terms netsuite assembly build, netsuite work order, netsuite assembly build vs work order, netsuite bom components, netsuite phantom item, netsuite work order completion, netsuite component availability error, netsuite manufacturing work orders feature, netsuite standard cost rollup, netsuite wip variance --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json