Corporate training
A customised curriculum for one organisation, covering the specific modules and business processes you have implemented, scheduled around your operating hours.
One of the leading causes of ERP failure is not the software. It is that the people who have to key transactions every day were never properly taught the system.
We train on your database, with your products, your customers and your approval rules — not on a demo. The store keeper, the accountant and the counter staff are the ones who decide whether an implementation succeeds.
Teams we have trained on Odoo
Odoo training is structured instruction that teaches a team to run their own business processes inside Odoo. It splits into three kinds: functional training for the people who use the modules daily, technical training for developers who will extend the system, and administration training for whoever manages users, access rights and backups. Most businesses need all three, aimed at different people.
Training managers is easy and almost useless. Adoption is decided by the people who enter transactions — store keepers, accountants, operators and counter staff.
Each programme is built around the modules you actually run, with exercises using your own master data.
A customised curriculum for one organisation, covering the specific modules and business processes you have implemented, scheduled around your operating hours.
Role-based sessions: sales team on quotations and pricelists, warehouse on receipts and transfers, accounts on reconciliation and GST, production on work orders.
Creating custom modules, fields and reports; the Odoo ORM; view inheritance; QWeb; integrating with APIs and third-party applications.
User management, access rights and record rules, scheduled actions, database backup and restore, and what to check when something stops working.
Run immediately before cutover: every role performs its daily transactions end to end in a test database until the steps are second nature.
Short sessions for staff who joined after go-live, and for teams whose processes have changed since. Usually the cheapest adoption fix available.
We have watched training fail often enough to know why. These are the differences that matter.
People learn the path to their own products and their own customers. Demo data teaches a workflow nobody will ever repeat.
A store keeper does not need the accounting module explained. Sessions are built around what one person does in a day.
Not their manager, not a representative. If the person doing the work was not in the room, the training did not happen.
Not a quiz. The attendee completes an actual order, receipt or entry in the test database, start to finish, unaided.
A one-page card per role with the exact menu path and the decisions at each step. People use it for months.
Questions only appear once people have hit real exceptions. One short follow-up session resolves more than doubling the original training.
Sometimes a business asks for more training when something else is wrong. We will say so rather than sell sessions.
If users keep making the same mistake, the system usually allows something it should not. A config change fixes it permanently; training only patches it.
If two departments disagree about who approves what, no amount of training resolves it. That is a decision, and it has to be made before the session — usually with an Odoo ERP consultant in the room.
People stop trusting a system that shows wrong stock or wrong prices, and go back to their spreadsheets. Fix the data first.
Training scheduled during your peak season will be cancelled halfway. Better to move it than to run it badly.
We train on systems we have implemented and on systems we have not, including ones where the original partner has gone. Sessions are led by consultants who configure Odoo for a living, so the answer to “can it do this?” is immediate and correct.
We point attendees at Odoo’s own material for product behaviour, and cover your configuration ourselves.
Tell us which roles are struggling and we will propose a session plan by role, on your own database, with the written step cards your team keeps afterwards.