Skip to Content

Training / Nimex Solutions

A successful ERP is one your team actually uses.

A project is not finished when the system is technically implemented. It is finished when the warehouse validates its own transfers, accounting posts its own invoices and managers read their own reports. We train by department and by role, on real scenarios, on a staging copy of your own environment, and we count progress as confirmed completion.

Prepare your team for Odoo Discuss your training plan
  • How we work
  • Standard Odoo
  • Scoped per project

From learning to readiness

A path, an exercise, a confirmation, a readiness state.

Every employee follows the same four steps. The system records the exercise, a person confirms it, and readiness is the count of confirmed exercises, nothing else. The photograph and the four screens below are how a warehouse session looks in practice.

A training room seen from behind: two participants at their own screens while a trainer works through a diagram on the large wall screen
The trainer explains at the board; everyone practises at their own screen.A session ends with each participant's exercise done on the staging copy of the company database, not with a slide deck.
Sample data

  1. 1Learning path

    Assigned per role: five exercises with the permissions the operator will have in production.

  2. 2Exercise

    A real scenario on the staging copy of your database: the operator validates the transfer herself.

  3. 3Confirmation

    The process owner checks the result in the system and confirms it. Attendance and watched videos are recorded, never counted.

  4. 4Readiness

    Ready for go-live when every exercise of the path is confirmed. Until then the tracker says "in training", and the blockers have an owner.

Two colleagues seen from behind at a workstation, one pointing at a line on the screen while the other follows
Guidance at the screen, not a slide deck.Each person works their own scenarios in a staging copy of the company's Odoo, with a trainer beside them.
Sample data

Adoption, not installation

The system goes live when people can do their job in it.

Configured workflows only pay off when the people who run them adopt them: the receiving clerk, the planner, the accountant, the sales representative. So we treat training as a part of the implementation, with the same discipline as data migration or testing.

  1. By department and by roleHow we work

    A warehouse operator and a warehouse manager do not need the same session. Each role gets its own path with the permissions it will actually have.

  2. Real scenarios, your dataHow we work

    Exercises use your products, partners and documents on a staging copy of your environment, so what people practise is what they will do on Monday.

  3. Progress is confirmed completionHow we work

    An exercise counts when the process owner confirms the result in the system. Attending a workshop or watching a video is recorded, but it is not competence.

Training by department

What each team must be able to do before go-live.

The curriculum follows your configured workflows, not the generic Odoo menu. Below is the typical scope per department; the exact list is written during solution design and becomes the exercise list of each learning path.

  1. Sales

    Quotation to confirmed order, price lists and discounts, delivery dates, customer portal, invoicing triggers.

    • Quotations
    • Confirmation
    • Price lists
    • Delivery status
    • Down payments

  2. Procurement

    Requests for quotation, vendor price lists, purchase approvals, receipts and three-way matching with vendor bills.

    • RFQ to PO
    • Approvals
    • Receipts
    • Bill control

  3. Warehouse

    Receiving, putaway and locations, barcode scanning, delivery validation, backorders and exceptions, inventory adjustments, stock move history.

    • Receipts
    • Barcode
    • Transfers
    • Exceptions
    • Adjustments
    • Traceability

  4. Manufacturing

    Bills of materials, work orders, component availability, production confirmation, scrap and quality checks where configured.

    • Manufacturing orders
    • Work orders
    • Availability
    • Scrap

  5. Accounting

    Customer invoices and vendor bills, payments and reconciliation, e-invoice and e-archive flows, closing routines, reports.

    • Invoices and bills
    • Payments
    • Bank reconciliation
    • e-Fatura
    • Period close

  6. Management

    Dashboards and pivot reports, approvals, what each status means, how to ask the right question of the system instead of the team.

    • Dashboards
    • Approvals
    • Pivot views
    • Status meanings

  7. HR

    Employee records, contracts, time off and approvals, attendance, expense flows and the hand-over to payroll.

    • Employees
    • Time off
    • Expenses
    • Payroll inputs

  8. Customer service

    Tickets or field service tasks, priorities, communication with customers from the record, hand-over to sales and warehouse.

    • Tickets
    • Priorities
    • Customer messages
    • Hand-overs

