ProjoMania

Odoo services

Odoo Customization

Studio configurations, custom modules, QWeb reports, OWL components, and API integrations. Clean code, upgrade-safe, tested.

Was wir tun

Customization, done well

Odoo customization ranges from a Studio-added field to a multi-module suite with tests and a CI pipeline. The discipline matters as much as the code — customizations that do not survive an upgrade are just technical debt with an invoice.

What we do

Studio customizations — fields, views, automated actions, server actions, reports, approvals. Fast, low-ceremony, upgrade-conscious.

Custom modules in Python / XML / OWL — when the logic is non-trivial. Clean ORM code, QWeb and PDF reports, OWL front-end components, ACLs and record rules, module tests, migration scripts.

Integrations — external APIs (Stripe, PayPal, Shopify, QuickBooks, Salesforce, HubSpot, Slack, Twilio, and the rest). XML-RPC and JSON-RPC clients. Webhook subscribers. Event-driven sync with queues where appropriate.

Code audits — someone else wrote the module and you inherited it. We review it, report on upgrade risk, test coverage, and security, and rewrite what should be rewritten.

How we write code we stand behind

  • Version-controlled in a repo you own, Conventional Commits, PRs reviewed before merge.
  • Pinned to your Odoo version; migration scripts when we ship across versions.
  • Tests where they catch things that matter (critical workflows, money-affecting logic, integration boundaries). Not tests for the sake of coverage numbers.
  • Documentation that says why the customization exists, because “what” is already in the code.
  • Security: no SQL concatenation, parameterized env.cr.execute, proper ACLs, sensible record rules.

Typischer Zeitplan

Drei indikative Engagement-Größen

Klein

1–3 weeks — Studio + small Python tweaks

Mittel

3–8 weeks — custom module with non-trivial logic

Groß

8+ weeks — deep customization or multiple modules

Jedes Angebot ist individuell. So funktioniert die Preisgestaltung →

FAQ

Häufige Fragen zu odoo customization

Studio or custom module — which should I use? +

Studio for fields and small automations where upgrade cost matters less than speed. Custom module when the logic is non-trivial, needs tests, needs review, or you expect it to live for years.

Can you take over code written by another developer? +

Yes. We do that regularly. First step is a code audit — you get an honest assessment of what you have.

Do I own the code? +

Yes. Everything we write for you goes into a repository you own, under a license you choose. No lock-in.

odoo customization-Projekt starten

Sagen Sie, woran Sie arbeiten. Wir antworten innerhalb eines Werktags.