The agentic planner Business Central was missing

Business Central gives you a forecast page, a Planning Worksheet, and a Requisition Worksheet. None of them decide what to order, when to rebalance, or which transfer to push. That judgment work still lives with your planner. Isovel is the planner Business Central is missing: the agentic AI layer that decides, then writes draft purchase orders and transfer orders back into BC for you to approve. Connect in one click. Watch it work in shadow mode for thirty days. Then approve the recommendations. Graduate the agent’s autonomy as your planner gets comfortable with its track record.

Phase 1   Pre-launch waitlist. One-click install. AppSource listing coming soon. $999/month or $10,000/year (12-month commitment, ~17% discount). Fair-use limits apply for high-volume tenants.

What Business Central gives you today

Business Central ships a complete planning surface. The Item card carries reorder points, safety stock, and lead-time fields. The Sales and Inventory Forecast extension wraps Azure AI on top of your sales history to produce a forecast. ^[4] The Planning Worksheet and Requisition Worksheet read that forecast plus on-hand inventory and turn it into action messages. Microsoft Copilot for BC, available in BC 24 and forward, explains what the system suggests and accelerates routine BC tasks.

That stack is the foundation. It is the data model and the integration points the rest of this page builds on. Isovel does not replace Business Central; it plugs into the entry points Microsoft itself documents, including the external-engine connection point in the Sales and Inventory Forecast Setup, which lets BC’s forecast page point at any external engine you nominate. ^[5]

The honest question is what BC’s planning surface does and does not decide for you on a Monday morning.

What it doesn’t decide for you

Six concrete gaps surface across BC operator discussions and Microsoft’s own documentation. They are the reason your planner still keeps a parallel Excel and a Power BI dashboard open next to the Planning Worksheet.

The Planning Worksheet generates noise at the SKU level you don’t run. A BC operator on r/MSDyn365BC in 2026 described the output verbatim: “thousands of emergency action messages for items we have never and will never use.” ^[6] They replaced the Planning Worksheet with an Excel MRP-helper file and a Power BI projected-inventory report that became “the most used report in the organization.” They were not unusual.

Item-card edits don’t back-propagate to existing Stockkeeping Units. BC’s SKU table is intentionally the per-location override layer. SKUs inherit from the Item card at creation, then diverge by design. The practical surprise: a planner who sets safety stock at the Item level later, expecting it to flow through, finds existing SKUs untouched. A community.dynamics.com BC planner captured the moment of discovery verbatim: “those setups are not replicated in the SKUs.” ^[7] The platform behavior is documented; the planner-experience friction is real.

The Sales and Inventory Forecast extension produces an aggregated forecast across all locations. Microsoft’s own documentation states the extension “produces aggregated forecast for all locations” and the planner “must distribute amounts afterwards.” ^[4] A multi-warehouse BC distributor gets one number per SKU and has to re-allocate it by hand.

Azure AI refuses to forecast sparse or volatile items. Microsoft’s documentation again: the underlying forecasting engine “won’t make a prediction” when an item has fewer than five historical periods or when variance exceeds the documented threshold. ^[4] Slow-movers and new items return no forecast. Most BC distributors have a long tail of both.

Microsoft Copilot for BC explains, it doesn’t decide. Microsoft’s own May 2026 Copilot for Business Central FAQ states that forecasting features “aren’t related to Copilot.” ^[8] Copilot is excellent at narrating BC data and accelerating in-system tasks. It is not the demand-planning agent.

Most BC operators still run Excel and Power BI as the actual planning UI. The Adelante SCM survey covered by Supply Chain Dive landed at 67.4% Excel reliance across supply-chain managers. ^[1] Inside BC mid-market distribution specifically, the pattern is unmistakable across community threads and r/MSDyn365BC.

None of those are Microsoft failures. They are scope boundaries. BC’s planning surface was built to give the planner a place to think. Isovel was built to do the deciding.

How Isovel decides: forecast, plan, write back to BC

Isovel sits on top of Business Central as a planning engine, connecting via the same external-engine entry point Microsoft documents in the Sales and Inventory Forecast Setup. ^[5] No consultant. No migration. No new forecast hierarchy to maintain.

The loop, in three lines:

