How assembly items, work orders and assembly builds work in NetSuite, and when to use each.
Work Orders and Assemblies is the NetSuite feature that records production: an assembly item with a bill of materials, a work order that reserves and consumes the components, and a completion that brings finished goods into stock at cost. It is the foundation every other manufacturing feature sits on, from routings and WIP to planning and costing. This page covers what it includes, how it runs day to day, the decisions to make at setup, and where it stops.
An assembly build on its own is enough for light manufacturing. Add routings and work in process when you need labor, machine time and operations tracked, which is covered on routings and WIP.
Issuing material to a work order gives an accurate picture of what is on the floor and takes discipline. Backflushing consumes components automatically at completion, which is faster and hides shortages until a count finds them. Most manufacturers land on a mix: backflush low-value hardware, issue the expensive and the traceable.
Sub-assemblies can be built as their own work orders or flattened with phantom items. Real sub-assembly work orders give visibility and cost at each level. Phantoms keep the paperwork light when the sub-assembly is never stocked.
Decide before go-live how scrap is recorded and who can record it. If scrap is only discovered at month end, the yield numbers and the job costs will both be wrong.
Traceable finished goods need their lot or serial captured at build. It is far easier to enforce this in the build screen than to reconstruct it later from paperwork.
A shop builds a pump assembly. The item record is an assembly item, the bill of materials calls for one housing, one impeller, two seals and a hardware kit, and a customer orders 200.
Every number on that trail is queryable afterward: what was required, what was committed, what was issued, what was completed and what was scrapped, per work order and per component.
Not every build starts with a customer. NetSuite creates work orders three other ways, and it is worth knowing which one your planners will live in.
Make-to-order shops usually run special order plus manual. Make-to-stock shops should be on planning runs within a few months of go-live, or the planner becomes the bottleneck.
Native work orders handle the transaction well. They do not give a visual schedule across machines, they do not capture shop floor time without additional setup, and they do not plan around capacity constraints.
A work order is the instruction to build a quantity of an assembly item by a date. An assembly build is the transaction that actually completes it: components are consumed, the finished item is received into stock, and the cost posts. You can build without a work order for simple production, but you lose the planning and status the work order carries.
Yes. A work order can be completed in stages, with each assembly build consuming the components for the quantity completed. The remaining quantity stays open, so work in process and the schedule stay accurate.
No. Work orders and assemblies come with the manufacturing capability in NetSuite. Advanced Manufacturing is a SuiteApp that adds a production work bench, planned times, work instructions and shop floor data collection.
Scrap recorded on the assembly build keeps the consumed quantity on the work order while lowering the completed quantity. The materials consumed by scrapped units stay in the job cost, so the variance shows up against that work order rather than being spread quietly across good units. If scrap is not recorded at all, the shortage surfaces later as a negative inventory adjustment with no job attached to it.
Yes. Quantities, dates and component lines can all be edited on a released work order, and the commitments recalculate. What does not change automatically is a work order whose BOM revision has since been superseded: it keeps the components it copied when it was created, which is usually what you want, but it means an engineering change does not reach open work orders unless someone updates or reissues them.
Setting this up, or fixing how it was set up? Get in touch and we will look at it with you. More on the whole production flow in the NetSuite manufacturing guide.
