Demand Planning Without a Crystal Ball: What Business Central Does Natively vs. What You Have to Add

Your planners are working in spreadsheets. Purchasing is carrying too much of one item and running out of another. Sales says the forecast is wrong. Operations wants demand-planning software.

Before you buy another system, look at what is already sitting inside Business Central.

Business Central has a real supply-planning engine. It can use forecasts, sales demand, inventory, purchase orders, production requirements, lead times, safety stock and item-level replenishment settings to calculate what you should buy, make or transfer and when.

What it does not give you is a sophisticated statistical forecasting platform that studies historical patterns, promotions and external signals and tells you what next quarter’s demand is likely to be.

Those are two different jobs.

Getting Business Central demand planning and forecasting right starts with knowing which one you are actually trying to fix.

The tool you are shopping for may already be installed

Business Central’s planning functionality is more capable than many organizations use.

Its planning engine balances demand and supply using a gross-to-net calculation. Demand can include sales orders, service orders, production and assembly component requirements, transfers, blanket orders and forecasts. Supply can include inventory, purchase orders, production orders, assembly orders and inbound transfers.

Run the planning calculation and Business Central can generate action messages telling you to create, change, reschedule or cancel supply.

That is not just a reorder-point calculation.

Business Central can plan by stock-keeping unit, meaning the same item can have different planning parameters by location and variant.

If purchasing is currently deciding what to order from an Excel export every Monday morning, do not assume you need another planning application.

First determine whether Business Central’s existing planning engine has ever been configured properly.

Often, that is the unfinished project.

What the planning engine genuinely does well

Business Central is good at translating known and anticipated demand into supply recommendations.

That distinction matters.

It knows you have 60 units on hand, 100 on an open purchase order, 40 committed to sales orders and additional forecast demand coming. It can calculate net requirements and suggest supply based on the planning rules configured for that item or SKU.

For manufacturers, the planning engine can also work through bills of material and production requirements. For distributors, it can recommend purchasing and transfers.

It can respond when demand changes too.

If supply already exists, Business Central can recommend that you increase, decrease, expedite, postpone or cancel it rather than blindly creating another order.

That is useful planning.

Where people get disappointed is forecasting.

Business Central planning can answer: “Given the demand we expect, what supply do we need?” It is not designed to answer: “Based on everything we know about historical demand and future conditions, what demand should we expect?”

Reordering policies: choose per item profile, not per company

Business Central supports four primary reordering policies:

• Fixed Reorder Qty. Replenishes inventory using a specified reorder quantity when projected availability reaches the reorder point.
• Maximum Qty. Works toward a defined maximum inventory level when replenishment is triggered.
• Order. Creates a supply order for each demand, which suits items bought or made specifically for customer orders.
• Lot-for-Lot. Groups net requirements within the planning horizon and can use a lot accumulation period to combine multiple needs into one supply order.

The planning parameters associated with them determine how the system reacts to demand. They exist because inventory behaves differently. The point is not to pick the “best” policy. There isn’t one.

A fast-moving stocked component should not automatically use the same planning logic as an expensive item bought specifically for customer orders. And the same item does not necessarily need identical rules everywhere.

Business Central SKUs allow planning parameters to be set for combinations of item, location and variant. Use them. The warehouse carrying your primary stock and a satellite location with occasional demand are different inventory problems. Configure them that way.

Where native planning breaks down

Business Central starts reaching its limit when the problem shifts from supply planning to sophisticated demand prediction. You can enter forecasts and use them in planning.

Business Central does not natively provide the same forecasting environment Microsoft provides in Dynamics 365 Supply Chain Management Demand Planning. That product can ingest historical data, transform it into time series, generate statistical forecasts, let planners review and adjust them and then export the resulting forecast for execution.

Its current forecasting options include Auto-ARIMA, ETS, Prophet and XGBoost, plus a best-fit model that can automatically select an appropriate algorithm for a product and dimension combination. Custom Azure Machine Learning algorithms can also be used.

That is a different category of planning. If you need to model seasonality, evaluate different statistical forecasting approaches or incorporate additional external signals, Business Central’s native functionality is not equivalent. Do not spend months customizing it until it looks like a demand-planning platform.

Buy or build the forecasting layer you actually need.

What Dynamics 365 Supply Chain Management adds (in plain terms)

Dynamics 365 Supply Chain Management goes further because demand planning is a dedicated capability rather than primarily an input into replenishment.

Planners can incorporate factors such as pricing, weather and promotional events when reviewing demand. The system also supports customizable worksheets and exception-based planning. Forecasting models can handle different demand patterns, including trends and seasonality, and XGBoost can use multiple inputs.

Supply Chain Management also has Planning Optimization for supply planning. Microsoft describes it as supporting rapid planning calculations so organizations can react to requirement changes without relying solely on a traditional overnight planning run.

But our recommendation is not to move from Business Central to Supply Chain Management just because an executive wants a better forecast. If forecasting is one of several signs the platform no longer fits, read seven signals you’ve outgrown Business Central first.

The ISV middle ground

There is a large gap between “use Business Central exactly as it comes” and “replace Business Central with Dynamics 365 Supply Chain Management.” That gap is where independent software vendor, or ISV, planning applications fit.

A specialized forecasting or inventory-planning application can sit alongside Business Central, use Business Central’s historical and operational data, generate forecasts or replenishment recommendations and return useful planning information without replacing the ERP.

However, if the application mostly recreates Business Central’s planning worksheet with a nicer interface, configure Business Central first. A relatively inexpensive planning application can become expensive if you spend years maintaining custom integrations around it.

Diagnostic: data problem or tooling problem

Before changing software, inspect the inputs going into the plan. Start with lead times. Then check reorder points, safety stock, order multiples, minimum and maximum quantities, item locations, SKUs, units of measure, calendars and current inventory.

Review the demand forecast itself. Then look at open purchase, sales, production and transfer orders.

Business Central’s planning engine depends on these inputs. Microsoft describes the Planning FastTab on the Item Card as central to supply-chain planning and specifically emphasizes correct planning parameters for inventory control and customer service.

If vendor lead time is configured as two weeks when it routinely takes eight, another planning system will not fix the underlying problem. Only after the inputs are credible should you decide whether the remaining gap is tooling. Otherwise, you can spend a considerable amount of money giving a more sophisticated planning engine the same bad data.

How a trusted partner can guide you

Do not start a demand-planning project by shopping for demand-planning software. Start with 20 to 30 representative items. Choose fast movers, slow movers, seasonal items, expensive inventory, make-to-order products and the items that repeatedly stock out.

For each one, document actual demand behaviour, lead time, current planning parameters, reordering policy and how the purchasing or production decision is made today.

Then run Business Central planning against them. You will know fairly quickly whether you have a configuration problem, a forecasting problem or a planning-platform problem.

Qixas Group works across Business Central, Dynamics 365 Supply Chain Management and the surrounding Microsoft data platform. We also spend a lot of time fixing implementations where more software was added before anyone established what the existing system could already do.