State of Odoo implementations in Latin America 2026: what we learned from 390 service engagements
Short answer: across 5,969 support requests from companies that run Odoo, 31% were about invoicing, accounting and tax compliance, and 23% about access, environments, modules and upgrades. 82% of the production instances we manage already run Odoo 18 or 19, and the median support period of a service package is 8 months. These are aggregated, anonymized figures from 390 service engagements for 208 companies in 20 countries, between December 2019 and November 2026.
Published on 21 November 2026 by Ganemo, an Odoo partner. Data as of 21 November 2026.
Key figures
390
service engagements
Implementation, support and upgrade packages for 208 companies in 20 countries, from December 2019 to November 2026.
5,969
support requests analyzed
Customer tickets logged in our help desk between January 2020 and November 2026.
31%
of tickets: invoicing, accounting and tax
35% in Peru and 14% in other countries. Topic classification based on the ticket title.
82%
of instances on Odoo 18 or 19
Customer production instances managed by Ganemo: 43% on 18, 39% on 19 and 18% on 17 or older.
1,421
Odoo Enterprise users managed
According to the odoo.com partner dashboard, November 2026.
8 months
median support period
Between the first and the last hour recorded in each service package. Half fall between 4 and 12 months.
Finding 1: almost a third of support is invoicing, accounting and tax
We classified the 5,969 support requests by topic. The largest group is invoicing, accounting and tax compliance: 31% of the total. In Peru it reaches 35%, because there we support the full localization (e-invoicing, electronic books, SIRE, withholding schemes and payroll); in other countries it is 14%.
Support requests by topic (%)
Base: 5,969 customer support requests, January 2020 to November 2026. Percentages are rounded.
How we read it
What generates the most requests is whatever changes with regulations and with the accounting close. That is why training is at the center of our method: key users learn the full invoicing and closing flow before go-live, and the agreements on how each transaction is recorded are put in writing. A team that masters those flows asks fewer questions and, when it does, can describe the case.
Finding 2: one in four tickets is about the platform
23% of requests deal with access, test databases, module installation, servers and version upgrades. Outside Peru the share is higher (37%, versus 23% in Peru), which is consistent with the fact that outside Peru we work on Odoo's official localization and our support focuses more on running Odoo technically.
Topic groups: Peru versus other countries (%)
Base: 3,814 requests from companies in Peru and 859 from companies in other countries with a recorded country.
How we read it
The technical side weighs as much as the functional one. Always working first in a test database, with a copy of production, keeps a configuration change or a new module from disrupting operations. It is also the rule under which the customer's own AI agent, Claude Code or ChatGPT Codex, works in Odoo: with its keys managed in Secrevo, first on the test database and with a person reviewing. We explain it in how we implement Odoo with AI.
Finding 3: 82% of instances already run Odoo 18 or 19
We reviewed the customer production instances we manage as of 21 November 2026. 43% run Odoo 18 and 39% run Odoo 19. 18% remain on Odoo 17 or an older version. 60% run on the cloud managed by Ganemo and the rest on Odoo.sh or other platforms.
Production instances by Odoo version (%)
Base: over 100 customer production instances, excluding test databases, demos and upgrade copies.
How we read it
Staying on a recent version is feasible when the implementation started with the standard. Every custom development has to be adapted at each migration, and that is what delays an upgrade the most. That is why we prefer to configure what Odoo already offers before writing code, and, in our process, the upgrade goes through a test copy that the customer's team validates before cut-over.
Finding 4: the core is invoicing, accounting and inventory
Among customers with active maintenance by functional area, e-invoicing is the most contracted area (86%), followed by accounting and electronic books (78% each) and by inventory and logistics (69%). The median is 4 areas per customer.
Customers with each area in their active maintenance (%)
Base: over 60 customers with active maintenance that includes at least one functional area; most are in Peru. A customer can have several areas, so percentages add up to more than 100.
How we read it
Companies start with what they cannot stop doing: invoicing, meeting tax authority requirements and keeping accounting and inventory. We recommend that order: first the standard core, well used, and then the other apps, once the team masters the previous ones. If your company is in Peru, the Peruvian localization of Odoo covers that core.
Finding 5: support lasts months, not weeks
In the 362 service packages with recorded hours, the median between the first and the last hour is 250 days, about 8 months. Half of the packages fall between 4 and 12 months. Packages per year show sustained demand since 2022.
Service engagements by start year
2019 and 2020 are grouped because 2019 has fewer than 5 engagements.
How we read it
The implementation does not end at go-live. Teams use the support over the months: the first month-end close, the first tax filing, a new user, a process that grows. In our method the customer leads and uses the hours when needed, and the goal of every session is for their team to learn to solve it on their own. We do not sell certificates, we deliver results.
Finding 6: 208 companies in 20 countries
Peru accounts for half of the companies with service engagements and two thirds of active customers. Mexico and Chile are the next markets. We serve companies worldwide and have a presence in Peru, Paraguay, Chile, Mexico, the US, Ecuador, Colombia, Argentina, Spain, Nicaragua and the Dominican Republic. Is your country not on the list? Your company can be the first.
Companies with service engagements by country (%), base 208
Active customers by country (%)
Active customers: companies with a current subscription or an active production instance as of 21 November 2026 (over 100). Country as recorded on the company record in our Odoo.
For companies outside Peru we work on Odoo's official localization for each country; we explain it in how we work in Latin America.
What this data cannot measure: rescues
Part of our work is rescuing Odoo implementations that did not work with another provider. We would have liked to say how many of these engagements were rescues, but our sales records did not flag it systematically: the tags "partner change" and "already uses Odoo" appear in fewer than 5 opportunities. We prefer not to give a figure we cannot back up.
In our experience, rescues usually reveal the same things the findings above point to: users without training in tax workflows, custom developments that block upgrades and changes made directly in production. If that is your case, see how we approach an Odoo implementation rescue.
Methodology
Source. Ganemo's production Odoo, where we record our customers' engagements, support, instances and subscriptions. Read-only extraction on 21 November 2026.
- Service engagements (390): projects with an assigned customer whose name corresponds to an implementation, support, upgrade or consulting package, from December 2019 to November 2026. Internal projects, templates, test projects and development-credit projects are excluded.
- Support period: days between the first and the last hour recorded in each project's timesheet; only projects with more than half an hour recorded.
- Support requests (5,969): tasks in the help desk project, from January 2020 to November 2026, excluding meeting recordings and requests from Ganemo group companies. The topic is assigned with keyword rules on the title, in a fixed order; 18% remain unclassified because the title does not allow it.
- Versions: active customer production instances in our instance registry, excluding test databases, demos, upgrade copies and internal instances.
- Areas: customers with a current maintenance subscription that includes at least one functional area (e-invoicing, accounting, electronic books, logistics, payroll, point of sale, website, manufacturing or messaging).
- Country: the one on the customer's company record. If a company has no country recorded, it appears as "country not recorded".
- Enterprise users: the figure of 1,421 comes from the odoo.com partner dashboard in November 2026, not from our database.
Anonymization. We only publish aggregates. No group has fewer than 5 cases: countries or years with fewer cases are grouped. We do not publish customer names or billing data. The figures describe our portfolio, not the whole Odoo market.
Limitations. The way packages were named changed between 2021 and 2022, so we do not split implementation from support. Topic classification depends on how the customer titled the request. Rescues cannot be measured with this data.
How to cite this report
You may quote and reproduce the figures with attribution to Ganemo and a link to this page. Recommended format:
Ganemo (2026). State of Odoo implementations in Latin America 2026: what we learned from 390 service engagements. GANEMO GLOBAL S.A.C. Published 21 November 2026. https://www.ganemo.com/en/informe-implementaciones-odoo-latam-2026
For press inquiries or questions about the data, message us on WhatsApp at +1 (828) 672 6150.
Frequently asked questions
In our data, the largest group of support requests (31%) concerns invoicing, accounting and tax compliance, such as e-invoicing, electronic books, journal entries and reconciliations. Next come platform requests (23%): access, test databases, modules and upgrades. Operations (inventory, sales, point of sale, purchasing and manufacturing) add up to 18%.
Of the customer production instances we manage, 43% run Odoo 18, 39% run Odoo 19 and 18% run Odoo 17 or an older version. It is a snapshot of our portfolio as of 21 November 2026, not of the whole market.
In our service packages, the median time between the first and the last recorded hour is 8 months (250 days). Half of the packages fall between 4 and 12 months. It measures how long the customer uses the support, not the time to go-live.
Among customers with active maintenance by area, e-invoicing appears in 86%, accounting and electronic books in 78% each, inventory and logistics in 69%, payroll in 35% and point of sale in 29%. The median is 4 areas per customer. Most of these customers are in Peru.
We do not know reliably, so we do not give a figure. Our sales records did not systematically flag whether a customer came from another partner or with a previous implementation: those tags appear in fewer than 5 opportunities.
Yes. You may quote and reproduce the figures with attribution to Ganemo and a link to this page. The recommended citation format is below.
Want to know how your implementation compares with this data?
In a diagnostic session we review your Odoo, your version and your processes, and tell you in writing what to fix first.