Distribution inventory software for Business Central distributors

Pre-launch — join the waitlist for founding pricing.

Last reviewed: 2026-05-26

If you are a wholesale distributor on Business Central — or evaluating BC after years of Sage 50, QuickBooks plus Fishbowl, or a legacy nineties ERP — the planning problem you face is not the one most inventory software is built to solve. It is not “should I buy more for warehouse A.” It is “I have stock sitting in one warehouse while another runs short, and the branch managers are ordering on hunches because the buy report has been broken since the last branch closed.”

Every named mid-market planning ISV publishes a distribution claim. The capability claim is contested across the category; the delivery posture is not. Isovel ships what an actual mid-market BC distributor needs: an agent that watches every branch continuously, decides which transfer or purchase order closes the imbalance, and writes a draft order back to Business Central — approval-gated, idempotent, reversible within twenty-four hours, audit-logged with the rationale visible on every line.

15–25%

of inventory value per year is what carrying excess costs you (storage, capital, obsolescence, insurance) — the universal mid-market distributor anchor.

APICS Puget Sound Chapter — Cost of Carrying Inventory [1]

49%

of expedited orders are driven by inaccurate forecasts (APQC Open Standards Benchmarking 2020) — best-in-class organizations spend 3% of logistics cost on expedited shipping vs. 10% for laggards.

APQC Open Standards Benchmarking 2020 [2]

13–19%

of logistics costs lost to poor multi-location coordination across distributor networks (McKinsey 2024, paraphrased — distributor-specific cost-of-not-rebalancing anchor).

McKinsey & Company — Distribution operational efficiency (2024, paraphrased) [3]

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

What distribution inventory software actually has to do

Distribution inventory software keeps the right stock at the right branch — managing demand across multiple locations, deciding when to transfer between them, and deciding when to reorder from suppliers. The job is different from single-warehouse inventory management (which only worries about reorder points), different from retail point-of-sale-tied tools (which assume one store per inventory pool), and different from enterprise multi-echelon optimization suites (which target Fortune-500 supply chains at six-figure implementation cost). A mid-market wholesale distributor with 200 to 6,500 SKUs and two to ten branches sits in the middle: enough complexity that Excel breaks, not enough budget or planner headcount to run a Lokad or a ToolsGroup deployment.

The category names you will see on the SERP — distribution inventory software, inventory software for distributors, wholesale distribution inventory management — all map to the same job. The vocabulary distributors actually use is “branch” for satellite locations, “hub” for the central warehouse or DC, “transfer to branch from hub” for the canonical multi-location decision, and “no quote” for what happens when you don’t have on-hand stock. Push, not pull: only what is on the shelf can be sold; backorder data does not exist at most mid-market distributors. [4] Isovel is built around that operator reality.

The four pains BC distributors actually hit

1. The planning problem is hub-to-branch, not “more for warehouse A”

A distributor running planning for multiple branches in 2025 puts it cleanly: “this is mostly for transfer to branch from hub, not buying.” [5] The unit of decision is the transfer order from the central warehouse to a branch — sized to the branch’s actual sell-through, constrained by what the hub can give up without going short itself. Most inventory tools treat replenishment as a purchase-order-to-vendor decision. For a distributor with branches, the transfer decision sits upstream of the purchase decision and gets resolved separately. Treating them as one problem misses the actual workflow.

2. The data is broken before any planning calculation runs

Distributor data hygiene is structurally fragile. Sales get assigned to branches by customer ID. Customer IDs carry locations that no longer match where the order ships. Closed branches keep accumulating sales attribution months after they close. One operator running a buy report in 2025 documented the cost: “between all the closed-down branches over the last six months, millions of dollars in sales have gone to them. Basically means all this stuff does not get assigned to any branch for the purposes of replenishing inventory.” [6] Until the data layer is right, no planning recommendation can be trusted — which is why Isovel runs a thirty-day shadow trial first, read-only, surfacing data-quality issues before writing anything back.

3. The planning tool is still Excel — even after the BC migration

