ambar 27 is a deployed ERP, not a self-serve subscription. What it costs depends on branches, counters, users and how much of your data needs migrating - so we scope first and quote against that. The structure below is fixed; the numbers are agreed in writing before anything starts.
Every quote is built from these three lines. There are no per-invoice fees, no per-transaction charges, and no module unlocks after go-live.
One-time. Discovery, configuration, master-data migration, parallel run, training and go-live.
Per year, by scale - branches, counters and named users. All modules included, always.
We provision, size and run the server, and keep it monitored, patched and backed up.
So you can estimate roughly where you will land before the call.
| Variable | Why it matters |
|---|---|
| Branches and GSTINs | Each branch needs its own configuration, tax profile, warehouses and counters, and adds consolidation work on the reporting side. |
| Counters and floors | Drives POS setup, print and thermal template work, settlement configuration and the volume of counter-staff training. |
| Named users | The licence scales with users, not with transactions. A large floor team on a single branch costs less than the same headcount split across four. |
| Master-data condition | The single biggest implementation variable. Clean categories and designs migrate in days; fifteen years of inconsistent naming takes weeks of reconciliation. |
| Opening balances and live stock | Migrating customer, supplier and ledger balances plus a physically verified opening stock is where most of the discovery effort goes. |
| Integrations required | GSP e-invoicing, WhatsApp Business, Tally mapping, payment gateway and bank statement formats each need configuration and testing against your accounts. |
| Custom reports and templates | The standard library covers most needs. Reports and documents specific to your business are scoped explicitly rather than discovered mid-project. |
| Server sizing | Sized against your peak trading week rather than your average day, so counters stay quick when it matters most. More counters and more concurrent users mean a larger instance. |
Software pricing that scales with your transaction count punishes you for growing and gives us a reason to want your busiest day. We would rather not have that incentive.
Because a number without a scope is either a lie or a starting point for a negotiation neither of us enjoys. A four-counter single showroom and a six-branch group are different projects, and the implementation half of the cost depends almost entirely on the state of your existing data. We scope in one call and quote in writing.
The licence is annual because implementation and support are annual commitments on our side. Payment terms within the year are negotiable and are agreed as part of the contract.
Updates, integration support, hosting and the support team all lapse, and the system stops being maintained. What happens to your data at that point is set out in your contract rather than on this page - ask us and we will put it in writing before you sign.
Yes, at a defined incremental rate agreed in your original contract, so opening a third showroom does not turn into a renegotiation. Additional branch implementation is quoted separately because it is real work.
That is the usual approach for multi-branch groups, and we recommend it. One branch goes live, runs for a season, and the rollout to the remaining branches is scoped with everything learned from the first.
Application issues, integration failures, configuration changes, and guidance for your team - from people who know your specific setup. The server is included where we host it. Genuinely new development is scoped separately.
One call about your branches, counters, users and data. You get a written scope and a fixed quote - not a proposal that changes after signature.