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 customization without the upgrade penalty
Every business believes its processes are unique, and some of them are. But in most Odoo projects a large share of requested customisations turn out to be achievable through configuration, a different use of a standard feature, or a small change in the process itself.
Overview
The short version
We work through a simple hierarchy: configure first, then use Studio or automated actions for light changes users can maintain, and write custom modules only when the requirement is genuinely specific and valuable. Each layer is cheaper to own than the next.
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
The customization ladder
Each step up adds capability and adds maintenance cost. We climb only as far as the requirement needs.
1. Configuration
Routes, operation types, approval settings, pricelists, fiscal positions, email templates. No code; survives every upgrade.
2. Studio and automated actions
Extra fields, view changes, simple server actions and scheduled automations. Maintainable by trained business users.
3. Light modules
Inherited views and models, computed fields, constraints, additional report layouts. Small code, low upgrade risk.
4. Substantial modules
New business objects, complex workflows and integrations. Justified only when the process is a real differentiator.
02
Customizations we are asked for most
Approval workflows on purchases and discounts. Customer-specific pricing that standard pricelists cannot express. Additional fields on products and partners that drive downstream logic. Custom sale order and invoice layouts. Barcode and picking flows adjusted to a specific warehouse layout. Commission calculations. Credit-hold rules that block deliveries rather than just warning.
Several of these have standard or near-standard solutions in recent Odoo versions. Before quoting development, we check whether the version you are on — or the next one — already handles it.
03
Keeping customizations healthy
We document every customisation in a register: what it does, why it exists, who requested it, and which module contains it. At each upgrade the register is reviewed, and customisations that standard Odoo has since made redundant are removed. That single habit keeps long-running Odoo systems from accumulating years of dead code.
Related
Related Odoo services and topics
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
Is Studio safe to use?
For simple fields, view changes and basic automations, yes. Problems start when Studio is used to build complex logic that nobody documents. We set rules about what belongs in Studio and what belongs in version-controlled code.
How do customizations affect upgrades?
Configuration and Studio changes usually migrate with the database. Custom modules must be adapted to each new version. The more a module overrides core behaviour rather than extending it, the more effort each upgrade takes.
Can you remove customizations a previous partner made?
Yes. We audit existing custom code, identify what standard features now cover, and plan a careful removal with data migration where custom fields held important information.
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
Want Odoo to fit how you work?
Bring your list of requirements. We will show you which need code and which do not.