Mid-market distributors migrating to BC come from Sage 50, QuickBooks plus Fishbowl, or a legacy ERP, and the migration is driven by the same trigger: “we’ve outgrown the band-aid stack, and the workarounds have workarounds.” [7] The expectation is that BC will replace the band-aids. The reality is that the planning surface still requires significant Excel work — 67.4% of supply-chain managers run Excel as their primary planning tool, with the corroborated range across recent surveys sitting between 47% and 81%. [8] The title varies — Inventory Analyst, Demand Planner, sometimes whoever has capacity that week — but the toolset is the same: Crystal Reports, Power BI, and a lot of Excel doing the work of a planning system. [9]

4. BC’s Item Availability does not look forward

For higher-volume distributors, BC’s standard Item Availability surface creates a specific failure mode. A 2026 thread from a BC distributor: “Microsoft has set up Item Availability to not look at future demand for an item when you enter a sales order. We will place an order, confirm the availability with our customer, then place another order that takes the inventory we verbally committed to the other customer, and we don’t know about it until we go to ship the first order.” [10] The workaround offered in the same thread is a third-party BC extension. Isovel does not solve the Item Availability look-ahead gap directly — that’s a sales-order-reservation feature, not a planning one — but the planning layer reasons against projected on-hand by location and surfaces the imbalance pattern as an exception in the planner dashboard. The Item Availability fix still belongs to the reservation extension; the planning-layer exception is the early warning, not the fix.

Average distributor inventory levels say the same thing

The average mid-market distributor runs roughly 38% excess inventory. Two unrelated 2024 sources converge on the same figure: McKinsey’s distribution operations work reports leading wholesale distributors at ~26% excess against an industry average closer to 38%, and Netstock’s 2024 SMB benchmark (n=2,400 customers) lands on the same 38% figure independently. [11] Between 20% and 30% of inventory becomes dead stock annually at the average distributor. [12] The money is sitting in the wrong place. The reason it stays sitting there is that the planning tool the distributor has — Excel, BC’s Planning Worksheet on its own, or a forecasting add-on without write-back — does not actually decide what to move where.

How Isovel works for distributors

MVP Tier 0 + Tier 1 + Tier 2

The closed loop, in four steps. The same loop every Isovel customer runs from day one.

1. Connect. One-click install (Microsoft AppSource listing coming at launch), Office 365 single sign-on, and the agent reads BC’s location master, item ledger entries, sales history, lead-time history derived from PO-receipt patterns, vendor cards (for MOQ and lot-size), and Transfer Routes if you have them configured. No data hierarchy setup, no ABC tagging by humans, no per-SKU per-location configuration. Time to first insight: under ten minutes, per Isovel’s standing non-negotiable.

2. Watch (thirty-day shadow trial). Isovel runs read-only for thirty days. The agent surfaces data-quality issues first — branch attribution gaps, customer-ID-to-ship-to mismatches, locations that have been closed in the master file but are still receiving sales — so you can clean before trusting recommendations. The forecast and the multi-location reasoning build alongside the data hygiene work. Nothing is written back to BC during shadow trial; the agent’s recommendations sit in the Isovel dashboard with rationale strings attached. You can audit the agent’s reasoning before turning anything on.

3. Decide. The agent reads per-location demand patterns from BC’s sales history, derives per-location lead-time distributions from PO-receipt history, infers per-location service-level targets from the planner’s historical safety-stock posture per SKU per location, and reads current on-hand from BC’s item ledger. It identifies imbalance — stock sitting in one branch while another runs short — and decides which transfers would close it without depleting the source. It identifies replenishment needs and decides which purchase orders to draft, MOQ-aware against the vendor card and pallet- or case-pack-rounding-aware on quantity. Every recommendation carries a rationale string. An illustrative example: “transfer 14 units from DC-Atlanta to Branch-Portland; Portland’s 8-week trailing demand exceeds on-hand by 11 units; Atlanta has 18 weeks of forward cover at current sell-through.”

4. Write back. When you convert to paid, write-back unlocks. Draft purchase orders land in BC’s Requisition Worksheet and draft transfer orders land in BC’s Planning Worksheet — the two share a single planning engine, and your planner Carries Out either via BC’s standard Carry Out Action Message workflow. Every write-back is approval-gated by default. Re-runs are idempotent — running the planning generation twice never duplicates draft orders. Any action is reversible within a 24-hour rollback window. Every line is audit-logged with the agent’s rationale attached. The trust primitives — pause, stop, rollback, restore manual approval — are permanent and never go away. As your planner gains comfort with the agent’s track record, the per-action approval requirement can loosen step by step — but the controls never disappear.