1. Forecast — ensemble ML across SKU-location time series, with confidence bands and graceful degradation. Every SKU returns a forecast with a rationale, including the slow-movers and new items BC’s built-in Azure AI engine excludes.
2. Decide — Isovel reads on-hand and committed inventory across every BC location, weighs lead times and MOQs from your vendor cards, and decides what to order, where to transfer, and when.
3. Write back — recommendations land in BC as draft purchase orders and Requisition Worksheet planning lines, idempotent (re-runs never duplicate writes) and reversible within a 24-hour rollback window. Approval-gated by default, audit-logged on every action.

Industry data on mid-market wholesale distribution converges on a single anchor: the average wholesale distributor operates with roughly 38% excess inventory, a number that recurs across McKinsey’s 2024 distribution work and Netstock’s 2024 SMB benchmark report (n=2,400). ^[9] Isovel’s job is to make that gap visible on your tenant, in your data, in the first ten minutes. Then close it, week by week, decision by decision.

Multi-location rebalancing: first-class

MVP Tier 0

The single strongest cross-source signal in our 2026 buyer research: every BC mid-market distributor with two or more warehouses is sitting on stock in one location while running short in another. A BC expert in a 2026 thread put the architectural problem flatly: “there is no capability in the system to say ‘consolidate into a location which already contains the item, but exclude the location it’s being picked from.’” ^[11]

The redistribution gap is industry-wide. Only 27% of overstocked SMBs actually redistribute warehouse-to-warehouse before reordering more stock from the supplier. ^[2]

Isovel reads on-hand and committed inventory across every BC location, models lateral demand, and surfaces transfer-order recommendations alongside purchase-order recommendations. The agent surfaces multi-warehouse imbalance automatically when the tenant has two or more locations. No toggle, no setup wizard, no per-location configuration.

See multi-location inventory rebalancing for the deep cut on the rebalancing engine itself.

30-day shadow mode, then graduated trust

Isovel’s 30-day trial is shadow mode. The agent connects to your BC tenant, pulls data, builds dashboards, and surfaces recommendations, without writing to BC. The IT director gets thirty days to compare Isovel’s recommendations against your planner’s decisions before the agent touches a single record.

Write-back unlocks at conversion to paid. Every write-back is approval-gated by default, idempotent, reversible within 24 hours, and logged in an audit trail you can hand to your auditor. Data residency, OAuth scopes, encryption, subprocessor list, and SOC 2 Type 1 audit timeline are documented at /security/ for IT and procurement review.

The agent’s autonomy is graduated. Day one, every action requires explicit approval. After a track record of correct recommendations, a planner can opt-in to auto-execute a class of actions (transfer orders below a value threshold, for instance). Auto-approve policies are configured per planner, audit-logged, and reversible. Manual approval can be restored at any time. The trust primitives — pause, rollback, audit, manual override — are permanent. Transparent, auditable, and reversible are non-negotiable when an agent writes back to an ERP of record.

Replaces the Enhanced Forecasting Worksheet, not added to it

The Enhanced Forecasting Worksheet from Insight Works is the BC-native incumbent for forecasting display. It does what it does well. It improves the forecast UI surface inside BC. It does not decide what to order, write back replenishment lines, or reason about multi-location stock.

Insight Works’ own engineering blog is candid about the scope boundary: BC’s built-in forecast is “a starting point but not a planning tool.” ^[15] EFW addresses the display half of that gap. The decision half is what Isovel is built for.

Coexistence is not the design point. Both EFW and Isovel would otherwise write demand forecast entries to the same Business Central tables, creating predictable write conflicts. Isovel’s onboarding detects EFW and walks the customer through disabling it before write-back is enabled. Read the deeper comparison at /alternatives/enhanced-forecasting-worksheet/.

The same logic applies to other planning systems already wired into your tenant: Isovel replaces the planning brain. It does not stack alongside Netstock, Streamline, StockIQ, EazyStock, Lokad, or any other write-back-enabled planning tool.

Every gap the agent closes was named first by a real BC distributor

Multi-location rebalancing, graceful-degradation forecasting for slow-movers and new items, idempotent write-back to BC’s Demand Forecast Entry table, automatic detection of an active Enhanced Forecasting Worksheet install during onboarding. Every one of these is a gap a real mid-market BC distributor named when asked what their planner was doing in Excel instead of in the Planning Worksheet. The agent’s behavior is shaped to that operator reality, not to an AI-evangelist deck.

