ERPNext Africa · commercial briefing
The commercial model: what ERPNext costs
The honest structure of an ERPNext investment — what is genuinely free, what you pay for, what drives the project fee, and how the ten-year picture compares with licensed ERP.
Business briefing · 2026 · companion to Why ERPNext (platform) and the migration playbooks
01 · The short answers
The questions every evaluation asks, answered directly:
| Question | Answer |
|---|---|
| Software licensing cost | R0 — ERPNext is open source (GPLv3). There is no licence fee to buy, and none to renew. |
| User licence pricing | R0 — no per-user pricing exists. 10 users and 100 users run the same software at the same software cost. Growing your team never grows a licence bill. |
| Module costs | R0 — accounting, inventory, manufacturing (MRP, work orders, job cards), buying, selling, CRM, projects, assets and HR ship in the same codebase. "Turning on" a module is configuration, not a purchase order. |
| Monthly subscription | The only recurring platform cost is hosting — from roughly $25–$50/month (managed cloud, small site) to $200–$400/month (dedicated resources for a busy manufacturer), or your own server. Plus an optional support retainer (below). |
| Implementation cost & project fees | The real investment — professional services, quoted as fixed-fee phases after a scoping exercise. Structure and drivers in §02–§05; a written estimate follows discovery. |
| Other costs to be aware of | Integrations (e.g. e-commerce sync), data migration effort from the old system, training time from your own team, and third-party services you already buy (backups, email). No hidden platform charges — §02 lists everything. |
The one-line summaryWith ERPNext the licence line item is deleted, not discounted — the budget goes to making the system fit your business and keeping it running well. You pay for outcomes, not permission.
02 · Where the money actually goes — three buckets
| Bucket | When | What it covers | Typical range |
|---|---|---|---|
| 1 · Implementation | Once-off, phased | Discovery, configuration, catalogue & BOM build, data migration, pilot, training, cutover, hypercare — the 12–16 week phased plan | Quoted fixed-fee per phase after scoping — the dominant cost, and the one that determines success |
| 2 · Hosting | Monthly | The servers the system runs on: managed cloud (Frappe Cloud — backups, updates and SSL included, no user limits) or a dedicated server we manage | ± $25–$400/month depending on scale and setup; a busy single-factory site sits comfortably in the low hundreds |
| 3 · Support & care | Monthly, optional tiers | A retainer for help, changes and month-end support; system updates applied on schedule; monitoring and backups verified. Vendor-level support from Frappe available on top if wanted | Tiered to response time and hours — scoped with the proposal |
What is deliberately absentNo annual licence renewal. No per-user charge. No per-module unlock. No compulsory upgrade project — version upgrades are routine maintenance inside the support arrangement, because customisations are built to survive them (see customising without forking).
03 · What drives the project fee up or down
Two implementations of the "same" system can differ several-fold in effort. These are the honest levers — worth knowing because most are within your control:
| Driver | Keeps cost down | Pushes cost up |
|---|---|---|
| Scope discipline | Core flows first (finance, stock, factory); phase 2 for the rest | "Everything on day one" — HR, portals, integrations in the go-live scope |
| Catalogue & BOMs | Current product range only; clean variant structure; product knowledge available | Migrating every SKU ever sold; BOMs reverse-engineered from memory |
| Data quality | Old-system data exported clean; stock count at cutover | Years of unreconciled balances migrated as-is (they don't get better in a new system) |
| Process change appetite | Adopt ERPNext's standard flows where they're good enough | Recreating every old-system habit as a customisation |
| Your team's availability | A named product owner; floor supervisors in the pilot | Decisions queued behind day jobs — the quiet schedule killer |
| Integrations | Standard connectors (e.g. one Shopify store) | Multiple channels, custom portals, EDI — each its own mini-project (see the channels pattern) |
04 · The ten-year cost shape vs licensed ERP
Comparing year-one numbers flatters licensed ERP; comparing decade shapes doesn't. Without publishing any vendor's price list, the structural difference is this:
| Licensed mid-market ERP (SysPro, Sage…) | ERPNext | |
|---|---|---|
| Year 1 | Implementation services plus licence purchase/subscription for every user and module | Implementation services. That's the list. |
| Every year after | Licence renewals / subscription + annual maintenance (typically ~20% of licence value) — priced per user, often in hard currency | Hosting (hundreds of rands to a few thousand) + support retainer sized to what you actually use |
| When you grow | More users = more licences; new function = new module purchase | More users = R0; new function = configuration or a scoped enhancement |
| At version end-of-life | An upgrade project, at project prices, on the vendor's timetable | Upgrades inside the retainer, on yours |
| Currency exposure | Licence line tracks USD/GBP | Costs are mostly local services; hosting is the only small hard-currency line |
The practical consequence we see repeatedly: the annual licence-plus-maintenance line of a mid-market licensed ERP, redirected for one to two years, funds the entire ERPNext implementation — after which that line simply stops recurring at licence scale.
05 · How we quote — no surprises by design
- Scoping first — a short paid discovery (factory walk-through, data review, module fit) produces the implementation plan and a fixed fee per phase — not an open-ended day rate into the fog.
- Phase gates — each phase has defined deliverables; you approve before the next begins. The phased plan shows the shape: discovery → core setup → catalogue & BOMs → pilot → migration → cutover.
- Included vs excluded, in writing — the proposal states what's in (configuration, migration, training, hypercare) and what's optional (integrations, custom apps, phase-2 modules) with each optional item priced separately.
- Run costs quoted alongside — hosting recommendation and support tiers in the same document, so the total monthly picture is visible before you commit to anything.
Next stepA scoping conversation costs a meeting, not a mandate: we'll walk the factory, look at the current system's data, and return a written estimate against the phased plan — alongside the manufacturing briefing's suggested working session, where we model two of your real products in a live demo instance.
Sources
ERPNext — open-source licensing (GPLv3), module scope · Frappe Cloud — published hosting plans (shared, private bench, dedicated; no user limits) · Why ERPNext (platform) — support layers, upgrade model · Furniture manufacturing briefing — the 12–16 week phased plan · SysPro → ERPNext migration playbook (this site)