Odoo Training
Odoo is only adopted when each team can complete its own work without asking for help.
Why It Matters
Each session is hands-on. Everyone is logged in under their own access rights and posts their own documents while we are in the room, so the first time a purchase manager confirms a real order is not the first time they have seen the screen.
The administrator track covers the routine work that otherwise becomes a support ticket every week: users and access rights, record rules, automated actions, QWeb layout tweaks, scheduled actions, backups, and knowing where to look when something fails.
We list who does what in the system and build a track for each role.
A training copy of your database is set up with your data and real logins.
Short hands-on sessions per role, with practice work in between.
Each team runs a full cycle on its own, and we note where people still hesitate.
Guides and recordings are handed over, with a refresher after go-live.
Pipeline stages, quotation templates, price lists, discount approvals and order confirmation.
Receipts, internal transfers, delivery orders, lot and serial tracking and stock counts.
Customer and vendor invoices, payments, bank reconciliation, taxes and the period close.
Bills of material, work orders, work centres, component issue and subcontracting.
Employee records, leave and attendance, timesheets and project stage management.
Users, access rights, record rules, automated actions, backups and first-line diagnosis.
The people teaching your team are the ones who configure Odoo, so the answers are specific.
Sessions run on a copy of your setup, which also exposes configuration gaps early.
Two hours with practice in between beats two days that nobody retains.
A track is finished when the team completes a cycle unaided, not when the slides end.
We aim to make your administrator self-sufficient for routine changes.
Everyone who will enter or approve a transaction, split by role rather than trained as one large group. Sales, inventory and dispatch, purchase, accounting, manufacturing and HR each get their own track, plus a separate deeper track for whoever will administer the database internally.
Yours, on a training copy of your configured database. People learn much faster when the product codes, customers and approval rules on screen are ones they already recognise, and it surfaces configuration gaps while there is still time to fix them.
Most rollouts need 5 to 10 sessions across two to three weeks, each about two to three hours. Short sessions with practice in between work far better than a two-day marathon nobody retains.
Yes. The administrator track covers users and access rights, record rules, automated actions, QWeb layouts, scheduled actions, backups and where to look when something fails. The aim is that routine changes stop needing us at all.
You keep the recorded sessions and the role guides written against your own configuration, which covers most new joiners. We also run refresher and new-hire sessions on request, and they come out of the change hours on our support plans.
Yes. We start by reviewing your database so the training matches how it is actually configured rather than a generic Odoo course. If we find setup problems that would confuse users, we flag them before the sessions begin.
Related
The other services in this section, and related pages from TCB Infotech.
No commitment. A practical look at what your team needs to learn.