Multi-location reasoning, the way distributors actually think about it

Multi-location is the load-bearing primitive for distribution. The mechanics: the agent reads BC’s location master, Transfer Routes if you have them configured, and the demand pattern at each location. It detects imbalance algorithmically — no planner-maintained threshold tags, no per-SKU per-location configuration burden. When the topology is hub-and-spoke (central DC feeding branches), the agent reads that from the routing. When the topology is flat (peer-to-peer warehouses, no designated hub), recommendations route peer-to-peer.

Two specifics that matter for distributors. First, the agent reasons peer-to-peer rather than cumulative-aggregate — it knows which source branch should give up stock to which destination branch, sized for the actual imbalance, not just whether the network as a whole has excess somewhere. Second, the agent’s transfer-order write-back is idempotent and 24-hour reversible — re-running the planning generation never duplicates transfers, and any transfer can be rolled back within 24 hours if the branch manager objects. The page that covers the full mechanics is multi-location inventory rebalancing.

What this replaces

Isovel replaces, not coexists with. The agent writes back to BC’s planning surfaces directly — the Requisition Worksheet for purchase orders and the Planning Worksheet for transfer orders, the same surfaces other planning tools write to — so running Isovel alongside a second planning system would create write conflicts at the worksheet-to-document Carry Out step (both systems carrying Action Messages against the same data state would produce duplicate Purchase Orders and Transfer Orders). Onboarding detects existing planning systems and guides customers to disable them as part of the cut-over.

Excel, Crystal Reports, and Power BI as the planning stack. The distributor’s workaround stack is the most common system Isovel replaces. The dashboards Power BI gives you stay — they are the audit trail. The Excel sheets where the planning decisions actually live get retired.

Insight Works’ Enhanced Forecasting Worksheet. Single-location restriction at the BC platform layer, manual recompute every period, non-idempotent on forecast write-back. The legacy BC-native planning extension Isovel replaces for distributors who already tried it.

Netstock. The most-recognized BC-integrated mid-market planning brand. Strong on visibility dashboards and approval workflow; planner-actioned rather than agent-decided. A 2026-captured customer review documented Netstock’s multi-location rebalancing operating on cumulative-aggregate terms rather than peer-to-peer. [13] Isovel is the agentic replacement for the BC tenant that needs peer-to-peer reasoning and write-back at the agent level.

Streamline, EazyStock, StockIQ, Flowlity, Cin7 ForesightAI. The named mid-market planning ISVs. Each markets a multi-location-redistribution feature — intersite optimization, automatic warehouse-to-warehouse transfers, smart rebalancing suggestions. The capability claim is contested across the category. [14] What is uncontested: none ships zero-setup + continuous + algorithm-decided + idempotent BC write-back as the default posture. The delivery shape is the wedge, not the feature list.

Inventory Planner by Sage. Shopify-first inventory planning; BC integration not documented on the product page or AppSource. Surfaces in ChatGPT’s BC-distributor recommendation set despite the integration gap — Isovel is the BC-native answer for that buyer.

Microsoft-complementary by construction

Microsoft published its first-party agentic-AI-for-inventory roadmap in February 2026 — “Agentic AI for inventory to deliver: From procurement to fulfillment” — introducing the Supplier Communications Agent in Dynamics 365 Supply Chain Management alongside three partner-built agents operating via Model Context Protocol servers: the Warehouse Advisor Agent by MCA Connect, the Inventory Acquisition and Re-Balancing Agent by RSM, and the Inbound Load Agent by Fellowmind. [15] Two things worth being specific about. First, Microsoft’s first-party agentic-inventory surface is Dynamics 365 Supply Chain Management — the enterprise / F&O tier — not Business Central. Second, the three named partner agents all target D365 SCM via MCP, not the BC mid-market tier where the wholesale distributor ICP for this page actually sits.

