Optimizing Production Scheduling in Business Central: Balancing Make-to-Order and Make-to-Stock for Manufacturing Agility

Manufacturing leaders in mid-market organizations face a recurring operational tension: how to balance customer responsiveness against inventory costs. When demand spikes, rigid production schedules create backlog and missed ship dates. When demand softens, safety stock accumulates, tying up working capital and consuming warehouse space. For finance leaders overseeing manufacturing operations, the cost of poor production planning compounds quickly—expedited component purchases, rushed production runs, excess finished goods inventory, and the operational overhead of expediting orders and managing exceptions.

Business Central provides production planning and scheduling capabilities that mid-market manufacturers can configure to match their specific production model, whether they operate primarily as make-to-order, make-to-stock, or hybrid operations. The question for most organizations is not whether Business Central can handle production planning, but how to configure and govern it effectively so that production schedules reflect actual demand, component availability, and capacity constraints rather than being overridden by ad-hoc changes and manual workarounds.

The Production Planning Architecture in Business Central

Business Central’s production module is organized around a few core concepts: production orders, bill of materials, routings, and component availability. A production order in Business Central represents a formal directive to manufacture a quantity of a finished good. That order can be generated automatically through demand forecasting and the Master Production Schedule, or created manually in response to a sales order or customer request. Either way, once a production order is released, Business Central explodes the bill of materials to calculate component requirements, cross-references routing data to establish labor and machine requirements, and reserves raw materials and subcomponents from inventory or creates purchase requisitions for items on order.

The routing data is critical to realistic production scheduling. A routing specifies which work centers or machines a production order must flow through, the sequence of operations, and the expected run time per unit plus setup time per lot. Business Central uses this routing information to calculate earliest completion dates, identify bottlenecks, and allocate capacity. Without accurate routing data, production schedules become disconnected from actual manufacturing constraints, leading to unrealistic promised dates and planner surprises when orders cannot be completed on time.

Make-to-Order Versus Make-to-Stock Configuration

The choice between make-to-order and make-to-stock production strategies profoundly affects both production planning and component purchasing. In make-to-order mode, Business Central creates production orders and purchase requisitions only in response to actual sales orders, minimizing work-in-process and finished goods inventory but requiring longer lead times to customers. In make-to-stock mode, Business Central generates production orders based on demand forecasts and inventory targets, allowing shorter delivery times to customers but requiring accurate demand forecasting and active inventory management to avoid overstock.

Most mid-market manufacturers operate a hybrid: high-volume standard products are made to stock, while low-volume or highly customizable products are made to order. Business Central supports this hybrid approach through item-level configuration. Each finished good item can be designated as make-to-order or make-to-stock, and the planning system respects these designations. However, hybrid operations introduce complexity: demand planners must maintain accurate sales forecasts for make-to-stock items, while order entry and sales teams must correctly route new customer requests to the appropriate production model rather than, for example, creating purchase orders for items that should be manufactured.

Demand Forecasting and the Master Production Schedule

Production planning begins with demand. In make-to-stock operations, Business Central generates production orders based on a combination of actual sales orders, statistical demand forecasts, and safety stock targets configured at the item level. This process, driven by the Master Production Schedule and regenerative planning, calculates net requirements for each finished good (current inventory plus open sales orders minus forecast demand equals required production quantity), then explodes those into component requirements.

The accuracy of the Master Production Schedule depends directly on the accuracy of the demand forecast. If forecasts are consistently too high, production orders generate excess inventory and cash flow is consumed by finished goods sitting in the warehouse. If forecasts are too low, production orders are insufficient to meet demand, sales orders are delayed, and the organization reverts to expediting (expensive) production runs to cover the shortage. For finance organizations, this is a working capital and operational efficiency problem: inaccurate forecasts translate directly into excess inventory days outstanding and emergency procurement costs.

