Configuring the system is not the end of the job: Odoo pays off only when employees use it in their daily work. BUline runs training by role, on your process and your data, online or in Tashkent.

Free diagnostic Odoo: overview

Functional trackTechnical trackCorporate trackOnline and in TashkentUzbek and RussianPractical test

Three tracks

Who learns what: the functional, technical and corporate tracks

The track is chosen by job function. A regular employee takes one track, while a key user takes two: one for their own role and one for running the system.

Functional track

For day-to-day staff: sales manager, warehouse keeper, purchaser, accountant, cashier, shop-floor foreman. Everyone practices running their own document chain in Odoo from start to finish. Details →

Technical track

For the key user, the person who imports data and the Odoo administrator: Studio, import, access rights, copies and backups, version upgrades. Details →

Corporate track

For managers and process owners: reports, approval rules, the access-rights matrix, system discipline and the procedure for onboarding a new employee. Details →

Functional track

How the work of your role is done in Odoo

The functional track starts with one question: which screen in Odoo does my work start from, and which document does it end with? A separate session runs for each role, so the warehouse keeper does not spend time on accounting screens, nor the accountant on warehouse screens.

The session is built around your process: the business requirements document (BRD) written during the diagnostic and the configured system form the basis. Result: the employee does their task without help, within their own access rights.

Sales and CRM: the quotation → order → invoice chain, the customer card, activities and forecast
Warehouse and purchasing: receiving and shipping goods, stocktaking, purchase orders; working with barcodes (Enterprise)
Manufacturing: bill of materials (BoM), manufacturing order, work orders; the shop-floor screen (Shop Floor, Enterprise)
Accounting: invoice and payment, bank statement reconciliation, taxes, period closing
Cash desk (POS): opening and closing a shift, sales, returns, payment methods
Employees: leave and expense requests. For such employees, Odoo has a “light user” role with limited capabilities

—

Technical track

Studio, data and administration: running the system yourself

The technical track is for people who run day-to-day operations after launch without depending on BUline. Usually these are one or two key users and an in-house IT employee.

The topics follow the official Odoo documentation and are adapted to your hosting type. On Odoo Online the work goes through the database manager, on Odoo.sh through code branches and staging, and on your own server server settings are added as well. The difference between Studio and a custom module is explained on the Studio page.

Studio: fields, views, automated rules, approval rules, PDF reports; exporting and importing changes to another database. Studio is part of Odoo’s Custom plan
Data: Excel and CSV import, reloading with an external identifier, cleaning up duplicate records (Data Cleaning)
Administration: users, roles and access rights, two-factor authentication, careful handling of keys and passwords
Copies and backups: creating a test copy, neutralization, separating the production and test databases
Upgrade: requesting an upgraded test database, the test checklist, upgrading the production database
Developer mode and the technical menu: only when needed; the Odoo documentation calls for using them with care

—

Corporate track

For managers and process owners

A manager does not enter documents into the system, but sets the discipline around it. The corporate track answers company-level questions: where do I get the report, who approves what, how is a new employee onboarded, and what happens when people work outside the system?

The session is short and focused on results, and usually runs separately with a group of managers.

Manager reports: pivot and graph views, filters and saved searches, dashboards
Approval rules: who approves which document, and from which threshold
Roles and access-rights matrix: who sees and changes what
System discipline: all documents are kept in Odoo; Excel and paper notebooks are not run in parallel
Onboarding a new employee: assigning a role, instructions and a trial task
Resistance to change: employees are involved from the start of the project, and after launch we check who is working in which system

—

Roles

Who attends which session and what they practice

The table below is an example. The exact plan is drawn up after the diagnostic, based on your roles and apps.

Role	Track	Scenario practiced	Can do after practice
Sales manager	Features	Create a quotation for a customer, convert it to an order, view the invoice	Handles the order to the end, sees the customer’s outstanding balance
Warehouse clerk	Features	Receiving goods, picking and shipping, stocktaking	Keeps stock levels consistent with documents
Purchaser	Features	Purchase request and order for a missing material	Handles the document chain with the supplier
Accountant	Features	Supplier invoice, payment, bank statement reconciliation	Gets entries ready for period closing
Cashier	Features	Opening a shift, a sale, a return, closing the shift	Closes the shift by payment method
Shop-floor foreman	Features	Starting and finishing a work order, recording defects	Carries out their task on the shop-floor screen
Key user	Technical	Adding a field, importing data, granting access rights	Makes small changes without waiting for a reply from BUline
Manager	Corporate	Opening a report, approving a document, viewing access rights	Sees the gap between plan and actual on their own