One price. No consultants.

No partner channel, no land-and-expand pricing trap, no “contact sales for a quote.” The page does the work, per Isovel’s sales-less GTM commitment. The only “contact us” on this page is the post-purchase fair-use conversation above, for tenants whose dataset materially exceeds the typical mid-market profile this tier was priced for.

Business Central planning FAQ

1. Which versions of Business Central does Isovel work with? Business Central 25, 24, and 23 on Cloud (SaaS) at launch; on-premises support is on the roadmap. The connector authenticates via Office 365 SSO; the integration uses BC’s documented OData and Web Services surfaces plus the Sales and Inventory Forecast Setup external-engine entry point.

2. Do I have to disable the Enhanced Forecasting Worksheet to use Isovel? Yes. EFW and Isovel both write demand forecast entries to BC’s underlying tables. Running both creates write conflicts. Isovel’s onboarding step detects EFW and walks you through disabling it before write-back is enabled. EFW remains a competent forecast-display tool; Isovel is a decision engine that needs sole ownership of the forecast and replenishment write-back path. See /alternatives/enhanced-forecasting-worksheet/ for the deeper comparison.

3. How is this different from Microsoft Copilot for Business Central? Microsoft’s own Copilot for Business Central FAQ, published May 2026, states that forecasting features “aren’t related to Copilot.” ^[8] The two products do different work. Copilot explains BC data, accelerates routine in-system tasks, and lets users query their tenant in natural language. Isovel forecasts demand, decides replenishment, and writes draft purchase orders and transfer orders back into BC. Both can coexist; they don’t overlap.

4. Is Isovel on Microsoft AppSource? The listing is coming to AppSource. In the interim, the connector is available via direct install with Office 365 SSO. The install experience is one-click in either path: sign in with your BC tenant credentials and Isovel pulls the data it needs to start surfacing recommendations.

5. What does the connector need to access, and where does Isovel’s write-back land? During the 30-day shadow trial: read-only access to sales orders, sales quotes, items, item ledger entries, locations, vendors, and BC’s demand forecast tables. No writes during the trial. After conversion to paid, Isovel’s recommendations land in BC as draft purchase orders and Requisition Worksheet planning lines that you Carry Out via BC’s standard approval and document-commit workflow. The Planning Worksheet remains your visibility surface; the Requisition Worksheet is the action surface. Write-back is approval-gated until the planner explicitly raises autonomy. Full OAuth scope list at /security/.

6. Will it work with our existing Item card setup, including Reordering Policy? Yes. Isovel reads BC’s existing Item card parameters — Reordering Policy (Fixed Reorder Qty, Maximum Qty, Order, Lot-for-Lot), reorder points, safety stock, lead times, vendor relationships, and unit-of-measure conversions — without re-setup. The agent respects your Reordering Policy on every write-back recommendation; it suggests refinements to the policy parameters as it learns from your real demand, but never overrides the policy itself without explicit planner consent.

7. Can I roll back a write-back? Every write-back action is reversible inside a 24-hour rollback window. Re-running a recommendation is idempotent: running the same recommendation twice never creates a duplicate purchase order or transfer order. Every action is logged in the audit trail.

8. Why is pricing on this page instead of behind a sales call? Because a planning agent that needs a salesperson to explain it is the wrong product. Isovel ships with no sales team — only engineering and marketing — and the website does all the conversion work. Pricing public, trial self-serve, conversion content-driven. That is the structural alternative to the partner-channel and quote-only norms in this category.

Start your 30-day shadow trial when we launch. Get early access →

Related Business Central pages

• Isovel for BC demand forecasting — ensemble ML + confidence bands as a replacement for the Sales and Inventory Forecast extension.
• Isovel for BC replenishment — multi-location-aware purchase and transfer write-back.
• Isovel for BC inventory AI — dynamic safety stock and reorder-point optimization.
• Enhanced Forecasting Worksheet alternative — head-to-head with the BC-native incumbent.
• vs. Netstock for Business Central — the most-evaluated alternative for BC mid-market distributors.