Odoo Partner in Africa | SERPA Odoo ERP: Tiers, SLAs & Costs

A finance director has just received two Odoo proposals. One is lower on licence cost, one carries a stronger partner label, and neither explains who will fix a failed integration after go-live.

That is where an Odoo certified consultant evaluation needs to start. For African enterprises, the decision is not simply whether a supplier sells Odoo. It is whether that supplier can deliver a localised ERP implementation, support it in your operating hours, and account for every recurring and one-off cost.

As of 22 September 2026, Africa has no single Odoo regulator, common tax regime, currency framework or continent-wide partner register. A supplier suited to Odoo implementation in Africa must be assessed market by market, including its tax localisation, payroll, language, data-hosting and integration capability.

Start with Odoo certification, then test delivery capability

Odoo’s official Find Resellers portal is the first screening step. It is the place to verify whether a prospective firm appears in the official directory on the day you make the decision. The directory currently lists partners in Botswana, Zambia and Zimbabwe, but directory presence is not evidence that a team can deliver your particular project.

This matters when evaluating Odoo partners in Zambia, Odoo partners in Zimbabwe or an Odoo Botswana implementation. A firm may be listed in a country while its available consultants, tax configuration experience or support coverage sits elsewhere. Ask who will actually lead discovery, configure finance, migrate data and own go-live.

Odoo has four official partnership levels:

These criteria are useful because they provide a common starting point. They do not establish that the partner understands your industry, entities, local tax rules or interfaces.

Certification also belongs to an individual, not the firm. A certified Odoo partner may employ one certified consultant while most of the delivery work is assigned to people without that qualification. Ask for the names of the certified consultants allocated to your project, the Odoo versions on which they are certified, and their planned responsibilities.

The criteria are based on net new Enterprise users sold in the previous 12 months, certification on one of the latest three Odoo versions, and retention. That means a tier is current commercial information, not a permanent quality rating. Check the official portal and partner status again immediately before contract signature because directory status, tiers and pricing can change.

The questions we would put into the RFP

Ask every shortlisted provider to answer the same questions in writing:

1. Who are the named delivery consultants? Request their certification status, functional role, technical role and local availability. This avoids buying a senior sales presentation and receiving an unplanned delivery team.
2. What has the team implemented in our country and operating model? Require relevant African references, including multi-entity requirements where applicable. A retail implementation and a multi-company distribution implementation create different controls and integration work.
3. What is the discovery output? Ask for a documented process map, gap register, solution design and signed scope baseline. [VERIFY] These documents are how a board can see what is included before change requests accumulate.
4. How will data move into Odoo? Require a data-migration plan covering source ownership, cleansing, trial migrations, reconciliation and acceptance criteria. [VERIFY] Finance teams need auditable opening balances, not only imported records.
5. Who owns testing, training and go-live? Request a test plan, role-based training plan, cutover plan and handover documentation. [VERIFY] Go-live responsibility should have a named owner on both sides.

At Serpa, we treat this as an implementation readiness exercise rather than a supplier presentation. The decision should be based on evidence that the proposed team can produce real-time operational visibility without leaving finance to manage untested workarounds.

Put support SLAs into the partner contract

The most expensive Odoo support and maintenance problem is often discovered after go-live. The buyer assumes a subscription includes implementation support, custom-code fixes and integration recovery. It does not necessarily do so.

Odoo states that its subscription support is email-based, available Monday to Friday for 24 hours a day, and offered in English, French, Spanish or Dutch. Implementation services, expert services and maintenance of custom code are excluded. This distinction matters for Odoo Africa and Afrique Odoo programmes where a business may require support during local operating hours and from a consultant who understands its configured localisation.

Do not accept a proposal that says only “support included”. Put measurable commitments into the partner agreement.

A useful judgement call is this: if your business has no internally agreed critical-process definition, do not sign a support SLA yet. First identify which processes stop invoicing, inventory movement, statutory reporting or financial close. An SLA cannot protect processes nobody has classified.

Worked example: comparing support promises

