A single version detail can change how you prepare: Odoo functional certification tests how the system behaves, not just whether you understand ERP terminology. That distinction matters for Odoo 20 functional certification changes, especially if the exam updates its questions, workflows, application coverage, or configuration expectations.
The safest approach is to combine official exam information with hands-on practice in an Odoo 20 environment. Review the current certification scope, rebuild essential workflows from a clean database, test US-specific accounting and operational settings, and document the differences between earlier Odoo versions and Odoo 20. Do not rely on memorized answers from an older exam version. Functional certification preparation should prove that you can select, configure, explain, and troubleshoot the right Odoo behavior for a business requirement.
What Could Change in Odoo 20 Functional Certification?
Odoo 20 functional certification changes are most likely to affect the version-specific knowledge behind common business workflows. That includes new features, renamed settings, revised menus, updated permissions, changed defaults, modified reports, and differences in how modules work together.
The exact exam changes should come from Odoo’s current certification portal and candidate guidance. Treat older study material as a reference, not as the definitive source. A practice question that was accurate for an earlier release can become misleading if Odoo changes a workflow or moves a configuration option.
A functional certification exam typically rewards practical system understanding across areas such as:
Core application concepts and module relationships
Sales, purchasing, inventory, accounting, and CRM workflows
Configuration settings and business rules
User roles, access rights, and record visibility
Automated actions, scheduled activities, and notifications
Reporting, dashboards, and data analysis
Localization requirements and company-specific settings
Common implementation decisions and workflow troubleshooting
The important preparation question is not only, “What changed in Odoo 20?” It is also, “Which business decisions now produce a different result in Odoo 20?”
For example, a change in the location of a setting is inconvenient, but a change in stock reservation behavior, invoicing logic, tax configuration, or approval flow affects how you answer scenario-based questions. That is where version-specific preparation creates the most value.
Which Odoo 20 Changes Should You Study First?
Start with changes that alter a business outcome. A new icon or menu location deserves attention, but it should not receive the same study time as a change that affects whether an order can be confirmed, a receipt can be validated, or an invoice can be posted.
| Study area | What to compare in Odoo 20 | Why it matters for certification |
|---|---|---|
| Sales and invoicing | Quotation flow, order confirmation, invoicing policies, payment terms | Questions may test which setting produces a particular billing result |
| Inventory | Routes, operations, replenishment, reservations, lots, and serial numbers | Small configuration differences can change warehouse behavior |
| Purchasing | Requests for quotation, purchase orders, vendor bills, and approvals | The exam may distinguish between procurement steps and accounting steps |
| Accounting | Journals, taxes, fiscal positions, payment registration, and reconciliation | Functional users must connect operational transactions to accounting results |
| Access control | User types, access rights, record rules, and multi-company visibility | A workflow may appear broken when the real issue is permissions |
| Studio and customization | Fields, views, automated actions, approval rules, and reporting changes | Candidates need to know when configuration is enough and when development is required |
| Localization | US accounting requirements, tax settings, currencies, and address or document formats | Regional settings affect implementation decisions and transaction results |
| Reporting | Filters, groupings, saved views, spreadsheets, and dashboards | Certification questions may test how users retrieve and interpret information |
For US candidates, study the US localization alongside the general accounting workflow. Review tax configuration, fiscal positions, payment terms, journals, and the relationship between sales documents and accounting entries. Candidates outside the United States should apply the same method to their own localization, including country-specific tax and invoicing rules where those are relevant.
Versich’s Odoo Consulting Services include functional consulting, configuration planning, reporting requirements, user permissions, and business process analysis. Those are the same areas that help an organization distinguish a genuine version change from a navigation difference.
How Should You Build an Odoo 20 Certification Study Environment?
A clean, controlled database is more useful than reading dozens of disconnected notes. Build a study environment that lets you repeat a workflow, change one setting, and observe the result.
Use a separate database for experimentation rather than a live production environment. Start with the applications most likely to appear in functional scenarios, then add related settings only when a workflow requires them. Keep the database simple enough that you understand why each result occurred.
A practical environment should include:
A company and user structure that reflects basic operational roles
Products with different product types, units of measure, and routes
Customers and vendors with relevant payment and tax settings
At least one warehouse with locations and an operational flow
Accounting journals, taxes, fiscal positions, and payment terms
Sample sales, purchasing, inventory, and invoicing transactions
A small set of access restrictions for testing user visibility
Do not turn every setting on at once. That makes it difficult to identify the cause of a result. Instead, create a baseline workflow, record the result, then change one configuration item and repeat the process.
For example, create a product, sell it, deliver it, and invoice it using the default configuration. Then change the invoicing policy and repeat the transaction. Compare the point at which the invoice becomes available, the values shown on the documents, and the accounting impact. This method develops functional reasoning rather than simple menu recognition.
The same approach works for purchasing and inventory. Test what happens when a product uses a different route, when stock is unavailable, when a receipt is partially completed, or when a vendor bill does not match the purchase order. These are practical conditions that expose whether you understand the process.
Which Odoo Workflows Deserve the Most Practice?
The highest-value workflows are those that cross application boundaries. Odoo does not treat sales, inventory, purchasing, and accounting as isolated subjects. A change in one document can affect several downstream records.
Sales to cash
Practice the complete sequence from quotation to sales order, delivery, invoice, payment, and reconciliation. Pay attention to:
The difference between ordered quantity and delivered quantity
Invoicing policy settings
Taxes and fiscal positions
Payment terms and due dates
Delivery status and invoice status
Credit notes and refunds
The accounting effect of posted transactions
The key certification skill is explaining why Odoo presents a particular next action. If an invoice is unavailable, identify whether the cause is the invoicing policy, delivery status, permissions, or configuration.
Purchase to pay
Build a purchase flow from request for quotation through purchase order, receipt, vendor bill, payment, and reconciliation. Practice partial receipts and bills that do not match the original order.
Three-way matching is an important concept to understand even when a specific database does not use every available control. The functional question is whether the purchase order, receipt, and vendor bill agree, and what the business should do when they do not.
Inventory operations
Inventory questions require more than knowing where products are stored. Practice warehouses, locations, routes, replenishment rules, operation types, transfers, backorders, lots, and serial numbers.
A useful exercise is to create a product with tracked inventory, receive multiple quantities, deliver only part of the available stock, and inspect the resulting transfer records. Then repeat the process with a backorder. This reveals the difference between a planned quantity, a processed quantity, and a remaining operation.
Accounting and localization
Accounting preparation should connect configuration to transaction results. Study journals, taxes, fiscal positions, accounts, payment registration, reconciliation, and reporting.
US users should inspect how customer and vendor transactions use tax settings, payment terms, and fiscal positions. Also review multi-company behavior if it is relevant to the exam scope. A user who understands the accounting logic behind a transaction is better prepared than someone who only remembers the location of a button.
CRM and activities
CRM preparation should cover leads, opportunities, stages, activities, scheduled actions, quotations, and pipeline reporting. Practice assigning activities, changing opportunity stages, creating quotations from opportunities, and filtering pipeline data.
The information gain here is the connection between a business activity and the next operational action. Functional users need to know whether a requirement belongs in a pipeline stage, an activity type, an automated action, or a separate application workflow.
How Do You Compare Odoo 19 and Odoo 20 for Certification?
Compare versions by business behavior, not by trying to memorize every visual difference. A version comparison document should show what a user does, what the system does in response, and what changed in Odoo 20.
| Comparison method | Example question | Evidence to record |
|---|---|---|
| Menu and navigation | Where is the configuration now? | Application, menu path, and user role |
| Workflow behavior | When does the next document become available? | Trigger, status, and resulting document |
| Field behavior | Is the field required, optional, computed, or hidden? | Field label, dependency, and effect |
| Security behavior | Which users can view or edit the record? | User type, access rights, and record rule |
| Reporting behavior | Which filters and groupings are available? | Report, filter, grouping, and saved view |
| Localization behavior | Which tax or accounting setting controls the result? | Company, fiscal position, tax, and journal |
| Automation behavior | What creates the notification or scheduled activity? | Trigger, condition, and action |
This comparison is especially important if your work experience comes from Odoo 17, Odoo 18, or Odoo 19. Familiarity with an earlier release gives you a foundation, but it can also create false confidence. You might select an answer because it was correct before, even though Odoo 20 uses a different setting or sequence.
Create a “changed, unchanged, verify” register. Put a workflow in the first column, then record whether the Odoo 20 behavior is confirmed, still consistent with the earlier version, or not yet verified. The third category is valuable because it prevents assumptions from becoming study notes.
What Role Do Configuration, Odoo Studio, and Custom Modules Play?
Certification preparation should include the boundary between standard configuration, Odoo Studio, and custom development. These approaches are related, but they are not interchangeable.
Configuration is appropriate when Odoo already supports the requirement through settings, permissions, workflow choices, templates, routes, or supported controls. Odoo Studio is useful for certain fields, views, reports, automated actions, and approval adjustments. Custom modules are appropriate when the requirement changes system behavior beyond supported configuration or Studio capabilities.
Consider a requirement such as, “Managers must approve discounts above a defined threshold.” The functional analysis should identify the approval condition, the affected sales document, the responsible user group, the notification, and the result after approval. Only then should you decide whether an existing approval feature, Studio, or custom development is appropriate.
A second example is a requirement to prevent confirmation when a customer exceeds a credit policy. That could involve accounting data, sales permissions, validation logic, and exception handling. The functional answer is not simply “add a field.” It requires understanding the process and the system behavior that must change.
Versich’s Odoo customization guidance explains the practical distinction between reviewing the existing environment, defining the scope, testing against requirements, and supporting the customized solution after deployment. That distinction is useful for certification scenarios and for real implementation decisions.
How Should You Practice Odoo 20 Security and Access Rights?
Access rights and record rules deserve focused practice because a functional issue is sometimes a security issue rather than a workflow issue. Test the same record with different user roles and companies. Compare what each user can see, create, edit, and delete.
Study these concepts separately:
User access and application permissions
Model-level access rights
Record rules that limit which records a user can access
Multi-company visibility and allowed companies
Field visibility and groups
Approval permissions
Access to accounting records and reports
Create a basic test matrix with rows for users and columns for actions such as viewing a quotation, confirming an order, editing a product, posting an invoice, and reading a report. Record the expected result before testing. This makes it easier to distinguish a permission failure from a missing configuration.
Security also affects customization decisions. A new field, report, automated action, or custom module must respect the existing access model. If the feature exposes financial or employee information to the wrong user group, the customization is functionally incorrect even if the screen works.
How Can You Prepare for Scenario-Based Certification Questions?
Scenario-based questions test judgment. They ask you to connect a business requirement to the right Odoo application, setting, workflow, or control.
Read each scenario for four details:
The business event that starts the process
The record or application that owns the decision
The expected system outcome
The constraint that rules out other options
For example, a requirement might mention that a company invoices customers only after delivery. The important clue is not the word “invoice.” It is the relationship between delivery completion and invoicing policy. Another scenario might describe a purchase receipt that arrives in two shipments. The important clue is the partial receipt and its effect on the remaining operation.
Avoid choosing the most elaborate answer automatically. Odoo implementations generally benefit from using standard functionality before introducing additional customization. A standard configuration that meets the requirement is easier to maintain than an unnecessary custom change.
Keep a decision log during study. For every scenario, write the requirement, the standard feature you selected, the setting that controls it, and the test result. If the requirement cannot be met with standard features, document why. This develops the same reasoning needed to evaluate configuration versus development in a live Odoo environment.
What Should You Do in the Final Week Before the Exam?
The final week should focus on active recall and workflow repetition rather than collecting more reading material. Rebuild key transactions without following a step-by-step guide. Explain each action aloud or in writing, including what the system should do next and why.
Review your changed, unchanged, and verify register. Give extra attention to items that produce a different outcome in Odoo 20, especially accounting, inventory, access rights, reporting, and localization.
A concise final review should cover:
Version-specific menus and terminology
Core cross-application workflows
Configuration dependencies
US localization settings or the localization relevant to your country
User permissions and record rules
Reporting filters and grouping
Studio and customization boundaries
Common transaction exceptions
Official exam instructions and current format
Do not spend the final study session memorizing screenshots. Screens can change with configuration, user permissions, localization, and minor interface updates. Memorize the relationship between the requirement, the setting, and the result.
If your organization is preparing multiple users, compare notes before the exam. Different users may discover that the same workflow behaves differently because they used different permissions, companies, warehouses, or accounting settings. Resolving those differences improves both certification readiness and operational consistency.
How Can Businesses Apply Certification Preparation to Real Odoo Work?
Certification study becomes more valuable when it exposes gaps in the organization’s own processes. If users cannot explain why an order remains unconfirmed, why a report excludes records, or why an invoice is not available, the issue deserves functional analysis before any development begins.
Use the study process to review:
Whether users follow the intended workflow
Whether permissions match job responsibilities
Whether reports answer operational questions
Whether custom modules still fit the current Odoo version
Whether manual workarounds indicate missing configuration
Whether upgrade planning includes data, integrations, and testing
That review should not become a disguised exam exercise. The goal is to identify where the current Odoo environment needs clarification, cleanup, training, or technical work.
If you are preparing a broader upgrade or functional assessment, contact our Odoo team with your current version, applications, customizations, and certification-related concerns. A focused review can separate version knowledge gaps from actual system design problems.
What to Watch as Odoo 20 Certification Develops
Odoo 20 functional certification preparation should remain active until your exam date. Watch the official certification guidance for changes to the exam scope, application coverage, delivery method, scoring information, and candidate requirements. Then compare those instructions with your own tested workflows.
The most useful preparation is not a larger collection of notes. It is a current, repeatable understanding of how Odoo 20 turns a business requirement into a configured process, a transaction, a permission decision, or a report. Build that understanding across sales, inventory, purchasing, accounting, CRM, security, and localization, and you will be ready for both certification changes and the practical work that follows.
