SAP Business One is SAP’s ERP system for small and midsize companies. It is a separate product from S/4HANA, built on a different codebase, sold only through partners, and priced per user rather than through an enterprise agreement. It has been on the market since 2002 and now runs in more than 170 countries.
Most of what is written about it is either partner marketing or a feature list. This review concentrates on the two questions buyers actually ask and rarely get a straight answer to: what it costs across three years once maintenance and implementation are counted, and where the product stands in its support lifecycle right now.
Current release: SAP Business One 10.0, currently at feature package 2602 (February 2026), with support package 2605 following in May 2026.
Status: actively sold and actively developed. SAP reported more than 83,000 customers in December 2025 and around 3,000 net-new customers a year.
What is SAP Business One ERP?
SAP Business One is an ERP software solution for small and medium-sized businesses. The software was designed to simplify business processes and give organizations real-time insights into their business.
It consolidates all your data into one system so that you can make better decisions faster. The software includes financials, CRM, inventory management, and reporting features.
It runs on either Microsoft SQL Server or SAP HANA, and the choice matters: the HANA version carries a separately licensed runtime but brings in-memory analytics and full-text search that the SQL build does not.
Dashboard
SAP Business One pricing in 2026
SAP does not publish a public price list for Business One, and it does not sell the product directly. Every licence is bought through an authorised SAP partner, and each partner sets its own margin, hosting fee and support rate. That is why two quotes for the same ten users can differ by thousands of dollars, and why the numbers you find online rarely agree.
The figures below separate the two things that usually get mixed together: SAP’s underlying list price per licence, and what partners actually quote once hosting, support and margin are added. Treat them as benchmarks for checking a quote, not as a price you can order at.
SAP list prices per licence type
| Licence type | Perpetual (one-time) | Cloud subscription | Who it is for |
|---|---|---|---|
| Professional | €2,700 | €91 / user / month | Full read-write access to every module. The licence finance, operations and system administrators need. |
| Limited | €1,400 | €47 / user / month | Access confined to one functional area (logistics, financials or CRM). Sold per area. |
| Starter Package | €1,140 | €38 / user / month | Capped at five users and a reduced feature set. Cannot be mixed with other licence types. |
What partners actually quote
Partner quotes for the cloud edition run well above SAP’s list price, because the monthly figure bundles the licence with hosting, backup, updates and a support desk. Benchmark data collected in June 2026 puts the typical range at:
| Licence | Multi-tenant cloud | Single-tenant cloud |
|---|---|---|
| Professional | $188 / user / month | $219 / user / month |
| Limited | $112 / user / month | $158 / user / month |
| Starter | $110 / user / month | $149 / user / month |
Annual maintenance: the line item most quotes leave out
If you buy perpetual licences, the one-time fee is not the end of it. SAP charges annual maintenance of 18 to 20% of the original licence value, every year, and it is not optional if you want updates, patches and support. On a $21,000 licence purchase that is roughly $4,000 a year, indefinitely. Cloud subscriptions have no separate maintenance fee, it is already inside the monthly price.
What ten users actually costs over three years
Published prices are per user per month, which makes it hard to see what you are committing to. Here is the arithmetic for a common small-business configuration: ten users, three of them Professional (finance and admin) and seven Limited (sales and warehouse), priced at the midpoint of the partner ranges above.
| Cloud subscription | Perpetual on-premise | |
|---|---|---|
| Up-front licence | – | $21,301 (3 × $3,213) + (7 × $1,666) |
| Recurring licence cost | $15,900 / year (3 × $185) + (7 × $110), monthly | $4,047 / year maintenance at 19% |
| Licence cost, 3 years | $47,700 | $33,442 |
| Implementation (one-off) | $25,000 to $100,000 depending on complexity, applies to both models | |
Two things fall out of that arithmetic. First, implementation is the largest single cost in year one, and it is identical either way, so it is not a reason to choose one model over the other. Second, the perpetual route costs about $14,000 less over three years, and the crossover point is roughly 22 months: buy perpetual and you are ahead of the subscription from month 22 onward, assuming you stay on the product.
That comparison is deliberately licence-only, because the on-premise column carries costs the cloud column does not. You supply the server, the Windows Server and SQL Server licences (or the SAP HANA runtime licence, which is charged separately), the backup arrangement and the administrator time to run all of it. Add those and the real crossover moves out past two years. The honest summary: subscription is cheaper to start and simpler to run; perpetual wins on a long horizon if you already have infrastructure and someone to look after it.
Implementation and minimum commitments
Implementation is quoted separately by the partner and covers configuration, data migration, integration and training. Straightforward finance-and-distribution rollouts start around $15,000 to $25,000; manufacturing or multi-entity projects with custom integrations reach $100,000 and beyond. Benchmark three-year totals for a small deployment land in the $50,000 to $250,000 band once licences and implementation are combined.
Cloud subscriptions carry a minimum commitment, commonly three to five users for twelve months, depending on the partner and region. The Starter Package is capped at five users and cannot be combined with Professional or Limited licences, so a growing company usually has to migrate off it rather than add to it. Ask where that ceiling sits before you sign, because moving off Starter later is repriced at full rates.
Deployment and implementation
This offers two types of deployment: cloud and on-premise.
You cannot buy Business One from SAP directly. An authorised partner sells the licences, scopes the project, configures the system, migrates your data and provides first-line support afterwards, so the partner you pick shapes the outcome at least as much as the software does.
A typical small rollout runs three to six months from kick-off to go-live; manufacturing or multi-entity projects take longer. SAP maintains a public help portal covering configuration, upgrades and the extension framework, which is worth reading before you commit, because it shows honestly how much of the system is configuration work rather than something that arrives switched on.
Support and services
You will get the following support if you have a valid maintenance contract.
- 24/7 support for critical issues
- Support through support launchpad
- Proactive and automation support tools
- Upgrades to new feature and support packages at no extra licence cost
Is SAP Business One still supported in 2026?
Searches for Business One turn up a steady supply of “SAP Business One discontinuation” articles. They are misleading. They generally take the end of mainstream maintenance for one release family and present it as the end of the product, which are different things.
The product itself is not being retired. In December 2025 SAP put the installed base at more than 83,000 customers and 1.2 million users across 170-plus countries, supported by 850 partners, and said around 3,000 net-new customers pick the product each year, roughly ten a day. SAP’s chief partner officer stated at the same time that “SAP continues to invest in the future of SAP Business One.”
What does move is the release family underneath you. Since version 10.0 shipped in April 2020, SAP has delivered Business One as feature and support packages rather than as annually numbered releases. The naming is a plain year-month code: two feature packages a year in February and August, two support packages in May and November, so FP 2602 is February 2026 and SP 2605 is May 2026. There is no version 10.1, the number stays at 10.0 and the packages accumulate.
Each release family carries a defined mainstream maintenance window. For version 10.0 that window runs to 31 December 2028, and SAP marks its own dates as subject to change, they have already moved twice, from an original June 2025 out to December 2026 and then to December 2028, which is why older articles quote dates that have since lapsed. One thing that does not change: SAP does not offer paid extended maintenance for Business One releases, so there is no equivalent of the ECC extension to fall back on. SAP’s March 2026 road map has version 11 following version 10 in 2027, and SAP states the point directly on its support pages: “the end of mainstream maintenance refers to the version and not to the overall product.”
The practical implication for a buyer is narrow but real: your maintenance obligations and upgrade timing are tied to the release family, not to the contract date, so ask the partner which family you are being placed on and what the upgrade path off it looks like before you sign. Confirm current dates against SAP’s own maintenance documentation rather than a partner blog, since these dates have been extended before.
SAP Business One Modules
Here are some popular modules and their features.
Financial Management
- Accounting
- Controlling
- Fixed asset management
- Banking and reconciliation
- Financial reporting and analysis
Sales and Customer Management
- Sales and opportunity management
- Marketing campaign management
- Customer management
- Service management
- Reporting and analysis
- Mobile sales
Purchasing and Inventory Control
- Procurement
- Master data management
- Warehouse and accounting integration
- Accounts payable
- Reporting
Business Intelligence
- Report creation and customization
- Interactive analysis
- Intuitive tools
- Analytics with predefined metrics
- Powerful data visualization
Analytics and Reporting
- Dashboards and reports
- Real-time analytics
Other Features
- Mobile apps
- Web client
- In-memory platform
SAP Business One advantages
One database, no inter-module sync
Financials, stock, purchasing and sales share a single transactional database, so a goods receipt updates inventory valuation and the accounts payable position in the same posting. There is no overnight batch to reconcile and no integration layer between finance and operations to maintain, which is the specific pain most companies are trying to escape when they leave a bookkeeping package plus spreadsheets.
A large partner and add-on ecosystem
SAP counts 850 partners and more than 500 industry and country-specific extensions built on Business One. For a niche requirement, such as batch traceability for food, service contract billing, a local e-invoicing mandate, there is usually an existing add-on rather than a custom development. With 28 languages and 50 country localisations, statutory reporting in a new market is generally a configuration exercise, which matters if you trade across borders.
A perpetual licence is still on the table
Most competitors in this segment are now subscription-only. Business One still offers perpetual licences, which turns ERP from an indefinite operating cost into a capital purchase with a maintenance line, and, on the arithmetic above, works out cheaper from roughly month 22 if you stay on the product.
Scales within the small and midsize range
Business One handles growth well inside the segment it was designed for. Independent install-base analysis puts roughly 61% of deployments at companies with fewer than 100 employees and a further third between 100 and 1,000, and the licence mix lets you add Limited users cheaply as headcount grows without moving everyone onto Professional.
What it does not do is scale beyond that band, and this is worth stating plainly because a lot of pages claim otherwise: Business One is not an ERP for organisations of any size. It assumes a single-company database, a modest user count and a functional footprint that stops well short of a large multinational’s requirements. If you outgrow it the path is a migration to a different SAP product line, which is a re-implementation rather than a licence upgrade.
SAP Business One disadvantages
You are buying a partner as much as a product
This is the single biggest risk and it is structural, not a flaw you can configure around. SAP does not sell, implement or first-line support Business One itself. Everything reaches you through a reseller whose capability, industry knowledge and staff turnover you cannot see from outside, and delivery quality across that network varies far more than the software does. Changing partner mid-implementation is expensive and sometimes means redoing configuration work. Take references from customers in your own industry and of your own size before signing, and establish who specifically will be on your project rather than who is in the sales meeting.
The real cost is hard to see up front
No published price list means no easy benchmark, and the headline per-user figure is not the commitment. Implementation typically exceeds the licences in year one. Perpetual buyers add 18 to 20% annual maintenance indefinitely. Several components are licensed separately, such as Crystal Reports for report authoring, the SAP HANA runtime if you take that route, and on-premise deployments still need server, database and backup infrastructure plus someone to administer it. Insist on a three-year total that names every line rather than a monthly per-user number.
There is a functional ceiling, and hitting it means re-implementing
Business One is built for a single company with a modest user count. Complex multi-entity consolidation, heavy international group reporting or large-scale process manufacturing sit outside what it was designed to do, and intercompany work needs an add-on rather than being native. Outgrowing it means moving to a different SAP product line, a fresh implementation with fresh data migration, not a licence upgrade. If you genuinely expect to multiply in size or add several international subsidiaries inside the contract term, price that migration in now.
The interface shows its age
The product dates from 2002 and parts of it look and behave like it. SAP has invested in the browser-based Web Client, which now covers a good share of day-to-day work, but the full functional surface still lives in the Windows desktop client. Users arriving from cloud-native tools generally find it dense and unintuitive at first, which lengthens training and is worth budgeting for honestly rather than discovering after go-live.
Industries Supported by SAP Business One
It supports many sectors, such as
- Consumer products
- Manufacturing
- Retail
- Professional services
- Wholesale distribution
SAP Business One alternatives
The realistic shortlist for a company evaluating Business One, using current product names, several competitors have been renamed or withdrawn in recent years and are still listed under dead names elsewhere:
- NetSuite: the closest like-for-like competitor. Cloud-only, with stronger multi-entity and multi-currency consolidation; usually the better choice if you run several legal entities.
- Acumatica: licensed by resource consumption rather than per named user, which changes the economics substantially if you have many occasional users.
- Microsoft Dynamics 365 Business Central: the direct Microsoft equivalent in this segment, and the stated migration target for the retired Dynamics GP and NAV lines. Worth weighing if you are already committed to Microsoft 365.
- Epicor Kinetic: the product formerly sold as Epicor ERP. Manufacturing-oriented and generally aimed at larger operations than Business One.
- Odoo: open-source core with paid applications. Materially cheaper on licences, with more of the cost and risk shifted into implementation and in-house capability.
- Sage 100 and Sage Intacct: Sage 100 (sold as Sage 100cloud until the “cloud” suffix was dropped) for distribution and light manufacturing; Sage Intacct where financial management matters more than operations.
- SYSPRO: narrower than the others but deep in manufacturing and distribution.
Two names that still circulate on competitor lists but no longer belong there: Microsoft Dynamics GP, closed to all new customers since April 2026 and now in wind-down, and Epicor ERP, which has been called Kinetic since 2020.
Who uses SAP Business One
SAP reported more than 83,000 Business One customers and 1.2 million users in December 2025, spread across 170-plus countries and served by 850 partners, with 28 languages and 50 country localisations available.
The size profile is the useful part. Independent install-base analysis puts roughly 61% of deployments at companies with fewer than 100 employees and about a third between 100 and 1,000, a far better guide to whether the product fits you than the enterprise logos that sometimes get attached to it. SAP itself describes Business One as its ERP for “small businesses and the lower midmarket”. Adoption is heaviest in wholesale distribution, discrete manufacturing, professional services and consumer products.
Frequently asked questions
How much does SAP Business One cost?
Cloud subscriptions are typically quoted at $110 to $190 per user per month for a professional user, and perpetual licences at roughly $1,350 to $3,300 per user one-time plus 18 to 20% annual maintenance. A ten-user deployment works out at about $47,700 in cloud subscription fees over three years, or about $33,400 on perpetual licences, with implementation of $25,000 to $100,000 on top in either case.
Is SAP Business One being discontinued?
No. The confusion comes from mixing up a release family with the product. Version 10.0 is in mainstream maintenance until 31 December 2028, after which version 11, already on SAP’s road map for 2027, takes over. SAP’s own wording is that “the end of mainstream maintenance refers to the version and not to the overall product”. SAP reported more than 83,000 customers in December 2025 and continues to add roughly 3,000 a year.
Can you still buy SAP Business One with a perpetual licence?
Yes. Unlike several competitors that have moved to subscription only, SAP still sells perpetual on-premise licences for Business One to new customers alongside the cloud subscription. The perpetual licence carries a mandatory annual maintenance fee of 18 to 20% of licence value.
What is the difference between the Professional, Limited and Starter licences?
Professional gives full read-write access to every module and is the most expensive tier. Limited confines a user to a single functional area, such as logistics, financials or CRM, and is sold per area. Starter is capped at five users with a reduced feature set, cannot be mixed with the other two, and has to be replaced rather than extended once you outgrow it.
Is SAP Business One cheaper than NetSuite?
Per-user list prices are broadly comparable; the difference is structural. Business One still offers a perpetual option that overtakes subscription on cost after roughly two years, while NetSuite is subscription-only. Business One is usually the lower-cost route for a single-entity company with stable headcount, and NetSuite tends to win once you need consolidated multi-entity reporting.
Is SAP Business One worth it?
Business One earns a place on the shortlist when you want SAP’s data model at small-business scale, you run one legal entity or a handful, and you have, or can find, a partner you trust, because you will depend on them for the life of the system. The perpetual option is a real advantage over subscription-only competitors if your horizon runs beyond two years.
The arguments against are equally concrete. Implementation usually costs more than the licences in year one. Everything reaches you through a partner, so delivery quality varies more than the software does. And the functional ceiling is real: companies that expect fast growth into several countries tend to reach it and face a migration to a different SAP product rather than an upgrade.
References: