Odoo 20 System Architecture and Modular Logic Encyclopedia

1. Architecture Overview: The Odoo Modular Philosophy That Breaks Down ERP Complexity

1.1 Single Database and Single Platform Seamless Integration Logic

Traditional enterprise software systems are often pieced together from multiple independent specialized systems—for example, a standalone customer relationship management (CRM) system, an independent third-party website hosting platform, an offline warehouse management system (WMS), and standalone financial software. This fragmented architecture creates severe data silos within the enterprise, forcing employees to perform tedious secondary manual data entry or to rely on costly third-party API interfaces that are prone to integration breakdowns.

Odoo 20's underlying core philosophy lies in the single database and unified platform. In Odoo's system architecture, all business applications (Apps) are not software running in isolation, but rather modular extensions built on the same database engine and a unified object-relational mapping (ORM) model. This means that all business data within the system is stored in a single central data source, and data linkage between modules does not rely on backend "scheduled asynchronous polling" or external API transmission, but is entirely based on the event-driven mechanism of the underlying unified ORM model.

For example, when a customer completes an online order in the Website/eCommerce module, the underlying data flow logic is as follows:

1. Object Status Change: The frontend triggers order confirmation, and the status of the ORM model sale.order changes;
2. Underlying linkage trigger: The status change of sale.order directly depends on triggering the underlying logic, creating the stock.picking warehouse transfer document in real time and freezing the corresponding inventory, without any scheduled synchronization delay;
3. Financial Draft Generation: The system automatically generates account.move financial invoice drafts in sync;
4. Real-time general ledger mapping: After invoice confirmation, transaction logs are mapped directly to the accounting general ledger, enabling millisecond-level real-time linkage across business domains.

To help beginners understand this intuitively, the table below compares the essential differences between the traditional decentralized architecture and Odoo 20's integrated unified architecture:

1.2 Evolution of Odoo 20's Interface and Interaction Architecture

Beyond the seamless integration of the underlying database, Odoo 20 has completed a system-level architectural evolution in its user interface (UI) and user experience (UX). Its design goal is to completely eliminate the heavy feel of traditional ERP systems and provide a modern operating experience that is as smooth, intuitive, and highly responsive as a consumer-grade app:

• Visual Hierarchy Restructuring: Adopting **Rounded Design** and subtle gray neutral backgrounds, paired with high-contrast white content card areas, enables users' visual attention to instantly focus on core business data.
• Modernized Icon System: Comprehensively introduced the brand-new Material Symbols icon library to replace the traditional Font Awesome icons, significantly enhancing the overall visual consistency and modern technological feel of the interface.
• Millisecond-level response and smooth transitions: The front-end DOM rendering and CSS dynamic transition effects have been optimized, boosting page switching and data loading speeds to the 10-millisecond level. Combined with smooth micro-interaction animations, this completely eliminates any sense of operational lag.
• Mobile and Touch Architecture Adaptation: A comprehensive restructuring of the mobile and tablet experience, supporting opening the command palette by pulling down on the main dashboard, a touch slide-out mechanism for the bottom panel, and a more secure modern login interface.

Having grasped the system's underlying architecture and interaction evolution, we can further extend our perspective into the four core business groups (Business Groups) that support the enterprise's daily operations.

2. Core Business Groups (Business Groups) Map and Panoramic Deconstruction

To help beginners clarify the vast functional system of Odoo 20, the system divides dozens of applications into four core business groups: the Financial Management group, the Sales and Customer-Facing Operations group, the Supply Chain and Manufacturing group, and the Human Resources and Service Operations group.

                    ┌─────────────────────────────────────────┐
                    │      Odoo 20 Single Database & Unified Platform     │
                    └────────────────────┬────────────────────┘
                                         │
        ┌───────────────────┬────────────┴───────┬───────────────────┐
        ▼                   ▼                    ▼                   ▼
 ┌──────────────┐    ┌──────────────┐     ┌──────────────┐    ┌──────────────┐
 │ Financial Mgmt Group │    │ Sales Frontend Group │     │ Supply Chain & Mfg Group │    │ HR Services Group │
 │ Accounting   │    │ CRM / Sales  │     │ Inventory    │    │ Employees    │
 │ Invoicing    │    │ POS / Rental │     │ Manufacturing│    │ Payroll      │
 │ Expenses/ESG │    │ Phone (VoIP) │     │ Purchase/PLM │    │ Project/Time │
 └──────────────┘    └──────────────┘     └──────────────┘    └──────────────┘

