What I learned customising ERPNext for real operations teams

ERPNext gives you a working business system on day one. The risk is that it is so malleable you can quietly paint yourself into a corner.

Never edit core

Every change belongs in a custom app. Core edits survive exactly until the next upgrade, and then you spend a week reconstructing what you changed and why.

• Use custom fields and Property Setters instead of altering DocTypes
• Put business logic in hooks, not in patched core methods
• Keep the custom app in version control and deploy it like any other code

The rollout is a people problem

The technical work is usually the smaller half. Mapping an existing manual process onto ERP concepts — and getting the team to trust the new numbers — is where projects succeed or stall.