Odoo 19 Custom Development
Custom Odoo 19 modules: models, XML views, controllers, reports, wizards and OWL assets.
testapp and todo_management built on Odoo 19
Custom modules
Business logic modelled with the Odoo ORM
ORM & models
XML views, reports, wizards and controllers
Full view stack
Hands-on Odoo 19 custom development involving custom modules, business models, controllers, XML views, reports, wizards, OWL frontend assets, PostgreSQL integration, internationalisation and Arabic localisation.
Odoo's real power is its framework, and that power only shows when you stop configuring and start coding. The challenge is to demonstrate the full development stack — custom models on the ORM, XML views, controllers, reports, wizards, OWL frontend assets and localisation — working together in real modules.
Built custom Odoo 19 modules — testapp and todo_management — using the Odoo ORM over PostgreSQL. Each module exercises the full stack of Odoo development: Python models, XML views, controllers, reports, wizards, OWL frontend assets and PO/POT-based internationalisation with full Arabic support.
How data moves through the system.
Custom addons sit on top of Odoo core and persist through the Odoo ORM into PostgreSQL.
- 01Odoo Core
- 02Addons
- 03Custom Modules
- 04PostgreSQL
- 01Custom modules: testapp and todo_management
- 02Business models via the Odoo ORM
- 03HTTP controllers
- 04XML form, tree and action views
- 05Report templates
- 06Wizard models
- 07OWL frontend assets
- 08Internationalisation
- 09Arabic support and localisation
- 10PostgreSQL-backed persistence
testapp and todo_management built on Odoo 19
Custom modules
Business logic modelled with the Odoo ORM
ORM & models
XML views, reports, wizards and controllers
Full view stack
Custom frontend assets in the Odoo UI
OWL frontend
PO/POT translations with full Arabic localisation
Arabic ready
testapp and todo_management are separate addons that demonstrate model, view and business-logic patterns in a framework-conformant structure — manifest, models, views, controllers and assets.
Custom business models defined with the Odoo ORM, mapped to PostgreSQL tables with fields, constraints and computed values.
Form, tree and action views authored in XML following Odoo's view architecture, including view inheritance where appropriate.
HTTP controllers that expose custom endpoints beyond Odoo's standard web routes.
Report templates and wizard models that drive guided, multi-step interactions with users.
OWL component assets bundled into Odoo's frontend asset pipeline to extend the interface.
PO/POT-based translation files covering module labels and strings, including full Arabic localisation.
Python virtual environment, Git version control, Odoo configuration and the standard development server on port 8069.
- Learning Odoo's framework conventions — inheritance, model scaffolding, view inheritance and the addon manifest system.
- Getting Arabic localisation right across labels, menus and reports.
- Wiring OWL frontend assets into Odoo's asset pipeline.
- Custom modules beat configuration when a business process is genuinely different.
- Framework-conformant structure makes an Odoo module maintainable and installable.
- Localisation is part of the module contract, not an afterthought.