Manufacturing ERP for mid-size companies, with published prices

Every price on this page comes from the vendor's own published pricing page, linked in the sources section. Where a vendor does not publish a figure, we write "not published" rather than estimating. There are no star ratings, no invented review scores and no ranking that puts one product first — because the right answer changes with headcount, process complexity and where you operate.

Comparison table

Figures are the values shown on each vendor's own pricing page at the time of checking and vary by country and billing term. Microsoft notes its published prices are informational and may not reflect actual list price by region.

The options one by one

MRPeasy — depth of manufacturing function at a low entry price

MRPeasy publishes four per-user tiers: Starter $49, Professional $69, Enterprise $99 and Unlimited $149 per user per month, with a two-user minimum on Unlimited. It also publishes a bulk rule: from the 11th user onward, $79 per 10 users.

What matters more than the headline number is where features sit. Production planning, bills of materials, drag-and-drop rescheduling, lot traceability, warehouse and CRM are already in Starter. Barcode scanning, backward production scheduling, master production schedule, maintenance management, multiple stock locations, multiple production sites and the approval system all begin at Enterprise. API and webhooks sit in Unlimited.

A good fit when: you are a 5-15 user manufacturer trying to get BOM and work-order discipline in place, and you want to know exactly what you are buying — the tier contents are published in detail. A poor fit when: you need integrations, because API access sits at the top tier and roughly triples the effective per-user cost, or when many shop-floor operators each need a login.

Katana — flat pricing for teams with many users

Katana publishes a Free plan ($0, up to 30 SKUs), Core from $299/month and an Advantage tier on an annual contract whose price is not published. The important detail in Core is that users are unlimited and one inventory location is included.

The add-ons are published too, and they change the real total: Manufacturing Management $199/month, Traceability $249/month, Warehouse Management $149/month, plus optional onboarding at $2,000 one-time. So $299 is a floor, not a configuration price — build your comparison from the add-ons you actually need.

A good fit when: you have 20 or more people who need access but a fairly standard process; per-head cost falls quickly because seats are free. A poor fit when: you are a small workshop with one or two users, where the $299 floor stays expensive, or when you need deep cost accounting.

Odoo — breadth of modules at the lowest per-user price

Odoo publishes three plans: One App Free (€0), Standard at €11.90 per user per month billed yearly (€14.80 monthly) and Custom at €17.90 per user per month billed yearly (€22.40 monthly). Both paid plans include all apps — manufacturing, inventory, purchasing, project and field service arrive at the same per-user price.

The Standard-versus-Custom line is the one that decides most manufacturing projects. Odoo's own page lists three things that only Custom adds: Odoo Studio, Multi-Company and External API. If you will integrate with a machine, a WMS or an accounting system, or if you run more than one legal entity, Custom is mandatory and your per-user cost rises by roughly 50%. Hosting options — Odoo Online, Odoo.sh or on-premise — are published on the same page.

A good fit when: you need many modules at once, have 5-25 users and operate internationally. A poor fit when: you want deep, out-of-the-box manufacturing scheduling with no implementation partner; breadth and depth are different things, and Odoo's strength is breadth.

Dynamics 365 Business Central — for companies already inside Microsoft

Microsoft publishes Essentials at $80.00 per user per month billed yearly, Premium at $110.00 and Team Members at $8.00. Manufacturing and service management sit in Premium, so a manufacturer should build the budget on the $110.00 line, not the $80.00 one.

Team Members is the tier most people overlook. It is intended for people who read records, approve, or enter limited data — which describes a large share of headcount in many plants. Getting the licence mix right is where the money is.

Microsoft adds a note on the same page: published prices are informational and may not reflect actual list price because of currency, country and regional variation.

A good fit when: Microsoft 365, Power BI and Azure are already in place and you report internationally. A poor fit when: more than 30 production staff each need full licences — per-user monthly cost is the fastest-growing line in a labour-heavy plant.

Acumatica — a different billing unit, no published numbers

Acumatica publishes no prices. Its pricing page describes a consumption-based model and states plainly that you "Pay only for the functionality you need—not for user seats", with price shaped by which applications you license, your business usage and resources, and your deployment option. It then routes you to a custom pricing review.

A good fit when: you have a large number of light users and a moderate transaction volume — the billing unit works in your favour. A poor fit when: you need a budget number before you engage with sales, or when procurement requires published list pricing for comparison.

Custom-built manufacturing systems (where KodDelta sits)

A custom build is not a better category, it is a different one: you pay once to have the process encoded the way your plant actually runs, instead of paying monthly to adapt to someone else's data model. KodDelta publishes its bands: $3,000-6,000 for a single-process solution (2-4 weeks), $8,000-15,000 for a multi-module corporate system (4-8 weeks), $20,000+ for an end-to-end platform (3-6 months), and $5,000-12,000 for a retrieval-augmented AI assistant over your own documents. Maintenance is optional at 12-25% per year. There is no per-user charge and no user cap.