2.1 Financial Management Group (Finance Group)

The financial management group serves as the digital control center for enterprise operations, where Odoo 20 has achieved a high degree of automation and compliance breakthroughs within this group.

In terms of financial automation, Odoo 20 ushers in two disruptive architectural innovations:

1. Peppol e-invoicing OCR-free technology: Peppol e-invoicing technology transmits standardized structured XML data (such as UBL/CII formats), which enables the system to achieve 100% automatic classification and precise posting, completely eliminating the errors and omissions and manual secondary verification costs associated with traditional scanned documents that rely on OCR recognition.
2. Embedded PISP (Payment Initiation Service) mechanism: The system has integrated a native PISP interface, allowing corporate finance staff to directly complete single or batch online banking signed payments within the Odoo interface. This design completely eliminates the cumbersome traditional process of exporting CPA 005 or SEPA payment batch files (Payment Batch Files) and then manually uploading them to online banking.

In addition, the system has restructured the asset depreciation model. The original asset model has been replaced by **depreciation models (Depreciation Models)**, supporting the overlay of multiple depreciation schedules on a single asset (for example, accommodating both tax Gap and IFRS standards). In the balance sheet, an auditable CTA (Cumulative Translation Adjustment) account has been added, which can automatically apportion multi-currency exchange rate differences.

2.2 Sales and Customer Front-Office Group (Sales & Front-Office Group)

The Sales and Customer Front Office group covers the entire business chain from marketing lead acquisition to final deal completion. In Odoo 20, the data flow steps in this chain are as follows:

1. Lead Capture and Assignment (CRM): The system automatically generates leads through website forms, integration with the Dun & Bradstreet database, or mobile business card scanning, and automatically distributes them to salespeople according to "round-robin assignment rules."
2. Built-in Phone Communication (Phone/VoIP): Sales representatives make calls directly within the system via a VoIP softphone. The system uses Call Flow Designer to handle call flows and automatically logs call records and voice transcription text in the Chatter feed.
3. Smart Quotation Generation (Sales): Salespeople quickly create quotations. Odoo 20 supports multi-level descriptions and section management, allowing salespeople to edit profit margins (Margin) in real time directly in order lines, and the system will automatically recalculate the final selling price based on cost.
4. Order Confirmation and Downstream Automatic Conversion: After the quotation is confirmed, the system automatically triggers downstream processes according to the configuration—if it is a product sale, an inventory shipment order is automatically generated; if it is a service order, a project and tasks are automatically created.

2.3 Supply Chain & Manufacturing Group

The Supply Chain and Manufacturing group covers procurement, inventory, manufacturing, PLM (Product Lifecycle), quality control, maintenance, and shop floor management. The three core links form a tightly integrated automated interconnection in Odoo 20:

• Procurement Stage (Purchase)
  • Demand-driven intelligent replenishment: The system introduces intelligent replenishment rules (Demand-based reordering rules) based on historical demand, target coverage days, and supplier lead time recommendations, and can dynamically calculate safe/danger red-orange warning thresholds according to parameters.
  • Inquiry and Terms Inheritance: Supports section management for procurement agreements and blanket orders, and can automatically populate supplier-specific international trade terms (Incoterms).
• Inventory Stage (Inventory)
  • Full Barcoding and Traceability: Supports barcode scanning to automatically create products (Barcode Lookup), full-path tracking of batch and serial numbers (Traceability Report).
  • Cross-Company Logistics: Supports the use of custom routes to achieve direct replenishment and cross-warehouse shipping between multiple companies, and enables precise cross-company transfer of inventory valuation and costs.
• Manufacturing Phase (Manufacturing)
  • BoM Comparison Tool: Provides a brand-new Bill of Materials (BoM) comparison tool that intuitively presents component differences and cost changes across different versions or products through pivot tables.
  • Priority and Kanban Planning: Manufacturing orders support priority setting via kanban drag-and-drop, and the system automatically recalculates planning time milestones based on priority.
  • Shop Floor Full Barcode Operation: Shop floor workers log in by scanning their personal badges on tablet devices, and by scanning the MO (Manufacturing Order) barcode, they can automatically switch work centers and perform quality checks and output registration.

