Phase 1 · Module M1

Odoo Foundations & Navigation

Odoo 20.0 Training Program · Sage Business Vision migration

90 minutes All roles Prerequisites: M0

From clicking around to reading the screen

Module 0 taught you where things are. This module teaches you how Odoo is put together. Once you can read a view, a status bar, and a chatter, you can open almost any app and understand what you are looking at.

Odoo uses the same patterns across Sales, Purchase, Inventory, and Accounting. A list view in Sales behaves like a list view in Purchase. A form view in Inventory behaves like a form view in Accounting. Learn the pattern once and you will recognize it everywhere.

One pattern, many apps: the app changes, but the view types, the search bar, the status bar, and the chatter do not. That consistency is the reason this module is worth the full 90 minutes.

Learning objectives

By the end of this module, you should be able to:

  • Explain how apps, menus, views, and actions relate to each other.
  • Read and use list, form, kanban, and pivot views.
  • Search across records and apply advanced filters and groupings.
  • Explain the difference between edit, save, and discard.
  • Read a record's status bar and chatter to understand where it is in its lifecycle.
  • Locate a sales order, a purchase order, and a product and explain the status of each.
Audience: all roles Format: demo + hands-on Sandbox: required

Core concepts

Apps, menus, views, and actions

An app is a collection of related features, such as Sales or Inventory. Inside an app, the menu groups records and operations. A view is how records are displayed: a list, a kanban board, a form, or a pivot table. An action is what happens when you click a button, such as confirming an order or validating a receipt.

Element What it does Example
App Groups related business features. Sales, Purchase, Inventory, Accounting.
Menu Navigates to records or operations inside an app. Sales > Orders > Quotations.
View Displays records in a particular layout. List view, kanban view, form view, pivot view.
Action Changes the state of a record or opens another view. Confirm, Validate, Register Payment, Send by Email.
Chatter Shows messages, activities, and history for a record. Notes, scheduled activities, status changes.

The four views you will use most

  • List view: rows and columns. Best for scanning many records and comparing values.
  • Kanban view: cards in columns. Best for seeing work by stage, such as quotations by status.
  • Form view: one record at a time. Best for editing details and running actions.
  • Pivot view: totals and cross-tabs. Best for analysis and reporting.

Edit, save, and discard

Odoo form views have two modes. In read mode, you can view the record but not change it. Click Edit to enter edit mode. In edit mode, changes are held in the form until you click Save. If you click Discard, the changes are thrown away. If you navigate away without saving, Odoo may warn you that changes will be lost. This is different from a spreadsheet that saves automatically. Treat Save as a deliberate step.

Watch the status bar. The status bar at the top right of a form shows the record's current state and the buttons that move it forward. A quotation is not a sales order until it is confirmed. A receipt is not done until it is validated. Read the status before you click an action.

Walkthrough

Follow along in the sandbox. Keep the training index open in another tab for reference.

  1. Open an app and read its menu

    Open the Sales app. Look at the top menu. It groups operations such as Orders, Products, Reporting, and Configuration. Open each menu without clicking a record. The goal is to see how the app is organized, not to change anything.

  2. Switch between views

    Go to Sales > Orders > Quotations. Use the view switcher in the top right to move between list, kanban, and pivot views. Notice that the same records appear in different layouts. Switch back to the list view and open one quotation in form view.

  3. Read the form view

    In the quotation form, identify the customer, the order lines, the totals, the status bar, and the chatter. Do not edit anything yet. Read the status. Is it a quotation, a sales order, or a cancelled document? The status bar tells you.

  4. Search and filter

    Return to the list view. Use the search bar to find a specific quotation by customer name. Then open the filters menu and apply a status filter. Add a group-by, for example by salesperson or by status. Remove the group-by and clear the filter when you are done.

  5. Practice edit, save, and discard

    Open a demo quotation. Click Edit. Change a non-critical field, such as the customer reference or an internal note. Click Discard and confirm that the change is gone. Then edit the same field again, click Save, and confirm that the change persists. This is the habit you want to build.

  6. Locate a purchase order

    Open the Purchase app and go to Orders > Purchase Orders. Find a demo purchase order. Open it and read the status bar. Is it an RFQ, a confirmed purchase order, or a locked order? Note the vendor and the receipt status.

  7. Locate a product

    Open the Inventory app and go to Products > Products. Find a demo storable product. Open the product form and read the product type, the unit of measure, and the on-hand quantity. Note whether the product is tracked by lot or serial number.

  8. Explain the status of each record

    Return to the sales order, the purchase order, and the product. For each one, say out loud what the status means and what the next action would be. This is the core skill of the module: read the screen, then decide the next step.

Exercise

Locate and explain

Complete these steps on your own. Use the sandbox and the demo data.

  • Find one sales order using search and filters. Note its status and the next action the status bar offers.
  • Find one purchase order. Note whether it is an RFQ or a confirmed order, and whether a receipt is expected.
  • Find one storable product. Note its unit of measure and on-hand quantity.
  • Switch each record between list view and form view at least once.
  • Open the chatter on one record and note one message or activity.

Expected result: you can explain the status of each record without guessing. You can describe what the next action would be and why. You can move between list and form views without losing your place.

Check your understanding

Answer these questions before moving to the next module. Open each answer to check yourself.

1. What is the difference between an app and a menu?

An app is a collection of related features. A menu is a navigation structure inside an app that leads to records or operations. Sales is an app. Sales > Orders > Quotations is a menu path.

2. When would you use a kanban view instead of a list view?

Use kanban when you want to see work grouped by stage or status, such as quotations by stage. Use list when you want to scan and compare many records in rows and columns.

3. What is the difference between save and discard?

Save writes your changes to the record. Discard throws them away. Odoo does not save automatically while you are in edit mode, so you must choose deliberately.

4. What does the status bar tell you?

The status bar shows the current state of the record and the actions that move it forward. It tells you whether a quotation is still a quotation or already a sales order, and what the next step is.

5. Why does the same customer record appear in Sales and Accounting?

Odoo uses a shared data model. The customer is a partner record, and every app that needs a customer uses the same partner. You do not create a separate customer for each app.

Facilitator notes

Suggested timing: 15 minutes concepts and demo, 35 minutes guided walkthrough, 30 minutes exercise, 10 minutes questions and close. Keep the demo short and let the exercise carry the learning.

  • Before the session, confirm that the sandbox has at least one quotation, one purchase order, and one storable product with stock on hand.
  • Demonstrate the view switcher once, then ask learners to do it. Do not click through every view for them.
  • When a learner cannot find a record, check for an active filter or group-by before anything else.
  • Use the status bar as a repeated teaching point. Ask, "What does the screen say the next step is?" rather than telling them.
  • If the group is advanced, add a short exercise on saving a custom filter or grouping by two fields.

Next steps

You can now read the screen and explain what a record's status means. The next module covers the shared data that every app depends on: partners, products, and taxes.