Contents8 sections ↓
NetSuite work orders: turning raw materials into finished goods
A NetSuite work order is the transaction that tells production which assembly item to build, how many, and from which components. It lists the components from the item's bill of materials (BOM), commits stock to them, and records issues, builds and costs as it moves through the statuses Planned, Released, In Process, Built and Closed. You turn it on with the Work Orders feature; WIP work orders with routing add labor and machine costing.
Last reviewed: 25 October 2026. Statuses, work order types and feature names re-checked against Oracle's NetSuite help; new section below on what 2026.1 and 2026.2 changed for manufacturing.
NetSuite offers two ways to produce assembled items: a basic assembly build, and a full work order with statuses, commitment of components and, optionally, routing and WIP tracking.
What changed in NetSuite 2026.1 and 2026.2
- 2026.1: warehouse staff can pick work orders in the WMS mobile app even when component items are backordered, and the app shows the backordered totals. See our 2026.1 operations and manufacturing summary.
- 2026.2: a new preference, Do Not Store Zero Quantity Components on Transaction Lines, stops zero-quantity component lines being stored on Assembly Build, Assembly Unbuild, Work Order Issue and Work Order Completion. It applies only to new transactions.
- 2026.2: costs of manufacturing charge items, including routing operation charges, can be bulk updated on production transactions, behind the Allow Bulk Update Costs for Production Charges preference.
- 2026.2: Rough-Cut Capacity Planning compares required and available capacity by work center, using planned time from work orders and planned work orders. Details in our 2026.2 operations summary.
These come from Oracle's 2026.2 Release Preview notes, which Oracle marks as subject to change. Check the final notes for your account's release.
Assembly builds vs. work orders
An assembly build is a single-step transaction: pick the assembly item and quantity, NetSuite consumes the BOM components and adds the finished assemblies to inventory. There is no routing and no WIP tracking, and cost is the cost of the components at the time of the build. It suits kitting and light assembly.
A work order adds a production cycle around the build:
- Statuses: Planned (no components committed), Released (nothing posted yet; components can be committed per your commit settings), In Process (a transaction has posted), Built (quantity built equals quantity planned) and Closed
- Component commitment and issuance
- Partial builds
- With WIP work orders and routing: operation tasks, labor and machine time, and costs that accumulate in a Work In Process account
Use work orders when production takes time, has several steps, or you need to see status and cost before the goods are finished.
What you need to enable. Oracle's help says the Work Orders feature must be enabled before you can use assembly work orders (Setup > Company > Enable Features). Routing is a separate step: enable Manufacturing Routing and Work Center, and note that routings work only on WIP work orders for assemblies using standard or average costing. Oracle's help does not tie these to a named edition or add-on, so confirm licensing for your account with your NetSuite account team.
The work order lifecycle
1. Planning
Work orders can be created:
- Manually, for a specific assembly item and quantity
- From a sales order, by checking Create WO on an assembly line; the work order joins the Mass Create Work Orders queue when the order is saved or approved
- For stock, when an assembly's back-ordered quantity reaches its build point, which adds a work order to the Mass Create Work Orders queue
- From Supply Planning (MRP), which generates planned work orders that planners review and firm
Each work order gets a BOM listing every component, with quantities scaled to the work order quantity.
For example, if the BOM for "Widget A" requires 2 Steel Plates, 4 Bolts M6 and 1 Motor Unit, a work order for 100 Widget A's needs 200 Steel Plates, 400 Bolts M6 and 100 Motor Units.
2. Component management
Three ways to get components to the work order:
- Commit: stock is committed to the work order so other transactions cannot take it. Committing happens from Released status, according to your commit option settings.
- Issue: components are issued to the work order as they are used.
- Backflush: issue components and complete the assembly in one step. Oracle's help notes backflush works at work order level, not per component, and cannot be used if the work order has serial-controlled components.
3. Release and production
Releasing the work order moves it out of Planned, where no components are committed. From there, production issues components and, on WIP work orders with routing, operators log time against operation tasks. Values for assets and expenses post to the designated WIP account while the assembly is built.
4. Completion
Record a work order completion for the quantity produced. On a WIP work order, the completion records labor against operations, issues materials, records scrap and reports the finished product. Finished assemblies enter inventory and WIP values move to the Asset for Assembly account.
A work order for 100 units can be completed in batches. It reaches Built when the quantity built equals the quantity planned.
5. Close
To close a work order you complete a build for the assemblies. Closing zeroes out remaining component back orders. If a work order will not be finished, close it rather than leave it open.
Work order types
NetSuite has two types of assembly work order, both on the same Work Order record:
- Special order: tracks assemblies built for a particular sale and stays linked to the sales order. It is the make-to-order case.
- Production: tracks assemblies built to increase stock. It has no customer and is not linked to a sales order. This is make-to-stock.
Taking an assembly apart again is a separate Assembly Unbuild transaction, not a work order type.
Scrap and yield
Scrap is recorded on the work order completion. The Component Yield Preferences in Setup control how component yield is handled when quantities are calculated. Check how your accounting treats scrap before go-live, and compare actual to planned component use regularly: rising scrap on one component or one work center usually points to a maintenance, quality or training problem.
Work order planning with MRP
Oracle's help describes Supply Planning (MRP) as the replacement for Time-Phased Planning, and tells new customers to use it. In outline:
- Demand: sales orders, demand plans and safety stock
- Supply: inventory, open purchase orders and open work orders
- Netting: MRP calculates the gap
- Planned orders: planned work orders and planned purchase orders to fill it
- Review and firm: the planner reviews them, for example in the Planning Workbench, and releases them as real transactions
MRP works through multi-level BOMs, since a sub-assembly has its own BOM. It plans material, not shop floor capacity; Rough-Cut Capacity Planning in 2026.2 is aimed at that second question.
Setting up MRP and work orders for the first time?
We configure manufacturing workflows, BOM structures, and MRP parameters for NetSuite. Get production right from day one.
Talk to a manufacturing consultantBest practices
Use the release step as a checkpoint. Review material and capacity before a work order starts, rather than discovering shortages halfway through.
Use back-flush selectively. Back-flushing cuts shop floor transactions but hides what happened during production. It suits low-value, high-volume components such as fasteners and packaging; issue high-value components explicitly for better WIP accuracy.
Close work orders promptly. Open work orders with remaining WIP balances distort inventory valuation. If a work order will not be completed, close it.
Review BOM accuracy regularly. Costing is only as accurate as your BOMs. If the BOM says 2 units of steel but production uses 2.3, you will see the same material variance every time.
Track cycle time. If routing is configured, compare actual operation times to standard times. Consistent overruns in one operation point to a bottleneck or a wrong standard.
What clients ask before signing
Cristina · BrokenRubik
Replies by email within 24 hours
Cristina
Not working the way this guide describes? Tell us what you see in your account and we'll reply with what we'd check first.
Gustavo Cañete
Co-Founder & Development Director
Co-founder and Development Director at BrokenRubik overseeing technical excellence and development operations. 12+ years of experience leading NetSuite development teams and delivering complex enterprise solutions.