NetSuiteFree referencePDF, Excel, Word exportNetSuiteDiscrete Manufacturing

NetSuite Work Order Status Reference

A NetSuite work order moves through a short set of statuses, but the transactions around it decide what actually happens to inventory and cost. This reference lists each status next to the related transactions and records so you can read a work order and know where it really stands.

Download:

Item	Type	Search value	What it means	What to check
Planned	Status	WorkOrd:A	Work order exists as a plan and has not been released to the shop floor.	Safe to edit quantity, dates and BOM revision. Components are not yet being issued.
Released	Status	WorkOrd:B	Released for production. Components can be committed and issued and the build can start.	Confirm component availability and the location on the order before releasing in bulk.
In Process	Status	WorkOrd:D	Production has started: at least one issue or completion has been posted but the quantity is not finished.	Look for partial issues with no completion, which leave value sitting in WIP.
Built	Status	WorkOrd:G	The full quantity has been reported complete.	Built does not mean closed. WIP variance is settled when the order is closed.
Closed	Status	WorkOrd:H	Order is closed out. No further issues or completions can be posted.	Closing short leaves unbuilt quantity unproduced. Review variances before closing.
Work Order Issue	Transaction	WOIssue	Moves component inventory to the work order when you use WIP-based manufacturing.	Backflush versus manual issue is set on the item and routing. Check which one you run.
Work Order Completion	Transaction	WOCompl	Reports finished quantity and moves cost from WIP into finished inventory.	Completion quantity above the order quantity is controlled by an overbuild setting.
Work Order Close	Transaction	WOClose	Closes the order and posts any remaining WIP variance.	Reopen is not available in every setup, so verify with a sandbox test first.
Assembly Build	Transaction	Build	Builds an assembly item from its components in one step. Without the WIP feature, a work order produces one when built.	Choose one flow per assembly. Mixing build and WIP flows confuses costing.
Assembly Unbuild	Transaction	Unbuild	Reverses a build and returns components to stock.	Cost on the returned components follows the costing method, not the original build.
Work Order record	Record	Transaction type Work Order	Header with assembly item, quantity, location, BOM and revision, start and end dates.	Lead time and dates drive MRP supply plans, so keep them current.
Bill of Materials	Record	Bill of Materials	Defines the component list for an assembly.	Work orders pick a revision, not the BOM header alone.
BOM Revision	Record	BOM Revision	Version of a BOM with effective and obsolete dates.	An expired revision silently stops a new work order from defaulting to it.
Manufacturing Routing	Record	Manufacturing Routing	Sequence of operations and work centers used with Advanced Manufacturing.	A routing is tied to location and assembly. Missing routing is a common reason for blank operations.
Manufacturing Operation Task	Record	Manufacturing Operation Task	Task created for each routing operation on the order for tracking progress.	Operation status rolls into overall progress and drives completion postings.
Work Center	Record	Entity Work Center	Resource or group of resources used in routing steps.	Capacity and labor resource counts feed scheduling.
Manufacturing Cost Template	Record	Manufacturing Cost Template	Holds labor and overhead rates applied to routing operations.	Rates here set standard and actual labor absorption into the assembly.

Search values are shown as commonly seen in saved search criteria. Internal IDs can vary by release and feature set, so confirm in your own account before hard-coding them in scripts.

Ask your NetSuite work orders questions in plain English

Optional: see how a read-only natural-language layer over NetSuite can answer questions like which Built work orders are still open.

Optional. The tool and every export work without this. No spam.

How to use this reference

Type a status, transaction or record name into the search box to filter the table. Use the Search value column when building saved search criteria on work order status, then confirm the value in your own account. The What to check column holds the practical notes admins and planners tend to learn the hard way. Export to Excel to share a one-page cheat sheet with your production team or paste it into your admin handover documentation.

Filter by Status to see the lifecycle only
Filter by Transaction to see what posts to the ledger
Use the Record rows to find setup gaps

The status lifecycle

A work order starts Planned, becomes Released when production is authorised, moves to In Process after the first issue or completion, becomes Built when the whole quantity is reported, and ends Closed. Planned work orders are typically generated by MRP planning actions. Released and later statuses are what shop floor and cost accounting care about. Built is the point where many teams stop, which is why Built orders pile up with unsettled variances.

Work order versus assembly build

Without the WIP feature, building an assembly is one step: components out, finished item in. With WIP and routing, you issue components to the work order, report completions as operations finish, and close the order to settle variance. Pick the flow that fits your shop. A job shop with real routings needs the WIP flow. A kit-and-pack operation is usually fine with a direct assembly build.

Common mistakes

Most work order problems are process gaps rather than system faults. Orders are released without checking component availability, partial issues are never completed, Built orders are never closed, and expired BOM revisions leave new orders with the wrong component list. A weekly saved search on Built but not Closed orders catches the biggest group of these.

Frequently Asked Questions

What are the work order statuses in NetSuite?

The standard statuses are Planned, Released, In Process, Built and Closed. Planned is a plan only, Released allows issues and builds, In Process means work has started, Built means full quantity is complete, and Closed means the order is settled and locked.

Why is my NetSuite work order stuck in Released?

Usually no issue or completion has been posted. Check that components are available at the order location, that the routing and operations exist, and that nobody has built the item through a separate assembly build transaction instead of the work order.

Do I need to close a Built work order?

Yes in a WIP flow. Closing settles the remaining WIP variance into the ledger. Leaving orders Built keeps value in WIP and makes period end inventory and manufacturing reports look wrong.

How do I search work orders by status?

Create a transaction saved search, set Type to Work Order, and add a Status criterion. Use the filter list in the UI to pick values rather than typing internal IDs, unless you are working in SuiteScript where the IDs matter.

If your team keeps asking the same work order questions, Netray can put a read-only natural-language layer over your NetSuite data so planners can ask them directly. It respects your roles and shows the query it ran.

Talk to an Expert Explore More Free Tools

Related Tools

NetSuite

More NetSuite tools

See all

Back to All Tools