2.4 Human Resources and Service Operations Group (HR & Operations Group)

The Human Resources and Service Operations Group manages the enterprise's core talent and service delivery processes.

Design Philosophy: The Core Foundation for Enhancing Data Entry Efficiency and Accuracy

Odoo 20's key breakthrough in the Human Resources and Project Operations modules lies in completely eliminating repetitive manual entry. From resume parsing on the recruitment side, to payroll simulation after onboarding, to intelligent timesheet tracking during project execution, all steps are interconnected through underlying components, ensuring data flows accurately and seamlessly among "Employee-Project-Payroll-Billing."

• Salary Simulator: In the Recruitment and Employees modules, HR or candidates can directly configure a benefits package (such as a company car, vacation days, and phone allowance) through the interactive salary simulator, and the system calculates gross and net salary and total company cost in real time.
• Project PDF Auto-Creation (Project): In the Project (Project) module, users only need to upload a PDF file containing project requirements, and the underlying AI can automatically parse the document and break it down into specific project tasks and phases.
• Timesheet Assistant: The Timesheet module integrates ActivityWatch local tracking technology. Privacy-first design ensures that all device activity tracking runs only on employees' local devices and is never uploaded to the cloud; the assistant intelligently analyzes operational activity locally on the device and, after a set threshold is reached, recommends timesheet entries to employees, both eliminating employees' concerns about privacy leakage and preventing the loss of billable service revenue caused by forgetting to log time.

Supporting the efficient interconnection of the above four major business groups is precisely Odoo 20's intelligent core engine, comprehensively rebuilt at the underlying level—the AI agents (Agents) and skills (Skills) mechanism.

3. Understanding the Core Foundation: Odoo 20 AI Agents and the "Skills" Mechanism

3.1 Conceptual Innovation: Architectural Evolution from "Themes" to "Skills"

In Odoo 20, the AI architecture underwent a major conceptual upgrade: the original “Themes” concept was officially renamed to “Skills”.

Traditional ERP system intelligent configuration is like setting fixed gears for a machine (static configuration), which can only work along preset paths; whereas Skills give an AI agent a "manual and toolbox" containing a preset instruction set, context prompts, and system tool calls. It clearly defines the AI agent's behavior patterns, permission boundaries, and output formats in specific business scenarios, enabling it to autonomously decide which tool to invoke (such as an API, a native report generator, or a database query) based on the user's natural language instructions.

Skills The essential difference between the syntax and traditional static configuration lies in:

Traditional static configuration: User inputs fixed parameters ──► Executes hardcoded rules ──► Outputs fixed results
Odoo 20 AI Skills: User's natural language instructions ──► Skills autonomously understand and select tools (calling native APIs/reports) ──► Dynamic reasoning and precise execution

3.2 Operating Mechanisms and Interaction Patterns of AI Agents

Odoo 20's AI agents employ a highly autonomous agentic architecture (Agentic Automation), with its 5 core operational characteristics as follows:

1. Agentic Automation (Agent Self-Update and Scheduled Waking): AI agents can self-update their configurations based on business scenarios. They can not only respond to users' real-time questions, but also be automatically awakened by the system's "automated actions" or "scheduled actions" (for example, automatically triggering financial variance analysis on the monthly closing date). Agents also have a dedicated Avatar that matches their role.
2. Interactive Confirmations and Tool Call Limits (Interactive Confirmations): To prevent agents from exceeding their authority or entering infinite loops, when an AI agent reaches a preset "Tool Call Limit" or attempts to perform sensitive operations such as modifying/deleting database records, the system will pop up an interactive confirmation button, and execution can continue only after the user manually clicks to confirm.
3. Model Context Protocol (MCP - Model Context Protocol): Agents establish secure connections with the underlying database through the MCP standard. The system automatically matches the most suitable underlying large language model (LLM) for the current scenario based on the task type.
4. IAP Credit Mechanism and Multimodal Interaction: AI features are uniformly billed through IAP (In-App Purchase) credits. Interaction methods have been fully upgraded, supporting dictating requests (voice interaction) directly to AI agents, uploading file attachments (such as PDFs and images), and displaying rich interactive clickable cards in conversations.
5. Chat History Retention (30-Day Chat History): All business conversation records with AI agents will be securely retained in the system for 30 days from the time the last message is sent, making it easy for the team to review and audit at any time.

