Custom CRM Module for ERPNext & Odoo, Built with AI

Features

What your CRM module can do

Pipelines that match your stages

Rename, add or split stages. "Site visit done" and "Sample sent" become real statuses with their own required fields, not tags someone forgets to set.

Assignment rules you can read

Round robin, by territory, by product line or by deal size. The rule lives in one Python file with a test next to it, so the next person can change it.

Follow-ups that actually fire

Scheduled jobs create ToDos and emails when a lead goes quiet for N days. You pick N per stage.

Quote approval before it leaves

Discount above a threshold? The Quotation waits in a Pending Approval state until the right role signs off. Audit trail included.

Links into the rest of your ERP

Won opportunities become Customers and Sales Orders with the same items and prices. No retyping between CRM and accounts.

The output

What actually gets generated

Real files in a real repository. Here’s the typical output when someone asks for CRM.

ERPNext / Frappe app

Custom fields on Lead and Opportunity
Territory Assignment Rule DocType
Workflow for Quotation approval
Scheduled follow-up job in hooks.py
Pipeline report (Script Report)

Odoo addon

crm.lead inheritance with new fields
crm.team assignment rules model
Approval states on sale.order
ir.cron follow-up action
Kanban and pivot views

territory_crm/assignment.py

import frappe
from frappe.utils import flt

APPROVAL_LIMIT = 20000

def assign_lead(doc, method=None):
    """Runs on Lead.before_insert. Picks the owner from the territory rule."""
    rule = frappe.get_cached_doc("Territory Assignment Rule", doc.territory)
    if not rule or not rule.sales_users:
        return
    # Round robin inside the territory, skipping people on leave
    active = [u.user for u in rule.sales_users if not u.on_leave]
    if active:
        doc.lead_owner = active[rule.next_index % len(active)]
        frappe.db.set_value(
            "Territory Assignment Rule", rule.name,
            "next_index", rule.next_index + 1,
        )

def needs_manager_approval(quotation):
    return flt(quotation.grand_total) > APPROVAL_LIMIT

Trimmed excerpt. The full module includes tests, fixtures and a README.

How it works

From a paragraph to a pull request

The long version

01
Describe it

In your own words. Paste the spreadsheet or a photo of the paper form if that's easier.
02
Answer a couple of questions

It asks only what it can't work out from your setup, like who's allowed to override.
03
Try it on a sandbox

A copy of your site with the module installed. Break it, then ask for changes.
04
Merge when it's right

Code lands as a pull request with tests. Your developer, or ours, reviews it first.

Why most ERP CRMs end up half used

Here’s a pattern we’ve seen more times than we’d like. A company moves onto ERPNext or Odoo, the finance team is happy, and the sales team keeps its own spreadsheet on the side. The CRM in the ERP isn’t bad. It just asks for fields the reps leave blank and skips the three things the sales manager checks every Monday.

The fix is rarely a different CRM. It’s a CRM that has been bent to fit. That used to mean hiring a Frappe or Odoo developer, writing a spec, waiting for a quote and then waiting again. erpfly shortens the loop to the part that matters: you describe the way your team sells, you look at what gets generated, and you ask for changes until it’s right.

What a CRM module from erpfly contains

When you ask for a CRM, you don’t get a screenshot or a no-code toy. You get source code laid out the way an experienced developer would lay it out.

On ERPNext, that’s a Frappe app. Custom fields go into fixtures so they travel between sites. New objects such as a territory rule or a visit log become DocTypes with proper permissions. Business logic hooks into document events (before_insert, on_update, on_submit) through hooks.py instead of Server Scripts, because Server Scripts are hard to test and harder to review.

On Odoo, it’s an addon with a manifest, models that _inherit from crm.lead and sale.order, XML views that extend rather than replace the stock ones, access rules in ir.model.access.csv, and data files for stages and crons.

Both come with a short README that explains what was added and why. You can hand that to an auditor or a new developer and they’ll follow it.

