For a lot of mid-size food manufacturers, Microsoft Dynamics 365 Business Central handles the job well enough, right up until a pallet of whole hams or a percentage-based formula turns up and the cracks start to show. A stock food manufacturing ERP setup on Business Central covers standard recipes, batch production, lot traceability, and expiry-driven picking without much fuss. Where it strains is variable-weight products, formulas that scale by potency, and yield that moves from one batch to the next. This piece walks through where the line actually sits across four workflows so you can tell whether native Business Central will carry your plant or whether you'll need to extend it.
If you're weighing a general-purpose platform against something built for the industry, the comparison is a useful frame. The same "what's our real system of record" question applies to food.
What a Food Manufacturing ERP Needs to Handle
Food production doesn't behave like discrete assembly, so before scoring Business Central it's worth naming the four places food operations diverge:
- Recipes and formulas that scale, with substitutions, co-products, and by-products, well past what a fixed ingredient list can hold.
- Batch production with forward-and-backward traceability, shelf-life, and quality holds.
- Catch weight, for items whose individual weight varies. Cheese wheels, primal cuts, whole fish.
- Yield, because inputs rarely equal outputs, and the gap shifts with quality, moisture, and potency.
Any credible food manufacturing ERP has to cover all four, and food manufacturing software that stops at one or two of them will push the rest back onto spreadsheets. Here's how the native platform scores on each.
What Business Central Handles Natively
This is where Business Central earns its keep. For discrete and semi-process manufacturers with stable recipes, the native tooling does real work.
Recipes via Production BOMs
Business Central models recipes through Production BOMs and routings. You define ingredients, versions, and quantities, tie them to a manufactured item, and drive production orders straight off them. For a bakery, a snack line, or a co-packer with fixed formulations, that covers the day-to-day, and it feeds costing and inventory without any custom development.
Batch Production and Lot Traceability
Native item tracking gives you lot numbers, expiration dates, and FEFO (First-Expired-First-Out) picking. You can trace a lot backward to the ingredients you received and forward to the finished goods you shipped, which is the whole basis of a recall response. Keep your dimension setup disciplined and your per-batch costs stay clean; a drifted dimension quietly distorts every production-run margin report before anyone thinks to check. Getting right is the part of food safety you cannot hand-wave, and the native core here is genuinely solid.
Catch Weight through Dual Unit of Measure
Business Central has no true catch weight feature. Teams approximate it with dual unit of measure, buying and stocking a product in kilograms while selling it by the piece. For occasional variable-weight items, that holds up fine. In a combined operation, this production work runs next to the other Dynamics 365 modules an agriculture business leans on on the same platform, so finance and the plant floor share one set of numbers.
Where Business Central Falls Short
The dual-unit catch weight trick is the tell: for several food-specific needs, the native product leans on approximations. Here's where the standard product runs out of road as a food manufacturing ERP:
| Workflow | Native Business Central | Where it falls short |
|---|---|---|
| Recipes / formulas | Production BOMs with fixed quantities | No percentage-based formula management, potency or concentration scaling, or automatic co-product and by-product handling |
| Batch production | Lot tracking, FEFO, expiry | Stage-by-stage QC hold-and-release is thin natively; extended lot attributes are limited |
| Catch weight | Dual unit of measure workaround | No true catch weight costing from purchase through production to sale, so margins on variable-weight items drift |
| Yield | Output vs. scrap on production orders | No dynamic yield tied to quality or moisture, no potency-based purchasing, no concentration-driven scaling |
The catch weight workaround usually holds up until variable-weight products become a real share of your volume. Then the margin math starts drifting, and nobody notices until someone questions why a strong sales month posted a soft gross margin. Heavy process manufacturing, where you purchase by potency or scale a formula to a target concentration, is where the native platform consistently needs help. That's the gap .
Food Manufacturing ERP on Business Central: When Native Is Enough
Here's the call in plain terms.
Native Business Central is enough if you run discrete or semi-process production with stable recipes and standard batch sizes, your variable-weight items are occasional, you don't price or purchase on potency, and you can treat yield as output minus scrap.
You'll want to extend it once you rely on percentage-based formulas, co-products, or by-products; sell real volume in catch-weight products; purchase or scale by potency, moisture, or concentration; or need dynamic yield and QC hold-and-release built into every stage. The same goes if FSMA and HACCP documentation is something your team currently rebuilds by hand at audit time.
The good news is you can add that capability on top of Business Central and keep everything you've already built.
Closing the Gap: AgriERP on Business Central
AgriERP, powered by Microsoft Dynamics 365 Business Central, adds the food-specific layer the native platform lacks: formula and recipe management past fixed BOMs, native catch weight handling, dynamic yield, QC hold-and-release, FEFO inventory, and lot traceability with extended attributes.
Because it's built on Business Central itself, your financials, reporting, and existing Power BI and Copilot work stay exactly where they are. You're adding capability to the platform your team already runs, which is a far smaller project than a migration. Most manufacturers who go this route do it precisely because they don't want to give up the Microsoft stack to get food-grade functionality.
FAQ
Is Business Central good for food manufacturing?
Yes, for mid-size manufacturers with discrete or semi-process production, stable recipes, and standard batch sizes. The native product covers Production BOMs, lot traceability, FEFO, and basic variable-weight scenarios. Process-heavy operations usually need an ISV extension.
Does Business Central support catch weight?
Not as a true native feature. Teams approximate catch weight with dual unit of measure, which works for simple cases but doesn't fully cost variable-weight items across purchase, production, and sale. A food-specific extension adds native catch weight handling.
Can Business Central handle recipe and formula management?
It handles recipes through Production BOMs with fixed quantities. It doesn't natively handle formula management, meaning percentage-based scaling, potency, or co-product and by-product yields, which process food manufacturers usually need.
What's the difference between a Production BOM and a formula?
A Production BOM lists fixed ingredient quantities for a manufactured item. A formula is percentage-based, scales dynamically to a target output or concentration, and accounts for co-products and by-products, which is closer to how process food production actually runs.
Do I need an ISV extension for food manufacturing in Business Central?
If your operation involves formulas, meaningful catch-weight volume, dynamic yield, or stage-by-stage QC, then yes. An extension like AgriERP adds those capabilities natively on top of Business Central without leaving the Microsoft stack.
Ready to see where your food manufacturing operation stands?
Native Business Central gets a lot of food manufacturers further than they expect. Recipes, catch weight, and yield are where the gaps show up. If you've hit any of them, the fix is to extend Business Central, not rip it out.