How consumption-based licensing works: users are free, usage is not
The pitch is simple: unlimited users at no per-seat charge. Your warehouse crew, field technicians, salespeople, and part-time bookkeeper can all have logins without anyone doing seat arithmetic, and for companies where per-user pricing has meant rationing access, that lands hard. What replaces the seat count is consumption. An Acumatica subscription is priced on three levers: which functionality you license, how much computing resource and transaction volume your business pushes through the platform, and how it is deployed. Grow your order volume and you move up a resource tier; add an application suite and the subscription grows with it. The vendor's framing is that you pay for the work the system does rather than the people who can see it.
Two structural facts sit underneath the model. First, pricing is quote-only: Acumatica does not publish a rate card, and the numbers arrive through its channel of value-added resellers, who both scope the license and deliver the implementation. Every figure circulating online is second-hand. Second, unlimited users does not mean unlimited identical users: role-based licensing distinguishes full users from lighter-weight access in some configurations, and the resource tier you are quoted assumes the transaction profile you described during the sales cycle. The model is honest, but it is not flat, and the growth curve is priced in transactions rather than heads.
- Unlimited users: no per-seat license fee, which is the model's genuine differentiator.
- Consumption pricing: the bill scales with licensed modules and transaction or resource tiers.
- Quote-only, channel-sold: numbers come from VARs, not a published price list.
- Annual subscription: SaaS on Acumatica's cloud, or private cloud and on-premises options for those who need them.
What actually drives the quote: edition, modules, tiers, deployment
The first driver is the edition. Acumatica packages the product in industry editions, at the time of writing the lineup includes General Business, Distribution, Manufacturing, Construction, and Retail, and the edition determines both the module bundle you start from and the pricing lane you are quoted in. A manufacturing edition with production management, MRP, and scheduling is a materially bigger subscription than core financials. The second driver is the modules beyond the bundle: CRM, field service, payroll, commerce connectors, and advanced capabilities are added to the order form individually, so the quote grows the same way a per-user vendor's does, one line at a time, even though no line says users.
The third driver is the consumption tier itself, and this is the one to interrogate hardest. Your quote assumes a band of transaction volume and computing resource, and crossing that band, more orders, more invoices, heavier integrations hammering the API, moves you to a higher tier at renewal. For a stable business this is predictable; for a business whose whole plan is volume growth, it means the license line grows with revenue even if headcount never moves, which is precisely the inverse of the per-user pain it replaces. The fourth driver is deployment: SaaS on Acumatica's cloud is the default, while private cloud and on-premises licensing change both the price and who carries the infrastructure. Add the support plan level and any first-term discounting, and you have the full anatomy of the number the VAR slides across the table.
- Edition: General Business, Distribution, Manufacturing, Construction, or Retail sets the baseline.
- Modules: capabilities beyond the edition bundle are individually priced order-form lines.
- Transaction and resource tiers: the growth axis; crossing a band reprices the renewal.
- Deployment and support: SaaS, private cloud, or on-premises, plus the support plan level.
Implementation through VARs, and a realistic total
Acumatica does not implement its own product; the VAR that quotes your license also scopes and delivers the project, and the quality range across that channel is wide. Implementation is billed as a services engagement covering discovery, configuration, data migration, integrations, and training, and for a mid-market company it is typically quoted in the five figures, with complex multi-site manufacturing or construction projects reaching six. The same partner usually proposes an ongoing support retainer afterward. None of this is unusual, it is how the entire mid-market ERP channel works, but it means the subscription is roughly half the decision, and the partner you pick is the other half. The table below is the structure we use when a prospect asks us to sanity-check an Acumatica proposal.
| Cost component | How it is charged | What to watch |
|---|---|---|
| Edition bundle | Annual subscription, quote-only | Industry editions price in different lanes |
| Additional modules | Per module, per year | Demo capabilities that are separate order-form lines |
| Consumption tier | Banded by transaction and resource volume | Volume growth reprices the renewal, even at flat headcount |
| Deployment | SaaS, private cloud, or on-premises | Infrastructure responsibility shifts with the choice |
| Implementation | One-time VAR services engagement | Typically five figures; complex projects reach six |
| Customization and integrations | Consulting rates, plus connector subscriptions | Framework work needs re-testing at platform releases |
| Ongoing support | Retainer or plan-based | Usually with the same VAR that sold the license |
To model this against alternatives on equal terms, our total cost of ownership calculator builds the same five-year stack, licenses, implementation, customization, integrations, and support, so the comparison is bill against bill rather than sticker against sticker. And if you want an experienced third party to pressure-test the proposal itself, that is exactly the work our ERP consulting practice does.
Who Acumatica genuinely fits
We compete with Acumatica, so read the concession as one: for the right profile, the consumption model is not a gimmick, it is the correct pricing shape. If you run a distribution, manufacturing, or construction business where most of the workforce touches the system occasionally, warehouse staff confirming picks, field crews logging time, project managers checking budgets, then per-user pricing taxes exactly the broad, shallow access you need most, and Acumatica removes that tax outright. The product itself is a credible modern mid-market ERP: true cloud, a real API, industry editions with depth in distribution and construction, and a customization framework that does not require exotic skills. Companies with many hands and moderate transaction volume get a genuinely good deal.
The fit weakens from two directions. A small team with high transaction volume, a lean e-commerce operation pushing thousands of orders, inverts the math: they would be cheap under per-user pricing and instead pay for volume. And any business whose growth story is transactional should model the tier crossings explicitly, because the renewal conversation arrives with the growth. Add the usual channel caveats, quote-only opacity, VAR quality variance, and the reality that your implementation partner and your license vendor are the same commercial relationship, and the honest summary is: right shape for many-users-moderate-volume, wrong shape for few-users-high-volume, and in all cases a model you should price at your projected volume, not your current one.
How it compares to per-user models, including ours
Against the quote-only per-user incumbents, NetSuite and Sage Intacct chief among them, Acumatica's model is a straightforward trade: you exchange seat-count anxiety for volume-tier anxiety, and which is cheaper depends entirely on the ratio of people to transactions in your business. Odoo sits in a third position that makes the comparison interesting: it is per-user, but the published per-user price is low, includes every application in one subscription, and has no module ladder and no transaction tiers at all, so the bill scales with headcount only, on a public rate card, with no quote required. For a hundred-person distributor, Acumatica's unlimited users may still win the license math; for most of the 20-to-100-person companies we work with, the flat, published, everything-included number wins it, and the wider developer pool for an open-source platform keeps the customization line lower too.
If you are evaluating this seriously, put real numbers on all three shapes. The Acumatica alternatives guide covers the field around it, and since most Acumatica evaluations start as NetSuite evaluations, the NetSuite alternatives guide is worth the pass too. Run your own volumes and headcount through the TCO calculator, and check our published implementation rates for what the Odoo side of the model costs, published because we think quote-only pricing is the part of this market most worth fixing.
See the full Acumatica alternatives guide →