Light manufacturing planning for Business Central teams
Pre-launch - join the waitlist for founding pricing.
Last reviewed: 2026-05-30
Light manufacturing teams on Business Central live in the overlap between distribution planning and shop-floor planning. You sell finished goods, buy components, move inventory between locations, assemble or produce a subset of items, and still need the buyer to know what to order this week. That workflow is too manufacturing-heavy for generic wholesale inventory tools and too planning-heavy for a spreadsheet bolted onto BC.
Isovel is being built for that middle ground. Phase 1 covers the demand, inventory, purchase-order, and transfer-order planning layer for Business Central. Production Order and Assembly Order agent decisioning is Phase 2, tied to BOM-driven make-to-stock light manufacturing. The page is explicit about that boundary because the wrong planning tool is worse than no planning tool.
revenue range from a representative Business Central buyer: a small wholesale distributor and light manufacturer processing 70-100 orders per week.
r/Dynamics365 light manufacturer thread [1]
order types in BC planning language: purchase, transfer, production, and assembly. Isovel Phase 1 writes back purchase and transfer; production and assembly move to Phase 2.
Microsoft Learn - Run MPS and MRP [6]
read-only shadow mode before write-back, so the agent's recommendations and data-quality findings are visible before it touches BC.
Isovel product scope [8]
Phase 2 beachhead Phase 1 is live for BC purchase and transfer planning. Production and assembly write-back is planned for the light-manufacturing expansion.
What light manufacturing planning has to do
Light manufacturing planning connects finished-good demand to the component inventory and supply actions required to make those goods available. In Business Central terms, the work touches sales demand, forecasts, purchase orders, transfer orders, assembly orders, production orders, stockkeeping units, locations, production BOMs, routings, and planning parameters.
Microsoft describes Business Central supply planning as covering anticipated and actual demand from sales, assembly, production, and distribution planning, including stockkeeping units and location transfers. [2] The Planning Worksheet can run MPS and MRP to create a supply plan at item levels, and BC’s planning functionality exposes item and SKU parameters such as reorder point, safety stock, manufacturing policy, assembly policy, minimum order quantity, maximum order quantity, and order multiple. [3]
For a light manufacturer, those primitives are necessary but not sufficient. The painful part is not whether BC can hold a production BOM. It is whether the planning process can answer a practical question before the buyer, planner, or owner has to rebuild the answer in Excel: what should we buy, move, assemble, or produce next, and why?
The operator reality
The clearest buyer signal is not a large enterprise manufacturer. It is the small wholesaler/light manufacturer moving from Sage 50 or a workaround stack into BC. One representative operator described a $10-$14M business with 10 employees and 5 system users, where 90% of the business is distribution and 10% is light manufacturing. They were manually handling sales orders, work orders, purchases, receiving, inventory tracking, and 70-100 orders per week, with inventory planning on the must-have list. [1]
That shape matters. The first planning problem is usually not finite-capacity scheduling. It is the mixed distribution/manufacturing queue: buy components, avoid excess finished goods, protect the stock position at each location, and stop the owner from being the planning system.
Where BC light manufacturers get stuck
1. Finished-good demand has to become component demand
Business Central production orders convert purchased materials into manufactured items, and production orders carry the materials required for planned production. [4] That is the core of BOM-driven planning: finished-good demand has to flow down into component needs before the buyer knows what to purchase. When demand changes quickly, static reorder points and stale item settings create a lag between what sales needs and what purchasing sees.
2. The same planner is balancing purchase, transfer, production, and assembly
BC’s planning language includes purchase orders, transfer orders, production orders, and assembly orders. [6] A light manufacturer does not want four disconnected queues. A shortage in one location might be solved by a transfer. A finished-good shortage might require a production order. A component shortage might require a purchase order. The planning system has to reason across those options before it asks a human to act.
3. BOM-level forecasting is hard to find and hard to trust
The questions operators ask in public are telling. A Business Central user searched for “BOM component level Forecast/MRP in Dynamics 365 Business Central” because the answer was not obvious from the workflow surface. [7] The indexed answer pointed back to BC’s Manufacturing and Assembly Management modules. For Isovel, the signal is the question itself: light manufacturers need BOM-level planning language, not just generic demand forecasting language.
4. Planning suggestions still need judgment
Microsoft’s planning-system documentation frames the planner as the user who reviews suggested actions after BC performs the extensive calculations of a plan. [5] That is the right division of labor. The risk is that the calculations become a wall of worksheet lines without enough explanation, history, or rollback to build trust. Light manufacturing raises that risk because a bad suggestion can ripple from component purchasing into production dates and customer commitments.
Current Isovel scope for light manufacturing
Honest scope boundary| Planning surface | Isovel Phase 1 | Light-manufacturing Phase 2 |
|---|---|---|
| Demand forecasting | Forecasts demand from BC sales history and item/location behavior. | Adds deeper BOM-aware planning views for finished goods and component exposure. |
| Purchase orders | Drafts MOQ-aware purchase recommendations for approval in BC. | Extends component-buy logic around production and assembly demand. |
| Transfer orders | Recommends transfer actions when one location can cover another without creating a new risk. | Extends transfer-first logic into manufacturing sites and component staging locations. |
| Production orders | Not auto-decided or written back by Isovel today. Production Orders continue through BC. | Agent decisioning for BOM-driven make-to-stock Production Orders. |
| Assembly orders | Not auto-decided or written back by Isovel today. Assembly Orders continue through BC. | Agent decisioning for Assembly Orders where the planning pattern fits light manufacturing. |
The short version: if your workload is mostly purchasing, transfers, and distribution-side replenishment with some light manufacturing attached, Isovel can help earlier. If your workload is mostly Production Orders, Assembly Orders, routings, and shop-floor scheduling, you should join the Phase 2 waitlist and keep production/assembly planning inside BC for now.
How Isovel fits
1. Connect to Business Central. Isovel reads item history, locations, item ledger entries, purchase history, vendor constraints, stockkeeping units, lead-time behavior, and transfer routes where configured. For light manufacturing, the Phase 2 path adds the BOM and manufacturing context required to reason across finished goods and components.
2. Run shadow mode. For thirty days, the agent is read-only. It shows recommendations, assumptions, and data-quality issues without writing to BC. This is especially important for light manufacturing because old item setup, inactive locations, stale lead times, and inconsistent BOM or SKU data can make a mathematically correct recommendation operationally wrong.
3. Decide purchase and transfer actions first. In Phase 1, the agent decides the purchase and transfer moves that stabilize the inventory position around BC. It explains why each recommendation exists: demand pattern, lead time, current stock, vendor MOQ, order multiple, source-location cover, and destination-location risk.
4. Keep production and assembly under planner control today. Production Orders and Assembly Orders continue to be planned and carried out in Business Central. That is not a hidden gap; it is the published scope boundary. The Phase 2 light-manufacturing expansion is where Isovel adds agent decisioning for BOM-driven make-to-stock production and assembly.
5. Write back with permanent trust controls. After the paid write-back stage is enabled, purchase and transfer recommendations write back approval-gated, idempotent, reversible within twenty-four hours, and audit-logged with rationale. Those trust primitives carry into Phase 2 because production/assembly write-back needs more transparency, not less.
What to look for in light manufacturing software
If you are evaluating planning software for a BC light manufacturer, ask questions that separate inventory visibility from planning ownership.
Does it understand the mixed business? Many light manufacturers are also wholesalers or distributors. The software should treat purchase, transfer, production, and assembly as a connected planning problem, not as four isolated modules.
Does it distinguish make-to-stock from make-to-order? Business Central planning parameters explicitly include Manufacturing Policy, with make-to-stock and make-to-order shaping how supply orders are suggested. [9] A planner needs the software to respect that difference instead of flattening every item into the same reorder logic.
Does it explain component exposure? A useful plan should say which finished-good demand is driving component risk, not just “buy more.” Component-level exposure is the point of BOM-driven planning.
Does it write back safely? For any system that writes to BC, idempotency, approvals, audit logs, and rollback are not optional. A re-run should not create duplicate drafts, and a bad action should not become permanent before a planner has a chance to review it.
Does it stay clear about finite-capacity scheduling? Light manufacturing planning and finite-capacity scheduling are adjacent but not identical. Isovel’s light-manufacturing expansion is for BOM-driven make-to-stock planning first, not a full advanced planning and scheduling replacement.
Where this sits in the Isovel roadmap
Isovel’s launch beachhead is Business Central distribution and wholesale planning. Light manufacturing is the next Business Central expansion because the same companies often do both: a distribution-heavy operator with a small make/assemble workload, or a light manufacturer whose planning pain starts in purchasing and inventory before it reaches the shop floor.
The founder-approved product boundary is direct: MVP stays Purchase Order and Transfer Order write-back only. Production Order and Assembly Order write-back is deferred to Phase 2, alongside the BOM-driven make-to-stock light-manufacturing beachhead. [8] That keeps the launch product useful for the business it is ready to serve and keeps us from selling a manufacturing workflow before the agent can own it safely.
If your BC tenant has the distribution/manufacturing blend, start with the waitlist. We will tell you plainly whether you belong in Phase 1 or Phase 2. Join early access
Light manufacturing planning FAQ
1. Is Isovel available for light manufacturers today? Isovel Phase 1 is for Business Central purchase and transfer planning. It can help light manufacturers whose current pain is inventory, component purchasing, and distribution-side replenishment. If your pain is primarily Production Order or Assembly Order decisioning, join the Phase 2 waitlist.
2. Does Isovel create Production Orders in Business Central? Not in Phase 1. Production Orders continue to flow through Business Central. Production Order agent decisioning is planned for the light-manufacturing Phase 2 expansion.
3. Does Isovel create Assembly Orders? Not in Phase 1. Assembly Orders stay in Business Central today. Assembly Order decisioning belongs to the same Phase 2 expansion as Production Order decisioning.
4. What is BOM-driven make-to-stock planning? It is planning finished goods for inventory, then translating that expected finished-good demand into component requirements, purchase needs, and production timing. In BC terms, it touches forecasts, production BOMs, planning parameters, purchase orders, production orders, assembly orders, and item/SKU settings.
5. Is this a full production scheduling or APS product? No. The Phase 2 light-manufacturing scope is BOM-driven make-to-stock planning first. Finite-capacity scheduling, detailed shop-floor dispatching, and full APS replacement are separate problems.
6. What if our business is 90% distribution and 10% light manufacturing? That is exactly the transition case this page is for. If the immediate workload is purchase and transfer planning around BC, Isovel can be relevant earlier. If the manufacturing slice controls the whole planning process, wait for Phase 2.
7. Does Isovel replace Business Central? No. BC remains the ERP and transaction system. Isovel replaces the spreadsheet-heavy deciding layer around BC and writes approved recommendations back into BC where the planner can process them.
8. How is pricing handled? Launch pricing is $999/month per BC tenant on a 12-month commitment, or $10,000 annually. The light-manufacturing Phase 2 offer may add additional scope when production and assembly write-back ship.
Related pages
- For Business Central - the parent hub for BC connector, write-back, and trust controls.
- Business Central replenishment - the current purchase and transfer planning scope.
- Demand planning software - category-level demand planning buyer guide.
- Purchase order automation - how recommendations become purchasing actions.
- For distributors - the distribution-heavy version of the same buyer profile.
- For wholesalers - transfer-first wholesale inventory planning.