Business Central’s demand forecasting is relatively basic: it calculates moving averages, exponential smoothing, or linear trends based on historical sales patterns, and allows manual adjustments by demand planners. For organizations requiring more sophisticated forecasting (factoring in seasonality, promotional calendars, or external signals such as economic indicators), the integration of Power Platform tools and externally generated forecasts is necessary. A common implementation pattern is to import external forecasts (from advanced statistical forecasting tools or AI-driven models) into Business Central as the basis for the Master Production Schedule, rather than relying on Business Central’s built-in forecasting alone.

Component Availability and Production Schedule Feasibility

Once a production order is generated and its bill of materials is exploded, Business Central must verify that required components are available in inventory or on order. The planning system calculates component requirements based on the production order’s start and completion dates, accounting for lead times. If a critical component is not available when needed, the production order cannot complete on time. This is where detailed lead time management becomes essential: if component lead times are incorrect in Business Central, production schedules are unrealistic and delivery commitments are missed.

In practice, many manufacturers discover that their component lead times in Business Central drift over time and no longer reflect supplier performance. A component that once arrived in two weeks now takes six weeks, but the lead time in the system was never updated. The result is that the Master Production Schedule calculates overly optimistic completion dates, and planners face repeated surprises when components arrive late and production orders cannot be completed as promised.

Governance and Execution

Effective production planning in Business Central requires discipline in a few operational areas. First, the bill of materials and routings must be maintained accurately and kept current. If the BOM is incorrect, component requirements are miscalculated, and either the wrong components are ordered or components run out unexpectedly. Second, lead times for components and subcontractors must be actively monitored and updated quarterly at minimum, particularly for suppliers or products subject to market volatility. Third, the demand forecast must be reviewed monthly, and actuals must be compared to forecast to assess accuracy and adjust the forecast model if needed. Fourth, safety stock targets and reorder points must reflect actual demand volatility and the organization’s service level objectives (how often is it acceptable for an item to be out of stock?), not arbitrary percentages carried over from years past.

The most successful mid-market manufacturers implement a formal monthly production planning cycle: demand planners review the upcoming twelve-month forecast, validate it against current sales pipeline and marketing calendar, production planners review production orders and identify bottlenecks or component constraints, purchasing updates lead times and flags any long-lead items that need early action, and finance reviews the projected inventory position and flags concerns about excess stock. This cadence ensures that production schedules remain realistic and aligned with actual business conditions.

Next Steps for Finance and Operations Leaders

If your organization manufactures products in Business Central, start with an audit of lead times: pull the component lead time report and compare it to current supplier performance. Identify any outliers or items with lead times more than 20 percent off actual experience. Update those lead times and re-run the Master Production Schedule to see how much the planned completion dates shift. Second, review the demand forecast accuracy for your top 20 percent of products by volume: calculate the forecast error (actual demand minus forecast) and assess whether the forecast is systematically high or low. If accuracy is consistently poor, consider importing external forecasts or implementing statistical forecasting tools. Third, establish a monthly production planning and review rhythm, and ensure the meeting includes demand planning, production, procurement, and finance so issues are surfaced and addressed collaboratively rather than becoming bottlenecks discovered too late.

Production planning in Business Central is not a set-it-and-forget-it capability; it requires ongoing governance and attention to data quality. Organizations that maintain disciplined forecasting, accurate lead times, and realistic safety stock levels find that Business Central’s production scheduling delivers genuine operational benefits: shorter lead times to customers, lower inventory days outstanding, fewer emergency procurement events, and more predictable delivery performance. For finance leaders, this translates to improved working capital, reduced expediting costs, and better cash flow forecasting.

#BusinessCentralManufacturing #ProductionPlanning #MakeTOStock #InventoryOptimization #DynamicsERP #SupplyChainPlanning

Building Demand Forecasting Intelligence in Dynamics 365 Supply Chain Management: Integrating AI Builder Predictive Models with Historical Data for Accuracy and Cost Reduction

Building Demand Forecasting Intelligence in Dynamics 365 Supply Chain Management: Integrating AI Builder Predictive Models with Historical Data for Accuracy and Cost Reduction

