A food and beverage distributor we talked with last week had a sharp list of must-have features, and a fair question behind it: would Business Central do all of these out of the box, or were some of them going to be a struggle? It's a question worth answering directly up front, because the answer shapes both your licensing and your project budget.
If you're evaluating Microsoft Dynamics 365 Business Central (Microsoft's enterprise resource planning, or ERP, system for small and mid-sized businesses), here's the short version: Business Central is built as a general-purpose platform, and Microsoft relies on its partner and ISV network to extend it for specific industries. ISV stands for independent software vendor, basically a third-party company that builds add-ons that plug into Business Central.
What Business Central does natively, and what it doesn't
Business Central handles core finance, inventory, purchasing, sales, and warehouse functions well right out of the gate. Where food and beverage companies tend to hit gaps is in the industry-specific stuff that the generic platform was never designed to cover on its own.
On this call, the features that came up as known gaps included things like catch weight, off-invoice discounts, bill-back allowances, and scan-down allowances. These aren't obscure requests in food distribution, they're everyday needs. They just aren't part of the base product.
Catch weight is when a product is priced by weight but sold by the case or unit, so the actual weight varies from item to item. Business Central doesn't handle this natively, but several ISVs have built solutions for it.
How an ISV fits in
The key thing to understand is that an ISV doesn't bolt a separate system onto the side of your ERP. You're still working in one platform. The ISV extends Business Central's capabilities so the industry-specific features live right inside the same system your team uses every day. There's no second login, no separate vendor to chase, and your IT partner owns the whole integration end to end.
For a given gap like catch weight, there can be eight or more ISVs that have built a solution. Part of the implementation work is selecting the right one for your exact needs, then quoting and integrating it properly.
The part buyers often miss: licensing and hours
Here's where it pays to ask the question this client asked. An ISV carries its own licensing cost, separate from and on top of your Business Central licensing. It also takes implementation hours to configure and integrate. Both of those should be spelled out before you sign anything.
| Cost component | What it covers |
|---|---|
| Business Central licensing | The core ERP platform and base functionality |
| ISV licensing | The third-party extension that fills industry-specific gaps |
| Implementation hours | Setup, configuration, and integration of the ISV alongside Business Central |
A good statement of work names the specific ISV, lists its licensing inside your overall licensing matrix, and either includes the implementation hours or calls them out distinctly. You should not be surprised by a separate software charge after the project starts.
A few questions worth asking your implementer
- Which of my requirements are native to Business Central, and which need an ISV?
- Which specific ISV are you recommending, and why that one over the alternatives?
- What is the ISV licensing cost, and is it reflected in my proposal?
- Are the implementation hours for the ISV included in the project fee?
- Who owns the integration if something breaks later?
The takeaway
Business Central plus the right ISV can absolutely cover food and beverage needs like catch weight and trade allowances. The right move is to map those gaps early, pick the extension deliberately, and put the full cost picture in front of you before you commit. If you're weighing Business Central for a food and beverage operation and want to talk through which gaps you'd run into, we're happy to walk through it with you.