ERP

Odoo Engineering

Professional experience from v10 to v19, with the deepest focus on v16–v19 Enterprise. Custom module development, complex integrations, multi-version migrations, and production system maintenance.

Odoo EnterpriseV10–V19Python · PostgreSQL · QWeb5+ yrs experience ↗

Version coverage

Version Coverage

First contact on v8 during a university internship. Professional from v10 onward. Migration history includes a v10 → v16 jump in a single project.

Internship
v8v10
Professional
v13v14v15
Primary focusEnterprise
v16v17v18v19

Completed multi-version migration projects, including a production instance moved from v10 to v16 in a single engagement.


Business coverage

Business Domains

Functional areas with strong technical and process familiarity.

Core coverage
SalesInventoryAccountingPurchaseHelpdeskPOSHR & Planning
Peripheral
eCommerce

Technical work

Technical Work

What gets built, debugged, integrated and shipped.

01

Core Development

  • Full module development lifecycle
  • ORM & computed fields
  • Server actions & automated actions
  • Cron jobs
  • Direct SQL queries
  • Constraints & onchange logic
02

Reporting

  • QWeb templates (PDF & web)
  • account.report framework
  • XLSX custom reports
  • Custom invoice & document layouts
03

Integrations

  • REST API controllers (inbound)
  • Outbound API integrations
  • Pentaho · Trusted Shops · OXID
  • Roomz · Quotapath
  • Bidirectional data sync patterns
04

Performance & Debugging

  • PostgreSQL query optimization
  • ORM profiling & N+1 detection
  • Production issue debugging
  • Index tuning & query planning
05

Infrastructure

  • Odoo.sh workflows
  • GitHub Actions CI/CD
  • Docker-based environments
  • Linux server management
06

Frontend

  • Owl component framework
  • POS frontend customizations
  • Website & eCommerce overrides
  • Modern JS tooling

How I work

How I Build

A few principles that shape the work.

  1. Upgrade-friendly over clever. If a customization requires heroics at upgrade time, it was built wrong.

  2. Module boundaries that reflect the business domain, not the development timeline.

  3. Integrations designed to fail gracefully, with clear errors, not silent data corruption.

  4. PostgreSQL treated as a first-class concern, not an afterthought when the module is already slow.

  5. Code readable by the next developer without a guided tour.

CONTACT

Have an Odoo project in mind?

Whether it's a new module, a migration, a complex integration or a production issue, get in touch and let's talk about it.