Station 1 of 10
Where to start with Odoo and why
What you leave this station with
A 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.
Odoo is not complicated. The order in which most people meet it is wrong.
The usual sequence: open a trial account, switch on twelve applications in the first session, get lost somewhere between inventory, manufacturing and HR, and conclude a fortnight later that the product is too complex. Nothing in that account was complex. Nothing in it was sequenced either.
This station opens no screen at all. It settles three decisions that make the next twenty hours produce something.
Decision one: what exactly are you for
The answer changes the entire path, and most people never write it down — so they walk a route that does not arrive where they wanted.
| Your goal | What you actually need | What you can ignore for now |
|---|---|---|
| A functional consultant job at an Odoo partner | The four cycles, localisation, Studio, the certification | Python, module architecture |
| Running your own company on Odoo | The four cycles, accounting, localisation | The certification, deep customisation |
| An Odoo developer track | All of the above, then module architecture, the ORM and QWeb | Nothing — a developer who does not understand the cycle writes code that breaks the ledger |
| Evaluating the system before buying it | Stations 2, 3 and 8, then the product guide | The rest of the path |
Look at the third row. A developer who started from the code and never walked the cycles is the most dangerous person on the project, because the modification they write runs, looks right, and corrupts stock balances silently. That is why customisation is station nine here and not station two, and why the ordering binds even on a purely technical route.
Decision two: Community or Enterprise to train on
This is where the most expensive confusion in learning Odoo sits. Two months are spent on the free edition, and then the interview asks about half a product that was never installed.
The dividing line is not free against paid. It is that the Community edition gives you invoicing, not accounting. It issues invoices and records payments, but bank reconciliation, asset management and the full accounting engine sit behind the licence. Outside the free edition with them: Studio, e-signature, quality, maintenance, requirements planning, and the mobile app.
What to do about it, in practice:
- Train on Enterprise, through the free trial covered in the next station, if your goal is a job or a purchase evaluation. What the interview asks about — and what you will meet in any company that paid — is Enterprise.
- Install Community on your own machine in parallel, because it does not expire after a fortnight. It is the environment you can wreck daily and rebuild. It is also the only way to read the source, and reading the source is the fastest route to understanding what a button does when nobody will explain it.
Running both is not indulgence. An environment that expires makes you cautious about experimenting; a permanent one without full accounting teaches you half the picture. Together they solve both problems, and together they cost nothing.
The licence figures themselves — what a company actually pays once training is over — are set out in the Odoo guide at the price published on Odoo’s site, with the date it was read.
Decision three: which release
Odoo ships a major release roughly every year, and the current one as this station is written is Odoo 19. The rule is simple and widely broken: train on the newest release, not on whichever one you found a tutorial for.
The difference between two distant releases is not cosmetic. Menus are renamed, settings migrate between screens, whole pages get rebuilt. Anyone who learned on a release four years old spends weeks later relearning what they believed they knew — and discovers it in the interview rather than before it.
Which produces the third rule governing this entire path: what is written here is concepts and their logical homes, never click paths. The practical difference: knowing that tax configuration lives in accounting settings rather than on the item card serves you in every release. Memorising that a button sits in the top-left corner lies to you in twelve months.
The weekly plan
This is an executable plan, not a suggestion. It assumes one hour a day.
| Week | Stations | What exists by the end of it |
|---|---|---|
| One | 1 and 2 | Odoo running in two editions, and an empty database you own |
| Two | 3 | A complete company: accounts, items, partners, taxes |
| Three | 4 and 5 | A purchase cycle and a sales cycle, executed end to end by you |
| Four | 6 | A working grasp of how costing method moves margin — measured, not read |
| Five | 7 | A bank reconciliation, a closed month, statements you read with confidence |
| Six | 8 | A settled answer on tax and e-invoicing in your own country |
| Seven | 9 | A written line between what configuration solves and what earns code |
| Eight | 10 | A portfolio, and a considered decision about the certification |
Eight weeks reaches a real operating standard. Reaching certification standard takes roughly twice that, and the estimate is honest rather than encouraging.
The one thing to know before line one
A single non-negotiable prerequisite: double-entry basics. You do not need to be an accountant. You do need to know what debit and credit mean, why every movement has two sides, and the difference between a balance-sheet account and a profit-and-loss account.
Without it, you learn to press buttons in a memorised order — and when a balance comes out wrong you have no way of finding out why. With it, you read every Odoo screen as a face over an entry you already understand. That is the whole difference.
If the foundation is not there, read the ledger and the close before the next station. Two hours there saves twenty here.
What comes next
The next station is entirely hands-on: Odoo running in front of you by three different routes, what separates them, when each is the right choice — and why the one that looks hardest teaches you the most.