Odoo development
When configuration runs out, we write code: custom Odoo modules, APIs, workflows and integrations, built as separate addons that survive the next upgrade. Configuration-first decisions belong on the customization page. This page is about what happens after them.
Reviewed by Atul Makwana, CEO & Co-Founder, Heliconia Solutions · Odoo 16 Functional Certification · Odoo Partner · Updated
Businesses that run on what we built
What we build
Odoo is a Python framework with an ERP on top. These are the things we engineer with it.
Business logic, workflows and whole applications: a jewellery saving-scheme engine, a foundry heat-to-part traceability system, a four-island payroll.
REST endpoints and custom controllers that expose exactly the business models a client or partner needs, with authentication designed in.
GraphQL layers (Graphene) for web and mobile clients that need fast, shaped data: the approach behind our headless commerce and mobile work.
Odoo as the backend with a Next.js, React, React Native or Flutter frontend, connected over APIs.
React Native and Flutter apps for customers, suppliers and field staff, talking to Odoo through GraphQL and REST.
Scheduled operations, recurring documents, approval chains, notifications and integrations that remove manual steps.
How a feature is built
Written with the process owner: what the business needs, the edge cases, and how success is checked. Then the configure / OCA / custom ladder. Custom only when the others fail.
Which models, which module boundaries, which existing Odoo mechanisms to extend (inheritance, computed fields, server actions) and what must stay outside Odoo.
Built as a separate addon against the target version, with security rules, tests and a migration script where data changes.
Unit tests on business logic, functional tests on the workflow, and review of performance on realistic data volumes.
Connected to the surrounding systems (frontend, mobile, payment, external APIs) with logging and retries.
Through version control and CI to staging, then production on Odoo.sh, cloud or on-premise, with a rollback path.
Development standards
Cheap customization is easy to buy and expensive to keep. These are the standards that separate a module you can upgrade from one you'll have to rewrite.
Every customization is its own addon. Odoo core is never edited, so version upgrades remain a migration of our modules, not a rewrite.
We contribute to the Odoo Community Association and follow its coding, naming and structure guidelines, so any Odoo developer can read our code.
Built against the target version with migration scripts where data changes. Upgrade-conscious from the first commit.
Shared modules (direct printing, operating-unit security, S3 storage, notifications) reused across clients instead of rebuilt.
Automated tests on business logic, code review before merge, Git history for every change, CI to staging before production.
Module READMEs, API documentation and deployment notes, so the system doesn't depend on the memory of whoever built it.
Headless Odoo
When the standard Odoo interface is the wrong experience for customers, suppliers or field teams, we keep Odoo as the system of record and build the frontend the product needs.
Web
Next.js / React
Mobile
React Native / Flutter
Custom apps
Portals, supplier tools, dashboards
API layer
GraphQL (Graphene) · REST · Webhooks · Odoo session auth
Odoo
Products, orders, customers, inventory, subscriptions: the business logic lives here
PostgreSQL + services
Redis, Meilisearch and S3-compatible storage where the product needs them
Development stack
Only what we actively use in production.
Evidence
The custom modules, APIs and frontends behind real production businesses.
Jewellery retail & manufacturing
Multi-store fine jewellery retail and manufacturing on Odoo Enterprise: daily metal rates, RFID-tagged serialized stock, gold saving schemes with recurring payments, and a customer mobile app synced over GraphQL.
Alloy casting & foundry manufacturing
Multi-stage alloy casting (molding, pouring, heat treatment, NDT, machining) on Odoo 16 Community, with furnace heat numbers traced to every dispatched part, a metallurgy lab module and Material Test Reports generated in seconds.
eCommerce, baby care
A direct-to-consumer baby care brand selling through a Next.js storefront, with Odoo behind it for ERP, inventory, orders and customers: connected over GraphQL, with Cashfree payments, Shiprocket shipping and a distributor onboarding portal.
Jewellery manufacturing
A bangle and fashion-jewellery manufacturer’s product catalog managed in Odoo and delivered to a cross-platform Flutter app over GraphQL, with media on Cloudflare R2 and production monitoring.
First-party experience
The customization that edits Odoo core to save a day costs a month at the next upgrade. We have migrated other teams' core edits. We don't create them.
GraphQL earns its place when a mobile app or storefront needs shaped, fast reads. For a simple integration, a REST endpoint is the better tool.
Realistic data volumes belong in testing. A workflow that is fine on 100 records can be unusable on 100,000 serialized items.
Reusable modules across clients (direct printing, operating-unit access, storage adapters) are where an engineering-led partner compounds value.
What clients say
Heliconia's Odoo Enterprise implementation, along with third-party system integration, has optimized our processes. Their expertise has been a game-changer.
Vladimir VukovicCEO, Mevalon ProdukteHeliconia delivered an impeccable Odoo Enterprise implementation with seamless integration. Their expertise has revolutionized our operations.
Kartson KrayChairman, TIMmunity GmbHQuestions
An Odoo developer builds and maintains Odoo modules (models, business logic, views, reports, security rules) and the APIs and integrations around them, in Python on the Odoo framework.
Senior Odoo developers also decide what shouldn't be custom: configuration, an OCA module or an external service are often the better answer.
Yes. Custom module development is the core of our development work, from single-feature modules to complete industry systems with dozens of modules, as at Aria Jewellers and Hi-Tech Alloys.
Yes. We build REST endpoints and GraphQL layers on Odoo for web, mobile and third-party clients, with authentication, rate limiting and documentation.
Yes. We build the mobile app (React Native or Flutter) and the Odoo API it talks to, as for Aria Jewellers' customer app, Ramdev Kangan's supplier catalog app and Freiburger Bund's member app.
Yes. Headless Odoo (Odoo as backend, a custom frontend in Next.js, React or a mobile framework) is one of our signature capabilities, used for LittleQ's storefront and Freiburger Bund's portal.
Yes, including modules we didn't write. Custom-module migration is part of every version upgrade we run.
Yes. We review the existing modules first (separation from core, upgrade risk, tests) then extend, refactor or replace them. Taking over another team's code is a normal starting point.
Yes. When the need is ongoing capacity rather than a defined project, developers, consultants or a full team can work inside your process, as they do for ERP Happy.
Related reading
Odoo
Explore the concept of context in Odoo, its importance, and practical uses. Learn how context enriches user interactions and system functionality.
Odoo
odoo-devtools-mcp is an MCP server by Heliconia Solutions that exposes Odoo development workflows to AI tools. Inspect models, fields, modules, and code faster.
Next step
Describe the requirement and the version you're on. We'll tell you whether it needs custom code at all, and if it does, how we would build it so it lasts.