Most supply chain teams operate on reactive forecasting. Demand planners pour through months of historical sales data, adjust for seasonality using spreadsheet logic, and send forecasts to procurement and manufacturing with the knowledge that 20 to 30 percent will miss by more than ten percent. When demand runs higher than forecast, stockouts ripple through fulfillment. When demand falls short, inventory sits as dead stock and cash ties up in warehouses.

The problem isn’t the people doing the forecasting. It’s the tools. Manual forecast methods plateau at a certain accuracy ceiling because they cannot account for the full complexity of relationships in historical data, and they cannot incorporate real-time signals from customer behavior, marketing campaigns, or supply disruptions as those signals arrive. By the time a planner notices a trend and adjusts the forecast, the cycle is already three weeks old.

Dynamics 365 Supply Chain Management paired with AI Builder’s predictive capabilities offers a path to higher forecast accuracy without rebuilding your entire planning process. The approach is to integrate AI-driven demand models into your existing planning workflow, using historical transaction data from Dynamics 365, external signals from Power Platform connectors, and iterative model refinement based on actual outcomes. This differs fundamentally from bolting on a separate forecasting tool. The predictions live inside Dynamics 365, flow directly into MRP and procurement workflows, and improve continuously as new transactions arrive.

How Predictive Models Change the Demand Planning Conversation

Demand forecasting in a traditional ERP context treats the forecast as a static monthly or weekly snapshot. Planners pull data as of a specific date, run a calculation, and submit the result. Thirty days later, they start over with a new snapshot. Changes in the forecast require manual reforecasting, which itself takes days or weeks depending on review cycle length.

AI-driven models operate differently. They identify patterns in historical data that human review would struggle to spot, particularly patterns involving multiple interacting variables. For instance, a model trained on two years of transactions might discover that demand for a product correlates not just with the previous month’s sales, but with a specific customer segment’s purchasing velocity, the day of the week orders arrive, promotional calendar markers from your marketing team, and supplier lead time variability. No spreadsheet naturally captures all four of these relationships simultaneously.

The second difference is recency. Once a model is trained and deployed into Dynamics 365, it can retrain continuously as new data arrives. New customer orders in March change the statistical weight of seasonal factors for April. A new supplier agreement changes the model’s understanding of lead-time risk. The model incorporates signal from these events automatically rather than waiting for the next manual reforecast cycle.

The Integration Architecture

An effective demand forecasting system in Dynamics 365 consists of four layers: data preparation, model training, prediction serving, and feedback integration.

Data preparation pulls historical sales transactions, customer attributes, product characteristics, and external signals into a consistent format. For Dynamics 365, this typically means extracting data from Dynamics tables (sales order history, customer master, product master, inventory transactions) and supplementing with external sources via Power Platform connectors (marketing campaign calendars from SharePoint, promotional events, supplier reliability scores from external systems, weather data if weather-sensitive). The preparation step also handles missing values, outlier detection, and feature engineering. A feature engineer might create derived columns such as “days since last customer purchase,” “product seasonality index,” or “forecast error from previous cycle,” which give the model richer input signals than raw transaction history alone.

Model training uses AI Builder’s predictive capabilities to build regression or time-series models that predict future demand based on the prepared features. Rather than writing code, you define the model through the AI Builder wizard by selecting input columns and the target column (historical demand volume). AI Builder handles train-test-split, hyperparameter tuning, and model validation. For supply chain, common model types are time-series forecasting (when you care about sequential patterns over time) or regression (when you’re predicting demand for a specific product-customer combination).

Prediction serving embeds the trained model into Dynamics 365 workflows and Power Automate flows, so forecasts are generated on-demand or on schedule. For example, you might configure a Power Automate flow that runs nightly, calls the AI Builder model for each product-customer combination, and writes the resulting forecast into a custom table in Dataverse. Those forecasts then feed directly into the MRP algorithm, procurement workflows, and safety stock calculations without manual intervention.

Feedback integration closes the loop by comparing actual demand (captured from sales orders) to forecast values, measuring accuracy, and flagging model drift. When accuracy drops below a threshold, the model is retrained with the latest data. This feedback loop is critical. A model trained on data from 2024 will degrade in predictive power by mid-2025 if customer behavior shifts, new product launches change the demand mix, or market conditions change. Continuous retraining keeps the model anchored to current reality.