Format

Online or in Tashkent, in Uzbek or Russian

The format is chosen by role and location. Both can be used in one project: managers face to face, branches online.

Online

A live session over video
The employee practices on their own computer in the test database
Convenient for branches and remote teams
Questions and answers during the session; a list of questions is collected afterwards

In person in Tashkent

Face to face with a BUline specialist, location to be agreed
Practice at their own workplace for the cashier, warehouse keeper and foreman
A separate session for managers
Side-by-side help at the workplace in the first days

Uzbek and Russian

Sessions and materials in both languages
A glossary of terms is agreed at the start of the project: the name on screen and the document name are the same
Each employee chooses their own interface language: the warehouse keeper can work in Uzbek, the accountant in Russian
On the state of translation: Odoo in Uzbekistan

Training process

Training plan → sessions → practical test → ongoing support

Training starts before go-live and does not stop after it. Dates are agreed in writing in the project plan. General procedure: implementation stages →

01Training planAt the architecture stage

The list of roles, scenarios for each role, session format and language, groups and dates are documented. Result: a plan stating who learns what, and when.

02SessionsAt the implementation stage

First, key users accept and learn the configuration during the sprints. Then short hands-on sessions run for each role, with key users taking part alongside their colleagues. Everything happens in the test database, with your data.

03Practical testBefore go-live

Each employee runs the scenario for their role with their own access rights. Results are recorded, and errors and questions are logged with an owner and a deadline.

04Post-launch support30 days + ongoing

In the first month after launch, intensified support via Telegram and email. Then agreed ongoing support: a new employee, a new app, a move to a new version.

Practice environment

Practice uses your data but never touches the production database

Sessions run on a copy of the production database. When Odoo creates the copy with the “for testing” flag, outgoing actions such as emails, payments and delivery orders are disabled, so no email reaches a customer and no money moves during practice. A red banner at the top of the screen reminds users that it is a copy.

Once the data is migrated, practice uses your own products, customers and stock levels. The employee then works not with “Table 1” from a lesson but with an item from their own catalog.

On Odoo Online a copy expires after 15 days, and there can be no more than five per database: session dates are planned accordingly
On Odoo.sh the staging database is a neutralized copy of the production database. The Tester role has access to staging but not to the production database
On your own server the copy is made in the database manager with the neutralize flag
Settings made during practice do not carry over to the production database on their own: changes are applied separately, under control
On the test database and neutralization

—

Materials

Materials you keep after the sessions

Materials are prepared with your terminology and your configuration, so a new employee can also start work using them.

Instructions by role

Step-by-step instructions for each role
With your document and screen names
In Uzbek and Russian
Screenshots from your own configuration

Video tutorials

Short: one video per scenario
Onboarding sequence for a new employee
Examples built on your own database structure
Can be placed in the internal knowledge base (Knowledge, Enterprise)

Practical exercises

Tasks built on your data
A checklist with the expected result
Common mistakes and how to fix them
Reusable for a new employee

Official Odoo materials

Odoo documentation for each app (odoo.com/documentation)
Odoo Learn: official lessons by app; according to Odoo’s pricing page, access to the eLearning platform is free with a subscription
They are generic; BUline’s material adds your own process to them

How we verify

How we check what has been learned

Training is measured not in hours but by whether the employee can do the job. The acceptance criterion is written down before the session. The test runs under the employee’s own role, not with administrator rights: otherwise hidden buttons and restrictions go unchecked. Details: acceptance testing (UAT)

Role	Test scenario (example)	Acceptance criterion
Sales manager	Creates an order with three line items, confirms it and processes a return of part of it	The order, stock levels and customer debt match the documents
Warehouse clerk	Enters received goods, picks and confirms a shipment	Stock equals the quantity on the document
Accountant	Enters a supplier invoice and matches the payment to a bank statement line	The debt amount matches the report
Key user	Adds a new field, imports data and checks it on the test copy	The change moves to the production database through the planned procedure
Manager	Finds this order in the report and carries out the approval	The figures match the documents, and the approval history is visible

Mistakes

Common training mistakes and how to prevent them

