NetSuite Demand Planning is the module that turns sales history or a sales forecast into a projection of what you will need, nets that against what you have and what is already on order, and proposes the purchase orders, work orders, and transfer orders to cover the gap. It replaces the reorder-point spreadsheet that most growing product businesses run alongside their ERP. This guide explains how it works, how to set it up, where its limits are, and what manufacturers in particular need alongside it.
What NetSuite Demand Planning does
The module works in two stages. First it builds an item demand plan: a time-phased forecast of demand for each planned item, by location, over a horizon you choose. Then it builds an item supply plan: the orders needed to meet that demand, allowing for current stock, open purchase and work orders, safety stock, and lead times. The supply plan generates order proposals that a planner reviews and releases as real transactions.
Demand can come from four methods. Linear regression fits a trend to historical sales and extends it. Moving average smooths recent history. Seasonal average uses the same period in prior years, which suits businesses with a strong annual cycle. Sales forecast takes expected demand from opportunities and quotes in NetSuite CRM rather than history, which suits new products and project-driven businesses. You choose the method per item and can adjust the resulting plan line by line.
Setting it up
- Enable the feature. Setup → Company → Enable Features → Items & Inventory → Demand Planning. It requires the Multi-Location Inventory feature.
- Configure planning on each item. On the item record’s Purchasing/Inventory subtab: supply type (build or buy), lead time, safety stock, lot sizing method (lot for lot, fixed order quantity, or periods of supply), and the demand source and forecast method.
- Set the planning horizon and time bucket. Weekly buckets over three to six months is the common starting point; monthly buckets suit long-lead purchased items.
- Generate item demand plans. Lists → Supply Chain → Item Demand Plans → Generate. Review the projection and override lines where you know something the history does not, such as a promotion or a lost customer.
- Generate item supply plans and review the order proposals on the Order Items page before releasing them.
- Schedule the regeneration. Once the setup is stable, run demand and supply plan generation on a schedule so planners work from a current plan rather than rebuilding it.
Getting the inputs right
Demand Planning is only as good as three inputs. Sales history has to be clean: returns, samples, intercompany transfers, and one-off bulk orders distort the projection and should be excluded or adjusted. Lead times on item records are often wrong, either never set or set at go-live and untouched since; a supply plan built on a two-week lead time for a ten-week item proposes orders that arrive late. Safety stock should reflect variability, not a round number. Reviewing these three across the planned item list is usually where an optimization delivers the most.
Where Demand Planning stops
The module plans at the item level against demand and lead time. It does not do several things a growing operation eventually needs.
- Capacity. It will propose work orders without knowing whether the work centers, vessels, or people have hours to run them.
- Constraints between items. A shared component, a shared line, or a changeover cost between products is invisible to it.
- Multi-level netting across locations. It plans each location independently; it does not optimize which plant supplies which warehouse.
- Formula-driven demand. For batch and process manufacturers, demand for ingredients depends on yield and batch size, which the item-level plan does not model.
What manufacturers need alongside it
For a distributor, Demand Planning plus a well-maintained item master is often enough. For a manufacturer the gap is capacity. The supply plan says what to make and when; it cannot say whether the plant can. That is where scheduling comes in. FactorySync takes the released work orders and places them on a finite schedule against work-center capacity, so the plan the module produces becomes a plan the floor can actually run. For formula and batch producers, ProShop scales recipes to real batch sizes and records actual yield, which feeds cleaner history back into the next demand plan. Both run natively inside NetSuite.
The pattern we see most often in manufacturing and wholesale distribution accounts is that Demand Planning was licensed, half-configured, and abandoned because the first plan looked wrong. It looked wrong because the inputs were wrong. Fixing lead times, cleaning history, and setting methods per item family turns it into the tool it was bought to be.
Frequently asked questions
Is Demand Planning included in NetSuite?
It is a licensed module, not part of the base subscription. It is included in some industry editions and available as an add-on to others. Check your license before planning around it, and if you are paying for it and not using it, configuring it is one of the highest-return items in a NetSuite optimization.
What forecasting methods does NetSuite Demand Planning use?
Four: linear regression, moving average, seasonal average, and a sales-forecast method that uses opportunity and quote data from NetSuite CRM. You choose the method per item and can override the generated plan by hand.
Does NetSuite Demand Planning consider production capacity?
No. It plans supply against demand and lead time at the item level. It does not know whether your work centers or vessels have the hours to build what it proposes. Capacity is handled separately, natively at a basic level or with a scheduling tool such as FactorySync.
How is Demand Planning different from reorder points?
Reorder points trigger a purchase when stock falls below a fixed level. Demand Planning projects future demand from history or forecasts, nets it against stock and open orders, and proposes time-phased supply. Reorder points suit stable, fast-moving items; Demand Planning suits seasonal, growing, or long-lead items.
Paying for Demand Planning and not getting value from it? That is a common finding in a NetSuite optimization. Talk to Consule about getting it running, or read the guide to NetSuite optimization for the wider picture.