How material requirements planning works in NetSuite, and the settings that decide what it proposes.
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.
Forecast-driven planning uses demand plans, which is covered on demand planning.
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 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.
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.
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 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.
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.
NetSuite can replenish two ways, and using the wrong one for an item is the most common reason planning output gets ignored.
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.
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.
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.
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.
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.
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.
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.