Odoo services · Odoo Training
Training on your data, in your language.
Generic Odoo training teaches the software. It does not teach your process, which is the part people actually need. We train each role on the exact workflow they will run on Monday morning.
—— Where it hurts
The problems this work actually solves.
The gap between a configured Odoo system and a used one is training. These are the problems that bring companies to us — often a few months after go-live, when the spreadsheets have started creeping back.
Go-live worked, adoption didn't
The system went live on schedule. Three months later, sales still quotes in Excel and the warehouse keeps its own stock sheet, with someone keying everything into Odoo at month-end. The ERP has become a reporting chore instead of the way work happens.
How we handle itWe retrain each role on its own daily workflow, on a copy of your database, then check actual usage two weeks later and fix what slipped.
The only person who knew Odoo resigned
One admin learned the system during implementation and everyone else routed their work through her. Now she has handed in her notice, and nobody else can close a month, adjust stock or fix a stuck delivery order.
How we handle itWe rebuild the knowledge across roles rather than in one head — a runbook per role, plus at least one trained super-user as the first line for questions.
One big training day for everyone
Everyone sat through the same full-day walkthrough before go-live. The warehouse team watched an hour of accounting screens, accounts watched barcode scanning, and by mid-afternoon nobody was absorbing anything.
How we handle itWe split training by role: a focused half-day per team, covering only the screens that team touches, in the order they touch them.
Workarounds became the official process
Somewhere along the way someone found a shortcut — cancelling and recreating orders instead of amending them, or booking every payment to one clearing account. It spread, and now the reports don't reconcile and nobody knows why.
How we handle itWe watch how people actually use the system, trace each workaround back to the missing knowledge, and retrain the correct path with the person who invented the shortcut in the room.
New hires learn by folklore
There is no written guide, so each new starter learns Odoo from whoever sits closest. Every bad habit gets copied along with the good ones, and the quality of your data ends up depending on the seating plan.
How we handle itEvery role gets a short written runbook in its own language, kept current, so onboarding is a document plus a checklist instead of an apprenticeship.
—— Learn from other projects
Mistakes we see, and how to avoid them.
Training before the configuration is frozen
Teams get trained on screens that change the following week, and the knowledge dies with the old configuration — worse, users stop trusting anything they were taught. We schedule sessions only after the relevant workflow is configuration-complete, and if a later change touches a screen, we retrain that screen specifically.
Treating training as a single event
One big session the week before go-live feels efficient, but the real questions only exist after people have run a month-end, a stock count and an angry customer through the system. We split delivery: core sessions before go-live, a refresher after the first close, and the two-week usage check in between.
Leaving managers out
Companies train the people who key data and skip the people who read it. When managers cannot pull their own numbers they ask for Excel exports, and within a quarter the team is maintaining two systems again. We give management its own short session on dashboards, approvals and the reports that replace the old spreadsheets.
Measuring attendance instead of usage
A signed attendance sheet proves people were in the room, not that they can do the work. The gap shows up weeks later as missing records and month-end surprises. Our measure is the database itself: two weeks after training we look at who is creating what, and rework the spots where usage never started.
Training in the wrong language
An English session for a Thai-speaking floor team produces polite nodding and zero retention — and the reverse is just as true for international managers. We run each session in the language of the people in it, Thai or English natively, and the runbooks match the session.
—— Ways to engage
Three ways to start with us.
Go-live training programme
The full role-mapped programme around a go-live — ours or another partner's. Sessions are scheduled against the implementation plan, so each team trains once its workflow is final.
- Half-day sessions per role, run on a copy of your database
- Runbooks per role in Thai or English, yours to keep
- A refresher session after the first month-end close
Adoption rescue
For a system that has been live for months but is quietly losing users to spreadsheets. We find where usage stopped and why, then retrain exactly those points.
- Usage review inside your live database — who enters what, and who has stopped
- Targeted retraining on the steps people avoid or work around
- Clean-entry guidance so records go in correctly from now on
Super-user development
We coach one or two of your staff past user level, so routine questions get answered in-house the same hour instead of waiting in a support queue.
- Deeper sessions on settings, access rights and common fixes
- Shadowing on real support questions until they can field them alone
- A written handover of what stays in-house and what still comes to us
Your implementation partner
A partner, not a licence reseller.
We are not chasing licence volume — we design, build and stay accountable for systems that companies run their operations on. The consultant who scopes your project stays through go-live and the support that follows, and everything we commit to is written into a fixed scope per phase.
—— What done looks like
Outcomes you can verify yourself.
Each role runs its own workflow unaided
By the end of the programme, a salesperson can take an order from quote to invoice and the warehouse can receive, pick and adjust without calling anyone. You verify this by watching your own people work, not by taking our word.
Runbooks that match the live system
Every role holds a short written guide that matches the current configuration, screen for screen. A new hire can follow it to a completed task on their first day.
Questions answered in-house first
A named super-user fields the routine questions, and only genuine system issues reach a vendor. The change shows up in your own support traffic within a month.
Work recorded where it happens
Records are created by the people doing the work, at the time they do it — not batch-keyed by one admin at month-end. The timestamped document trail in Odoo shows it, if you care to look.
—— How we work
What the engagement looks like.
Role mapping
Sales, warehouse, accounts and management each need a different half-day, not the same full day.
Hands-on with real records
Sessions run on a copy of your database, so people practise on products and customers they recognise.
Written runbooks
Each role leaves with a short guide for their own tasks, in their language. Onboarding the next hire is then a document, not a repeat booking.
—— Why us
What you get that you would not elsewhere.
Thai-language delivery
Delivered by the Thailand team in Thai, including the written materials. Not an English deck read aloud.
Adoption, not attendance
We follow up two weeks later to see what people actually stopped using, and fix that.
Materials you keep
Runbooks and recordings are yours to reuse for every future hire.
Not sure where to start? A short call sorts it.
Talk to an Odoo specialist ➜—— Why us
What working with us is actually like.
Taught by the person who built your system
When we implement, the consultant who configured your workflows is the one standing in the training room — the same person from your first call through go-live. Questions get answers about your setup, not readings from a generic manual.
Thai and English, both native
Our Bangkok team trains in Thai, and the Thai materials are written in Thai — not translated from an English deck. International managers get the same content natively in English.
A written scope before you book
Training, like every phase we sell, has a fixed written scope: which roles, how many sessions, which deliverables. You know the full cost before the first session, and per role-session pricing means you never pay for seats that do not attend.
An Official Odoo Partner
We are an Official Odoo Partner under the India programme, working in current Odoo versions every day. What we teach is how the product behaves in your version, not how it worked three releases ago.
No licence agenda in the classroom
Community is free and we say so; Enterprise is billed by Odoo directly and we never mark it up. Our trainers earn nothing from what you license, so the advice in the room is about your workflow, not our margin.
Three offices, your working hours
Bangkok, New York and Delhi NCR between them cover most of the clock. Refresher sessions and follow-up questions land in your business hours, not at nine at night because the trainer is on another continent.
We measure adoption, not applause
The two-week follow-up is part of the standard scope, not an upsell. We look at what people actually do in the database after the room empties, and we come back for the parts that did not stick.
Built so you stop needing us
Runbooks, recordings and a trained super-user all exist to make the next question answerable without us. A training vendor whose clients must keep coming back has failed at the job.
—— Partner tiers, explained
What an Odoo partner tier does and does not tell you.
Odoo ranks partners by certifications held and licence volume sold. A tier signals commitment to the programme — it does not tell you who will actually staff your project. Ask that question of any partner, including us.
Learning Partner
New to the programme, building their first certified consultants and reference projects. Not a red flag — everyone starts here — but ask for hands-on proof.
Official Partner
Certified consultants and active delivery. This is where we sit, enrolled through the India programme, delivering from Thailand, the USA and India.
Silver & Gold
Higher tiers earned mainly through licence sales volume and headcount of certified staff. A strong signal of scale — not automatically of fit for your project.
—— Who this is for
Built for your size, not resized for it.
Growing companies (5–100 people)
For companies of 5–100 people, training is usually the difference between Odoo running the business and Odoo becoming one person's side job.
- Per role-session pricing fits a team where the whole sales department is three people.
- The whole company can be trained inside a week, scheduled around real work.
- The management session is built for an owner who still approves everything personally.
- Runbooks hold the knowledge when your one back-office admin is on leave.
Mid-market (100–500 people)
At 100–500 people, the problem is no longer teaching Odoo — it is teaching it consistently across shifts, sites and staff turnover.
- Sessions repeat per shift, so the night crew is trained as well as the day crew.
- A super-user per department gives each floor its own first line of support.
- Training tracks a phased rollout, so each site learns just before its own cutover.
- Thai and English sessions run in parallel for a mixed local and international staff.
—— Risks
What usually goes wrong — and how we prevent it.
Training on demo data
Lessons learned on demo records evaporate in a week. Sessions run on your configuration and your documents.
One session before go-live
A single class cannot survive the first month-end. We schedule refreshers after the close, when the real questions exist.
Every question routed to a vendor
Adoption stalls when nobody in-house can answer. We train an internal super-user who fields questions first.
—— Pricing
What this costs.
Priced per role-session. Bundled at no extra charge with any implementation — untrained users are how implementations fail.
—— Editions & hosting
Community, Enterprise, and where it runs.
The licence and the hosting are separate decisions, and both are yours — we implement either edition and hand over whichever infrastructure you choose.
$0 licence
Odoo Community
Open source and free to license. Covers sales, purchasing, inventory, invoicing, manufacturing and more. You pay for implementation, not rent.
Per user, billed by Odoo
Odoo Enterprise
Adds studio, advanced accounting and localisations, mobile apps and official support. Billed by Odoo directly — never marked up by us.
Odoo.sh · VPS · on-premise
Your server or the cloud
Odoo.sh, a VPS we manage, or your own hardware. We recommend based on your compliance and budget, then document the choice so it stays portable.
—— The toolkit
What this service usually touches.
—— Related
Explore what else we do.
—— FAQ
Questions teams ask about this service.
Onsite or remote?
Both. Warehouse and production teams learn better onsite with the scanners in hand; office roles do fine remotely.
What if our team changes?
That is what the runbooks are for. Refresher sessions are available, but most clients find the written guides cover new starters without one.
How long does a full training programme take?
Each role needs about half a day. For most SMEs the whole programme runs inside one to two weeks, scheduled around normal work so no department has to stop. The refresher after your first month-end close adds one more short session.
Can you train us on a system another partner implemented?
Yes, and it is common. We review the configuration first, so we teach how your system actually behaves rather than a generic version of it. If that review turns up configuration problems, we tell you plainly instead of training people to work around them.
How many people can join one session?
Small enough that everyone works at their own keyboard — usually one team at a time. Training only works when every person drives; a session where most people watch is a presentation, and presentations do not create users.
What do we need to prepare before the first session?
Three things: a list of who does which role, a recent copy of your database (we handle this ourselves if we host or support your system), and a handful of real documents — actual quotations, purchase orders, invoices — to practise on. Onsite sessions also need a room where each person has a computer.
Do participants get a certificate?
We can issue a letter confirming who attended and what was covered, if your HR process needs one. But we will be straight with you: no certificate proves someone can run their workflow. The two-week usage check does, and that is the measure we stand behind.
Let's find out whether Odoo actually fits your business.
A short call, an honest answer. If it isn't the right system for you, we'll say so.