Odoo certification, portfolio and first job

Nine stations built a capability. This one makes it provable to somebody who does not know you and will give you no more than half an hour.

Two separate questions get merged here: do you take the certification, and how do you prove your capability? The second matters more, but we start with the first because it costs money.

The certification, by its published figures

These are published on Odoo’s learning platform, read on 6 September 2026, on a page stating it was last updated 15 November 2025.

Item	Value
Name	Odoo 19 Functional Certification
Fee	$250
Questions	120
Duration	An hour and a half
Pass mark	70%
A wrong answer	Costs half a mark
A skipped question	Costs zero
Type	Nominative — not transferable to another account

Two rows deserve a pause.

The time. 120 questions in 90 minutes is 45 seconds per question. This is not a reasoning exam; it is a recall exam. Anyone who has to derive the answer fails on the clock rather than on knowledge, and anyone who has run the cycles twenty times answers without thinking.

The negative marking. A wrong answer costs half a mark and a skip costs nothing. Which produces an explicit strategy: do not guess blind. If you have eliminated two of four options, guessing is worth it. If you do not know the subject at all, skipping is mathematically better than throwing.

Read those two paragraphs again before the exam. Most people who fail an exam with negative marking fail because they answered everything.

The exam’s scope against this path’s scope

The published scope is eighteen subjects: website, e-commerce, surveys, marketing, artificial intelligence, CRM, sales, purchasing, projects, timesheets, accounting, inventory, manufacturing, human resources, spreadsheets, knowledge, point of sale, and Studio.

The exam is deliberately broader than this path, as the path page said from the outset. The path builds the backbone people are hired on — the cycles, accounting, inventory and localisation — while the exam sweeps the whole product, including applications an ERP consultant never touches in daily work.

So the sensible preparation plan is: two weeks before the date, given over to the applications the path did not cover, at an acquaintance level rather than mastery — what the application is for, where its main configuration lives, and what it connects to. Do not try to master eighteen applications; nobody does.

Is the certification worth its fee?

The honest answer: it depends on who reads your CV, not on its knowledge value.

Your situation	The decision
Applying to a certified Odoo partner	Yes — many treat it as a first screen
Going freelance	Late — delivered work outranks it in this market
Running your own company on Odoo	No — you are not selling yourself to anyone
Two years of experience documented by projects	Optional — it adds little
No experience and no projects	Yes — it is the cheapest credible signal you have

And the judgement that holds in every case: the certificate opens the door; the portfolio passes the interview. Having both is preferred. Forced to choose, the portfolio weighs more with anyone who knows the market.

The portfolio — and this is the more important half

You already have something to show and do not realise it. The nine stations produced real material: a working environment, a complete company with master data, purchase and sales cycles executed with their entries, a measured comparison of costing methods, a month closed against a checklist, a sourced localisation answer, and a written customisation boundary.

Turn it into five presentable pieces.

1. A company configuration document. The company you built at station three: the localisation package chosen, the chart of accounts, the items and their types, and the costing method with the reason it was chosen. That reason sentence is what separates you from everyone who “trained on Odoo”.

2. The two-cycle sheet with its entries. Steps against generated entries, from station four and station five. Nothing proves comprehension faster, because it shows you read what the system produces rather than what you press into it.

3. The costing comparison, with numbers. The table from station six, run on your own data. One executed number is worth ten theoretical sentences.

4. The close checklist. From station seven, including the suspense accounts and what a balance on each means. This is the piece a finance director reads and concludes that you have actually worked.

5. A written customisation decision. A real request you refused or downgraded, with its reasoning, from station nine. This is the piece that most distinguishes you, because almost every applicant presents what they built and nobody presents what they declined to build.

One page per piece, with screenshots from your own database. A portfolio read in ten minutes beats a forty-page document nobody opens.

What interviews actually ask

The questions that sort candidates in this field are not about menu names. They are about mechanisms, and you have met all of them:

• “What does confirming a sales order do to stock?” — separates those who know available from reserved.
• “What is the entry when goods arrive before the invoice?” — separates those who read entries from those who memorised steps.
• “When is revenue recognised?” — separates those who understand accounting from those who operate a screen.
• “The client wants a change that does not exist — what do you do?” — separates the consultant from the implementer. A good answer opens with a question about the reason, not a promise to build.
• “Why did the margin drop after the close?” — separates those who know the cause lies in cost or timing rather than price.

Those five are the five middle stations restated as questions. If you can answer them with an example from your own database, you are ready — certificate or no certificate.

The final acceptance test

1. Write the five pieces, one page each.
2. Answer the five questions above out loud, two minutes each, with an example from your own work.
3. Make the certification decision in writing, using the table above rather than an impression.
4. Run a full purchase and sales cycle in under twenty minutes with no reference material. That is the pace of a practical interview.
5. Rebuild your database from nothing in under an hour, from creation to the first posted invoice. If you can, you did not memorise the path; you understood it.

Where the path leads

You have reached the end of the ten stations, and three directions are open, chosen according to what you started for at station one.

Functional depth — manufacturing, point of sale, and projects, the applications that open entire sectors.

The development track — module architecture, the ORM, and QWeb. You now enter it through the right door: a developer who understands the cycle before writing code for it, rather than the reverse.

Evaluation and selection — becoming the person who decides which system gets bought rather than the person who implements it. That road runs through the systems comparison and the Odoo guide, which says where the product breaks — the thing training on it alone never teaches.