Take an illustrative distributor planning for 10 initial Odoo users. One supplier includes “business-hours support” in its proposal but does not define response or restoration. Another supplier prices support separately and states severity definitions, escalation contacts, upgrade responsibilities and Odoo server maintenance boundaries.

The first proposal may appear less costly on day one, but the board cannot calculate its exposure during a critical incident. The second proposal creates a measurable operating commitment, even if its support line is higher. We would ask both suppliers to complete the same SLA schedule before comparing commercial totals.

The number of 10 users is relevant because it is also the current Ready-tier threshold for net new Enterprise users. It does not prove that a provider can support your distributor, which is precisely why the SLA must stand on its own.

Calculate the real cost of an Odoo implementation

Licence price is a component of ERP ROI, not the total cost of ownership. Separate recurring software and hosting costs from implementation, integrations, training, travel, support and maintenance.

Odoo’s published annual-billing list price is US$24.90 per user per month for Standard and US$49 per user per month for Custom, for initial users. Odoo.sh hosting is additional. Partner rates are not standardised, so a proposal cannot be benchmarked by licence price alone.

For 10 initial users, the published annual licence arithmetic is US$2,988 for Standard and US$5,880 for Custom. Those figures are calculated as the monthly list price multiplied by 10 users and 12 months. They are useful planning baselines, but they exclude hosting, implementation and partner services.

Use a commercial schedule like this when requesting proposals:

Custom modules need particular attention. Odoo’s pricing configurator includes maintenance of extra lines of code, while its command-line documentation describes Odoo Cloc as a rough measure used for pricing that maintenance. Ask for the custom code-line count, source-code ownership, repository access, upgrade budget and exit plan before approving custom development.

Worked example: the low licence comparison

Consider an illustrative group comparing two Custom proposals for 10 initial users. Both start from the published US$49 per-user, per-month list price, which gives a US$5,880 annual licence baseline before additional services.

Supplier A quotes only licences and an implementation headline. Supplier B separates Odoo.sh hosting, data migration, tax localisation, integration testing, training, ongoing Odoo support and maintenance services, and custom-code maintenance. Supplier B may look more expensive, but its board paper is more auditable because it shows what management is agreeing to fund.

Before selecting Supplier A, we would require the omitted lines to be priced or expressly excluded. The recurring licence number is known, while the cost of an unsupported integration or an unplanned upgrade can only be governed through scope, support terms and ownership.

Score partners against an evidence-based matrix

A practical selection matrix prevents a procurement team from over-weighting a demonstration or a discount. Score each supplier against the same evidence requirements.

If a supplier cannot provide this evidence before contract signature, treat that as a delivery risk rather than a paperwork issue. The step most teams skip is reconciling the sales scope to the support scope. A process may be included in implementation but excluded from post-go-live support, especially where customisation or third-party integration is involved.

When comparing providers such as Gasparai Consulting and Implementation Services or other regional suppliers, use the same matrix. Do not allow familiarity with a brand, a partnership label or a lower subscription figure to replace documented proof.

Frequently Asked Questions

Is a certified Odoo partner always the right Odoo implementation partner?

No. Official status and certification are useful screening signals, but certification belongs to individuals and a tier does not prove industry knowledge, local tax localisation capability or integration experience. Require named consultants and project evidence. [VERIFY]

How can we verify an Odoo certified consultant?

Check the prospective firm on Odoo’s official Find Resellers portal, then ask for the names and current certification details of the people assigned to your implementation. Check again on publication or contract-signing day because directory information and tier status can change.

Does an Odoo subscription include support and maintenance?

Odoo subscription support is email-based and available Monday to Friday, 24 hours a day, in English, French, Spanish or Dutch. Implementation, expert services and custom-code maintenance are excluded, so partner support obligations must be defined in your contract.

What should a board include in an Odoo total-cost model?

Include subscription licences, Odoo.sh or self-hosting, implementation, integrations, localisation, data migration, training, travel, support and custom-code maintenance. Published subscription prices are only one part of the investment.

A partner should be able to show who will deliver, what will be delivered, how support will be measured and what the full programme will cost. Request a Consultation with Serpa to assess your Odoo partner shortlist and ERP readiness.