Most ERPNext systems that need attention are not broken. Invoices still go out, stock still moves, payroll still runs. The problems are quieter: workarounds, reports nobody trusts, and settings that no longer match how the business operates.
The main ERPNext health check signs are: staff keep spreadsheets alongside the system, reports need manual correction, nobody can explain old customizations, upgrades keep getting postponed, and new hires are trained on workarounds instead of the actual workflow. Any one is common. Several together mean a review is overdue.
What Is an ERPNext Health Check?
An ERPNext health check is a structured review of a live system. It looks at how the system is configured, customized and used, and compares that with how your business works today. It is not an audit of whether the implementation was done “correctly” years ago. It asks whether the system still fits.
That distinction matters. A setup that was right at go-live can drift as you add product lines, warehouses, tax rules or people. Nobody makes a bad decision. Small changes pile up.
7 ERPNext Health Check Signs to Watch For
Spreadsheets are running next to the system
If finance, stores or sales keep a "real" sheet because the system output cannot be trusted, the system has lost its role as the source of truth. The sheet usually exists for a reason: a missing field, a report that does not match, or a step the workflow does not allow. That reason is what a review should find.
Reports need manual fixing before anyone uses them
Exports that get cleaned, filtered or re-added in Excel every month point to a report that does not answer the question being asked. Sometimes the fix is a custom report. Sometimes the real problem is upstream: inconsistent item groups, missing links between documents, or data entered in different ways by different people.
Nobody can explain the customizations
Custom scripts, custom fields and server-side changes are normal in ERPNext. The warning sign is when no one knows why they exist, who wrote them, or what breaks if they are removed. Undocumented customization makes every future change riskier and slower.
Upgrades keep getting postponed
Teams delay version upgrades when they fear something will break. That fear is often justified if customizations edit core behavior instead of extending it through Frappe's supported hooks. The longer the gap grows, the harder the eventual upgrade becomes. This is also a security and support concern, since older versions fall out of active maintenance.
Users work around the workflow
Look at how people actually enter data. If approvals are bypassed, documents are created in the wrong order, or one person has an administrator role "just to get things done," the permission and workflow design no longer matches reality. This is both a control risk and a data-quality risk.
The system feels slower than it used to
Slowness has many causes: growing data volume, heavy custom queries, background jobs piling up, or server resources sized for an earlier stage of the business. It is rarely fixed by guessing. A review looks at where the time is going before recommending a change.
The system feels slower than it used to
When training sounds like "ignore that screen, do this instead," the gap between design and practice has become part of your culture. It is also a good moment to check whether the business changed and the system did not follow.
What a Health Check Actually Looks At
| Area | What is checked |
|---|---|
| Configuration | Company, accounting, stock and tax settings against current operations |
| Customizations | Custom fields, scripts and apps: purpose, ownership, upgrade risk |
| Roles and permissions | Who can do what, and whether it matches approvals in practice |
| Data quality | Duplicate masters, inconsistent item or party data, broken links between documents |
| Reports | Which reports are used, trusted, or replaced by spreadsheets |
| Performance and infrastructure | Server sizing, background jobs, backups, version and update status |
| User adoption | Where people bypass the system and why |
When a Sign Is Not a Problem
Not every sign means something is wrong. A spreadsheet might be a one-off analysis. A custom script might be well written and simply undocumented. A slow report might be slow because the question is genuinely heavy.
The goal is not to find faults. It is to separate the things that are quietly costing you time or control from the things that are just how a growing business works.
How Often Should You Review?
Frequently Asked Questions
Next Step
If your ERPNext “works fine” but several of these signs sound familiar, a short review will tell you whether it is drift or just growth. Talk to our ERPNext support team and we will tell you what we would look at first.
