Training on Your Own Database, Not a Demo Company
Odoo is only adopted when each team can complete its own work without asking for help. We train role by role on a copy of your configured database, with your products, customers and approval rules, until every department can run a full cycle unaided.
50+ ERP and software projects. Zero failed projects since 2021.
Systems do not get rejected, they get worked around
When people are unsure how to do something in Odoo, they do it in a spreadsheet instead, and the data quietly stops being reliable.
People remember what they have done, not what they watched
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.
- Everyone on their own login and access rights.
- Real transactions posted during the session.
- Practice work between sessions, reviewed at the next.
Your administrator should not call us to add a user
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.
- Users, groups, access rights and record rules.
- Automated actions and QWeb layout changes.
- Backups, scheduled actions and first-line diagnosis.
Training formats we run
Most rollouts use a mix, depending on how many sites and shifts you need to cover.
From a training plan to teams working unaided
The tracks we run by role
Sales and CRM
Pipeline stages, quotation templates, price lists, discount approvals and order confirmation.
Inventory and dispatch
Receipts, internal transfers, delivery orders, lot and serial tracking and stock counts.
Accounting
Customer and vendor invoices, payments, bank reconciliation, taxes and the period close.
Manufacturing
Bills of material, work orders, work centres, component issue and subcontracting.
HR and Project
Employee records, leave and attendance, timesheets and project stage management.
Administrator
Users, access rights, record rules, automated actions, backups and first-line diagnosis.
What proper training changes
Why teams choose TCB Infotech for Odoo training
Odoo training questions
Who should attend Odoo training?
Do you train on a demo database or ours?
How long does Odoo training take?
Can you train the person who will administer Odoo internally?
What happens when we hire new staff later?
Do you train teams that did not implement with you?
Get Your Team Confident in Odoo
Book a free consultation. Tell us who uses the system and where they get stuck, and we will put together a role-based training plan for your team.
Book a Free Consultation →No commitment. A practical look at what your team needs to learn.
What Is Inside Our Odoo Training
Tracks built per role, run on a copy of your own database, and finished only when the team can complete its work unaided. Here is what each track covers and what you keep afterwards.
Built around what each person actually has to do
Nobody sits through apps they will never open
We start from a list of who does what, then build a separate track per role. An inventory team learns receipts, transfers and counts. Accounting learns invoicing, payments, reconciliation and the close. Each track follows one end-to-end cycle rather than touring the app menu.
- A track per department, not one combined course.
- Built around your real document flow.
- Approval rules and access rights as they will be live.
A track ends when the team can run the cycle alone
Every attendee is logged in under their own access rights and posts their own documents during the session, with practice work in between. At the end each team runs a complete cycle without help while we watch, and we note where people hesitated so those points get a second pass.
- Individual logins with production access rights.
- Practice work reviewed at the following session.
- A final unaided run-through per department.
So routine changes stop needing an outside call
A deeper technical track for whoever will own the database internally: users, groups and access rights, record rules, automated and scheduled actions, QWeb layout adjustments, backups, and the first steps of diagnosing a failure before it becomes a ticket.
- Users, groups, access rights and record rules.
- Automated actions and QWeb layout changes.
- Backups, scheduled actions and first-line diagnosis.
Everything training leaves behind
A written training plan
Roles, tracks, session dates and who attends what, agreed before the first session.
A training database
A safe copy of your configured system with your data, so mistakes cost nothing.
Role guides
Step-by-step documents written against your own setup, not generic Odoo screenshots.
Session recordings
Kept by you, so a new joiner in six months gets the same explanation.
Assessment notes
Where each team is confident and where it still needs a second pass before go-live.
Post go-live refresher
A follow-up session once people have met the cases no training can anticipate.