Building the System: A Phased Approach

Phase 1: Foundation (Weeks 1-4)

Define forecast granularity: are you forecasting by product, product-customer, or product-location? Finer granularity requires more training data but offers more actionable predictions. Most teams start at product or product-location level because customer-level forecasts require sufficient transaction history per customer to be statistically reliable.

Extract two years of historical sales transactions from Dynamics 365. If your data is older than two years or contains structural breaks (major product discontinuations, customer wins or losses that shift volume), the older data may confuse the model more than help. Two years of clean, stable history is usually optimal starting point.

Prepare the data: clean missing values, remove anomalous transactions, create seasonal and trend features. Document data quality issues discovered during this phase, because they’ll inform model accuracy expectations. If your historical data has significant gaps or inconsistencies, the model’s predictions will inherit that uncertainty.

Phase 2: Model Development and Testing (Weeks 5-8)

Train an initial AI Builder model using the prepared data. Start simple: predict monthly product demand using sales history, seasonality, and trend. Measure model accuracy using mean absolute percentage error (MAPE) or similar metric on a test set held back from training.

At this stage, expect MAPE in the 15-25 percent range for most B2B supply chains. This is better than many manual forecasts, but not excellent. The model is baseline.

Phase 3: Feature Expansion and Iterative Improvement (Weeks 9-12)

Introduce external signals: marketing campaign calendar, holiday calendars, supplier lead time changes, customer segmentation. Retrain the model with these additional features. Often, MAPE improves to 10-18 percent range as the model learns that certain products spike around promotional events or that specific customer segments follow different seasonal patterns than others.

This phase is iterative. Test different feature combinations, measure their impact on model accuracy, and retain features that improve generalization to new data (not just training accuracy).

Phase 4: Operationalization (Weeks 13-16)

Build Power Automate flows that call the trained model on a schedule (daily or weekly) and write predictions into a forecast table in Dataverse. Connect that forecast table to your MRP algorithm, procurement approval workflows, and safety stock calculations.

Create dashboards in Power BI that show forecast accuracy over time, broken down by product category or customer segment. This surfaces model drift early and guides retraining decisions.

Run the system in parallel with your existing forecast process for 4-8 weeks. Measure whether AI-driven forecasts outperform the previous method on unseen data. If accuracy is demonstrably better, transition to AI-driven forecasts as primary. If not, investigate why: common reasons include data quality issues, inappropriate feature selection, or a mismatch between forecast granularity and demand volatility.

Practical Considerations and Common Pitfalls

Data quality is foundational. If your historical sales data conflates cancellations, returns, and adjustments with actual demand, the model learns from noisy signals. Clean this before model training. Separate true demand from inventory adjustments and reverse transactions.

Seasonality must be explicit. Demand for swimming pools peaks in spring and summer; demand for holiday decorations peaks in October. If the model sees only two years of data, it may not capture these seasonal patterns reliably. Consider augmenting training data with external industry benchmarks or promotional calendar features to help the model learn seasonality even from limited historical windows.

Forecast accuracy degrades without feedback. The model is only as good as the data it was trained on. As your business changes (new customers, new products, market shifts), retrain monthly or quarterly. This is not a set-and-forget system.

Start with products that have stable demand. If a product’s demand varies wildly based on external events you cannot predict (e.g., government spending decisions, competitor actions), forecasting it will be difficult even with an AI model. Begin with products that have predictable demand patterns, validate the system there, and expand gradually.

Avoid overfitting during development. A model that achieves 5 percent MAPE on historical training data but 25 percent MAPE on future data is worthless. Use a held-back test set during model development to ensure the model generalizes. AI Builder handles this, but understanding the concept helps you interpret results.

Expected Impact and ROI

Organizations implementing demand forecasting typically see three categories of benefit.

Accuracy: Forecast error typically falls from 25-35 percent to 12-18 percent MAPE. For a 100-product portfolio with 10,000 units monthly demand and 30 percent average order value, improving forecast error from 30 percent to 15 percent reduces unintended stockouts by 50 percent and decreases safety stock holding by 20-30 percent. Carrying cost savings alone can reach 5 to 15K annually for mid-market organizations.

