Replacing Enhanced Forecasting Worksheet — the agentic alternative for Business Central

Insight Works’ own Director of Marketing put it on record: “Forecasting in Business Central is fine if you’re just curious. But if you need actually to act on the data—plan, optimize, or scale—you need something better.” ^[1] They are right about the diagnosis. The Enhanced Forecasting Worksheet — their product — is a worksheet wrapper over the same Azure ML extension that ships inside Business Central. Insight Works confirms this themselves: “EFW leverages the same Azure model integrated within native Business Central forecasting.” ^[2] The wrapper inherits the thinness it was built to fix, and then adds a single-location restriction, planner-authored expressions, and non-idempotent write-back on top.

Isovel is the agentic alternative for the same job. It runs its own forecasting layer, decides what your planner should do next, and writes draft lines back to Business Central — approval-gated by default, idempotent, reversible within a 24-hour window, audit-logged with the agent’s rationale on every line.

Phase 1   Pre-launch waitlist. One-click install — listing coming to Microsoft AppSource. $999/month or $10,000/year (12-month commitment, ~17% discount). Fair-use limits apply for high-volume tenants — typical mid-market datasets (100–5,000 SKUs, multi-location) sit comfortably within them.

Insight Works is right about the diagnosis. EFW just doesn’t fix it.

The Brian Neufeld quote at the top of this page is Insight Works’ own framing — published on LinkedIn and cross-posted to dmsiworks.com. ^[1] Their argument: Business Central’s built-in forecasting is curious-only; you need “something better” to actually plan, optimize, or scale.

The argument is correct as far as it goes. Business Central’s built-in Sales and Inventory Forecast extension is a single Azure Machine Learning Timeseries model surfaced behind a worksheet view, and the surface that consumes its output — the Demand Forecast — has a documented external-engine entry point. A BC operator on r/Dynamics365 puts it plainly: “You can point the forecast to any external engine you want in the Sales and Inventory Forecast Setup.” ^[20] The built-in is a hook for a real planning engine to plug into. A 2026 BC operator put a stronger version of the same point: “In 10 large implementations I only had to use the standard twice.” ^[18] Native MRP is rarely deployed as-is.

The disagreement is the solution. EFW is a worksheet wrapper over the same Azure ML extension. Insight Works themselves describe it that way on r/BCAppsCommunity: “EFW leverages the same Azure model integrated within native Business Central forecasting.” ^[2] The wrapper is a UX layer — six algorithm choices drawn from Azure ML’s Timeseries Model options, a worksheet to filter and review the outputs, a button to write entries back to BC’s Demand Forecast Entry table. The forecasting engine underneath remains Microsoft’s hosted Azure ML endpoint, with whatever lifecycle constraints Microsoft chooses to put on it.

Isovel runs its own forecasting layer. The agent computes ensemble ML forecasts with confidence bands per SKU per location from your actual BC data — sales history, lead-time variance, return patterns, service-level target — and decides safety stock, reorder points, reorder quantities, and replenishment lines off the back of that forecast. The Brian Neufeld diagnosis is right. The EFW solution is a half step.

