Learn Odoo from scratch — a ten-station path in order
Before you start
- Honest time for the whole path
- 80 to 120 hours actually on the screen — three months at an hour a day
- Assumed knowledge
- Double-entry basics · Comfortable using a computer
- The buying question, not the learning one
- Odoo: the real cost and where it breaks
Three things about Odoo are public, free, and reachable without speaking to a salesperson: the complete product source, official documentation rebuilt with every release, and live environments you can open in the next five minutes.
That combination is rare. It is what makes teaching yourself Odoo to an employable standard genuinely possible, and it is not true of most systems in this market. The people who never get there are almost never the ones who lacked access. They are the ones who watched instead of ran.
What this path is, and what it deliberately is not
This is not a walkthrough of Odoo’s screens one by one. That material is already free on Odoo’s own channel, needs no second version, and expires with every annual release.
This builds a different person: someone who can run a company on Odoo. Who knows why a particular journal entry appeared, where tax is configured, why the gross margin moved after the month closed, and when the correct answer is to write no code at all.
If your question is instead “should my company buy Odoo?”, that is a different question with a different page. It is answered in the Odoo guide: real cost and where it breaks, which covers the free-edition trap and the annual upgrade bill that no demonstration mentions.
The ten stations
| # | Station | What you walk away holding |
|---|---|---|
| 1 | Where to start | A written weekly plan, and a decision: Community or Enterprise to train on |
| 2 | A real training environment | Odoo running in front of you, on a database you are free to destroy |
| 3 | Company and master data | A complete company: accounts, items, partners, units, taxes |
| 4 | The purchase cycle | A purchase executed from requisition to supplier payment, entries read |
| 5 | The sales cycle | A full sale, and the knowledge of when stock is reserved and revenue recognised |
| 6 | Inventory and costing | A measured difference between average and FIFO, and its effect on margin |
| 7 | Accounting and the close | A bank reconciliation, a closed month, and statements you read with confidence |
| 8 | Localisation and e-invoicing | Which module serves Saudi Arabia and Egypt, and where the product does not reach |
| 9 | Customisation | A written line between what configuration solves and what deserves code |
| 10 | Certification and first job | The exam with its published numbers, and a portfolio that survives an interview |
The honest number of hours
The figure usually published — “learn Odoo in a week” — measures watching time, not operating time. From actual training work, three checkpoints:
- 20 hours before you can execute a full purchase and a full sale without hesitating.
- 50 hours before you understand the accounting entries behind each movement rather than memorising them.
- 80 to 120 hours to reach the standard the functional certification tests.
How those hours are distributed matters more than their number. An hour a day, every day, beats seven hours in one sitting, because half of what happens here is forgetting and then retrieving.
Three rules that govern this path
Do not watch. Execute. Every station ends with something you build inside your own database. Reading the purchase station without creating a purchase order means the station is not finished.
Read the journal entry after every movement. This is the whole difference between someone who “knows Odoo” and someone who understands it. After each receipt, each invoice, each payment, open the entry that was generated and read both sides of it. Do that twenty times and you can diagnose a fault in any system, not only this one.
Assume the version has moved. Odoo ships a major release roughly annually and menu names travel with it. So what is written here is the concept and its logical home — tax configuration lives in accounting settings, not on the item card — never a click path that reads true today and lies in a year. The deciding reference is always Odoo’s official documentation for release 19, which is free in full and moves with the product.
What sits at the end of the path
The official exam is the Odoo 19 Functional Certification, published on Odoo’s learning platform with every number stated. Read on 6 September 2026: 120 questions in an hour and a half, pass mark 70%, and a wrong answer costs half a mark while a skipped one costs nothing. That last rule alone should change how you sit the exam. The published fee is $250, and the certificate is nominative — it does not transfer to another account.
Its declared scope runs to eighteen subjects: website, e-commerce, surveys, marketing, AI, CRM, sales, purchase, project, timesheets, accounting, inventory, manufacturing, HR, spreadsheets, knowledge, point of sale and Studio. Read that list again, because it matters: the exam is wider than this path on purpose. The path gives you the spine the market hires on; the fortnight before the exam is when you sweep the applications it did not cover.
Whether the fee is worth paying at all, and what an interview actually asks for instead, is settled at station ten.
Start here
Station one opens no screen. It settles one decision before you type a line — which edition you train on — and why the answer differs depending on whether you want a job at a partner, to run your own company, or to become a developer.
The path, in order
Each station assumes the one before it. Jump to the seventh before the third and you are reading about journal entries posted to accounts you have not created yet.
- 1Where to start and whyA written decision on which edition you train on and why, a weekly plan that tells you what to do each day, and an honest estimate of the time before you spend it.
- 2A real training environmentAn Odoo instance running in front of you that you can destroy and rebuild in minutes, and a clear grasp of hosted versus local before you build eight weeks on top of it.
- 3Company and master dataA complete company inside your database: a configured chart of accounts, items with the right types, partners, units of measure and taxes that apply themselves — and an understanding of which field decides what, before the first document exists.
- 4The purchase cycleA full purchase cycle executed inside your database, and the ability to state before each step which entry will be generated and what both sides of it are — then open it and check.
- 5The sales cycleA full sales cycle executed, a settled understanding of on hand versus reserved versus forecast, and of the moment revenue is recognised alongside the cost-of-goods-sold entry.
- 6Inventory and costingA numeric difference between the three costing methods on identical data, and the ability to trace any margin movement back to either the costing method or a stock adjustment.
- 7Accounting and the closeA month closed by your own hand against a written checklist, a complete bank reconciliation, and the ability to read the three statements and trace any figure back to the movement that produced it.
- 8Localisation and e-invoicingA settled, sourced answer on Odoo's e-invoicing coverage in your country, and the ability to separate what the product ships from what needs a third party — the single most frequently asked question in interviews.
- 9CustomisationA written decision rule you apply to every customisation request, an understanding of what each level costs at upgrade, and the ability to say no on technical grounds rather than build what will be regretted.
- 10Certification and a first jobA considered decision on the certification based on its published figures rather than an impression, and a presentable portfolio built out of what you executed across the previous nine stations.