The quick answer
Open the past-due work order and compare its planned dates with its actual production evidence. Check Built, component commitments and consumption, routing operations, and Related Records. Released indicates that the order is available for production processing under the account’s enabled features and controls; it does not mean the assembly has been built.
This example investigates a released order for 12 Aurora Control Units at Reno. It is linked to customer demand, its planned end date has passed, and its materials are committed. The screenshots use sample data and fictional person and operating-company names.
Before you start
Confirm which saved search or dashboard portlet marked the order past due. Its filters determine which date, location, status, and order types qualify. Saved-search fields and availability vary by role and account.
The Work Orders feature must be enabled, and your role needs permission to view the work order and the related production records you plan to inspect. Viewing the order does not guarantee access to every related transaction. WIP is required for Work Order Issues and Work Order Completions; a non-WIP flow may use an Assembly Build. Manufacturing Routing is required for routing operations and work-center activity.
Have the work order number, location, and the date used by the exception ready. Component visibility and commitment depend on the commit option, manufacturing preferences, inventory availability, location, and allocation rules. If you intend to enter production after the review, confirm inventory-detail and posting-period requirements separately.
01 · Open the past-due exception
Start from Work Orders - Past Due on the production dashboard. Check the result’s date context and location before opening the order. In this example, WO-7430 is Released, has a planned end date of September 10, 2026, and shows Built 0 of 12.
02 · Check the work-order plan
On WO-7430, confirm Created From, assembly, quantity, location, status, and planned dates. Here, Created From points to Sales Order SO-7429, which explains the make-to-order demand. The work order remains a separate production record.
Read Built independently from Status. The example is Released with Built 0, so NetSuite has not recorded finished output against this work order. Treat the memo as local context. “Material staged” and “laser cell repaired” still need operational confirmation.
03 · Check what production recorded
Open Items and compare Required, Committed, and Issued where those fields apply. WO-7430 has 12 Sensor Boards and 12 Housings committed, but none issued. A committed quantity indicates that NetSuite has committed or allocated that quantity under the account’s commitment rules. It does not record physical staging or consumption.
In a WIP flow, review Issued and related Work Order Issue records. In a non-WIP flow, component consumption may be recorded through an Assembly Build, and an Issued value or Work Order Issue may not be available.
Open Operations and review the planned routing and work centers. The example expects Cut / Prep in the Laser Cell and Final Assembly in the Assembly Cell. Confirm the work-center condition with the production team rather than treating the memo as proof.
04 · Decide what happens next
Open the available related-records area. WIP accounts may show Work Order Issues and Work Order Completions; non-WIP work orders may use an Assembly Build. The tabs and labels depend on enabled features, form customization, role permissions, and the production flow.
WO-7430 shows Built 0, Issued 0, and no visible related production records. Built 0 shows that no finished output is recorded. Issued 0 shows that no component issue is recorded on this order, but it does not decide whether production can proceed because backflush, inventory detail, operation scope, and account controls may affect completion. Confirm the physical production status before entering a transaction.
Check the result
- Plan: the source demand, quantity, location, and planned dates match the exception.
- Production: Built, component-consumption, and operation quantities agree with the production records available in this account.
- Next action: operations can confirm the work-center condition and staging claim before production begins or resumes.
Common questions
What does a Released status mean on a past-due work order?
Released means the work order is available for production processing under the account’s enabled features and controls. It does not mean the assembly has been built. Check Built and the related production records separately.
What should I check first when a work order appears past due?
Confirm the saved search or dashboard portlet’s date context, location, status, and order-type filters. Then verify the work order’s Created From, assembly, quantity, location, status, and planned dates.
What is the difference between Committed and Issued quantity?
Committed indicates that NetSuite committed or allocated the component quantity under the account’s rules. Issued indicates recorded component consumption where that field applies. Commitment alone does not prove that materials were physically staged or consumed.
How do WIP and non-WIP work orders record production differently?
In a WIP flow, review Work Order Issue and Work Order Completion records. In a non-WIP flow, production may be recorded through an Assembly Build, and an Issued value or Work Order Issue may not be available.
Can Built 0 and Issued 0 determine whether production can proceed?
No. Built 0 shows that no finished output is recorded, and Issued 0 shows that no component issue is recorded on the order. Backflush, inventory detail, operation scope, account controls, and the physical production status may still affect whether production can proceed.