By Louis Balla, Chief Revenue Officer, Nuage. Updated October 2026.
NetSuite demand planning forecasts item demand from sales history or a sales forecast, then turns the demand plan into a supply plan of suggested purchase orders and work orders. Oracle states that Advanced Inventory Management must be enabled. You choose a projection method for each item, set lead times and safety stock, and review the plan before ordering.
This guide covers how the calculation works, which replenishment method to give each item, the setup steps in order, and the data problems we see when planners move off spreadsheets.
What is NetSuite demand planning?
Oracle’s Demand Planning documentation describes it as a way to analyze stock demand to determine reorder quantities and timing, which is most useful for items with fluctuating demand through the year. It produces two kinds of plan:
- Demand plans show expected future demand, based on past demand or on a projection. You create them on the Calculate Demand Plan page.
- Supply plans show suggested purchase and manufacturing schedules. They are generated from demand plans on the Calculate Supply Plan page and take lead times, safety stock levels and preferred vendors into account. For assembly items, the supply plan also plans work orders for every sub-component and raw material.
Forecasting and planning are separate steps. Forecasting estimates what customers will want, using history and statistical methods. Planning decides how to meet that demand by choosing quantities, timing and sources. NetSuite connects them: the demand plan is the forecast, and the supply plan is the response.
Oracle also states that its Supply Planning (MRP) solution replaces Time-Phased Planning and offers more features and better performance. New customers should use MRP, and existing customers should plan to move from Time-Phased Planning to MRP (Oracle’s item record setup page). The Time Phased replenishment method, the demand plan setup and the import steps below describe the Time-Phased Planning path for accounts that still use it. A new account should confirm with its NetSuite team whether to start on MRP instead.
You can generate orders from a supply plan with the Order Items page for purchases or the Mass Create Work Orders page for assemblies. Oracle notes the process handles up to 10,000 items at a time, works with Multiple-Location Inventory, and supports the Available to Promise feature for calculating availability.
How does NetSuite calculate demand?
The Calculate Item Demand Plan page analyzes past demand, not past forecasts. You pick a projection method, an interval, a duration and the items. Oracle’s Calculating Item Demand page describes four methods.
| Method | What it does | What to know |
|---|---|---|
| Linear regression | Projects future demand from past demand using the ordinary least squares method | Needs a historical analysis duration |
| Moving average | Uses the moving average of historical demand as a smoothing function, and applies the same average to every projected period | Needs a historical analysis duration |
| Seasonal average | Finds seasonal trends in past demand and uses them to forecast future stock levels | Needs a historical analysis duration, and the projection interval must be monthly |
| Sales forecast | Uses forward-looking sales data from estimates, opportunities, sales orders, item fulfillments, cash sales and invoices | Does not need a historical analysis duration |
The method you choose should follow the item’s behavior. Steady items with a trend suit linear regression, volatile items suit the moving average, and items with recurring peaks suit seasonal average. Items sold against a pipeline suit sales forecast.
A separate preference controls which transactions count as demand for reorder point calculations. Oracle’s Inventory Management Preferences offer an Orders option, which uses sales orders and work orders, and an Actual Sales option, which uses cash sales, invoices and assembly builds. Oracle’s guidance is that a company that uses both sales orders and standalone cash sales or invoices should choose Actual Sales.
Reorder point or time phased: which replenishment method should an item use?
Each item carries a Replenishment Method. The choice decides whether the item is ordered from reorder points or from its demand plan.
| Reorder Point | Time Phased | |
|---|---|---|
| What drives orders | Advanced Inventory Management settings, with orders created from replenishment reminders on the Order Items, Replenish Items and Mass Create Work Orders pages | The item’s demand plan |
| Fields that apply | Reorder point, reorder multiple, preferred stock level, safety stock days, build point, seasonal demand | Alternate source item, lot sizing method, fixed lot size, supply type, demand source |
| Fits | Items with steady demand where a stock level triggers an order | Items whose demand moves through the year and needs a forward plan |
Oracle documents the auto-calculation for reorder points. Without safety stock, the reorder point is the average lead time in days multiplied by demand. With safety stock in days it is (average lead time days plus safety stock days) multiplied by demand, and with a safety stock quantity it is (average lead time days multiplied by demand) plus that quantity. Lead time itself can be calculated from the three most recent purchase orders. The preferences page lists defaults of 14 days for lead time, 7 days for safety stock, 30 days for preferred stock level and a six-month order analysis interval. Check what your account uses.
How do you set up NetSuite demand planning?
The order below follows Oracle’s documentation for the Time-Phased Planning path.
- Enable Advanced Inventory Management and Demand Planning. Demand plans are available for inventory items once the Demand Planning feature is on. Assembly and bill of materials items also need the Work Orders feature.
- Choose the demand basis. Set the preference for Orders or Actual Sales so reorder point calculations use the right transactions.
- Set up each item record. Choose the replenishment method. Time Phased is required for an item to have a demand plan. Enter lead time, or let NetSuite calculate it, and set safety stock. For seasonal items, add the expected demand change, which applies only to the seasonal average method.
- Set time fences. The demand time fence and planning time fence each accept 0 to 365 days and default to the account-level values. Reschedule in days (1 to 90) and reschedule out days (1 to 180) set the most days an order can be moved earlier or later. Left blank, NetSuite recommends no rescheduling in that direction.
- Calculate the item demand plan. Select the subsidiary and location where they apply, choose the method, interval, duration and items, then submit.
- Review and adjust. In an existing plan you can edit the quantity for each line or interval. Only the custom form, unit of measure and memo header fields can be edited, and the calculated column is for reference.
- Calculate the supply plan and create orders. Use the Order Items page for purchase orders and the Mass Create Work Orders page for assemblies.
What goes wrong with demand plans, and how to fix it?
Three situations from our client work show where setup decisions matter.
Reorder points set from the wrong sales history
An industrial rigging supplier with several branches found the system suggesting a reorder point at one branch where it should have been zero, and the issue was affecting orders. Our consultant tested the settings in a sandbox and found the auto-calculation was working from a location with no sales order history to draw on. The recommendation was to switch off auto-calculation for that location and set its reorder points by hand until it has history.
For a new item, Oracle documents a related option: an alternate source item lets the plan use another item’s history when the new one has too little. The alternate source must be the same item type, and the expected demand change for the original item still applies.
Stocking levels loaded in passes
An industrial distributor’s purchasing agent set out a four-pass plan for reorder points and preferred stock levels and asked our team to load it. Fast movers, items that sold in at least 6 of the last 12 months with no stocking policy, came first; then items that sold in at least 4 of the 12; then items whose existing levels needed adjusting for sales history and vendor lead times; and last, dead stock with quantity on hand and no sales order or invoice in 12 months, which goes to zero. The passes separate the items that need a policy now from the ones that need judgment, so each load can be checked on its own.
Replenishment rules that lived in one person’s head
A specialty chemical products manufacturer keeps some stock at an off-site storage warehouse, and when its buyer was out, a stand-in sent a rush order straight to the manufacturer when the stock should have come from storage. The buyer told us he wants “whoever is filling in for me knows where this product would come from, because we’re only adding more items to outside locations.” The rules we mapped with him: when the production site hits its reorder point, suggest a transfer from storage; when storage hits its reorder point, suggest a purchase order to the manufacturer; and use different reorder multiples by location, cases at one and pallets at the other.
Put each rule in the item and location records: reorder points, transfer sources and reorder multiples by location.
How Nuage approaches NetSuite demand planning
In recent client work, our team has taken or recommended these steps. The order changes with each account.
- Group items by how they behave. We separate steady, seasonal and new items, because each needs a different projection method or an alternate source item.
- Load stocking levels in passes. Fast movers come first, and each pass is checked before the next one starts.
- Test sales history by location. Before auto-calculation is relied on, we check which locations have history to draw on and set the rest by hand.
- Write replenishment rules into the records. Transfer and purchase rules by location replace knowledge held by one buyer.
- Review the first supply plans with the planner. Time fences and lead times get adjusted against what the planner sees on real items.
Nuage’s NetSuite experts do this work as part of NetSuite optimization and managed services. For related planning topics, see our guides to production planning software, inventory management optimization and the NetSuite advanced manufacturing guide, and our companion piece on why NetSuite for manufacturers.
NetSuite demand planning FAQ
How does NetSuite handle seasonal demand?
Use the seasonal average projection method, which examines past demand for recurring patterns and forecasts from them. The projection interval has to be monthly. On the item record you can add an expected demand change, a percentage that adjusts the forecast, and it applies only to the seasonal average method. Plans can also be edited by hand where you know a peak will move.
How do I forecast a new item with no sales history?
Set an alternate source item on the new item’s record, so NetSuite uses another item’s history. Oracle requires the alternate to be the same item type, and the expected demand change for the new item is still applied. The item must be set to the Time Phased replenishment method, because alternate source item is not available on reorder point items.
Can I import existing demand data into NetSuite?
Yes. Oracle documents an Item Demand Plan import through the CSV Import Assistant. Each file covers one period type, monthly, weekly or daily, and each plan identifies the item, start and end dates, and the location or subsidiary where those apply. Demand plans can only be created for items set to Time Phased, so set the replenishment method before you import.
What does NetSuite demand planning require, and does it cost extra?
Oracle states that Advanced Inventory Management must be enabled, and that assembly and bill of materials items need Work Orders as well. Which features and modules are included in your subscription, and what they cost, is a question for your NetSuite account team. Confirm it before you scope the project.
Can I change a calculated demand plan by hand?
Yes. When you edit a plan, you can enter a new number in the Quantity field for each line or interval, while the calculated column stays as a reference. Only the custom form, unit of measure and memo header fields can be edited, so the projection method and dates stay as calculated. Review manual edits when the plan is recalculated.
About the author
Louis Balla is Chief Revenue Officer at Nuage, a NetSuite optimization partner that has served 250+ clients since 2011 and holds a 4.9 out of 5 rating on Clutch. The client work in this article is our team’s.