Microsoft’s roadmap is Isovel’s tailwind. Microsoft’s first-party agentic-inventory surface addresses the D365 SCM enterprise tier — the Supplier Communications Agent plus partner extensions from MCA Connect, RSM, and Fellowmind, all via Model Context Protocol. Isovel addresses the BC mid-market tier with the same agentic principles: transparent, reviewable, keeps the planner in the loop, by design. Microsoft Copilot for Business Central is complementary in the same way on the BC side: Copilot accelerates routine in-system tasks and narrates BC data in natural language; Isovel decides multi-location replenishment and writes back. Different ERP tiers, different operator personas, different price points — complementary surfaces, not competing ones.

Watch the agent decide on your data — read-only for thirty days. Get early access →

Distribution inventory software FAQ

1. Does Isovel work for distributors not on Business Central? Phase 1 ships the Business Central connector. NetSuite, Acumatica, Odoo, and SAP Business One are on the Phase 2 roadmap. Isovel is available today for Microsoft Dynamics 365 Business Central; designed for every ERP. The connector adapter is BC-first until the Phase 2 connectors ship.

2. What’s the smallest distributor Isovel is designed for? Isovel’s ICP is the $5–$20M wholesale distributor with 100–5,000 SKUs and multi-location inventory across two to ten branches or DCs. Below that — under 200 SKUs running from one warehouse — the supply-chain community itself recommends Excel until a mitigating factor (multi-location complexity, BC migration, planner-headcount constraint) requires software. Isovel agrees.

3. How does Isovel handle hub-to-branch transfers? The agent reads BC’s location master and Transfer Routes if configured, detects imbalance algorithmically without planner-maintained threshold tags, and writes draft transfer orders into BC’s Planning Worksheet with per-line rationale strings. Your planner Carries Out via BC’s standard Carry Out Action Message workflow. Re-running the agent never duplicates a draft (idempotent). Any transfer can be rolled back within a 24-hour window. Multi-location reasoning surfaces automatically when the BC tenant has two or more locations — no toggle, no setup wizard.

4. What does the 30-day shadow trial actually do? Isovel pulls BC data, runs the planning agent in read-only mode, and surfaces both data-quality issues (sales attributed to closed branches, ship-to / customer-ID mismatches, location-master inconsistencies) and inventory recommendations with rationale strings. The agent does not write back to BC during shadow trial. Write-back unlocks at conversion to paid.

5. What about Microsoft Copilot for Business Central? Copilot is Microsoft’s chat and Q&A surface inside BC — it answers questions about your data. Isovel is the planning agent that decides and acts on your data: detects multi-branch imbalance, sizes transfers, drafts purchase orders MOQ-aware against the vendor card, and writes them back to BC’s planning surfaces (Requisition Worksheet for POs, Planning Worksheet for transfers). The two surfaces are complementary; many distributors will run both.

6. What about Microsoft’s February 2026 agentic-AI announcement? Microsoft’s February 2026 announcement scopes to Dynamics 365 Supply Chain Management — the enterprise tier — not Business Central. The Supplier Communications Agent + three partner agents (MCA Connect, RSM, Fellowmind) operate on D365 SCM via Model Context Protocol servers. Isovel covers the BC mid-market side of the same category with the same agentic principles.

7. How does pricing work? $999/month per BC tenant on a 12-month commitment, or $10,000 annually (~17% discount). Single flat launch tier. All users, all locations, and all write-back actions are included for typical mid-market datasets. Quantitative fair-use limits apply for high-volume tenants — concrete thresholds exist internally; customers approaching them are reached out to for a customer-success conversation, not a pre-purchase sales gate. Full detail on pricing.

8. Which versions of Business Central does this support? Business Central 25, 24, and 23. Cloud (SaaS) at launch; on-premises is on the roadmap.

Built around the operator reality distributors actually face

The shape of distribution planning is not the shape most inventory software is built around. The unit of decision is the transfer order from hub to branch as much as it is the purchase order from vendor to hub. The data is broken before any forecast runs. The planning system is still Excel even after the BC migration. The trust threshold for letting any tool write back is high — distributors have lived through too many BC partner implementations and ERP migrations to take “AI inventory” claims at face value.

Isovel is built around all four: agent-decided, BC-native write-back, shadow-mode-first, with idempotent + reversible + audit-logged primitives on every action. The agent’s behavior on every recommendation is shaped to the operator reality BC mid-market distributors actually face — broken buy reports, attribution drift across closed branches, transfer decisions that no rule-table catches.