A good fit when: subcontract routing, mould life, batch merging, machine-level scrap or customer-specific quality forms keep forcing workarounds in a package; when headcount is growing; when source code ownership is a contractual requirement. A poor fit when: your process is standard and you need something running next week — a package installs the same day, while the fastest custom build takes 2-4 weeks. We also advise against writing statutory accounting and tax filing from scratch; packaged products track that legislation far more cheaply than any bespoke build can. We say so at the quotation stage rather than after the contract.

Which one, in which situation

Three lines that break most comparisons

• Headcount growth. Per-user models triple in cost when you go from 10 to 30 people. Per-company and custom models do not move at all. Run the arithmetic twice: today's headcount and your three-year headcount.
• The tier that unlocks what you need. Odoo's API and Studio sit in Custom; MRPeasy's API sits in Unlimited; Business Central's manufacturing sits in Premium; Katana's manufacturing depth sits in a $199/month add-on. Comparing entry tiers compares products you would never actually buy.
• Localisation and compliance. None of the published feature lists here cover Turkish e-invoicing, and country-specific tax handling is usually partner work. If you operate across borders, that line belongs in the budget from day one.

To map your own scope onto published bands, see our pricing page, and for the packaged-versus-custom trade-off in more depth, our package vs custom comparison.

This page compares products and their published prices. Whether the shop floor needs an execution layer at all — and what an ERP genuinely cannot record — is a separate question, answered in MES vs ERP: which system should track the floor.

Sources

• MRPeasy Pricing (mrpeasy.com)
• Katana Pricing (katanamrp.com)
• Odoo Pricing (odoo.com)
• Dynamics 365 Business Central Pricing (microsoft.com)
• Acumatica Pricing (acumatica.com)
• KodDelta pricing and delivery bands

Sources checked in August 2026. Vendors change prices without notice and promotional rates are temporary; verify the linked page before deciding. Product names belong to their respective owners; KodDelta is not a partner or reseller of any vendor listed here.

Frequently asked questions

What does manufacturing ERP actually cost for a mid-size company?

Published entry prices differ by an order of magnitude because the models differ. MRPeasy publishes $49/user/month for Starter. Katana publishes Core from $299/month with unlimited users. Dynamics 365 Business Central publishes $80.00/user/month for Essentials and $110.00 for Premium, which is the tier that carries manufacturing. Odoo publishes €11.90/user/month billed yearly with all apps included.

Which vendors do not publish prices at all?

Acumatica publishes no figures; its pricing page describes a consumption-based model and states you pay for functionality "not for user seats", then routes you to a custom pricing review. Katana publishes Core but leaves its Advantage tier as custom, annual-contract pricing. When a vendor does not publish, we say so rather than guessing.

Per-user or per-company pricing — which is cheaper?

It depends entirely on headcount. Per-user pricing is cheaper for small teams and gets expensive fast on the shop floor, where many people need to record work. Per-company pricing, like Katana Core at $299/month for unlimited users, flattens that curve but sets a higher floor. Model both at today's headcount and at your three-year headcount before deciding.

When is a custom manufacturing system the right answer?

When the process does not fit the package data model — subcontract routing, mould life tracking, batch merging, customer-specific quality forms — and you keep solving it with spreadsheets beside the ERP. KodDelta publishes bands for this work: $3,000-6,000 for a single process, $8,000-15,000 for a multi-module system, $20,000+ for an end-to-end platform.

Does API access cost extra?

Often yes, and it is easy to miss. Odoo places its External API in the Custom plan only, alongside Odoo Studio and multi-company. MRPeasy places API and webhooks in its Unlimited tier at $149/user/month. If you plan any integration, run the comparison at the tier that actually includes API access.

How should maintenance and upgrades be budgeted?

With subscriptions, the payment simply never stops — that is the maintenance model. With one-time licences and custom builds, maintenance is a separate, optional line. KodDelta publishes maintenance at 12%, 18% or 25% per year of the project value; skipping it leaves the system running, it only stops updates and new features.

Test your own situation in three questions

1. How many people will be entering data in three years? Under 15 and per-user pricing is comfortable. Over 25 and you should put a per-company or custom model in the same table — that is where the curves cross, and the gap only widens after that.
2. How many spreadsheets do you keep alongside the ERP? Each one marks a place the package does not fit. Two or three can be absorbed by configuration; more than five usually means the data model is wrong for your plant, and configuration will keep costing you at every upgrade.
3. Which tier actually contains what you need? Write down manufacturing depth, API access and multi-entity separately, then find the tier that carries all three. Comparing entry tiers you would never buy is the most common way these decisions go wrong.

If at least two answers land on the "large headcount, non-standard process" side, a custom build is worth pricing. If they do not, one of the packaged products above will be cheaper and faster — and we will tell you that directly.