SAP Business One has no public price: its official page only offers “Contact us” or “Request a quote”, and what SAP Business One really costs an SME depends on the number and type of named user licenses, the deployment model (on-premise or cloud), add-on modules and implementation days. To get an accurate figure, you need to work out the total cost over five years, quote in hand, rather than look for a price per user.
This article therefore gives no amount for SAP that does not appear on an official page from the vendor. It shows what the bill is made of, which questions to ask whoever prices it for you, and how to set the result against an ERP whose price list is public, Odoo. SAP Business One remains a serious product, with solid, proven accounting. The issue is not its quality, it is how readable its price is.
Why does SAP not display any price for Business One?
On the product's French page, SAP presents Business One as a solution for SMEs and midsize companies, used by more than 85,000 customers worldwide. The vendor states that “there is no minimum size required” and highlights cloud or on-premise deployment options. The page, however, shows no pricing at all.
“SAP Business One is an affordable, all-in-one ERP system for small and midsize businesses.” (SAP, official SAP Business One page, 2026)
“Affordable”, then, but with no amount. The price is built case by case, at quote time, and in practice with an SAP partner who puts together licenses, services and add-ons. Two SMEs of the same size can therefore receive very different proposals.
For a business owner, the consequence is concrete: the only reliable figure is the one on your quote, provided you know how to read it. A price found on a forum or in an article takes into account neither your number of users, nor their rights, nor your modules, nor your hosting.
You when you clicked “Request a quote” and are still waiting to find out how much a license costs.
Which SAP Business One licenses do you need?
First cost item: the user license. SAP Business One is licensed per named user. The licensing guide published by SAP for version 10.0 says so plainly:
“SAP Business One is based on a named user licensing model, in which each license is assigned to a specific user name.” (SAP, License Guide for SAP Business One 10.0, 2019)
The same guide states that named licenses cannot be shared between employees. In practice: three pickers who take turns at the same shipping station means three licenses, not one. Before asking for a quote, list the people who will actually use the software, not just the workstations.
The guide then distinguishes several license types, with different rights. Depending on the type assigned, a user has full control of a screen, opens it in read-only mode or has no access to it at all. The types listed are:
- the Professional license;
- limited licenses, focused on one area as their name suggests: Limited Financials (finance), Limited Logistics (logistics) and Limited CRM (customer relationship management);
- the Starter Package, an entry-level offer that cannot be combined with the other license types in the same license file.
Take a fictional SME with 30 employees and 12 users: two accountants, four sales reps, four people in logistics, the CEO and an assistant. The quote depends on the split between Professional licenses and limited licenses, and on who gets what. An accountant, a field sales rep and a warehouse worker do not need the same rights. Ask for the breakdown by type and by person, never a total.
Two other rules in the guide matter for a growing SME. Licenses are specific to a localization: a subsidiary in another country gets its own license file, and its users only access the companies in that country. And the Starter Package does not mix with other licenses: the guide provides for upgrading it to other types, a change to have priced the day the company outgrows this offer.
This guide dates from 2019: have your SAP contact confirm the rules that apply to your version and your contract.
What does the total cost include, beyond licenses?
The license is only the visible part. Over five years, the cost of an ERP is made up of items found with every vendor, but each offer splits them up its own way. For SAP Business One, four items deserve their own line in your spreadsheet.
Support and maintenance
With a perpetual license, annual maintenance is added to the purchase price every year. It is a recurring cost that runs as long as you use the software. Its amount, its calculation basis and how it is revised over time must be spelled out in black and white in the quote. The licensing guide states that the number of users under contract is the basis for the maintenance contract, and that returning unused licenses does not reduce that number. One can infer that a license bought in excess keeps weighing on maintenance: a point to have confirmed for your contract. With a cloud subscription, the question becomes: what is included in the monthly price, and what is billed separately?
Infrastructure
On-premise, you need a server, its backup and a database, Microsoft SQL Server or SAP HANA depending on the version chosen. These costs are not always in the software quote: they may fall to your IT provider. In the cloud, ask what the offer includes: hosting, backups, test environment, version upgrades.
Add-on modules
Depending on your business, some functions go through add-on modules, from third-party vendors or from SAP itself. Our comparison notes some in particular for point of sale, the online store, barcode order picking or finite-capacity production scheduling. Each module has its own license, its own maintenance and its own update cycle. SAP's licensing guide adds a rule worth knowing: any user who goes through a module not registered with SAP must also hold a valid user license.
Implementation services
Finally, service days: configuration, data migration, training, custom development. They depend less on the software than on your scope and the quality of your data.
This split between upfront investment and recurring costs applies to any ERP. For Odoo, we break down the first-year budget, the budget for the following years, the pitfalls that drive up the bill and the funding options, on a page you can read here: how much an Odoo project costs, and how to fund it.
What questions should you ask to read an SAP Business One quote?
A detailed quote can be compared. A lump-sum quote compares to nothing. Before signing, ask these questions in writing and request a priced answer for each one.
| Item | Question to ask | Why |
|---|---|---|
| Licenses | How many licenses of each type, and for whom? | The amount depends on the number of licenses of each type. |
| Purchase model | Perpetual license or subscription, and for what commitment period? | The two models can only be compared on cumulative cost. |
| Maintenance | What amount each year, on what basis, revised how? | It is a recurring cost that runs as long as the software is in use. |
| Infrastructure | Who hosts, who backs up, who pays for the database? | On-premise, these costs may fall outside the software quote. |
| Third-party modules | Which modules, from which vendor, with what annual license? | Each one adds to the bill and to version upgrades. |
| Connections | Which tools will read from or write to SAP, and with which licenses? | SAP's guide provides a license type for indirect access. |
| Services | How many days, for what written scope? | Without a written scope, a number of days commits no one. |
| Version upgrades | Who revalidates third-party modules and custom developments with each version? | Each version upgrade becomes a small project to budget for. |
With these answers, build a five-year table: the first-year cost, then the recurring annual cost, year by year. It is the only way to compare a perpetual license with a subscription, or two partners who do not split up their offer the same way. Compare five-year totals, not license prices: maintenance, third-party modules and version upgrades are paid every year.
One last tip: have each vendor price the same scope in writing. Same users, same functions, same hosting. Without this common basis, you are comparing promises, not prices.
You when you put two ERP quotes side by side and one of them “forgot” the maintenance for the next five years.
What would the same SME pay on Odoo?
Odoo makes the opposite choice: its price list is public. On odoo.com, the Standard plan costs €19.90 per user per month with an annual commitment in the first year, then €24.90 (Custom: €35.90 then €44.90). Calculating the license therefore comes down to one multiplication: number of users times the public price. According to the FAQ on the same page, customers and suppliers who use the portal are not paying users; an employee registered in Odoo without a user account, however, is billed.
According to Odoo's pricing page, the Standard and Custom plans include all apps for a single price: sales, accounting, inventory, website, point of sale and many more. Point of sale and the online store are not modules to buy on top. Adding an app later does not change the license price, except Studio, which moves you to the Custom plan.
The Custom plan adds, among other things, Odoo Studio, multi-company management, the external API and a choice of hosting: Odoo Online, Odoo.sh or your own servers. An SME whose other software needs to read from or write to Odoo through the API, or that manages several companies in one database, therefore starts on this plan. The FAQ specifies that connections initiated from Odoo (online payment, carriers, bank synchronization) fall under the Standard plan. Like indirect access with SAP, this is a question to ask from the start.
Let's be clear: the license is not the whole budget. The pricing page states that all plans include support, hosting and maintenance provided by the vendor, but that the cost of Odoo.sh hosting is not included. On top of that come the credits used by artificial intelligence features, bought separately, and above all the project: configuration, data migration, training, then ongoing support after go-live. The difference with SAP Business One comes down to readability: the software price is known before any sales conversation; what remains is pricing the project.
Price is only one criterion among others. We compared the two software packages feature by feature, across eight areas, from accounting to point of sale, including manufacturing and customization, with the cost ranges observed on the SAP side: you will find this work in our Odoo 19 vs SAP Business One comparison.
Switching ERP: how do you compare over five years without getting it wrong?
If you already run SAP Business One, the real question is not the price of a license. It is the cost of staying, compared to the cost of leaving. Staying means maintenance or the subscription, third-party modules and version upgrades. Leaving means a project: data migration, new habits for your teams, a period of close monitoring after go-live.
Let's go back to our fictional SME and assume it is a wholesaler, with a point of sale in its showroom and an online store for its business customers. On the SAP Business One side, the quote must price licenses by type, maintenance, hosting, then the point-of-sale and online store add-ons, with their own licenses. On the Odoo side, these two functions are apps included in the subscription: the software budget is calculated from the public price, before any Odoo.sh hosting and the project.
The migration itself should not be oversized. SAP Business One data is stored in a SQL Server or HANA database, so it is readable. The trap lies elsewhere: the temptation to migrate everything, ten years of history included. We explain which data to migrate, and why full history costs a lot for little use, on this page: migrating your data to Odoo without holding up go-live.
Custom developments written for SAP Business One do not carry over: they rely on SAP's proprietary development kit. You carry over the business rule, not the code, and a good part of it can be rebuilt through configuration or automation.
Finally, do not compare two software packages in the abstract. Compare them on your real processes: your sales cycle, your inventory, your month-end close. On the Odoo side, that is the role of an audit and scoping phase, which tests your flows against the software's standard features and turns a vague intention into a priced plan. How it unfolds (role of the project lead and key users, gap analysis, trade-offs, deliverables) is described here: how an Odoo audit works.
In short, SAP Business One does not cost “so much per user”. It costs the sum of named user licenses by type, maintenance or a subscription, infrastructure, add-on modules and service days. Demand every line, calculate over five years, and set the total against a public price list. The decision becomes a calculation, no longer a gamble.
- SAP, official “SAP Business One” page (France), accessed October 17, 2026: https://www.sap.com/france/products/erp/business-one.html
- SAP, “License Guide for SAP Business One 10.0”, 2019: https://help.sap.com/doc/14c6d92982fd4a9dbf7df66b5108433b/10.0/en-US/LicenseGuide.pdf
Article written by Billy Felicie
Odoo integration expert at Hors du Commun (Lyon). I have been helping SMEs implement their digital tools and optimize their business processes for more than 5 years.