ERPNext v15 vs v16: What Actually Changed (2026)

Every ERPNext major version carries the same question from clients: is the jump worth the disruption? I am Manoj, an ERPNext and Frappe implementation consultant at Mith Tech in Bengaluru, and I have set up and migrated both versions for Indian SMBs across trading, manufacturing, and services. This post compares what actually changed — not the marketing bullets, but the differences you feel in daily use.

My honest take: the headline "50+ new features" matters less than three quiet shifts — the performance rewrite, the PDF engine change, and the raised runtime requirements — because those touch every install, not just the modules you happen to use.

What actually changed between ERPNext v15 and v16?

Direction changed. ERPNext v15 concentrated on stabilising the platform after a large framework migration, tightening existing modules rather than adding many new ones. ERPNext v16 shifts toward performance and functional depth: a faster core, a redesigned workspace, a new PDF engine, and meaningful additions across accounting, manufacturing, and inventory. Both remain free and open source under GPLv3.

Here is the difference at a glance, on capability and fit rather than any price:

If you want the migration mechanics rather than the feature comparison, our companion guide on the ERPNext v15 to v16 upgrade walks through testing and cutover.

Skimmable summary: v15 stabilised the platform; v16 makes it faster and deeper. The biggest cross-cutting changes are performance, the new PDF engine, and a raised runtime stack — everything else is module-specific.

When were ERPNext v15 and v16 released?

Release timing sets the maturity context. ERPNext v15 shipped in October 2023, so by 2026 it is a well-settled, heavily deployed release. ERPNext v16 entered public beta on 15 November 2025 and reached its final release on 12 January 2026 — the original December 2025 target was pushed to give the beta more testing time.

That two-year-plus gap explains why v16 feels substantial rather than incremental. A single point release rarely changes much; a jump across a major version that had this long to accumulate work naturally bundles more. Because v16 is still early in its life at the time of writing, its ecosystem apps and third-party integrations are catching up, while v15 remains fully supported with security fixes.

Skimmable summary: v15 launched October 2023; v16 went beta on 15 November 2025 and hit final release on 12 January 2026. The long gap is why v16 bundles so much, and why v15 is the more battle-tested option today.

How much faster is ERPNext v16, and what else improved system-wide?

Speed is the headline system-wide change. ERPNext v16, built on Frappe Framework v16, delivers roughly 2x faster performance across many common operations — list views, report loads, and background jobs feel noticeably quicker. Beyond raw speed, two platform-level changes affect every install regardless of which modules you use.

The first is PDF generation. v15 renders PDFs with wkhtmltopdf, an older engine that struggles with modern CSS such as flexbox and grid. v16 adds a Chrome-based generator you can select per print format, so complex invoice and report layouts render the way they look on screen, and generation is faster. wkhtmltopdf still exists as an option, so nothing forces you to switch.

The second is the redesigned workspace. Navigation, the sidebar, and module dashboards were reworked for clarity. For teams standing up new dashboards, our ERPNext v16 workspace guide covers the new layout in detail. Frappe v16 also introduces SQLite as an optional database for small or portable setups, though production deployments still run on MariaDB.

Skimmable summary: v16 is roughly 2x faster, renders PDFs with an optional Chrome engine that handles modern CSS, and ships a redesigned workspace. These platform changes touch every install, not just specific modules.

What new accounting and finance features arrived in v16?

Accounting gained real depth in v16. ERPNext v15 covers standard statutory and management reporting well, but customising a Profit & Loss or Balance Sheet meant working around fixed structures. v16 introduces Financial Report Templates that turn those statements into formula-driven, fully customisable layouts — useful for multi-company groups, IFRS-style presentations, or board formats.

Two more additions stand out for Indian finance teams. Purchase Expense Booking makes Cost of Goods Sold easier to compute by capturing purchase-side costs with fewer clicks and less manual reconciliation. And the TDS and Asset modules were refactored, tidying up two areas that Indian businesses touch constantly at month-end and year-end. None of this removes v15 functionality — it extends what finance teams can express without custom code.

Skimmable summary: v16 adds formula-driven Financial Report Templates, Purchase Expense Booking for easier COGS, and refactored TDS and Asset modules — more reporting flexibility without custom development, especially valuable for Indian statutory work.

What changed in manufacturing and inventory?

