Becoming an Odoo consultant stages 01
How Odoo covers a whole business
Odoo is not one program but a large set of apps sharing one database. What those apps are, which part of a company each one runs, and how a single order travels through all of them.
After this stage: A clear map of Odoo — what exists, what it is called, and where each app sits in a business.
The most common mistake newcomers make is thinking of Odoo as one program, like an accounting package with extra screens. It is not. Odoo is a large set of applications that all share one database.
That single fact explains almost everything else about the product, and about the job.
One database instead of many systems
In most companies, the sales team has one system, accounting has another, and the warehouse has a third. Data is exported, emailed and re-entered. The numbers disagree, and someone spends every month finding out why.
In Odoo, those are not separate systems. A sale, the delivery of the goods and the customer invoice are one connected chain of records. Nothing is re-typed, and nothing needs to be reconciled between systems, because there is only one.
This is why the job is called functional consulting rather than software installation. Your work is deciding how a company’s real processes should map onto that shared structure.
The app map
Roughly this is what exists. You do not need to learn it all — you need to know what is there, so you never build something Odoo already does.
| Area of the business | What it handles | Main apps |
|---|---|---|
| Selling | Leads, quotations, orders, recurring revenue | CRM, Sales, Subscriptions, Rental |
| Buying | Requests, purchase orders, vendor bills | Purchase |
| Stock | Receiving, storing, moving, delivering goods | Inventory, Barcode |
| Making | Production orders, bills of materials, shop floor | Manufacturing, Quality, Maintenance, PLM |
| Money | Invoices, payments, ledger, reporting | Invoicing, Accounting, Expenses, Spreadsheet |
| Services | Billable work, tickets, on-site jobs, scheduling | Project, Timesheets, Helpdesk, Field Service, Planning, Appointments |
| People | Records, hiring, absence, pay, vehicles | Employees, Recruitment, Time Off, Appraisals, Payroll, Fleet |
| Shops and web | Selling in person and online | Point of Sale, Website, eCommerce |
| Marketing | Reaching and following up customers | Email Marketing, SMS, Marketing Automation, Social, Events, Surveys |
| Working together | Everyday internal tools | Discuss, Documents, Sign, Knowledge, Calendar, Contacts, Approvals |
| Changing Odoo | Adjusting screens and adding logic without code | Studio |
Two things follow from this table, and both matter in your first job.
Nobody knows all of it. Experienced consultants are strong in a few areas and know roughly what the rest do. That is normal, and it is the right target.
Most requirements are already solved. When a client describes a need, the first question is never “how do we build this” but “which app already does this”. Learning the map is what lets you answer.
Following one order through the system
The clearest way to see how the apps connect is to follow a single sale. Each step below happens in a different app, and every one is created from the step before it.
- CRM — a lead comes in and becomes an opportunity with a salesperson and an expected value.
- Sales — the opportunity becomes a quotation. The customer accepts, and it becomes a confirmed sales order.
- Inventory — the confirmed order automatically creates a delivery order. The warehouse picks the goods and validates it. Stock drops, and the value of that stock is recorded.
- Invoicing / Accounting — the order is invoiced. The invoice posts entries to the ledger: revenue, tax, and the amount the customer owes.
- Accounting — the customer pays. The payment is matched against the invoice and the bank statement.
- Reporting — the margin on that order is already visible, because the sale price and the stock cost were both recorded along the way.
Nobody exported a file. Nobody re-typed a line. The salesperson, the storekeeper and the accountant each did their normal work, in their own app, on the same records.
Buying works as a mirror image: a purchase order creates an expected receipt in Inventory, the receipt updates stock and its value, and the vendor bill posts to the ledger.
If you understand these two chains properly, you understand the spine of most implementations.
One customer order, before and after
The same order, in a company of forty people, handled the way most of them work today and then on one system.
Before — on paper 8 steps
- The customer telephones a salesman, who writes the order in a notebook.
- The salesman walks to the warehouse to ask whether the goods are there.
- The storekeeper checks a shelf and a handwritten stock card, and estimates.
- A delivery note is written by hand in three copies. One of them is lost.
- The invoice is typed again into Excel, from the delivery note.
- Accounts type the same invoice a third time into the accounting program.
- The stock card is reduced, sometimes that day, sometimes on Thursday.
- At month end somebody reconciles the notebook, the Excel file and the accounts, and they disagree.
The same order is typed four times, and nobody in the building can say today's stock or this month's margin.
After — in Odoo 5 steps
- The salesman enters the quotation once, seeing real stock as he types it.
- The customer confirms, and the delivery order appears in the warehouse.
- The storekeeper validates it on a screen. Stock and its value drop together.
- The invoice is created from the order, already matching what was delivered.
- The payment is matched against the invoice when the bank statement is imported.
Entered once. Stock, cost, revenue and the ledger all move from the same action.
The two editions
Odoo comes in two editions, and the difference affects every project.
Community is free and open source. You host it yourself. It covers the core: sales, purchasing, stock, manufacturing, invoicing, projects, website and more.
Enterprise is a paid subscription. It includes everything in Community and adds more apps and features — full Accounting, Studio, Documents, Sign, Planning, Field Service, Helpdesk, Marketing Automation, Quality, Payroll and others — plus support and version upgrades.
Which apps sit on which side moves between versions, so check the official comparison instead of relying on memory. What matters for now is that “does Odoo do this” often has the answer “yes, in Enterprise”, and that is a budget conversation, not a technical one.
Where Odoo runs
Three options, and the choice decides what can be built later:
| Option | What it is | Custom code? |
|---|---|---|
| Odoo Online | Odoo hosts it. Simplest and fastest to start. | No — configuration and Studio only |
| Odoo.sh | Odoo’s hosting platform, built for projects with custom modules. | Yes |
| On-premise | Your own server or cloud. Full control, and full responsibility. | Yes |
Beginners regularly design a solution that needs a custom module for a client on Odoo Online, where it cannot be installed. Ask where the system will run early.
Versions
Odoo releases a new major version every year — 17, 18, 19 and so on. Apps move between editions, features are added, and screens change.
Always check which version a tutorial, video or answer refers to before trusting it. “Odoo does not have that” is very often “that version did not have it”.
What to do with this map
Learn the spine first, in this order: sell → buy → stock → invoice → accounts. That chain runs in almost every company, whatever the industry, and it is where most of the work is.
Add the other areas when a real client needs them. That is the order the rest of this path follows.