Responsiveness: When forecasts update daily rather than monthly, your supply chain responds faster to real demand signals. Lead time variability shrinks because you’re ordering based on more current expectations. Customer fulfillment improves because stockouts drop.

Cost: Better forecasts reduce emergency freight and expedited purchases caused by stock-outs. For organizations spending 500K to 2M annually on procurement, a 5-10 percent reduction in emergency purchases equals 25K to 200K in savings. Implementation cost (40-80K consulting plus ongoing model maintenance) pays back within 6-12 months for most mid-market supply chains.

Next Steps

Begin by auditing two years of historical demand in your top 30 percent of products by revenue. Assess data quality. Engage your forecasting team to identify which external signals they believe drive demand in your business. Work with technical resources to extract and prepare that data. Then run a proof of concept on a single product line before full deployment.

Predictive demand forecasting is not exotic anymore. It is a practical capability now available to any Dynamics 365 customer with historical data and the discipline to maintain model quality. Organizations that implement it gain a structural advantage: better forecast accuracy without needing larger planning teams, and the ability to respond to demand signals in weeks rather than months. The tools are ready. The question is whether your supply chain will use them.

#DemandForecasting #DynamicsSCM #AIBuilder #SupplyChainIntelligence #PredictiveAnalytics #D365SupplyChain #ProcurementOptimization

License Optimization and Cost Control: Right-sizing Your Dynamics 365 Seats

Most enterprise IT directors face the same challenge in their second or third year of a Dynamics 365 deployment: the licensing bill arrived larger than expected, and it continues to grow. Every new user seems to require a full seat. Contractors and temporary staff get assigned permanent licenses. Entire departments hold licenses they never actively use. By year three, many organizations spend 2 to 3 times what they budgeted for user seats alone. The problem is not that Dynamics 365 is expensive. It is that most organizations have no visibility into who actually needs what type of access, and licenses proliferate without governance.

Dynamics 365 licensing offers genuine flexibility. It provides multiple access tiers that cost substantially less than full user seats, yet many organizations pay for unlimited access for users who need only read-only report access or occasional data entry. This is not a product limitation. It is a governance problem with a direct financial solution.

## Understanding the Licensing Landscape

Dynamics 365 charges for user access through several distinct license types, each designed for different roles. Full user seats cost between 100 and 200 dollars per month per person and grant full read, write, create, and delete capabilities across the assigned module. Limited user seats cost 40 to 60 dollars per month and provide meaningful but restricted capabilities: users can view, create, and update records within defined scope but typically cannot configure systems or access advanced features. Read-only access through community licenses might cost 5 to 10 dollars per month or be free. Many organizations hand out full seats to business intelligence analysts, auditors, and executives who need only dashboard access, immediately wasting 30 percent of their licensing investment.

Most organizations pay for module licensing beyond user seats. Finance and Operations, Customer Service, and Power Platform each add separate line items. Many organizations pay for licenses they do not actively use across their entire user base because the license allocation model never gets revisited after initial deployment.

## The Hidden Cost of Inertia

Once a user is created in Dynamics 365, that license seat stays active indefinitely. Contractors finish projects and remain licensed. Departments restructure and roles change, but seat allocations remain static. Sales organizations with seasonal hiring keep temporary employees licensed year-round even though they are active only during peak season. Finance departments maintain full-user seats for recently promoted employees who now spend 80 percent of their time in Excel rather than in the system.

For a 500-person organization, this inertia typically means 10 to 15 percent of active user seats are either under-utilized or completely unused. At 150 dollars per month per seat, that represents 75,000 to 112,500 dollars annually that generates zero business value. For a 1,000-person organization, the number climbs toward 180,000 to 270,000 dollars per year. Beyond direct license waste, each idle seat requires identity management, security reviews, and compliance overhead. Organizations that do not regularly audit licensing pay not just the licensing cost but also the indirect cost of managing orphaned accounts.

