What ERPNext covers out of the box, and where customisation starts
The feature list is rarely the problem. The interesting part is where the standard ends and what that means for your project.
What is there without customisation
Sales and purchasing, inventory, manufacturing with bills of materials, projects with time tracking, accounting and CRM belong to the ERPNext core. HR and payroll are added through the separate Frappe HR app. The applications and features your project needs are checked before setup.
You do not have to switch them all on. The usual approach is to start with the area where most of the numbers fall apart today.
Configuration is not customisation
Many custom fields, print formats, workflows and permissions can be configured without custom application code. More advanced print formats and specialised workflows may require code. Configurations and custom apps are tested before an update; compatibility is not assumed automatically.
When a dedicated app is the more honest answer
If additional application logic is required, a dedicated Frappe app can create a clear boundary with the standard. Suitability depends on scope, testing and maintenance responsibility. Separate apps also need compatibility checks during updates.
Where it gets uncomfortable
Industry-specific edge logic, very large group structures with many entities, and deeply integrated specialist systems are the places where ERPNext costs effort. That belongs before the decision, not after it.
Separate standard features, configuration and development in a test.
Test a specific order in the intended version and app combination. Document which steps work without additional setup and which fields, roles or approvals need configuration. A module name alone does not prove complete workflow coverage.
ERPNext workflows allow configurable states and transitions. Frappe HR is a separate application for HR topics. These facts help planning; they prove neither a ready-made customer-specific approval nor payroll suitable for every market.
If additional logic is needed, record triggers, data, failure cases and owners. A dedicated app requires development, tests, documentation and maintenance in the scope. Separate code creates a clearer boundary but does not replace compatibility testing during upgrades.
Each requirement should end with a reasoned classification: standard, configuration, additional app, custom development or currently unsupported. Unresolved points go into consulting before the quote instead of appearing later as unexpected extra work.
ERPNext: workflows · Frappe HR: separate HR app · Clarify requirements in consulting
Classify the requirement in five categories.
Illustrative example, not a client case: a purchase order above an agreed amount needs a second approval. Assess available states, roles and transitions in the installed version first. Then record whether standard features, configuration or extra logic are needed.
The full classification is: standard features, configuration, an additional app, custom development or currently unsupported. Record the test case, version and owner for each requirement. Unresolved requirements should not silently count as standard features.
Also test a change after approval and a rejected purchase order. For payroll, taxes and industry-specific records, an available module is not proof of suitability for your market. The responsible specialists need to validate the specific workflow.