NetSuite MRP: Manufacturing Resource Planning Explained

Material Requirements Planning (MRP) answers three questions:

• what do I need to buy or make?

• how much?

• when?

NetSuite MRP compares demand (sales orders, forecasts, safety stock, Bill of Materials (BOM) driven component requirements) against available and planned supply (on-hand inventory, open purchase orders, in-progress work orders), then generates recommendations to close the gaps.

Unlike simple reorder-point systems, NetSuite MRP time-phases requirements, considers multi-level BOM dependencies, applies lead times, and produces a coordinated supply plan across locations.

This guide covers the MRP module itself: how the engine works, how to configure it, and what each planning layer adds.

To make this concrete, we will follow a single example throughout: a mid-sized manufacturer that builds industrial pumps from cast housings, machined shafts, seals, and motors. They carry about 200 finished pump models, source castings from three vendors, machine shafts in-house, and assemble to order.

Where NetSuite MRP Fits in the ERP Stack

NetSuite Enterprise Resource Planning (ERP) systems blend transactional capability with planning logic across three layers:

• Core ERP. General ledger, accounts payable/receivable, purchasing, inventory, and item masters.

• Manufacturing modules. Bills of Materials, routings, work orders, Work in Progress (WIP), shop floor tracking, and costing.

• MRP and supply planning. Demand planning, Master Production Schedule (MPS), MRP runs, planned orders, exception messages, and planner workbenches.

This blog focuses on the planning layer: how NetSuite MRP uses your manufacturing data to drive production planning, not on the execution steps covered in vertical manufacturing content.

Core MRP Master Data: Items, BOMs, and Routings

MRP is only as good as its master data. Three areas drive MRP behavior in NetSuite.

Item Master and Planning Parameters

Each item has planning parameters that control how MRP behaves:

• Replenishment method. MRP, reorder point, time-phased, or min/max. Choosing MRP enables the full planning engine for that item.

• Vendor lead time. Used to offset planned purchase orders backward from the required date.

• Safety stock. Treated as an additional demand requirement in MRP calculations.

• Lot sizing rules. Lot for Lot (order exactly what is needed), Fixed Lot Size, Periods of Supply, or minimum/maximum order quantities.

• Planning horizon and time fence. Defines how far ahead MRP plans and the frozen period within which planned orders are not automatically moved.

Important: Do not enable Auto-Calculate Lead Time until the system has at least six months of purchase order and receipt history. Without sufficient history, auto-calculated lead times will be unreliable and will produce poor MRP recommendations.

Example: The pump manufacturer sets a 12-week vendor lead time on cast housings (long lead, sourced from a foundry), a 3-day production lead time on machined shafts (in-house), and safety stock of 50 units on their highest-volume seal kit. MRP uses these parameters to offset planned orders backward from the required date.

BOM Management

NetSuite BOMs define the components and subassemblies that go into finished goods. For MRP:

• BOM explosion. MRP takes demand for a parent item and calculates the quantity and timing needed for every component at every level.

• Multi-level pegging. Planners can trace demand from top-level orders all the way down through subassemblies to lowest-level components.

• BOM revisions. Revision control with effective dates ensures MRP plans against the correct version of the BOM for any given production period.

• Component types. Inventory items, assembly items, non-inventory items, service items, and other charge types can all be part of a BOM.

• Yield factors. Component yield can be configured at the BOM level, so MRP accounts for expected scrap in its quantity calculations.

Example: A Model P-200 pump has a three-level BOM. Level 0 is the finished pump. Level 1 includes a machined shaft subassembly, a cast housing, a motor, and a seal kit. Level 2 breaks the shaft subassembly into a raw steel bar and machining labor. When MRP receives demand for 100 P-200 pumps, it explodes the BOM to calculate that it needs 100 cast housings, 100 motors, 100 seal kits, and 100 raw steel bars (adjusted for the 5% yield factor on machining).

Routings

Routings specify how an item is manufactured: work centers, operation sequences, setup time, and run time. Basic MRP functions without routings, but adding them unlocks capacity planning and realistic scheduling. Without routings, you can still plan materials, but you cannot check work center load or schedule operations against available resource time.

Demand Planning in NetSuite MRP

Demand planning is the front end of MRP. It defines what you expect to sell or consume so NetSuite can calculate what to buy and make.

Demand Inputs

NetSuite MRP handles both independent and dependent demand:

• Independent demand. Sales orders, transfer orders, demand plans/forecasts, and safety stock requirements.

