In this article
- Key takeaway
- Choose an internal owner, not another messenger
- Set decision rights before configuration is signed off
- Communicate the change by role
- Train for transactions, not attendance
- Two illustrative adoption situations
- A distributor with offline approvals
- A retailer with recurring stock corrections
- The adoption scorecard leadership should review
- A practical champion checklist
- Frequently Asked Questions
- Who should act as ERP change champion?
- Can the implementation project manager also fill the role?
- When should users be trained?
- What proves ERP adoption?
- How SERPA can help
Author’s role: SERPA — ERP Change Management and Adoption Team
Key takeaway
Appoint an empowered internal owner, train users on real transactions and measure correct processing, repeat errors and off-system work to sustain Odoo adoption.
A practical guide to internal change ownership, role-based training and measurable ERP adoption for African enterprises.
An Odoo system can be live while the business is still running on paper. A warehouse supervisor prints yesterday’s stock list because staff distrust the new inventory balance; finance approves an invoice over WhatsApp because the approval route has not become routine. Neither problem is solved by announcing another go-live date.
A well-supported ERP change champion turns that gap into an operating plan. The champion connects decision-makers, key users and implementation specialists; explains what changes for each job; and helps prove that transactions now happen correctly in Odoo, rather than in parallel spreadsheets.
Choose an internal owner, not another messenger
Odoo’s implementation approach describes the client Single Point of Contact (SPoC) as a central internal project participant: coordinating requirements, key users, training and first-line support. The person needs adequate time, organisational credibility and delegated authority. For a complex multi-entity deployment, the role may require dedicated capacity; in a smaller rollout, a clearly empowered owner and reliable escalation path may be sufficient.
Appointing the employee who knows the old system best is not enough. Someone must be able to resolve routine cross-team questions while promptly escalating changes to policy, scope, risk or budget. Otherwise operational choices wait for meetings and users return to familiar off-system workarounds.
Set decision rights before configuration is signed off
| Decision area | Champion / SPoC | Executive sponsor or steering group |
|---|---|---|
| Day-to-day process | Clarify approved steps and make decisions within delegated limits | Resolve policy changes and conflicts beyond delegated authority |
| Requirements and testing | Coordinate scenarios, users and acceptance evidence | Set priorities when teams disagree |
| Training and support | Organise role-based practice, log blockers and first-line requests | Provide time, staffing and support resources |
| Scope, risk and investment | Explain operational implications with evidence | Approve material changes to scope, risk or budget |
Record those limits in a short project mandate. When approval responsibility is visible, frontline employees know whom to ask and auditors can trace why a process changed.
Communicate the change by role
A blanket email announcing that Odoo is available does not tell a receiving clerk how to record a partial delivery or explain to an accounts clerk which evidence must accompany a supplier bill. Change communication should give each role four answers:
-
Why the old procedure is changing and what risk the new control addresses.
-
Which steps the person must complete in Odoo, including exceptions.
-
Who provides immediate help when a transaction cannot be completed.
-
How frontline users can report an impractical workflow or a recurring workaround.
The champion must also bring user feedback to the project team. A closed support ticket does not demonstrate adoption if the department continues to use spreadsheets or informal messages for the same task.
Train for transactions, not attendance
Train key users early enough to test real workflows. Give end users hands-on practice near go-live and targeted refresher sessions during stabilisation. Rather than asking whether employees attended, ask them to demonstrate a correct invoice, stock move, return, receipt or approval under realistic conditions.
A missed inventory step may cause adjustments; a misunderstood invoice approval may delay collections. Training effectiveness should therefore be assessed against the business transaction, not the number of people in a meeting.
Two illustrative adoption situations
A distributor with offline approvals
A Zimbabwean distributor implements Odoo Inventory and Invoicing. During the early operating weeks, supervisors still authorise urgent exceptions by messaging rather than using the configured approvals. The internal champion observes the real transaction, identifies whether the cause is a missing right, unclear delegation or a process-design gap, and schedules targeted retraining after the fix. Management then measures how many relevant approvals are completed in Odoo without an off-system workaround.
A retailer with recurring stock corrections
A retailer reports strong training attendance, but stock adjustments and invoice reversals continue rising. The change champion looks at the process behind the corrections and discovers uncertainty in the return-and-exchange workflow. A supervised practice session, clarified job aid and re-test are more useful than another generic training presentation. A declining correction rate is evidence that the behaviour has changed.
The adoption scorecard leadership should review
| Indicator | Management question | Why it matters |
|---|---|---|
| Active users by role | Are expected users working in the system? | Reveals unused licences and bypassed roles |
| Process completion in Odoo | Do invoices, receipts and approvals stay in the workflow? | Shows whether Odoo is becoming the system of record |
| First-time-right rate | Can users complete transactions without rework? | Tests practical competency |
| Reversals and stock adjustments | Where do repeated corrections begin? | Identifies process or training failures |
| Order-to-invoice time | Is operational throughput recovering? | Links adoption to customer delivery |
| Recurring helpdesk questions | Are users gaining independence? | Separates root causes from ticket counts |
Use consistent definitions from the first adoption review onward. The champion should bring unresolved decisions, repeat workarounds and corrective-action owners to the steering group; the project should not be judged on training completion alone.
A practical champion checklist
-
Written internal SPoC mandate with named executive sponsor and decision limits.
-
Key users nominated for finance, procurement, inventory and sales as relevant.
-
Role-specific communications, job aids and hands-on scenarios.
-
Visible process for logging, escalating and resolving adoption obstacles.
-
Weekly measures of correct transaction completion, repeat errors and off-system work.
-
A handover plan that leaves business users capable of operating without the project team.
Frequently Asked Questions
Who should act as ERP change champion?
A respected internal owner with available time, user credibility, authority for routine decisions and direct access to executive sponsors.
Can the implementation project manager also fill the role?
Sometimes, but an external project manager does not replace the client’s internal process owner. There must still be someone accountable for adoption after handover.
When should users be trained?
Train key users early for design and testing. Train end users close to go-live, then reinforce learning through practical tasks and targeted refresher support.
What proves ERP adoption?
Consistent, correct processing in Odoo, fewer unnecessary reversals, declining workarounds and improved end-to-end cycle times. Attendance alone does not prove capability.
How SERPA can help
SERPA helps leadership teams define change ownership, practical Odoo user training, adoption dashboards and a handover model that sustains day-to-day operation. Request a consultation to review your change champion mandate and ERP adoption plan.