Manufacturing saw the biggest functional additions. ERPNext v15 handles work orders, BOMs, and basic subcontracting, but material planning often relied on manual analysis or custom reports. ERPNext v16 adds a dedicated Material Requirements Planning workflow that combines forecasts, delivery schedules, and lead times to tell you what to buy or produce and when.

Two other additions matter for factories and traders. Inward Subcontracting lets you receive raw materials from a customer and manufacture finished goods for them — a common job-work pattern in Indian manufacturing that previously needed workarounds. On the stock side, v16 adds landed cost handling on stock entries and a Serial & Batch Traceability Report, so you can trace backward to the raw materials and batches in a product, or forward to every customer and location it reached.

Skimmable summary: v16 adds a dedicated MRP workflow, inward subcontracting for customer-supplied raw materials, landed cost on stock entries, and full serial/batch traceability — closing gaps that v15 users filled with manual work or custom reports.

Do the system requirements change when moving to v16?

Requirements did rise, and this catches people out. ERPNext v15 runs on an older runtime — Python 3.10-era and an older Node.js — which suited servers provisioned in 2023 and 2024. ERPNext v16, built on Frappe v16, requires a notably newer Python and a newer Node.js, so an older server usually needs its language runtimes upgraded before v16 will even build assets.

Because exact minimums shift during a release's early life, check the official Frappe prerequisites and the v16 release notes for the confirmed versions before you provision. The practical point stands either way: v16 is not a drop-in on a v15 box. Plan a fresh, correctly-provisioned environment — whether self-hosted or on the Frappe/ERPNext platform — and migrate onto it rather than upgrading in place on old dependencies.

Skimmable summary: v16 needs a newer Python and Node.js than v15, so an old server must have its runtimes upgraded first. Confirm exact minimums on Frappe's official prerequisites page, and provision a fresh environment rather than upgrading in place.

Should you move from v15 to v16 now?

Need should drive the decision, not the version number. Move to ERPNext v16 when you want one of its flagship additions — the MRP workflow, formula-driven financial reports, inward subcontracting, or the Chrome PDF engine — and you can test the migration properly first. If v15 runs your business well and none of those solve a current problem, staying put is a sound choice, because v15 still receives security fixes.

The pattern I recommend to clients is to let a fresh major release settle through its early point releases while ecosystem apps catch up, then upgrade on a tested staging copy. Being one major version behind on a stable, supported release is a perfectly professional position. If you want a second opinion on your specific setup, that is exactly the kind of question we help Indian SMBs answer at Mith Tech.

Skimmable summary: Upgrade when a specific v16 feature solves a real problem and you can test first; otherwise stay on supported v15 and let v16 mature. The decision is about need and timing, not chasing the newest number.

Frequently asked questions

What is the main difference between ERPNext v15 and v16?

The main difference is direction. v15 was a stability release that consolidated the platform, while v16 is a performance-and-depth release: roughly 2x faster, with a redesigned workspace, Chrome-based PDF generation, and new accounting and manufacturing features. Both are free and open source under GPLv3.

When was ERPNext v16 released?

ERPNext v16 entered public beta on 15 November 2025 and reached its final release on 12 January 2026. The original December 2025 target was moved to allow more beta testing. ERPNext v15, by comparison, was released in October 2023.

Is ERPNext v16 stable enough for production?

v16 reached its final release in January 2026 and is production-grade, but any major x.0 release matures over its early point releases as ecosystem apps and integrations catch up. Risk-averse businesses often let it settle for a few months and stay on supported v15 in the meantime.

Can I upgrade directly from ERPNext v15 to v16?

Yes, but it is not a drop-in. v16 requires a newer Python and Node.js than v15, so your server's runtimes usually need upgrading first, and every custom app must be tested for v16 compatibility. Always run the upgrade on a staging copy before touching production.

Does ERPNext v16 cost more than v15?

No. ERPNext is free and open source under GPLv3 in both v15 and v16 — there is no licence fee for the software itself. Your costs are hosting, implementation, and any support you choose; those depend on your setup, not the version number.

Will my v15 customisations work on v16?

Core functionality carries over, but customisations, custom apps, and third-party integrations written for v15 may need adjustment for v16 — especially anything touching the refactored TDS and Asset modules or the new PDF engine. Test every customisation on a staging environment before cutover.