New ERPNext v16 apps are here

Build, customize ERPNext with AI

Start building free Talk to us

ERPNext v15 & v16
Frappe Cloud or self-hosted
Code in your own repo

Sandbox Running

staging-copy.erpfly.dev

Module installed 38s

#128 Expenses module

+1,142 −0 · 21 files

✓ tests ✓ migrate Ready to merge

expense_claimsERPNext v16

+ New chat History

We still track expenses in a spreadsheet. Build us an expenses module: staff add receipts from their phone, their manager approves, and anything over $500 comes to me as well.

2 questions answered

Which expense types? · Reimburse with payroll or by bank transfer?

› Worked for 6m 18s

Expenses module is live on your sandbox

It's a separate app with its own Expense Report form, so your Accounts setup isn't touched.

•Receipt photo required on every line
•Over $500: manager first, then you
•Paid reports post a Journal Entry by bank transfer

Ask for a change… ↑

Preview Code

New module ready Open in ERPNext

Sandbox · copy of your staging site Viewing as [email protected]

Expense Report / EXP-2026-00041 Pending Approval

Actions ▾

Approve

Reject

Ask for receipts

Details Receipts Accounting Connections

Employee

Sam Okafor

Approver

Dana Hill

DateTypeDescriptionReceiptAmount

08-09-2026 Meals Client dinner, Northfield ✓ $186.40

09-09-2026 Travel Hotel, 2 nights Leeds ✓ $412.00

10-09-2026 Travel Taxi to airport ✓ $58.00

Total Claimed$656.40

DDana approved. Waiting on you: total is over $500.4 min ago

People are building: Bin locations & pick lists Biometric attendance Milestone invoicing Territory-based CRM Job cards for the shop floor

ERPNext: v15 · v16; Frappe apps that install with bench or on Frappe Cloud.
Modules to start from: 21; CRM, stock, HR, projects and more, bent to fit how you work.
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

DocType · Rental Booking submittable

FieldTypeOptions

customerLinkCustomer

machineLinkRental Machine

start_dateDate

return_dateDate

depositCurrency

inspectionsTableDamage Log

Already live on ERPNext?

Change what you already run

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

ERPNext customization

Years of Server Scripts?

Move business rules out of the desk

Ten scripts on one Sales Order, no tests, no history. erpfly rewrites the ones that block documents or touch money as Python in an app, wired through doc_events.

# credit_rules/hooks.py
doc_events = {
    "Sales Order": {
        "validate": "credit_rules.sales_order.check_credit_hold",
    },
}

Server Scripts vs a custom app

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

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.

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 or Frappe 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

job_card.py hooks.py test_job_card_block.py

import frappe
from frappe import _

def validate(doc, method=None):
    overdue = get_overdue_tools(doc)
    if overdue and not frappe.has_role("Production Manager"):
        frappe.throw(
            _("Tool {0} is overdue for calibration")
            .format(overdue[0]),
            title=_("Job card blocked"),
        )

#128 Block job cards on overdue tools

Open

erpfly → main · 11 files · +186 −2

✓ 9 tests ✓ lint ✓ migrate

$ bench run-tests --app tool_calibration

Ran 9 tests in 4.1s

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

Finance

Operations

People

Service

Industry

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 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 with sane role 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

All posts ›

ERPNext 7 min read Connecting biometric attendance devices to ERPNext August 18, 2026 ERPNext 6 min read Server Scripts vs a custom app in ERPNext: when to use which June 23, 2026 Guides 6 min read Reviewing AI-generated ERP code: a checklist May 12, 2026

Questions people ask us

Something missing? Email [email protected] 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 that installs next to ERPNext. 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.

How much does erpfly cost?

Pro is $20 a month and includes $20 of AI credit every month, so what you pay is what you get to spend on building. There’s no per-user fee on your ERP. Plans and how credit works are on the pricing page.

Which versions do you support?

ERPNext and Frappe v15 and v16, including Frappe HR. Apps install with bench on your own server or on Frappe Cloud. 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 and Server Scripts 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.