NetSuite gives manufacturers three ways to record production: a standalone assembly build, a work order completed with an assembly build, and a WIP work order run through issues, completions and a close. All three end with finished goods in stock, which is why the choice often gets made by whoever configures the first transaction. It matters more than it looks. The method decides when components leave inventory, whether work in process appears on the balance sheet, whether labor and machine time are captured, and whether variances ever post. This post explains how each works, which manufacturers should use which, and how to move from one to another.
The three ways to build
Standalone assembly build
An assembly build without a work order consumes the components on the bill of materials and adds the finished assembly to inventory in a single transaction. There is no plan, no schedule and no record of the build before it happens. It suits simple kitting and light assembly done in minutes, where the only thing worth recording is that it happened.
Work order completed by assembly build
A standard work order is a plan: build this many of this assembly, by this date, at this location. It commits components, shows up in supply planning and gives the floor something to work from. When the build is done, an assembly build is entered against the work order, which consumes components and adds the finished goods in one step, and the work order is marked built. There is no WIP stage; components move straight from raw material to finished goods.
WIP work order with issues, completions and close
With the Manufacturing Work In Process feature enabled, a work order can be marked WIP. Production is then recorded in stages. A work order issue moves components out of inventory into a WIP account. One or more work order completions record finished output, optionally against the operations in a routing, with labor and machine time attached. A work order close calculates the difference between what was put into WIP and what came out at cost, and posts it to variance accounts. Assembly builds cannot be entered against a WIP work order; the three WIP transactions replace them.
Which one to use
The decision comes down to how long production takes, whether you need to see work in process, and whether labor and machine costs matter to your margins.
- Use standalone builds for kitting, simple assembly and repacking that finishes in one sitting with no planning needed.
- Use work orders with assembly builds when you need planning, component commitment and a schedule, but production is short enough that nothing meaningful sits half-finished at month end, and conversion costs are small or applied as overhead.
- Use WIP work orders when jobs span days or weeks, when material is issued in stages, when you need labor and machine time by operation, or when you run standard costing and want production variances by cause.
Many manufacturers end up with a mix: WIP work orders for the main production lines and standalone builds for packaging or kitting steps at the end.
What changes in the books
With assembly builds, inventory moves from components to finished goods instantly. If a job is half done at month end, the books show either all of the components still in raw materials or all of the output in finished goods, depending on whether the build has been entered. For short jobs that is close enough.
With WIP, the balance sheet carries a work in process balance that reflects material issued and conversion cost applied to jobs not yet completed. That is more accurate for longer production, but it puts a responsibility on the plant: WIP is only right if issues and completions are recorded when they happen and work orders are closed promptly. A WIP account that grows month after month is almost always a list of work orders that finished long ago and were never closed. Our page on routings and WIP covers the routing side.
Routings and labor
A routing lists the operations an assembly passes through, the work center for each, and setup and run times. With Manufacturing Routing enabled, WIP completions can be recorded operation by operation, labor and machine time post to WIP at the work center rates, and the work order shows progress through the routing. Assembly builds do not use routings in this way. If knowing where a job is on the floor, or what it really cost in labor, matters to you, that alone points to WIP.
Issuing components
On a WIP work order, components can be issued in a separate work order issue transaction or backflushed at completion. That choice is made per component and has its own trade-offs, covered in our post on backflush vs. manual issue in NetSuite. With assembly builds, components are always consumed at the BOM quantity when the build is entered, unless someone edits the quantities on the build itself.
Moving from assembly builds to WIP
Manufacturers who outgrow assembly builds usually notice it as a costing problem: margins that do not reconcile with the floor, or month-end inventory that never matches a count. Moving to WIP is a configuration change plus a process change.
- Enable Manufacturing Work In Process and Manufacturing Routing, and set up the WIP, scrap and variance accounts.
- Build routings with realistic setup and run times for the assemblies that will use WIP. Start with the highest-volume or highest-value lines.
- Decide, per component, whether it is issued or backflushed.
- Finish or close all open standard work orders for those assemblies, then switch new work orders to WIP from a clean cutover date.
- Train the floor on recording completions as they happen, and set a rule for closing work orders within a day or two of the last completion.
- Review the WIP balance weekly for the first month, to catch work orders left open.
The process change is the hard part. WIP depends on the floor recording what happens when it happens, which is why Consule built FactoryBridge to put WIP completions, operation start and stop and scrap on a tablet at the machine, and FactorySync to schedule WIP work orders against real work center capacity. Both work on NetSuite’s own work orders, so the accounting stays native.
Consule Solutions helps manufacturers choose and configure the right production model in NetSuite, including moving from assembly builds to WIP without disrupting month end. Get in touch if your WIP balance or your margins do not match the floor. For the module overview, see work orders and assemblies in NetSuite.
Frequently asked questions
What is the difference between a work order and an assembly build in NetSuite?
A work order is a plan to produce a quantity of an assembly by a date; it commits components and appears in supply planning but moves no inventory. An assembly build is the transaction that actually consumes components and adds the finished assembly to inventory. A build can be entered against a standard work order or on its own.
Can you use an assembly build on a WIP work order?
No. WIP work orders are recorded with work order issues, work order completions and a work order close. Those three transactions replace the assembly build and move costs through a work in process account rather than straight to finished goods.
When should a manufacturer use WIP in NetSuite?
Use WIP when production spans days or weeks, when material is issued in stages, when you need labor and machine time captured by operation, or when you run standard costing and want production variances. For short jobs with small conversion costs, work orders completed by assembly builds are usually enough.
Why does my NetSuite WIP balance keep growing?
Almost always because work orders are not being closed after production finishes. Costs sit in WIP until the work order is closed and variances post. A saved search of WIP work orders with no completions in the last week, sorted by WIP value, usually finds the cause in minutes.