• Dependent demand. Component requirements automatically generated from BOM explosions for higher-level items.

This allows NetSuite to plan not only finished goods but all lower-level components and subassemblies needed to support the production plan.

Demand Planning Workflows

NetSuite Demand Planning provides:

• Statistical forecast generation from historical sales data (moving average, linear regression, seasonal methods)

• Manual or imported demand plans (including Excel/CSV upload for collaborative planning)

• Location-level demand plans by item and time bucket

Those demand plans feed directly into MRP, which nets them against supply and generates planned orders.

Sales-Order vs Forecast-Driven Planning

Many NetSuite customers start with sales order-driven planning: MRP looks at open sales orders and calculates the materials and production needed to fulfill them. This works well for make-to-order and short-lead-time environments.

As the business matures or lead times lengthen, teams layer in forecasts so MRP can plan ahead of actual orders. When sales orders arrive, they consume the forecast, preventing double-counting. This progression from reactive to proactive planning happens within the same NetSuite MRP engine without changing systems.

Example: The pump manufacturer starts by running MRP against open sales orders only. When a distributor places an order for 50 P-200 pumps with a 6-week delivery, MRP calculates the material and production requirements to fulfill it. As the business grows and lead times for castings stretch to 12 weeks, they add demand plans: a monthly forecast by pump model, uploaded from their sales team's spreadsheet. MRP now plans castings and motors against the forecast, and actual orders consume the forecast as they arrive.

The MRP Calculation Cycle

A Supply Plan Definition in NetSuite specifies the planning horizon, which locations to include, the demand source (sales orders, demand plans, or both), and which items or item groups to plan. When the supply plan runs, MRP follows this sequence:

1. Calculate gross requirements. Sum demand from orders, forecasts, dependent BOM demand, and safety stock across the planning horizon.

2. Net against supply. Subtract on-hand inventory, open purchase orders, incoming transfer orders, and in-progress work orders.

3. Apply lot sizing and lead times. Adjust quantities based on lot sizing rules and offset requirements backward using vendor or production lead times.

4. Explode BOMs. For manufactured items, MRP walks down the BOM tree, generating time-phased component requirements at each level.

5. Generate planned orders. Output is planned purchase orders, transfer orders, and work orders ready for planner review.

Example: MRP runs for the P-200 pump. Gross requirement: 150 units over the next 8 weeks (100 from forecast, 50 from a confirmed sales order). On-hand: 20 finished pumps, plus 30 cast housings in stock and a PO for 80 more arriving in week 3. MRP nets the requirement, explodes the BOM, and generates: a planned work order for 130 pumps (150 minus 20 on hand), a planned PO for 20 additional cast housings (130 needed minus 30 on hand minus 80 inbound), and a planned work order for 137 machined shafts (130 plus 5% scrap). It offsets the casting PO by 12 weeks of lead time and flags an exception: "expedite existing PO for cast housings, current delivery date is 2 weeks late."

Throughout this process, NetSuite also generates exception and action messages: "expedite this purchase order," "cancel this work order," "increase quantity on this planned order." These messages help planners focus on what has changed rather than reviewing every order from scratch.

The Supply Planning Workbench

The Supply Planning Workbench is where planners review, adjust, and release MRP recommendations. It shows:

• Items with projected shortages or excess

• Planned purchase orders, transfer orders, and work orders for each item

• Multi-level pegging so planners can drill from a component shortage to the sales orders or forecasts driving demand

• Action messages flagging orders that need attention

From the Workbench, planners can firm individual planned orders (locking them so subsequent MRP runs will not reschedule them) and release them in bulk or individually to become actual purchase orders or work orders.

The Workbench also supports Distribution Requirements Planning (DRP) for multi-location manufacturers, where supply is coordinated across warehouses and production facilities.

Example: The planner opens the Workbench and sees the P-200 pump flagged with an action message: "expedite cast housing PO." They drill into the pegging and see that the 50-unit sales order is driving the urgency. They firm the planned work order for 130 pumps, release the planned PO for 20 additional castings, and call the foundry to expedite the existing order. The shaft work order is released to the machine shop. All of this happens in one screen.

Work Orders in NetSuite MRP

Work orders are how MRP turns "make" recommendations into executable production orders.

Work Order Lifecycle

When MRP recommends manufacturing, planners or automated rules create work orders. Work orders track:

• Components allocated to the job and their issue status

• Production status: planned, released, in progress, complete