The single-location restriction (load-bearing limit #1)

Insight Works’ own knowledge base documents the limit verbatim: “If your company is using multiple locations and SKUs, you must choose a single location to forecast; otherwise, the first SKU updates when applying the forecast.” ^[3] The EFW marketing copy says the opposite — “Filter by item, category, or location to focus on specific inventory needs, enhancing accuracy in forecasting” ^[4] — but the KB is the operational truth. A planner with three warehouses runs the worksheet three times, once per location, and reconciles by hand.

Business Central mid-market distributors are multi-location by definition. The reason CLAUDE-internal pricing puts Multi-Location Rebalancing in the launch MVP tier is the same reason the EFW single-location restriction is load-bearing: cross-location demand asymmetry is the dominant pattern in mid-market wholesale, and a planner can not run the same forecast three times and call it multi-location. The forecasts don’t reconcile; the safety stock per location doesn’t share information with peer locations; the planner has no way to surface a transfer that closes one location’s shortage from another location’s excess without leaving both depleted.

Isovel’s forecast is per-SKU per-location in a single pass, and the planner sees per-location confidence bands plus cross-location transfer recommendations next to per-location stock and demand. The architecture is covered in depth on /multi-location-inventory-rebalancing/. The point on this page is simpler: the multi-location surface is where EFW is documented as not working, and where Isovel is built to work.

Re-running EFW doubles your forecast. By design.

Insight Works’ KB also documents this one, in plain language: “Update Demand Forecast does not modify/delete existing demand forecast entries; the action inserts entries based on the results in the worksheet… sending the same forecast results twice to the same demand forecast results in two times the forecasted quantity being added to the forecast entry for the appropriate period.” ^[5] This is documented behavior, not a bug. A planner who reruns “to be safe” — to refresh after a parameter change, to re-pull after a slow data sync, to recover from a partial run — silently doubles the forecast in BC.

The risk is structural at the BC platform layer: the underlying Demand Forecast Entry table is not idempotent at the platform layer either — a 2026 r/Dynamics365 operator documented that “importing a Demand Forecast with RapidStart creates duplicate entries.” ^[13] Any layer that writes to that table without explicit idempotency enforcement inherits the same risk. EFW does not enforce idempotency; the KB above is the documentation of that choice.

Isovel’s write-back layer enforces idempotency. Re-running a planning generation never duplicates writes. Every action is reversible within a 24-hour rollback window. Every recommendation and every write-back is visible in the audit trail with the agent’s rationale string attached, so your planner can see why the agent recommended what it recommended before deciding whether to keep the write. This is the same pattern Isovel uses for purchase order automation and transfer order recommendations — covered in depth on /for-business-central/replenishment/.

EFW asks the planner to author expressions. Isovel asks for nothing.

The KB documents the planner-config burden too: “Input expressions for item planning parameter calculations into the following fields… Safety Stock Expression, Reorder Point Expression, Reorder Quantity Expression, Maximum Inventory Expression.” ^[6] Default expressions are provided for “an initial experiment,” but the planner is then responsible for tuning, testing, and maintaining a custom expression DSL per item. Further setup is required to surface the algorithm and confidence-level fields at all — the KB says “you may need to add Confidence Level and Forecast Algorithm fields to the page via Personalize/Design.” ^[7]

Insight Works themselves have published the gap that follows from this. Two examples from their own r/BCAppsCommunity channel:

The slow-moving-inventory gap (admitted by Insight Works)

“The Enhanced Forecasting Worksheet app is extensible and allows adding custom logic, but no slow moving inventory feature is provided out of the box.” ^[8] “Extensible” framed as a feature is the admission of the gap — the planner, or a paid Insight Works consultant, has to build the extension.

The Enhanced Planning Pack demand-date gap (admitted by Insight Works)

On their adjacent Enhanced Planning Pack: “The Calculate Purchase Plan ignores exact demand dates, potentially overlooking urgent demands with nearby supply arrival.” ^[9] The Insight Works planning stack is “extensible” in the same sense the BC built-in is “customizable” — the burden is on the operator.

Isovel asks for nothing at onboarding. No expression DSL. No ABC tags entered by hand. No promo-calendar to maintain. No safety-stock formula to author. The agent derives Reorder Point, Safety Stock Quantity, Reorder Quantity, Reordering Policy, Dampener Period, Time Bucket, Safety Lead Time, and the rest from your actual sales and lead-time data, and updates them on its own clock. Time-to-first-insight from “click connect” to first actionable recommendation is <10 minutes by product commitment.

Feature matrix

The matrix below cites Insight Works’ own published materials on every EFW row. Honest where EFW has the comparable feature; explicit where it does not.

Pricing — transparent vs freemium-via-bundle

Two categorically different commercial models.

Honest where EFW wins

If you have one planner running on one BC location and you are comfortable authoring the planning expressions yourself, the EFW free tier costs you nothing. That is the use case EFW’s freemium model is built for.

Where Isovel wins

Multi-planner teams. Multi-location distributors. Anyone who wants the agent to decide what the planner used to author. Anyone who wants the write-back to be safe to rerun. Anyone whose forecast accuracy depends on more than a single Azure ML Timeseries algorithm. Anyone who wants transparent pricing on the marketing site.

When EFW is the right answer (and when it isn’t)

EFW fits if: you run one BC location, you have one planner, you want a free tool to dip your toe into BC-resident demand forecasting, and you are comfortable authoring Safety Stock / Reorder Point / Reorder Quantity / Maximum Inventory expressions and reasoning about Azure ML algorithm choices. EFW gets you a forecast inside Business Central with no out-of-pocket cost on Cloud, and a thoughtful UX on top of the Microsoft Azure ML extension that ships with BC. For that exact profile, it is the right answer.

Isovel fits if: you run multiple BC locations, you want the agent to decide what to forecast and what to do next rather than asking your planner to author expressions, you want the write-back to be safe to rerun without doubling your forecast, you want decision automation that produces draft PO and Transfer lines as well as forecasts, and you want a single transparent price you can read on the marketing site without a sales call. For mid-market BC distributors with multi-warehouse inventory and one to three planners running things in Excel, Isovel is built for the job.

Replacing EFW — and why side-by-side doesn’t work

The Isovel posture on existing planning systems is replace, not coexist. On EFW specifically, this is not a marketing preference — it is a write-conflict reality.

EFW writes to BC’s Demand Forecast Entry table, and the same compounding-write pattern documented for RapidStart imports applies — re-runs and additive writes against this table do not de-duplicate at the platform layer. ^[13] If both EFW and Isovel are writing to the same table on the same BC tenant, every Isovel write that lands on a period EFW has already populated inherits the same non-idempotent-table risk EFW’s own KB documents.

The forecast in BC becomes a sum of two engines, weighted by whoever wrote last. The planner cannot tell which entries came from which engine without a custom audit. Action messages downstream of the corrupted forecast are then derived from the sum, not from either engine’s intended output.

Isovel’s onboarding detects an active EFW installation on the tenant and walks your planner through disabling EFW before Isovel’s write-back is enabled. The 30-day shadow trial is read-only — your team can evaluate Isovel on your BC data without disabling EFW, because Isovel writes nothing back to the tenant during the trial. Write-back unlocks at conversion to paid; that is when the EFW disable step is required.

Graduated trust — permanent primitives, line-by-line autonomy

The page enumerates EFW’s documented limits at the level of the BC Demand Forecast Entry table and the Sales and Inventory Forecast Setup page because the same tables and the same setup surface are where Isovel writes. Isovel’s posture on those write surfaces is the opposite of EFW’s: every recommendation is approval-gated by default at the start, and the trust primitives — pause, stop, rollback, restore manual approval — are permanent. They never go away.

The agent’s autonomy is graduated independently. As a planner gains comfort with the agent’s track record, the default-required-approval-per-action can loosen step by step — for example, transfer orders below a value threshold can be opted into auto-execute after a track record of correct recommendations. But the planner can always restore explicit approval, pause the agent, or roll back any action within the 24-hour window. The graduated-trust posture is the structural answer to the same write-conflict risk this page documents on the EFW side. The agent earns autonomy line by line; it never assumes it.

Enhanced Forecasting Worksheet alternative FAQ

1. Does EFW support multi-location forecasting? No. Insight Works’ own knowledge base documents the restriction: “If your company is using multiple locations and SKUs, you must choose a single location to forecast; otherwise, the first SKU updates when applying the forecast.” ^[3] A planner with three warehouses runs the EFW worksheet three times — once per location — and reconciles by hand. The marketing copy on dmsiworks.com says “filter by location” ^[4] but the KB is the operational source of truth.

2. What’s the difference between EFW and the Enhanced Planning Pack? Enhanced Forecasting Worksheet is the standalone forecasting tool — free for 1 concurrent Cloud user. Enhanced Planning Pack is a six-app bundle from Insight Works that includes EFW plus five other apps (planning, inventory, replenishment-adjacent), priced at $138/month/company on annual subscription. ^[11] The bundle is the standard upsell path from the free EFW tier.

3. Can I run EFW and Isovel side-by-side? Not safely. Both products write to BC’s Demand Forecast Entry table, and the table is not idempotent at the platform layer. Layering Isovel on top of an existing EFW installation compounds EFW’s documented double-write behavior at the platform level — the forecast in BC becomes a sum of two engines and the planner cannot tell which entries came from which without a custom audit. Onboarding detects an active EFW installation and guides disabling it before Isovel write-back is enabled. The 30-day shadow trial is read-only, so evaluation does not require disabling EFW.

4. Why is EFW free for one user? Insight Works’ free-for-one-Cloud-user tier is a customer-acquisition surface for the paid Enhanced Planning Pack bundle at $138/month/company. On-premises EFW is paid only. ^[12]

5. How does Isovel handle the Azure ML reconfigure step EFW required in 2024? Microsoft retired the Azure ML Gallery in September 2024. ISVs that wrapped it — including EFW — had to reconfigure. Insight Works’ own KB documents the change and the workaround: “The reason why you are receiving this error is because the Microsoft Gallery.azure.ai has been deprecated as of September 2024… on Business Central SaaS, please… blank out the URI and key. If you are on-prem, please reach out to your Microsoft Partner to obtain the URI and Key for the specific machine learning endpoint.” ^[10] Isovel runs its own forecasting layer; there is no hosted Microsoft endpoint for the forecasting backend, and no equivalent reconfigure step when Microsoft’s Azure ML lifecycle changes.

6. What is the Planning Worksheet in Business Central? The Planning Worksheet and the Requisition Worksheet are Business Central’s two replenishment surfaces. They share a single planning engine: “Anticipated and actual customer demand, and inventory reordering parameters, drive the planning system. Running the planning calculation results in suggestions for specific actions (Action Messages) to take for possible replenishment from vendors, transfers between warehouses, or production.” ^[16] Transfer Orders flow through the Planning Worksheet; Purchase Orders flow through the Requisition Worksheet. The Demand Forecast that EFW (or Isovel) produces is one of the inputs the engine consumes. (Note: Dynamics 365 Supply Chain Management is the enterprise-tier Microsoft sibling with its own forecasting and planning surfaces; EFW and Isovel both target BC mid-market, not D365 SCM.)

7. How do I forecast in BC without EFW? Three paths. (a) BC’s built-in Sales and Inventory Forecast extension — single Azure ML Timeseries model surfaced behind the Demand Forecast view. (b) Point BC at any external engine via the Sales and Inventory Forecast Setup page: “You can point the forecast to any external engine you want.” ^[20] (c) Replace the forecasting surface entirely with an agentic alternative that decides what the planner used to author. Isovel is path (c) — see /for-business-central/demand-forecasting/ for the architecture.

8. How does Isovel handle new items with no sales history? Graceful degradation is a product commitment. The agent never returns a “cannot forecast” wall — it always returns a confidence-banded estimate with a rationale string explaining the basis (hierarchical multi-location fallback, category-mean prior, vendor lead-time inference). EFW’s KB by contrast requires “sufficient sales history (posted Sale-type item ledger entries)” ^[15] and excludes the item from the forecast otherwise.

9. When is EFW actually the right answer? Single BC location. Single planner. You want a free tool to dip your toe into BC-resident forecasting. You are comfortable authoring Safety Stock, Reorder Point, Reorder Quantity, and Maximum Inventory expressions, and you are willing to author a slow-moving-inventory extension yourself or pay for one. For that profile, EFW gives you a forecast inside Business Central at no out-of-pocket Cloud cost. For multi-location distributors with multiple planners and a write-back-safety requirement, Isovel is built for the job.

30-day shadow trial. Read-only on your BC tenant. Write-back unlocks at conversion to paid. Phase 1 launch tier: $999/month or $10,000/year per BC tenant (12-month commitment). Fair-use limits apply for high-volume tenants.

Related Business Central pages

• Isovel for Business Central (hub) — the parent narrative covering connector, write-back, multi-location, and trust controls.
• Isovel for BC demand forecasting — ensemble ML demand forecasting architecture that replaces the EFW use case.
• Isovel for BC replenishment — draft PO + Transfer lines written back to the Requisition Worksheet, idempotent and reversible.
• Isovel for BC inventory AI — dynamic safety stock and reorder-point derivation upstream of the replenishment decision.
• Multi-location inventory rebalancing — the deep cut on the cross-location reasoning EFW does not do.