These mistakes are known risks. We close them at the planning stage.

Starting too late

If training is left to the eve of go-live, employees go back to the old software
Key users take part from the sprints onward, so they know the configuration in advance

The same lesson for everyone

Accounting screens are surplus for the warehouse keeper, and warehouse screens for the accountant
Separate groups and scenarios by role

Administrator rights during testing

An administrator sees every button, so the warehouse keeper’s “there is no button” problem does not show up in testing
Every scenario is run under the employee’s actual role

Leaving it unmonitored after go-live

A few days later, we check that employees are really working in the new system
Intensified support for questions in the first month

Preparation

What we need from you before we start

This list speeds up training. We can start even if not everything is ready.

People

A single point of contact: someone assigned to the project who can make decisions (BUline’s recommendation)
A key user from each department
Written backing from management

Time

Session hours are set aside in the work schedule in advance
Spare days for retesting
Groups are formed so that cash desk and warehouse work does not stop

Organizational

The list of roles and who joins which group
A room and screen for in-person sessions, stable internet for online
Group language: Uzbek or Russian

FAQ

Frequently asked questions

How much does training cost and how many hours does it take?

The scope depends on the number of roles, groups, apps, the format (online or in person) and the amount of customization. The exact plan and cost are given in a written proposal after the free diagnostic.

Is every employee trained, or only key users?

Both. Key users are trained in more depth first, then a hands-on session is held for each role. In a large team a key user teaches colleagues, while BUline provides the materials, sessions and oversight.

In which language are the sessions held?

In Uzbek and Russian; instructions and video lessons are in these languages too. An Uzbek translation of Odoo exists; we check how complete it is for your apps and version during the diagnostic: Odoo in Uzbekistan.

Odoo has official lessons. Why do we need training from BUline?

Official lessons are generic: they do not know your documents, terminology, roles and configuration. BUline sessions close that gap. You can use both together.

What do we do when a new employee joins?

A new employee starts with the instructions and video lessons for their role and practices alongside a key user. If a repeat session is needed, it is agreed as part of ongoing support.

Does the technical track train developers?

No. It trains the key user and administrator who run Studio, import, access rights and upgrade testing themselves. Writing a custom module is a separate service: Studio and modules.

Do you also train for Odoo Community?

No. BUline’s services are provided for Odoo Enterprise and Odoo Online. General information about the editions: Versions and hosting.

Sources

Data sources

Odoo

Related sections

BUline servicesBUline servicesImplementation, integration, training BUline servicesIndustries13 areas, 109 industries BUline servicesIntegrationsTax, bank, messaging, marketplaces, equipment BUline servicesElectronic documents and taxE-faktura, e-signature (ERI), MXIK, cash register, waybill

← PreviousExternal systems and equipment Next →General manufacturing

Free diagnostic

Let’s decide together which Odoo apps to start with

During the diagnostic, we review your processes and tell you where standard Odoo is enough and where configuration is needed — with an app list, edition and phases.

Submit a request Message us on Telegram OR CALL US+998 77 275 36 15

Free diagnostic

Savdo

Ombor va ishlab chiqarish

Boshqaruv

Texnologiya

Oʻzbekiston

BUline bilan

Ilovalar

Platforma

Oʻzbekiston uchun

BUline bilan

BUline xizmatlari

Savdo va avtomatlashtirish

Aloqa kanallari

Nazorat va AI

Integratsiyalar

BUline bilan

Asoslar

Yoʻnalishlar

Amaliyot

Strategiya va kontent

Reklama kanallari

Organik oʻsish

Oʻlchov va analitika

Savdo va mijozlar

Operatsiyalar

Ichki ish

Tamoyillar

Продажи

Склад и производство

Управление

Технологии

Узбекистан

С BUline

Приложения

Платформа

Для Узбекистана

С BUline

Услуги BUline

Продажи и автоматизация

Каналы связи

Контроль и AI

Интеграции

С BUline

Основы

Направления

Практика

Стратегия и контент

Рекламные каналы

Органический рост

Измерение и аналитика

Продажи и клиенты

Операции

Внутренняя работа

Принципы

Sales

Inventory and manufacturing

Management

Technology

Uzbekistan

With BUline

Apps

Platform

For Uzbekistan

With BUline

BUline services

Sales and automation

Communication channels

Control and AI

Integrations