• Planned vs actual quantities, including scrap and yield variances

• Material, labor, and overhead costs rolling into the finished good cost

Work Orders Without Routings

Many manufacturers start without routings. MRP still plans material requirements from BOMs, and work orders manage component allocation and completions. However, capacity planning is limited and labor/machine loading is not visible. As operations become more complex, adding routings unlocks costing, capacity visibility, and scheduling accuracy.

BOM Revision at Work Order Creation

When a work order is created, NetSuite locks the BOM revision. If the work order is un-firmed, planners can switch BOM revisions before releasing. Once firmed, the revision is fixed, ensuring materials are planned against the correct specification.

Capacity Planning and Scheduling

Material requirements planning tells you what and when. Capacity planning tells you whether you can actually execute the plan.

Rough-Cut Capacity Planning (RCP)

Available with NetSuite Advanced Manufacturing, Rough-Cut Capacity Planning:

• Compares production demand from work orders and demand plans to work center availability over time

• Reports work center utilization percentages and remaining capacity

• Highlights bottlenecks before they cause schedule failures

RCP acts as a sanity check on the Master Production Schedule, letting planners identify overloaded resources and adjust the plan before releasing work to the shop floor.

MPS and Finite Capacity Scheduling

For resource-constrained environments, MPS sits above MRP in the planning hierarchy:

• MPS determines what finished goods to build and when, considering capacity constraints.

• MRP then calculates the raw material and component requirements to support the MPS.

• Finite capacity scheduling (Advanced Manufacturing) releases work orders only when required machines and labor are actually available, preventing work center overloads.

Finite scheduling in NetSuite considers operation concurrency, respects sequence rules and priorities, and builds a realistic, resource-constrained production schedule.

Work Center Load Visibility

NetSuite provides Work Center Load saved searches that show planned and released hours per work center by time period. Combined with work calendars that define resource availability, planners can identify where capacity is tight before releasing orders.

Example: The planner checks the machining work center load and sees that weeks 4 and 5 are at 115% utilization because the shaft work orders overlap with a batch of custom orders. RCP flags the bottleneck. The planner either moves 20 shaft work orders to week 3 (where capacity is available) or approves overtime for the machining cell. With finite capacity scheduling enabled, NetSuite would not have released those overlapping orders in the first place, automatically spreading them into weeks with available capacity.

NetSuite MRP Feature Overview

Practical Implementation Tips

1. Start with clean master data. Ensure lead times, safety stock, and BOM quantities are accurate before running MRP. Start with a subset of critical SKUs.

2. Use a Supply Plan Definition to scope your first run. Limit the planning horizon, locations, and item groups to something manageable rather than planning everything at once.

3. Start with material planning only. Run MRP focused on materials using infinite capacity while you build planner confidence.

4. Introduce demand plans gradually. Move from purely sales-order-driven planning to forecast-backed demand plans once your team understands the basics.

5. Layer in capacity last. Add routings and Rough-Cut Capacity Planning once material planning is stable. Finite scheduling comes after that.

6. Close the loop with actuals. Implement barcode-based labor and material reporting where possible. Variance and utilization data refines your planning parameters over time.

How Softype Configures NetSuite MRP

Softype has configured NetSuite MRP for manufacturers and distributors across multiple industries and planning models.

For a food manufacturer, we configured a full Plan to Produce workflow: demand plans imported from external forecasting tools, MRP-driven replenishment replacing legacy time-phased rules, work order generation with BOM management, WIP and routing configuration, and a custom Supply Analytics capacity workbook for finite capacity checking. The engagement covered lot sizing rules, safety stock parameters, planning fences, and the Supply Planning Workbench.

For a health supplement distributor with outsourced production, we configured MRP for raw material replenishment triggering purchase orders rather than work orders, replacing a manual planning process that depended on spreadsheets and multiple legacy tools. The Supply Planning Workbench replaced three separate planning systems.

Our MRP implementations follow a staged approach: clean the item and BOM data first, configure Supply Plan Definitions and parameters, run parallel tests against historical demand before going live, and train planners on Workbench workflows before the cutover.

Talk to Softype about configuring NetSuite MRP for your operation.

Frequently Asked Questions

RELATED BLOG: NetSuite WMS: Warehouse Management Features & RF Barcode Scanning

RELATED BLOG: NetSuite for Assembly Manufacturing: Production Tracking, MRP & Shop Floor Control

RELATED BLOG: NetSuite for Manufacturing: Complete Implementation Guide 2026