Describe the change in plain words. erpfly writes a proper addon for Odoo 17, 18 or 19, tests it on a sandbox, and hands you the code.
Two ways in
Build
For things Odoo doesn’t ship, or only ships in Enterprise: equipment rentals, inspections, a helpdesk on Community. You get models, views, menus, access rules and tests, packaged with a manifest.
Odoo module development
Customize
For changes to quotations, invoices, deliveries and contacts. New fields, view changes and report tweaks go into a small addon, so an update to Odoo doesn’t wipe them out.
Odoo customization
Example requests
Typical requests, written the way people type them. Underneath each one, what ends up in the odoo addon.
Quotations over $10,000 need Sales Manager approval before confirmation.
sale.order inherited with a To Approve state, an Approve button added by xpath, and a group check in action_confirm.
Sales order module ›Warn the warehouse lead 30 days before a lot expires.
An ir.cron job reading expiration_date on stock.lot, a mail template, and a setting for how many days ahead to warn.
Inventory module ›A helpdesk for Community edition, with tickets from email and a customer portal.
A ticket model with mail.thread and a mail alias, stages in kanban, an SLA deadline field and a portal controller.
Helpdesk module ›Technicians fill in a job sheet with photos and get the customer to sign it.
A job sheet model linked to the task, attachments for photos, a signature field and a QWeb report emailed on completion.
Field service module ›Monthly invoices from contract lines, without the Enterprise Subscriptions app.
A contract model with lines and a next invoice date, and an ir.cron job that creates draft account.move records.
Subscription billing module ›Delivery windows on sales orders, printed on the delivery slip.
Two fields on sale.order, related fields on stock.picking, and an inherited QWeb template for the slip.
Odoo customization ›Fits your setup
from odoo import _, fields, models
from odoo.exceptions import UserError
class ResPartner(models.Model):
_inherit = "res.partner"
credit_hold = fields.Boolean(tracking=True)
class SaleOrder(models.Model):
_inherit = "sale.order"
def action_confirm(self):
held = self.filtered(lambda o: o.partner_id.commercial_partner_id.credit_hold)
if held and not self.env.user.has_group("account.group_account_manager"):
raise UserError(_("%s is on credit hold.", held[0].partner_id.display_name))
return super().action_confirm()The Odoo Online SaaS plan only installs Odoo’s own apps and Studio changes. A custom Python addon needs Odoo.sh or a server you host. If you’re on Online today, moving to Odoo.sh is the first step, and it’s worth pricing before anything else.
Generated addons depend only on what they use. An addon that extends helpdesk or account_accountant will only install on Enterprise, and the manifest says so up front. A lot of what people ask for (approval steps, extra fields, reports, scheduled jobs) works on Community.
Odoo 17 dropped attrs and states in views in favour of plain expressions like invisible="state != 'draft'". Odoo 18 renamed tree views to list. Code written for one version often won’t load on the next, so erpfly writes for the exact version you pick.
Changes to standard models use _inherit and view changes use xpath, so an update to the sale or stock module doesn’t overwrite your work. The difference between _inherit and _inherits trips up a lot of teams, and we wrote a guide on it.
Odoo _inherit vs _inherits ›How it works
In your own words. Paste the spreadsheet or a photo of the paper form if that's easier.
It asks only what it can't work out from your setup, like who's allowed to override.
A copy of your site with the module installed. Break it, then ask for changes.
Code lands as a pull request with tests. Your developer, or ours, reviews it first.
Module library
Every one of these can be built as a odoo addon. Open one to see what gets generated, then describe your version.
Guides
The official documentation and source code this page was checked against.
Glossary
Something missing? Email [email protected] and a person will answer.
Not ones you can install there. Odoo Online doesn’t accept custom Python addons. The code works on Odoo.sh or a self-hosted server with the same version and edition, so moving to Odoo.sh is usually the answer.
Both. Tell erpfly which edition you run and it only depends on modules you have. If a request really needs an Enterprise app, such as Helpdesk or full Accounting, it says so before writing anything.
Odoo 17, 18 and 19. View syntax and a few model APIs changed between them, so the addon targets the version you pick. Odoo’s own schedule ends standard support for 17 in September 2026, so if you’re on 17 it’s worth planning the move to 18 or 19 now.
Yes. Connect the repository and erpfly reads your existing addons before it writes anything. Changes arrive as a pull request against them, so your developer sees a normal diff.
Merge the pull request into a staging branch first. Odoo.sh builds it with a copy of production data, and once you’ve checked it there, merge into the production branch. The module then shows up under Apps to install or update.
It opens the erpfly builder with your description, the Odoo version and the Build or Customize choice already filled in. Nothing is generated until you sign in and confirm.
Running ERPNext instead? The same chat builds and customizes ERPNext too. Last updated .
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.