## Implementing License Optimization

The starting point is visibility. Most organizations cannot answer basic questions: How many full seats are actually in use? Who holds a license but has not logged in for 90 days? Which departments are over-seated? Begin with a data-driven audit of your Dynamics 365 instance. Extract login history for every active user over the past 60 to 90 days. The goal is not to penalize occasional users but to identify inactivity patterns and role misalignment. Users with no logins in 90 days are candidates for license removal. Users with very infrequent logins (fewer than five per month) might be candidates for limited-access licenses.

In parallel, audit actual business functions. Schedule interviews with department managers. Ask specific questions: What does this role do in Dynamics 365 weekly? Do they create or update data, or primarily read dashboards? Do they need all modules or just one? Are there seasonal variations? This qualitative data, combined with login history, reveals which users are correctly licensed and which represent optimization opportunities.

Create a role-based licensing matrix: Which roles need full user seats? Which can operate effectively on limited licenses? Which should use read-only access? This matrix becomes your governance policy. As you hire, the policy dictates the appropriate license type rather than defaulting every new user to a full seat.

For many organizations, the biggest opportunity lies in consolidating reporting access. Executives, business intelligence teams, controllers, and compliance officers rarely need to create or modify data. They need to read dashboards and run reports. A read-only license costs one-tenth of a full seat. Many organizations license these roles as full users simply out of habit. Moving 50 or 100 reporting-only users to read-only access often pays for the entire optimization project in the first month.

Temporary and contractor access presents another opportunity. Rather than assigning permanent licenses, implement temporary assignments tied to contract end dates. Work with finance and HR to establish a calendar-based license review process. This requires minimal administration but typically prevents the accumulation of 20 to 40 permanently-licensed former contractors within three years.

## Building Sustainable Governance

License optimization is not a one-time project. Establish a quarterly license review cycle. Generate a report of all active licenses, login history, department assignment, and license type. Review with each department leader. Adjust allocations based on hiring, reorganizations, and role evolution. This quarterly cadence requires roughly 20 to 40 hours of IT time per quarter but prevents the cost drift that claims thousands of dollars annually.

Implement approval gates for new license requests. Rather than automatically provisioning licenses, establish a process where the hiring manager specifies the required access level, the reason, and expected duration. Most hiring managers, when asked explicitly, accurately assess their new employee’s actual needs. Connect licensing decisions to your broader identity governance. If a user is deprovisioned from Azure AD due to termination or role change, their Dynamics 365 licenses should be deactivated automatically or flagged for review. Many organizations maintain separate processes for AD and Dynamics 365, leaving orphaned licenses behind.

## Measuring Impact

Right-sizing typically reduces per-user licensing costs 25 to 40 percent for organizations that have never optimized. A 500-person organization with 250 active Dynamics 365 users, currently spending 37,500 dollars monthly, can typically reduce that to 22,500 to 28,000 dollars monthly. A 1,000-person organization with 600 active users spending 90,000 monthly can reduce to 54,000 to 67,500 monthly. Across three years, these savings compound to 500,000 to 1.4 million dollars.

Beyond direct cost reduction, optimized governance improves security posture and compliance. Your organization maintains fewer orphaned accounts. Identity management becomes cleaner. Access reviews become faster because you have clear role-based policies. Your IT team spends less time managing user accounts and more time on strategic work.

## Next Steps

If your organization has never formally reviewed Dynamics 365 licensing, start now. Engage your CFO and business unit leaders in a conversation about whether every licensed user actively needs full access. Extract login history from Dynamics 365. Develop a role-based licensing matrix. Begin with a pilot reallocation of 25 to 50 users across read-only and limited-access tiers, measure the impact, and expand from there.

License optimization is not about restricting access. It is about ensuring that every person holds the specific level of access their role requires, nothing more and nothing less. For most organizations, that discipline delivers meaningful cost savings within the first quarter, with minimal disruption and clear business value.

#DynamicsLicensing #CostOptimization #D365Governance #EnterpriseIT #LicenseManagement #DigitalTransformation #CloudCostControl #DynamicsImplementation