Dynamics 365 Business Central Pricing for a 35-User Manufacturer, Worked Through
A labelled five-year bill for a 35-user manufacturer comes to roughly $600,000, and licences are under 30% of it. Here's where the rest goes and which lines you can negotiate.
Why the licence price is the smallest decision in the deal
If about 35 people at your manufacturing company need to touch the ERP, Dynamics 365 Business Central pricing looks simple on Microsoft's price list: a monthly fee per full user, a much smaller one for light users. The real five-year bill doesn't work that way. In the hypothetical model below, subscription licences are about 28% of total cost. Partner services and third-party (ISV) apps make up most of the rest.
This article builds that bill line by line: the full-user vs Team Member split, the Essentials vs Premium decision, implementation fees, EDI and shop-floor add-ons, extra environments and storage, and renewal increases. Every figure is a typical 2026 market range that varies by contract, country and reseller. Use the numbers to sanity-check a quote, not to replace one. Confirm current list prices with Microsoft or your Cloud Solution Provider (CSP) partner before you budget.
Three list prices anchor the model, and they're approximations: about $80 per user per month for Essentials, $110 for Premium and $8 for Team Members, on annual commitments. Microsoft has adjusted list prices before and can do so again, which is why the renewal assumptions later matter.
Splitting 35 people into full users and team members
Most licence savings come from deciding who really needs a full seat. Business Central is licensed per named user, not per concurrent user. If 35 people log in, you need 35 licences of some kind. The question is which kind.
A full user can post transactions in the areas their tier allows: purchasing, sales, production, inventory, finance. A Team Member can read broadly, approve or reject workflow items, edit existing records such as customer or item cards, and create some documents, such as quotes, that a full user then processes. They can't post invoices, release production orders or run MRP.
Here's how our hypothetical 35-user manufacturer splits its seats:
- 22 full users: finance (5), purchasing and planning (4), sales order processing (5), production management and scheduling (4), warehouse leads who post receipts and shipments (4).
- 13 team members: department managers who approve purchase orders, quality staff who look up lots and update item records, the owner and two executives who read dashboards, and a few engineers who maintain item data.
Don't let anyone default everyone to full seats. Don't push too hard the other way either. If a warehouse lead is licensed as a Team Member but has to post a shipment, you'll buy a full seat anyway, usually in a hurry. For each borderline person, write down the three transactions they perform most often and check them against Microsoft's current licensing guide. Shared shop-floor terminals are a separate case: a device licence, or a shop-floor app licensed per device, can beat a named seat for every operator. Ask your partner to price both.
Business Central Essentials vs Premium when you run production orders
The Essentials vs Premium question usually turns on one test: do you need production orders, routings, capacity planning or service management? Essentials covers finance, sales, purchasing, inventory, warehousing, project jobs and assembly BOMs. Premium adds manufacturing: production BOMs, routings, work and machine centers, MRP and capacity planning, plus service management.
A light assembler that builds kits to order from stocked components can often run on Essentials with assembly orders. A company with multi-level BOMs, work-in-progress tracking, scheduled work centers or backflushing needs Premium.
The cost gap is about $30 per user per month at the list prices above. If all 22 full users in our model were on Premium rather than Essentials, that's 22 × $30 × 12, or about $7,900 a year. Microsoft's licensing guide has generally allowed Essentials and Premium users to coexist in one tenant, with Premium needed only for people who use Premium functionality. Confirm that with your partner for your exact setup. If it holds, say 12 of the 22 touch production, routings or service, and 10 stay on Essentials. The saving is roughly $3,600 a year, but only if those 10 never need a manufacturing screen.
For a true discrete or process manufacturer, Premium is the right call for the production team. Some companies run production in spreadsheets or a separate MES to stay on Essentials. That usually costs more in reconciliation work than the licence saving. Essentials for production users makes sense only when production is really assembly, or when a third-party manufacturing app covers the shop floor and your partner confirms in writing that it doesn't depend on Premium objects. The model below conservatively licenses all 22 as Premium.
The hypothetical five-year bill, line by line
Hypothetical example. Say a 35-user discrete manufacturer with $40–60 million in revenue, one legal entity, one plant and a few large retail and distributor customers who require EDI. It licenses 22 Premium full users and 13 Team Members, uses one partner for implementation and ongoing support, and adds four ISV apps. We assume a 5% yearly increase on subscriptions, a planning figure, not a forecast. Figures are in USD and rounded.
| Cost line | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | 5-year total |
|---|---|---|---|---|---|---|
| Licences (22 Premium + 13 Team Members) | 30,288 | 31,802 | 33,392 | 35,062 | 36,815 | 167,359 |
| Extra environment and storage | 1,500 | 1,575 | 1,654 | 1,736 | 1,823 | 8,288 |
| ISV add-ons (EDI, scheduling/shop floor, document capture, reporting) | 34,500 | 36,225 | 38,036 | 39,938 | 41,935 | 190,634 |
| Partner implementation (one-off) | 150,000 | – | – | – | – | 150,000 |
| Partner support and release testing | 8,000 | 20,000 | 20,000 | 20,000 | 20,000 | 88,000 |
| Total | 224,288 | 89,602 | 93,082 | 96,736 | 100,573 | 604,281 |
That's about $288 per user per month over five years, against a $110 Premium list price. Here's what drives each line.
Business Central implementation cost
We used $150,000. For a single-entity manufacturer with EDI, a realistic range is $90,000–$220,000. Where you land depends on how messy your BOM and routing data is, how many custom extensions you need, and how many EDI trading partners must be mapped and certified. Partner day rates commonly run $1,000–$1,800 in North America, the UK and Western Europe, and often $300–$800 in India, Eastern Europe and parts of Southeast Asia, though onshore project management narrows that gap. Data migration and testing are the lines buyers underestimate most.
Business Central ISV add-ons
Here the add-ons cost more than the Microsoft licences. That's common in manufacturing and distribution. Typical 2026 annual ranges:
- EDI connector plus VAN or translation service: $10,000–$30,000, scaling with trading partners and document volume. We used $18,000.
- Visual production scheduling or shop-floor data collection: $4,000–$12,000. We used $7,000.
- AP document capture and expense workflow: $3,000–$7,000. We used $4,500.
- Reporting and analytics beyond Power BI basics: $3,000–$8,000. We used $5,000.
Many ISVs price per Business Central user, so each full seat you add costs you twice: once to Microsoft and once to the ISV.
Environments, storage and support
Microsoft includes a production environment, some sandboxes and a base database storage allowance that grows with licence count. We budgeted one extra production environment for UAT or training, plus modest storage overage as transaction history and attachments accumulate. The support line covers questions, small fixes, and regression testing of your extensions and ISV apps before each of Microsoft's two major releases a year. Microsoft runs the upgrades. Your partner confirms nothing breaks.
The model excludes internal costs: backfill for key users during the project, travel, and any Power BI Pro or Microsoft 365 uplift. Budget those separately.
Where pricing moves by country, reseller and contract
The same 35-user bill can look quite different depending on where you buy. Four factors matter.
Local-currency price lists. Microsoft publishes regional price lists in EUR, GBP, INR, AUD and other currencies and adjusts them periodically, so a local price won't always match the USD figure at today's exchange rate. VAT or GST usually applies on top. Whether you can recover it depends on your local tax position, so ask your tax adviser.
CSP partner margins and terms. Most buyers purchase through a CSP reseller, which sets its own price around Microsoft's list. Discounts are usually modest at 35 seats. Payment terms, monthly vs annual billing on an annual commitment, and how easily you can reduce seats all vary by reseller. Get them in writing.
Localization and e-invoicing. Business Central offers Microsoft-provided localizations in many countries. Other markets rely on partner-built localization apps with their own subscription fee. Compliance adds more: India's GST e-invoicing, Saudi Arabia's ZATCA e-invoicing, Mexico's CFDI, Italy's SDI and the broader European move toward mandatory B2B e-invoicing can each call for a connector or service, often in the range of $2,000–$10,000 a year. If you operate in one of these countries, add that line.
Data residency. Your tenant's data sits in a Microsoft region. If you have strict residency obligations, as in some Middle East, European or Asian jurisdictions, confirm which region your tenant will use before you sign. Moving it later is a project in itself.
Red flags and negotiation points before you sign
Most of the money in this bill isn't on Microsoft's price list, and that's where you have room to negotiate. Before signing, check the following:
- Ask for a named-user licensing matrix, not a seat count. If the partner can't say who gets a full seat and who gets a Team Member seat, the quote is a guess. Expect to need more full seats later.
- Get the Essentials vs Premium split confirmed in writing, along with confirmation that every proposed ISV app works on the tier you're buying.
- Push back on open-ended time-and-materials quotes. Ask for fixed-price phases, or at least a capped estimate for data migration and EDI partner onboarding. Overruns usually start there.
- Check renewal terms for every ISV. Find out whether they price per user, how much notice they give before an increase, and whether you can drop seats at renewal. A 5% assumption is just that. Some apps rise faster.
- Limit custom code. Every custom extension adds testing work twice a year. A partner who proposes heavy customization of standard processes is raising your support costs.
- Plan for Microsoft price changes. You can't negotiate the list price. You can negotiate how long your CSP holds its price after a Microsoft change, and the start date of your annual term.
Decision rule: get two partners to quote against the same 35-person licensing matrix and the same add-on list, then compare five-year totals, not year-one totals. If one partner's five-year number is more than 25% below the other's, ask what they've left out before you assume they're cheaper.
Common questions
Can we mix Business Central Essentials and Premium users to save money?
Microsoft's licensing has generally allowed both tiers in one tenant, with Premium needed for users who work with manufacturing or service management functionality. Rules change, so have your partner confirm the split in writing. Team Members are a separate, cheaper licence and can sit alongside either tier.
What does a Business Central implementation typically cost for a 35-user manufacturer?
For a single-entity manufacturer, partner fees typically fall between $90,000 and $220,000 as a 2026 market range. Data quality, custom extensions and the number of EDI trading partners drive most of the spread. Partner rates also vary a lot by country, so get fixed-price or capped quotes from at least two partners.
Do we pay extra when Microsoft releases Business Central updates?
Microsoft runs the major updates, which arrive twice a year, without a separate licence charge. You still pay your partner to test custom extensions and ISV apps against each release. Budget that as part of an annual support agreement.
How much do Microsoft ERP licensing prices change at renewal?
Microsoft has adjusted Business Central list prices in the past, and ISVs change theirs independently, sometimes more often. A 3–7% yearly planning assumption on subscriptions is reasonable. Before you commit, ask your CSP and each ISV to state in writing how they handle notice periods and price protection.
Written by the Cargodeskflow editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.