ERP pricing 2026: every published number, one table

Most ERP pricing articles are estimates dressed as facts. This one only contains numbers the vendor published on its own page, each linked in the sources section. Where a vendor publishes nothing, that is recorded as a finding rather than filled in with a guess — because "does not publish" is itself useful information when you are planning a procurement.

The published price table

Figures are the values shown on each vendor's own pricing page at the time of checking. Microsoft notes its published prices are informational and may not reflect actual list price by currency, country or regional variant. Odoo prices shown were published in euros on the regional pricing page.

Add-ons and tier gates that change the total

The entry number is rarely the number you pay. These are the published lines that most often move a budget:

How the four billing models behave

The reason ERP price comparisons go wrong is that the products are not billed in the same unit. There are four models in this market and each has a different shape over time.

• Per user, per month. Cheapest to start, and directly proportional to headcount forever. Growing from 10 to 30 users triples the bill. Best when your user count is small and stable, or when a large share of your people qualify for a cheaper light-user licence.
• Per company, per month. Higher floor, flat ceiling. Katana Core at $299/month with unlimited users is the clearest published example. Excellent when many people need access and the process is standard; poor for very small teams.
• Consumption or volume based. Acumatica prices by applications, usage and resources rather than seats; Procore prices by annual construction volume with unlimited users. Both can be favourable for headcount-heavy operations, but neither publishes numbers, so you cannot budget before a quote.
• One-time project fee. Highest on day one, flattest afterwards, with maintenance optional rather than mandatory. This is the custom development model, and it is the only one where the cost does not move when you hire.

Normalising is straightforward: pick a horizon of five years, take your three-year headcount, choose the tier that genuinely contains what you need, and multiply out. Then add implementation, localisation and configuration to every option — including the custom one — because those lines exist regardless of which side you choose.

What almost nobody publishes

1. Implementation and data migration. Effectively no ERP vendor publishes a fixed price for this, and it is frequently comparable to a year or more of licence cost. Ask for it in writing before signing anything.
2. Localisation. Country-specific tax handling and mandatory electronic invoicing regimes are typically partner work, and none of the international products above list them as included features.
3. Configuration maintenance. Every field and automation you add has to survive the next version. This is a real recurring cost that appears on no price list.
4. Exit. What it takes to get your data out in a usable form, and in what format. Worth establishing at the start rather than at the end.

Where custom development fits

Custom development is not a cheaper ERP; it is a different trade. You pay once, there is no per-user fee, and the data model is shaped around your process instead of the other way round. KodDelta publishes its bands openly: $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, and source code is delivered under contract.

Where it does not win: breadth and speed. No custom build matches an all-apps subscription for module coverage per euro, and nothing beats a packaged product for being live the same day. We also advise keeping statutory accounting and tax filing in a packaged product; buying legislation tracking is always cheaper than building it. The pattern that works most often is a packaged core with a custom edge — and knowing where to draw that line is the actual decision.

Test your own situation in three questions

1. What is your headcount in three years, and which tier do you truly need? Multiply those two together across sixty months. If you skip this and compare entry tiers, you are comparing products you would never buy.
2. How many of your requirements are missing from every published feature list? Write them down. Zero to five means configure and move on. More than fifteen means you are about to build a bespoke system inside someone else's framework, and should at least price building it properly.
3. What is your implementation budget, separately from licences? If you cannot answer this, the comparison is not ready yet — it is the line that most often doubles a project and the one no vendor publishes.

Bring those three numbers and the decision resolves quickly. If they point to a packaged product, we will say so plainly rather than proposing a build that should not happen.

Sources

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

Sources checked in August 2026. Vendors change prices without notice and regional rates differ; 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

Which ERP vendors publish their prices?

Odoo, Microsoft (Dynamics 365 Business Central), MRPeasy, Katana, Jobber, Housecall Pro and Fieldwire all publish rates on their own pricing pages. Acumatica, Procore and ServiceTitan publish none and require a quote. Katana publishes its Core tier but leaves Advantage as custom pricing.

What are the four ERP billing models?

Per user per month (Odoo, Business Central, MRPeasy); per company per month regardless of users (Katana Core); consumption or volume based (Acumatica by resources, Procore by annual construction volume); and one-time project fee (custom development). Comparing products across models without normalising to a five-year total is the most common budgeting mistake.

Which model is cheapest?

None universally. Per-user pricing is cheapest at small headcount and worst at large headcount. Flat per-company pricing sets a higher floor and a lower ceiling. One-time fees are highest on day one and flattest thereafter. The crossover depends on your user count and your time horizon, which is why every serious comparison ends in arithmetic, not opinion.

What is usually missing from an ERP budget?

Four lines: implementation and data migration, which almost no vendor publishes; the tier upgrade needed to unlock API access or multi-company; country-specific localisation and electronic invoicing; and the ongoing cost of configuration, which has to be retested at every version upgrade.

Where does custom development sit on this table?

As a one-time fee with no per-user charge. KodDelta publishes $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 and $5,000-12,000 for a retrieval-augmented AI assistant, with optional maintenance at 12-25% per year. It wins on cost at large headcount and loses on speed and breadth.

How should I actually run this comparison?

Pick your three-year user count, choose the tier that genuinely contains what you need rather than the entry tier, multiply out sixty months, then add implementation, localisation and configuration to every option including the custom one. The winner is usually obvious once all four lines are on the same page.