Most ERP projects don’t fail on the hard parts
They stall on the ordinary ones. A form that needs three extra fields and an approval. A report finance asked for in March. An integration that’s been “next sprint” for a year.
None of that work is difficult. It’s just slow, because every change goes through the same queue: find a developer who knows Frappe or Odoo, explain the business, wait, test, explain again.
erpfly is our attempt to shorten that queue. You explain the business once, in your own words, and get code a developer would recognise as their own style, with tests.
What we believe about ERP code
You should own your code
If a tool holds your business logic hostage, it isn’t a tool. Everything erpfly writes goes into your repository as plain Python, JavaScript and XML.
Core files are off limits
Editing ERPNext or Odoo core is the fastest way to a project nobody can upgrade. We extend, inherit and hook. We never patch.
Tests aren’t optional
Humans skip them because they’re tedious. A machine has no excuse, so every module ships with tests for the rules you described.
Say when a human is needed
Some changes need an experienced consultant. We would rather tell you that than generate something confidently wrong.
Who uses erpfly
Three kinds of people, mostly. Operations and finance leads at companies already running ERPNext or Odoo, who know exactly what they need and are tired of waiting for it.
In-house developers who’d rather review a pull request than write their fortieth DocType by hand.
And implementation partners, who use it to get a client’s first custom modules on screen during the discovery workshop instead of three weeks after it.
Questions, partnership ideas or a module you think we’ll get wrong? Get in touch.
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.