Role-based learning tracker

Progress means confirmed exercises, not attendance.

The warehouse path has five exercises: receive a purchase delivery, scan product and location, validate a transfer, correct an exception, find a stock move history. Each one is done on the staging database and confirmed by the process owner. A watched video is recorded, not counted; a blocker gets an owner and a date.

  1. Assign the pathEach user gets the exercises of their role, with the permissions they will have in production.How we work
  2. Practise on stagingExercises run on a neutralised copy of the company database, with the company's own products and partners.How we work
  3. Confirm the resultThe process owner checks the result in the system (a done transfer, a posted invoice) and confirms the exercise.How we work
  4. Own the blockersMissing configuration, open questions and decisions are listed with an owner and a date until they are closed.How we work

Formats

The formats we deliver, and how we scope them.

Every project combines a few of these. Remote workshops and staging practice are our default; on-site sessions and super-user programmes are agreed per project. We do not hand out attendance diplomas or promise learning outcomes.

A training session in a meeting room: participants at tables, a presenter at a large screen showing a process diagram
Workshops are for decisions and questions; practice happens at the keyboard.A department session ends with the exercise list each participant will complete on staging.
  • Live remote workshopsPer department, on the staging environment, recorded for the people who could not attend.How we work
  • On-site sessionsAt your site when the project scope includes it: warehouse floor, production line, shared screens in the office.Where agreed
  • Step-by-step manualsWritten for your configuration, with screenshots of your own environment and your document numbers.How we work
  • Short videosRecorded on the staging database for the recurring tasks of a role; a complement to practice, not a substitute.How we work
  • Guided exercises and staging practiceScenario, guidance, result: the format of every learning path, confirmed by the process owner.How we work
  • UAT sessionsUser acceptance tests double as training: the people who will run a workflow test it with their own data before go-live.How we work
  • Super-user and champion programmeOne or two people per department learn the configuration deeper and become the first point of contact after go-live.Scoped per project
  • Post-launch Q&AScheduled question rounds in the first weeks after go-live, feeding the manuals and the open-question list.How we work
  • Process-owner responsibilityEach workflow has a named owner on your side who confirms exercises and decides open questions.How we work

Adoption management

What we track between the first workshop and the first month live.

Adoption is managed like any other work package: with owners, a list and a weekly review. The readiness board is shared with your project lead, so nobody discovers at go-live that a department never practised.

  • OwnershipA process owner per workflow; a key user per department.
  • AttendanceWho attended which session; recorded, never used as the readiness measure.
  • Practical task completionExercises done on staging and confirmed in the system.
  • Process confirmationThe owner confirms that the documented workflow is the one the team will follow.
  • Open questions and blockersListed with owner and date; closed in the weekly review.
  • Post-launch reinforcementQ&A rounds, manual updates and a second pass on the exercises people found hard.

Watching a video is not competence. Our tracker records it, but readiness only moves when exercises are completed and confirmed. We do not publish adoption rates or outcomes of past projects.

Training materials

Manuals, annotated screens and short lessons, made from your environment.

Materials show your menus, your document numbers and your products, so they stay useful after the trainer has left. Everything below is a composition on sample data.

  • Step-by-step manual

    Written per workflow, with the decisions a user must make, not only the clicks; your menus and document numbers.

    How we work

  • Annotated screenshots

    From the staging copy of your database, numbered where a decision is made, embedded in the manual next to the step.

    How we work

  • Short video lessons

    One task per lesson, recorded on staging, with chapters that follow the manual. Watching is recorded in the tracker; completion is not.

    How we work

Related services

Training sits between go-live and support.

Chat with us