3.3 Case Study: How AI Drives Cross-Module Automation as an Underlying Technology

To demonstrate how AI capabilities permeate the entire Odoo 20 architecture, the following table summarizes the implementation scenarios and outcomes of AI agents across various business domains:

Having mastered the underlying engine of AI agents and skill mechanisms, beginners can then follow specific business scenarios to appreciate the powerful practical strength of Odoo 20's cross-module integration.

4. Beginner's Guide: Application Linkage Paths in Business Scenarios

To help beginners thoroughly clarify the logical connections within Odoo 20's vast functional system, this chapter uses two typical end-to-end business scenarios to demonstrate how data flows seamlessly between different modules.

4.1 End-to-End Process Example 1: Closed Loop for a Service-Oriented Enterprise (from Customer Leads and Phone Communication to Quotation, Project Delivery, and Settlement Invoicing)

This process demonstrates the seamless integration loop between the front-office sales and back-office service operations modules:

[CRM Lead Generation] ──► [Phone/VoIP Call Log] ──► [Sales Smart Quotation]
                                                    │
                                                    ▼
[Invoicing Automatic Invoice] ◄── [Timesheet Time Tracking] ◄── [Project Automatic Task Generation]

1. [Customer Relationship Management (CRM)]: The system obtains a new potential customer lead through a website form or business card scanning, and automatically distributes it to sales personnel through rotation assignment rules.
2. [Phone (Phone/VoIP)]: Salespeople directly use the VoIP softphone within the system to call customers. During the call, the softphone is displayed as a floating window; after the call ends, the voice recording and text transcription are automatically archived in the lead's Chatter.
3. [Sales]: Based on the communication results, sales personnel generate a Sales quotation with one click. Select a product template and adjust quantities by section, edit the target profit margin (Margin) directly in the detail lines, and the system automatically recalculates the sales price and sends an email.
4. [Project Management (Project)]: After the customer signs and confirms the order online, the system automatically triggers the downstream mechanism to create a new delivery project in the Project Management (Project) module and convert the service terms in the quotation into specific subtasks.
5. [Timesheet] and [Invoicing]: When developers execute tasks, they use the Timesheet Assistant to automatically record working hours. After the project is completed, the system extracts the verified timesheet data and automatically generates accurate customer settlement invoices in the Invoicing module.

4.2 End-to-End Process Example 2: Closed Loop for Supply Chain and Manufacturing Enterprises (From Procurement Negotiation and Inventory Replenishment to Production and Automated Financial Reconciliation)

This process demonstrates the automated closed-loop integration between the supply chain, manufacturing, and financial accounting modules:

[Purchase AI Recognition and PO] ──► [Inventory Scan for Inbound] ──► [Manufacturing Workshop Production]
                                                             │
                                                             ▼
[Payments Embedded Payments] ◄── [Accounting E-Invoice Auto-Reconciliation] ◄────┘

1. 【Purchase】: The AI agent in the Purchase module analyzes historical orders, identifies supplier discount potential in the price of a certain raw material, and automatically alerts the purchaser. After the purchaser confirms, the system generates a purchase order (PO) and sends it to the supplier.
2. [Inventory]: The supplier ships the goods to the warehouse. The warehouse manager uses a mobile device to open the Barcode app, scans the QR code on the packaging box, and completes goods receipt and automatic inventory entry into the system in one go.
3. [Manufacturing (Manufacturing)]: After raw materials are received into inventory, a manufacturing order (MO) in the Manufacturing (Manufacturing) module is automatically triggered. Shop floor workers open the Shop Floor (Shop Floor) interface, scan their personal work badge to log in, execute production tasks step by step, record actual material consumption, and complete quality control inspection.
4. [Accounting (Accounting)]: Electronic invoices (E-invoice) sent by suppliers through the Peppol network directly enter the Accounting (Accounting) system. Based on structured XML data, the system automatically performs three-way matching between invoices, purchase orders (PO), and inventory goods receipts, without relying on OCR recognition, achieving 100% automatic posting.
5. 【Online Payment (Payments)】: Finance personnel select invoices pending payment in the accounting dashboard, click “Pay Now”, and through the built-in PISP (Payment Initiation Service) interface directly connect to corporate online banking to complete single or batch transfers; the system automatically completes bank account reconciliation and settlement.