Odoo Development

1,499.99 LE

Responsible	INFO
Last Update	04/25/2026
Completion Time	21 hours 23 minutes

Odoo Architecture Overview

2Lessons · 19 min
- Introduction To Odoo Development
- Configure & Install Odoo
Creating Custom Modules

1Lessons · 4 min
- Scaffolding your first module & Create Custom Addon
Views and UI in Odoo

4Lessons · 9 hr
- Form view deep dive
- List view & kanban view
- Search view, filters & group-by
- Actions & menu items
🧾 Business Case: Automated Service Billing & Contract Management Addon

1Lessons · 12 hr
- Reference Book

Course AI Assistant On-device AI · Odoo Development Local · private

Hi! I am your AI assistant for this course. I can map your progress, check your skills, and answer your questions — pick a tool below, or type a question of your own.

AI tools

Course questions

Getting set up

Building a module

Views and UI

Odoo uses a three-tier architecture: a PostgreSQL database that stores the data, an application server that holds the business logic, and a web client that runs in the browser. Everything in Odoo is built as modules -- even the core features -- which is what makes the system so easy to extend.

You set up Python, PostgreSQL, and the Odoo source code, then configure Odoo through a configuration file that points to your database and your addons paths. Turning on developer mode unlocks the technical tools you need while building. The "Configure & Install Odoo" lesson covers the full setup step by step.

Odoo can generate a module skeleton for you with its scaffold command -- it creates the standard folder structure, including the manifest file and the models, views, and security folders. From that starting point you add your own models, views, and access rules. The "Scaffolding your first module" lesson walks through it.

A form view is the screen for viewing and editing a single record, such as one customer or one product. It is defined in XML and arranges fields into groups, tabs, and buttons. The "Form view deep dive" lesson covers required and readonly fields, header buttons, and status bars.

A list view shows many records as rows in a table -- good for scanning and quick edits. A kanban view shows records as cards arranged in columns -- better for visual workflows such as a sales pipeline. A single model can offer several views, and the user switches between them.

The search view defines what appears in the search box above a list or kanban view: which fields are searchable, the predefined Filters, and the Group By options. It lets users slice and explore large sets of data without writing any code.

A menu item is what the user clicks in the interface; an action is what that click does -- usually opening a particular model in a particular view. Together, menu items and actions define how users navigate through your module.