NetSuite Insights & Guides | CuriousRubik

NetSuite Manufacturing Design for BOMs Orders and WIP

Written by CuriousRubik | Mar 14, 2018, 1:26:00 PM

Updated 6 October 2026.

NetSuite manufacturing design should connect the engineering definition of a product to material consumption, production progress and financial cost. Start by deciding which events the factory can reliably record, then choose assembly, work-order, WIP and routing capabilities that support those events. Enabling every manufacturing feature does not establish a workable production process.

The production lead and controller need a common model of what is being built, where unfinished material sits and when costs become finished inventory. Use one representative product and a realistic exception to validate that model before expanding the item catalogue.

Separate the product structure from the execution method

A bill of materials describes the materials required to make a product. A work order authorizes a production quantity. The transactions entered against production establish what actually happened. Keep these concepts separate during discovery so an engineering revision is not confused with an instruction to change every open order.

Oracle documents assembly items, work orders, Advanced Bill of Materials, WIP and routing as distinct capabilities. Enabling Advanced BOM changes the BOM record model; Advanced Manufacturing has its own SuiteApp dependency.

Ask which facilities can make the item, whether they use the same components and how approved substitutions are controlled. Define the effective date of a revision and the rule for already released production. Store evidence of the business decision, including who can approve a deviation and who must be notified.

Choose the events that production will capture

For a short, straightforward assembly, the business may need a simpler production transaction model. Longer production cycles often require explicit visibility into issued materials, partial completions and remaining WIP. Evaluate the physical process rather than choosing a model solely because it produces more detailed reports.

NetSuite WIP separates work-order issue, completion and close. Its documentation also requires the WIP line location to agree across those transactions. The factory must therefore know when material leaves stock, how finished output is reported and who confirms that an order is ready to close.

Define whether consumption is recorded directly or calculated through an approved backflush process. Test the chosen configuration with actual operational behavior, including late entries. A process that assumes exact consumption at completion may need additional controls when components are frequently substituted, damaged or returned to stores.

Design the BOM and units together

For each representative assembly, capture component identity, quantity, unit, yield assumption and revision. Review decimal precision and package conversions. A small conversion error repeated across a production run can become a large material variance.

Include purchased subassemblies and internally built subassemblies in the same review. Clarify whether a supplier performs a production step or simply sells a finished component. Outsourced production can create different purchasing, inventory and costing requirements from an internal work center.

Avoid migrating every historical BOM as an active production choice. Identify the revisions required for current products, service obligations and open orders. Keep obsolete engineering history accessible under an agreed archive policy without presenting it as an approved build instruction.

Add routing only when the operational detail is useful

Routing is appropriate when the business needs to schedule and capture distinct operations with work centers, resource time or operation-level costs. NetSuite Manufacturing Routing is limited to WIP work orders and average- or standard-cost assembly items.

Before selecting it, ask whether employees can distinguish setup time from run time, whether machines and labor run together and how interruptions are recorded. Decide what the planner will do with actual-versus-planned results. Reporting detailed time without a decision process can create effort without improving scheduling or cost control.

Confirm licensed functionality, permissions and the interaction with any shop-floor system. An external production application should not independently create the same completion that NetSuite receives through another integration.

Set up the first WIP assembly and work order

Validate this sequence in an authorized test account with the manufacturing and finance owners. Feature availability, roles and costing design determine the applicable fields.

  1. Confirm Assemblies and Work Orders are enabled. An administrator can enable Manufacturing Work In Process under Setup > Company > Enable Features > Items & Inventory.
  2. On a suitable assembly item, review the approved WIP, scrap and WIP cost-variance accounts. Oracle limits WIP work-order items to standard or average costing; save only after the accounting design is accepted.
  3. Open Transactions > Manufacturing > Enter Work Orders, complete the assembly and quantity, select WIP and the required location, then save.
  4. Process the order through supported component issue, completion and close transactions. Verify partial completions, remaining materials and close variances against the actual costing behavior before adopting the procedure.

Validate WIP enablement, assembly setup and the work-order settings together before processing production activity.

Hypothetical production scenario

A manufacturer plans 100 assemblies, each requiring two brackets and one housing. The expected material requirement is therefore 200 brackets and 100 housings. Production issues those quantities but completes only 96 good assemblies before the reporting cutoff.

The remaining material could represent unfinished units, scrap, unused components or a recording error. Do not resolve the difference by assuming every issued component belongs to the 96 completed units. Ask the supervisor to identify the four unfinished assemblies and any damaged components physically.

The acceptance test should show the finished quantity, component movements, remaining WIP and expected accounting entries. When the final units are completed or the remaining work is cancelled, the controller reviews the supported variance and order closure. This is a hypothetical control example, not a costing prediction; the actual amounts depend on costing method, rates and account configuration.

Reconcile costs at the production boundary

For selected orders, build a bridge from opening WIP through material and conversion costs to completed output, approved variances and ending WIP. Trace the bridge to transaction evidence and the general ledger. Investigate open orders with no recent activity and completed orders that still carry unexplained balances.

Separate quantity investigation from rate investigation. Extra consumption and an incorrect component cost can produce similar financial variances but need different fixes. Review labor or overhead rates with finance, and establish who approves changes and their effective dates.

A manufacturing acceptance matrix

Use these scenarios before signoff:

  • Standard build with the approved BOM revision
  • Partial material issue and partial completion across a period end
  • Approved substitution or engineering revision affecting an open order
  • Scrap and unused-material disposition
  • Rework or unbuild where the selected process supports it
  • Incorrect completion reversal and controlled re-entry
  • External shop-floor message replay without duplicate production
  • Work-order close with explained cost variances

Record expected quantities, transaction references, cost treatment and an owner for every scenario. A screenshot of a completed order is insufficient evidence if the component and WIP balances remain unexplained.

Manufacturing design is ready when engineering, production and finance can follow the same order from its approved structure to its final cost. Use that evidence to scope a CuriousRubik implementation discussion, including any factory-specific exceptions that need a more detailed design.

Related resources