ERPNext

ERPNext has no per-user licence. None. Frappe's pricing page lists $0 per user per month, and that single fact changes how the maths works for a growing company. The catch sits elsewhere: hosting, implementation and, for Spanish companies, a localisation that you'll have to assemble yourself.

ERPNext is an open-source ERP developed by Frappe Technologies in India, released under the GPL-3.0 licence and built on the Frappe Framework, a Python and JavaScript web framework. Frappe says 30,000+ companies have adopted it. That's a vendor claim, but the project is clearly alive: the GitHub repository ships releases almost every week on two parallel version lines.

What ERPNext Is in 2026

The current major version is ERPNext v16, released on 12 January 2026. Version 15 is still maintained alongside it. In mid-October 2026 both lines received releases in the same week (v16.51.1 and v15.123.0). For a new project, start on v16.

The v16 core covers these modules: Accounts, CRM, Buying, Selling, Stock, Manufacturing, Projects, Assets, Support, Quality Management, Maintenance, Subcontracting and EDI, plus point of sale. Version 16 added stock reservation on work orders and production plans, and new Master Production Schedule and Material Requirements Planning views, so manufacturing got real attention.

HR and payroll are a separate app. Frappe HR (the `hrms` repository, also GPL-3.0) installs on top of ERPNext. It's free too, but it's one more app to install, update and test.

Everything is customisable without forking: custom fields, DocTypes (Frappe's data models), print formats, workflows and server scripts, all from the browser. Frappe's own page lists a no-code builder among the modules.

Editions and Pricing (October 2026)

There's one product. What changes is who runs it.

• Self-hosted: free under GPL-3.0. You pay for the server and the people who keep it patched, backed up and upgraded.
• Frappe Cloud, site plans: shared hosting priced by resources, not users. As listed in October 2026, AWS-hosted plans go from $5/month (0.5 h CPU, 250 MB database, 2.5 GB storage) through $10, $25 and $38 to $50/month (4 h CPU, 2 GB database, 50 GB storage). Cheaper-per-resource Hetzner plans exist, but Frappe itself recommends them for development, testing and demo sites.
• Frappe Cloud, server plans: a full virtual machine for multiple sites, from $40/month.
• Support: the Frappe Cloud "Product Warranty" covers bug fixes in Frappe apps and the hosting platform. It explicitly doesn't include functional support ("how do I set this up?"). That's what partners are for.

Prices are in USD (and INR); Frappe doesn't publish euro prices. There's a 14-day free trial.

What does that mean in practice? Hiring a sixteenth employee doesn't change the hosting bill. Plan size depends on CPU time and data volume, not headcount. Licence cost is not where your budget goes. Implementation is.

Strengths

• No per-user fees. Costs scale with compute, not headcount. This suits companies with many occasional users: warehouse staff, technicians, shop-floor terminals.
• Genuinely open. Every module is in the GPL repository. There's no Community/Enterprise split holding back features you'd pay for later.
• Manufacturing depth for the price. BOMs, work orders, subcontracting, MPS and MRP views, quality inspections and maintenance are all in the core.
• Customisation from the browser. Many changes that need a developer in other ERPs are configuration here.
• Release velocity. Weekly patch releases mean bugs get fixed quickly. They also mean you need a way to test updates.

Limitations

• Spanish localisation is thin. This is the big one for this audience; see the dedicated section below.
• Functional support isn't included anywhere. Not even in Frappe Cloud's warranty. You need a partner, in-house expertise or the community forum.
• Self-hosting is real operations work. Backups, upgrades across major versions, background workers, email queues. Frappe's own comparison lists these as manual chores when self-hosting.
• Smaller partner ecosystem in Spain than the big commercial ERPs. Frappe cites 200+ partners worldwide; finding one with Spanish tax experience takes more searching.

Spain: Verifactu, SII and Localisation

Here's the honest picture, checked against the code in October 2026.

ERPNext's core has no Spanish regional module. The repository's regional folder covers Australia, Italy, South Africa, Turkey, the UAE and the United States. A Spanish chart of accounts template exists, but it sits in the "unverified" charts folder, not with the verified country charts.

Spanish compliance therefore comes from third-party Frappe apps, not from Frappe itself. As of October 2026, what's publicly visible is small:

• erpnext-spain (Marti Solutions, GitHub): Spanish translations, the Plan General Contable and VAT/IGIC tax templates, for v16 only and designed for a clean install.
• erpnext_spain_verifactu (same author, MIT licence): a Verifactu integration for ERPNext sales invoices. It's a young project with little public activity.
• spain_compliance (Xappiens, GitHub): PGC tree, consecutive invoice numbering, separate series for credit notes (facturas rectificativas) and doubtful-debt statuses. Its README lists SII, Verifactu and tax forms as placeholders for upcoming work.
• At least one vendor advertises a build-to-order Verifactu, TicketBAI and Facturae app for v15 and v16 on a quote basis.

There's no SII module from Frappe, no official Modelo 303 or 390 report, and no TicketBAI support in core.

Does that rule ERPNext out? Not necessarily, but timing matters. Under Real Decreto-ley 15/2025, Verifactu applies from 1 January 2027 for corporate income tax payers and 1 July 2027 for autónomos and other taxpayers. If you issue invoices from ERPNext, you need a Verifactu solution you trust, tested against the AEAT, before your date. Companies on SII (turnover above €6 million, REDEME or VAT groups) are outside Verifactu but need SII instead, and ERPNext has no mature SII option to point to.

One workable approach is to keep ERPNext for operations (stock, manufacturing, purchasing) and run Spanish invoicing, accounting filings and payroll in local tools. It works, but you give up part of the single-database benefit.

Implementation: Time, Cost Drivers, Partners

Frappe says implementation for most small businesses takes 2 to 8 weeks, with manufacturing and custom workflows taking longer. Frappe doesn't implement projects directly; certified partners do, and you can also self-implement with the documentation.

For a Spanish company, add time for:

• Building or validating the localisation: chart of accounts, VAT and IGIC templates, invoice series and rectificativas.
• Verifactu (or SII) integration and AEAT testing, which may mean commissioning or co-funding an app.
• Payroll, either via Frappe HR plus Spanish rules you'll have to build, or an external payroll provider.
• Upgrade discipline. Frequent releases need a staging site and a test routine.

The real cost driver is people. No licence fee means the budget goes almost entirely to consultants, developers and whoever runs the system.

Who Should (and Shouldn't) Choose ERPNext

Good fit:

• Manufacturers and distributors with many occasional users, where per-user licences would hurt.
• Companies with in-house Python developers or a long-term partner relationship.
• Spanish subsidiaries of groups already running ERPNext elsewhere, with invoicing or compliance handled by a local tool.
• Organisations that need full source code access and no vendor lock-in.

Look elsewhere if:

• You need Verifactu or SII working out of the box from a vendor that maintains it. Odoo or a Spanish ERP is the safer route today.
• You have no technical capacity and no budget for a partner.
• You want a vendor to call when something in your accounting setup doesn't work.

Bottom line? ERPNext is an excellent value ERP with no licence bill and solid manufacturing, but in Spain you're buying the localisation project along with it. Price that project honestly before choosing.