Odoo2 min read
Odoo 20 POS and eCommerce: What Retailers Get
Odoo 20 for retailers: POS self-ordering, multiple currencies, employee access levels, label printing, plus eCommerce cross-sells, review requests and AI editing.
ERP platform · Odoo
Odoo development that survives the next upgrade
The Odoo framework makes it easy to add a field, override a method or patch a view. It also makes it easy to build a system that cannot be upgraded without a rewrite. The difference is engineering discipline: inheriting instead of copying, extending instead of overriding, and writing tests that fail loudly when a new version changes behaviour.
Overview
The short version
Our developers work in Python, the Odoo ORM, XML views, QWeb and the OWL JavaScript framework. Every module goes through code review, runs against automated tests on a staging branch, and ships with enough documentation that another competent Odoo developer could maintain it.
ERP Builders is an independent Odoo services company and is not affiliated with or endorsed by Odoo S.A. “Odoo” is a trademark of Odoo S.A.
01
What we build
Most development work falls into a few recognisable categories.
Business logic extensions
Pricing rules, approval workflows, allocation logic, custom costing — implemented as inherited models with clear entry points.
New applications
Purpose-built apps for processes Odoo does not cover: equipment certification, consignment tracking, tolling agreements, rental contracts.
Reports and documents
QWeb PDF reports, Excel exports and SQL-backed reporting views for operational and management reporting.
Portals and front-end
Customer and supplier portal extensions, website features and OWL components for the back-office interface.
Integrations and APIs
Connectors to external systems, webhook receivers, scheduled synchronisation jobs and custom REST endpoints.
Performance work
Profiling slow screens and reports, replacing loops with batched ORM calls, adding indexes and stored computed fields.
02
Engineering standards
Code lives in Git, one repository per client, with separate staging and production branches. Modules are small and single-purpose so they can be upgraded, tested and removed independently. We avoid monkey-patching core code and avoid overriding methods without calling super() unless there is a documented reason.
Before any module ships we check access rights and record rules, multi-company behaviour, translation of user-facing strings, and performance with realistic data volumes. Those are the four areas where custom Odoo code most often fails in production.
03
Working with your existing code
Many clients come to us with modules written by previous partners or freelancers. We start with a code audit: which modules are still used, which duplicate standard functionality now available out of the box, and which are fragile. Removing unnecessary custom code is often the fastest way to make a system cheaper to run.
Related
Related Odoo services and topics
Integrations
Industries
Insights
Related reading
Odoo2 min read
Odoo Partner vs Independent Odoo Consultant
Official Odoo partners, independent Odoo firms and freelancers compared on pricing, independence and support, plus questions to ask before you sign.
Odoo2 min read
Odoo POS for Retail: Setup, Hardware and Lessons
Running retail on Odoo Point of Sale: shop setup, hardware choices, offline mode, multi-store stock, loyalty, cash control and connecting stores to online sales.
FAQ
Frequently asked questions
Which Odoo versions do you develop for?
We develop for currently supported Odoo versions and regularly migrate modules from older versions. For new work we recommend the latest stable release unless a dependency prevents it.
Do we own the code you write?
Yes. All code, documentation and configuration we produce for you belongs to you and lives in a repository you control.
Can you build on Odoo Online?
Odoo Online does not allow custom Python modules. Customisation there is limited to configuration and Studio. Custom development requires Odoo.sh or a self-hosted environment.
Should we use Studio or custom modules?
Studio is fine for simple fields, views and automations that business users maintain themselves. Anything with real logic, integrations or performance requirements belongs in a proper module under version control.
Comparisons
Weighing Odoo against alternatives?
Odoo vs SAPIntegrated, extensible suite for SMB and mid-market versus the deepest enterprise ERP ecosystem on the market.Odoo vs Dynamics 365An all-in-one suite versus Microsoft's ERP ecosystem with deep Office, Teams and Power Platform integration.Odoo vs NetSuiteFlexible, lower-cost suite versus a mature cloud-only ERP with strong financials and multi-entity support.
Next step
Need an Odoo developer who writes maintainable code?
Describe what you need built. We will tell you whether it needs code at all.