Skip to content
New Odoo 19 addons are here

Build, customize ERPNext and Odoo with AI

Start building free Talk to us
People are building: Bin locations & pick listsBiometric attendanceMilestone invoicingTerritory-based CRMJob cards for the shop floor
ERPNext
v15 · v16
Frappe apps that install with bench or on Frappe Cloud.
Odoo
17 · 18 · 19
Community and Enterprise addons, deployable to Odoo.sh.
Core files edited
0
Everything extends or inherits, so upgrades stay boring.
Code you own
100%
Pull requests to your GitHub or GitLab. No hosted black box.

What you can build

Start with one annoying gap. Go as far as you like.

ERPNext · Frappe

New modules on ERPNext

A proper Frappe app with DocTypes, workflows, reports and tests. Installs with bench, runs on Frappe Cloud.

ERPNext module development

Already live on ERPNext or Odoo?

Change what you already run

Fields, approvals, print formats. Shipped as fixtures, so they survive upgrades.

ERPNext customization

Odoo 17 · 18 · 19

Odoo addons without the boilerplate

Models, inherited views, access rules and QWeb reports. Community or Enterprise.

Odoo module development

When nothing off the shelf fits

A custom ERP from scratch

Start on the Frappe framework, not a blank repo. Users, permissions, API and reports exist on day one.

Custom ERP development

How it works

From a paragraph to a pull request

The long version
  1. 01

    Describe it

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

  2. 02

    Answer a couple of questions

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

  3. 03

    Try it on a sandbox

    A copy of your site with the module installed. Break it, then ask for changes.

  4. 04

    Merge when it's right

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

For developers

Real code in your repo. Not a black box.

Every change is a pull request your developer would recognise: app structure, tests, migrations and a README that says what changed and why.

  • Never edits ERPNext, Frappe or Odoo core files
  • Validation on the server, not only in the browser
  • Tests and migration patches in every pull request
  • Keeps working if you cancel erpfly tomorrow
See the full pipeline

Module library

Pick a starting point

The modules people ask for most. Each is a template you bend to fit, not a fixed product.

All 21 modules ›

Sales & CRM

3

Finance

4

Operations

5

People

3

Service

4

Industry

2

By industry

Built around how your trade works

Lot tracking for food. Retention on progress bills for construction. Trip sheets for logistics. The details generic ERP demos skip.

Straight answer

Why not just hire a Frappe or Odoo developer?

Sometimes you should. A good ERP developer knows accounting edge cases no model does. But most module work isn't that. It's DocTypes, views, permissions, a report, a print format and the tests that always slip to next sprint.

erpfly does that part in minutes, so expensive human hours go where they matter.

Read the full comparison ›

erpfly is good at

  • New DocTypes and Odoo models with sane permissions
  • Workflows and approval chains
  • Extending standard documents without core edits
  • Reports, print formats, dashboards
  • Import scripts from spreadsheets
  • Writing the tests you’d skip

Bring a human for

  • Changing how GL entries are posted
  • Country-specific payroll and tax law
  • Data migrations with years of history
  • Performance tuning on huge sites
  • Deciding what the process should be
  • Anything you can’t explain yet

From the blog

Written by people who ship ERP code

ERPNext 7 min read Connecting biometric attendance devices to ERPNext August 18, 2026 Odoo 6 min read _inherit vs _inherits in Odoo, explained with examples August 11, 2026 Odoo 6 min read Odoo Studio vs a custom module: which should you use? June 30, 2026

Questions people ask us

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

What exactly is erpfly?

It’s an AI builder for ERP code. You describe a module (a CRM rule, a warehouse process, a whole rental business) and erpfly writes it as a Frappe app for ERPNext or an addon for Odoo. You test it on a sandbox copy of your site, then merge it into your own repository.

Is this a no-code tool?

No, and that’s on purpose. No-code tools keep your logic inside their platform. erpfly produces ordinary source code, so a developer can read it, you can version it, and it keeps working if you stop paying us.

Do I still need a developer?

For small modules, often not. For anything touching accounting entries, heavy integrations or a production go-live, we recommend a developer reviews the pull request. erpfly turns weeks of their time into an afternoon of review.

Which versions do you support?

ERPNext and Frappe v15 and v16, and Odoo 17, 18 and 19 (Community and Enterprise). We add new major versions shortly after they’re released.

Can it work with my existing customizations?

Yes. Connect a staging site and erpfly reads your current DocTypes, custom fields or Odoo models first, so new code builds on what you have instead of fighting it.

Where does my data go?

erpfly needs your schema, not your records. A read-only key on a staging site is enough. Sandbox copies are deleted when you close a project. See our privacy page for the details.

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.

ERPNext v16