There is no list price, and this page will not pretend otherwise. What it will do is tell you exactly what you are buying, what moves the number, and what is not in it — so the quote you ask for is one you can read.
Five things — and the list is worth reading for what is absent as much as for what is on it. Branches are not there. A company running one branch and a company running twelve are the same purchase here, and linking them so balances and quantities are visible across all of them does not move the number either.
Nama is 46 modules in nine families, and you licence the ones you need rather than the whole catalogue. This is the largest single driver — a finance-and-inventory rollout and a full manufacturing-plus-HR rollout are not the same purchase.
Companies, not branches. Each additional legal entity is more analysis before anything is built, and the relationships between them — inter-company transactions, and consolidating the group's position out of them — are designed rather than switched on. Branches under a single company are neither counted nor charged, however many you open.
Concurrent users, and the ceiling matters at the small end far more than at the large one. The software itself sets none; your licence does — and licences are sized with enough headroom that for most buyers it stops being the thing that decides the price. Users can be added later at any time, for a fee, so the count you start with is a budgeting decision rather than a permanent one.
Point of sale is licensed per machine rather than per user, because each register holds its own local database and keeps selling through a dropped connection. A register does not consume one of your concurrent users — the tills and the back office are counted separately.
Prices differ by market. Ask the office nearest you rather than assuming a figure quoted elsewhere applies.
Three things that are commonly quoted as extras by other vendors are inside the price of the system here.
Nama commits to implementing the system to meet your requirements — the analysis, the setup, the migration and the configuration are part of what you bought, not a services line beside it.
Delivered against a planned schedule by Nama's own support team or an authorised training centre, and included rather than charged per head.
Fixes for reported defects and the enhancements customers have asked for, downloadable throughout your warranty period or service agreement.
Documented to OpenAPI 3.0 and available to every customer at no additional cost. Where an integration does cost more, that cost usually originates on the other system's side.
Written down deliberately. A quote that hides these is not cheaper — it just moves the conversation to month eight.
The warranty covers you for its term. After that a service agreement is what keeps technical support and access to new releases in place, and it is a separate commitment.
Training during implementation is included. Training for staff who join after go-live is arranged through your nearest office and quoted separately.
Adding users later is possible at any time, and it is priced.
Nama runs on your own infrastructure or on hosting Nama provides. Either way the hardware and its running costs sit outside the software licence — the documented minimum specification is worth reading before you budget.
Not in one instalment against a signature. There is an initial payment at the start of the contract, and the rest is staged across the implementation and training periods against work actually delivered. The detail is a conversation with the office nearest you.
Because the five drivers above multiply. A four-user distributor licensing finance and inventory as a single company, and a two-hundred-user group licensing manufacturing, HR and project accounting across four legal entities with sixty registers on the shop floor, are not on the same page of the same price list — and a published figure would be right for neither of them. What is publishable is the model, which is what this page is. Send us the shape of your business and you get a number against it.
Tell us what you need priced and we will come back with a figure against your scope. This is not a demo booking — you do not have to sit through anything.
Your details go to our sales team so they can reply to your enquiry. We do not sell your personal data, and we do not share it for anyone else's marketing. Privacy policy
Prefer email? Write to info@namasoft.com
Because the price depends on which of the 46 modules you licence, how many legal entities you run, how many concurrent users and POS registers you need, and the country you buy in. Any single published figure would be wrong for most readers. Ask for a quote against your own scope and you get a number that means something.
No. Branch count is not a pricing factor, and neither is linking branches so that balances and quantities are visible across all of them. What is counted is legal entities — separate companies, which bring their own analysis and their own inter-company relationships with them.
Per machine. Each register holds its own local database and keeps selling when the connection drops, and it is licensed on that basis rather than as a user. A register does not consume one of your concurrent user licences.
No. Installation, implementation and training are inside the price of the system. Nama commits to implementing the system to meet your requirements and to training your staff against a planned schedule.
Yes, at any time. The software places no ceiling on concurrent users — the licence does — and increasing it is priced by your nearest office.
No. There is an initial payment at the start of the contract and the remainder is staged across the implementation and training periods, against the work delivered.
A service agreement, if you want to keep technical support and access to new releases. During the warranty, or under an agreement afterwards, releases carrying defect fixes and customer-requested enhancements are downloadable throughout.
No. The REST API is documented to OpenAPI 3.0 and available to every customer at no additional cost. Where an integration carries a cost it usually comes from the other system's side rather than from Nama.
When I joined the company I found that the system in use was Namasoft's, but it was not fully operational — parts of it were not working. I took on the challenge, we surfaced every problem in it, and within six months it was running and the system had been configured to match the way we work.
Tell us how your business runs and we will show you how Nama ERP fits it — in your language, on your infrastructure.
