Odoo Architecture Explained
May 20, 2026 · 8 min read
Odoo’s architecture is simpler than it sounds: modular apps, one PostgreSQL database, and documents that move through defined workflows.
Apps on a shared core
Install only what you need. Apps register models, views, and menus on top of a shared framework, so Sales and Inventory can reference the same product and partner records.
Documents, not islands
Business objects — leads, quotations, receipts, invoices — are records with states. Confirming a sales order can reserve stock and later create a delivery. That state machine is the heartbeat of Odoo.
Why setup quality matters
Because everything shares data, messy product masters or unclear warehouse routes ripple everywhere. Architecture rewards clean foundations more than clever custom modules.
Customization in context
Studio, custom modules, and integrations are powerful — and expensive to maintain if used as a first resort. Prefer configuration and standard flows before writing code.