I have a custom app to change some of the way that ERPNext’s CRM works. I maintain it all in a custom app for my own business, and some of my customers’ instances.
I originally built it for myself, but they’re pretty broadly useful and I think a lot of people could benefit from them.
The app includes (but not limited to):
Overriding the setting of a Lead’s phone number to the mobile_no field when it’s left blank.
Various CRM-specific Number Cards
Checking Leads/Prospects for duplicates at time of creation (based on Lead name or the name of the business)
Opportunity Net Amount Field (calculate the net amount $ of an Opportunity based on selling/buying prices of items)
Opportunity Theoretical Value Field (calculate the theoretical value of an Opportunity based on the Sales Stage - the user can define the various % of likelihood to closed in the settings page).
None of the features override any default behavior except number 1.
Honestly, it can be difficult and slow to get code merged. I get why that frustrates people, but I also get why it’s that way.
Your best bet is to try to break your PRs into parts that are as small as possible. Label them accurately, give a good description, and provide unit tests if appropriate. After some time, you may need to ping maintainers.
Also, it’s worth noting that ERPNext’s CRM module is no longer actively developed. I don’t know if that will make the maintainers more or less likely to consider your changes.
Yes, I’m assuming that the ERPNext CRM module was “abandoned” in favor of the new Frappe CRM app, which is unfortunate, because the Frappe CRM really doesn’t integrate that well with the rest of ERPNext.
For me, the abandoning of the ERPNext CRM module has been something of a blessing, since it makes it easier for me to maintain any modifications that I make to it…