CSLogo BlackBlue
Oracle NetSuite Alliance Partner

NetSuite MRP and Supply Planning

How material requirements planning works in NetSuite, and the settings that decide what it proposes.

The Difference Between Planning and Reacting

Material requirements planning reads what you owe, what you hold, what is already on order and how long things take, then proposes the purchase orders, work orders and transfers that close the gap. In NetSuite this is supply planning: a planning run produces planned orders, a planner reviews them, and approved ones become real transactions. Done well it replaces the reorder spreadsheet. Done carelessly it produces noise that planners learn to ignore.

What the Planning Run Reads

  • Demand: sales orders, forecasts, work order component requirements, transfer requests.
  • Supply: on hand by location, open purchase orders, open work orders, in transit stock.
  • Item settings: lead time, safety stock, reorder point, preferred stock level, lot sizing.
  • Calendars and horizons: how far ahead to plan and how demand is bucketed.
  • Sourcing: whether an item is bought, built or transferred, and from where.

Forecast-driven planning uses demand plans, which is covered on demand planning.

How a Planner Uses It

  • Run planning on a schedule, usually nightly, so the morning starts with proposals rather than questions.
  • Review exceptions first: late supply, shortages inside lead time, orders to expedite or pull in.
  • Adjust quantities and dates where reality differs from the rules, and note why.
  • Approve, which creates the purchase orders, work orders and transfer orders.
  • Watch what the run keeps proposing and fix the item settings behind it rather than editing the same line every week.

Settings That Decide the Output

Lead times that reflect the supplier, not the contract

If a vendor quotes three weeks and delivers in five, planning built on three weeks will always be late. Review actual receipt performance and set lead times from it.

Safety stock with a reason

Safety stock should cover variability in demand or supply, not cover for a process nobody wants to fix. Review it by item class, not once across the whole catalog.

Lot sizing

Minimum order quantities, multiples and preferred stock levels shape every proposal. They are also where obsolete assumptions hide, especially after a supplier or packaging change.

Who owns the exceptions

A planning run is only as good as the person who works the exception list. Name them, and give them time in the day for it.

A Planning Run, Line by Line

A planner runs supply planning on Monday morning for a pump built from a housing bought in, an impeller machined in house, and hardware bought in.

  • Demand for the pump is 400 over six weeks: 150 from open sales orders and 250 from the forecast.
  • On hand is 60, with 100 already on an open work order due in ten days. Net requirement is 240.
  • The run proposes work orders for the pump, sized by the lot sizing rule. With a minimum of 100 and a multiple of 50, that is 250 rather than 240.
  • Those proposed work orders create dependent demand for the impeller and the housing, offset by the pump lead time, so the impeller work orders and the housing purchase orders land before the pump builds start.
  • The housing has a 21 day supplier lead time and 14 days of safety stock, so the purchase requisitions are dated 35 days ahead of the demand that drives them.
  • The output is a list of planned orders with suggested dates, plus reschedule messages on the orders that already exist: pull this one in, push that one out, cancel the third.

The reschedule messages are the part planners undervalue. A run that only proposes new orders and never tells you the existing ones are wrongly dated leaves the schedule quietly out of step with demand.

Reorder Points or MRP

NetSuite can replenish two ways, and using the wrong one for an item is the most common reason planning output gets ignored.

  • Reorder point. The item has a reorder point and a preferred stock level, and NetSuite proposes an order when projected stock drops below the point. It looks at history, not at the order book. Cheap to run, cheap to maintain, and right for fasteners, packaging and anything consumed steadily.
  • MRP. The item is planned from actual demand, dependent demand and lead times. It reacts to a large order the day it lands, and it needs lead times and BOMs to be true or it produces noise.

Most manufacturers run both, split by item: MRP on assemblies, long-lead and expensive components, reorder points on the rest. The split is set per item, so it can be changed as the profile of an item changes. Where the forecast feeding MRP comes from is covered on demand planning.

Where It Stops

NetSuite plans material and dates. It does not schedule finite capacity on the floor, and it does not build the statistical forecast for you beyond the methods in demand planning. Constraint scheduling and shop floor sequencing are what FactorySync adds.

Frequently Asked Questions

Is MRP included in NetSuite?

Supply planning, which covers material requirements planning, is part of NetSuite advanced inventory and supply chain capability. It reads demand, stock, open orders and item settings, and proposes planned orders for a planner to review.

What is the difference between reorder point and MRP in NetSuite?

Reorder point planning triggers replenishment when stock falls below a level. MRP is time-phased: it looks forward at actual and forecast demand across lead times and proposes what is needed when. Most manufacturers use MRP for components with real demand signals and reorder points for low-value consumables.

How often should we run planning?

Nightly is typical, with the planner working exceptions each morning. Running it more often rarely helps, because the inputs do not change that fast and constant re-planning erodes trust in the dates.

Why does NetSuite MRP propose orders we do not need?

Almost always because of what it is reading rather than the run itself. The usual causes are lead times left at zero or at a default nobody checked, safety stock set on items that do not need it, demand from a forecast that was never consumed by actual orders, and open work orders or purchase orders that were completed on the floor but never closed in the system. Fixing the data fixes the output.

How often should a supply planning run be scheduled?

Daily overnight is the common pattern, with planners working the output each morning and rerunning on demand after a large order. Weekly is enough only where lead times are long and demand is stable. What matters more than frequency is that someone owns the output: a run nobody actions produces the same messages the next day and teaches everyone to ignore them.

Setting this up, or fixing how it was set up? Get in touch and we will look at it with you. More on the whole production flow in the NetSuite manufacturing guide.