A realistic example

Say you sell industrial pumps. Leads come in from your website and from three trade shows a year. Your rules are:

Leads in the Gulf region go to Omar and Priya, alternating.
If a lead sits untouched for 5 working days, the owner gets a reminder. After 10 days, their manager does too.
Any quote over $20,000, or with more than 12% discount, needs the sales head to approve.
When a deal is won, create the customer, the sales order and a delivery task for the service team.

That’s the whole prompt. erpfly asks one follow-up question (should people on leave be skipped in the rotation?) and then writes the module. The assignment rule is about 40 lines of Python. The approval step is a standard Workflow, so it shows up in the ERPNext UI exactly where your team expects it.

Things we’d tell you not to build

Not every CRM request is a good idea, and we’d rather say so up front.

A lead scoring model with 30 inputs. Start with three signals you trust. You can add more once you see which leads actually close.
A replacement for your email client. Logging emails against leads works well. Rebuilding Gmail inside ERPNext doesn’t.
Custom fields for every edge case. If a field is filled in on less than one lead in ten, it probably belongs in a comment.

What to prepare before you ask

You don’t need a spec. But ten minutes of prep makes the first version much closer to right. Pull up an export of last quarter’s leads and look at which columns your team actually filled in. Write down your pipeline stages as the sales manager says them out loud, not as they appear in the software. And decide who is allowed to approve a discount, because that single question causes more back-and-forth than everything else combined.

How it fits with the rest of your ERP

A CRM on its own is a contact list with extra steps. The value shows up when it connects to what happens after the deal. Because erpfly generates modules against your real ERP schema, a won opportunity can flow into sales orders, then invoices, then support tickets in a helpdesk, without a single CSV export.

If you’re running ERPNext and want the wider picture, our page on ERPNext custom module development explains how generated apps are structured and deployed. Odoo teams should look at Odoo module development.

Guides and terms for CRM

Guide · ERPNext Upgrading ERPNext without breaking your customizations Updated September 10, 2026 Guide · ERPNext How much does ERPNext customization cost? Updated May 6, 2026 Guide · ERPNext How to create a custom DocType in ERPNext Updated September 12, 2026

Terms used on this page

CRM module questions

Something missing? Email hello@erpfly.com and a person will answer.

Can erpfly change the CRM I already have, or only build a new one?

Both. Most people start by extending the stock CRM in ERPNext or Odoo, adding fields, stages and rules on top. We only generate a separate CRM app when the data model is different enough that bending the standard one would hurt.

Will my customisations survive an ERPNext or Odoo upgrade?

They sit in their own app or addon and never edit core files. That's the main reason upgrades break, and we avoid it. You'll still want to run the included tests after a major version jump.

Does it work with HubSpot or Salesforce data?

We can generate an import script or a scheduled sync that pulls contacts and deals over their APIs. Two-way sync is possible but we'll ask you which system wins when both change the same record.

Who owns the code?

You do. It's a normal Frappe app or Odoo addon in your Git repository. Cancel erpfly tomorrow and the CRM keeps running.

How long does a CRM module take?

The first working version usually appears in a few minutes. Getting it right takes longer, typically a day or two of trying it with real leads and asking for changes.

Sales & CRM Sales order management The stock Sales Order in ERPNext or Odoo is fine until an order sells under cost, ships in three drops or gets confirmed by someone who shouldn't. Build it Finance Invoice management Invoices rarely go unpaid because the customer forgot. Build it Service Helpdesk Most support teams run a separate ticketing tool, and half of every ticket is someone switching to the ERP to check the contract, the serial number and whether the last invoice got paid. Build it Something else? Browse every module, or describe one we haven't listed. Build it

Your next module is one paragraph away

Write it the way you’d explain it to a new hire. We’ll turn it into an app you can read, test and install.

Build a custom CRM on ERPNext or Odoo, without the six-week wait