Home / Case Studies / Puma Energy

/ Case Study · Fuel & Retail

A Multi-Country Retail Network on Odoo 18.
One Platform, Every Site.

/ The engagement

One ERP and POS Across 12 Countries.

A multi-country, multi-entity Odoo 18 ERP and POS platform for Puma Energy's CODO and COCO convenience-store network, built on a legal entity → dealer → site rollout model with country-specific fiscal localization in every market.

Dealer Rollout AppSite-Aware POSMulti-Entity AccountingFiscal Localization
87.5%Faster dealer and branch onboarding
~95%POS uptime through network outages
700+Sites targeted across the network
12Countries on one standardized core

/ About the client

Puma EnergyPuma Energy

Puma Energy is a global energy company operating fuel stations and their attached CODO (Company Owned, Dealer Operated) and COCO (Company Owned, Company Operated) convenience stores. Its C-Store network spans 12 African countries: Congo, Namibia, Botswana, South Africa, Eswatini, Ghana, Lesotho, Mozambique, Malawi, Tanzania, Zambia, and Zimbabwe.

Puma partnered with Brainvire to standardize operations across that network. We delivered a multi-country, multi-entity Odoo 18 ERP and POS platform built around a legal entity → dealer → site rollout hierarchy, enabling standardized configuration with country-specific fiscal localization, site-level data isolation, and group-wide financial consolidation.

/ The approach

Design, architecture, and features, shipped as one program.

/01Automation

Guided dealer rollout

We turned manual dealer and branch onboarding into a single guided form with automated backend configuration of users, approvals, accounting, and taxes.

/02Governance

Scoped by site and entity

A seven-role security matrix with custom record rules and 2FA enforces strict site- and entity-level data segregation across a single Odoo instance.

/03Resilience

POS that survives outages

Odoo POS handles orders offline and auto-resyncs to the central database once connectivity returns, so C-Stores keep selling with zero data loss.

/04Standardization

Localized on a common core

Country-specific fiscal localization layers onto a standardized, mergeable group Chart of Accounts, with dual go-live tracks for fast, consistent rollouts.

/ What stood in the way

Four problems between Puma and one standard playbook.

Select a challenge to see how it shaped the build.

/01 Manual dealer onboarding
/02 Data segregation across sites
/03 POS reliability during outages
/04 Fragmented fiscal compliance

Manual dealer onboarding

Onboarding a new dealer or branch meant many manual, error-prone steps across accounting, purchase, and user setup. We engineered a custom Dealer Rollout app: a single guided form provisions scoped user accounts, sets PO approval thresholds, and configures localized accounting, payment methods, and taxes automatically.

Data segregation across sites

With many sites, dealers, and legal entities sharing one Odoo instance, Puma needed strict isolation so dealers and site managers couldn't view cross-site metrics. A seven-role security matrix reinforced with 2FA, layering native groups with custom record rules, scopes POs, receipts, valuations, and financial reports to each user's assigned site and branch.

POS reliability during outages

C-Store locations needed a dependable POS even during network outages, with no lost sales. We configured Odoo POS with native offline order handling: transactions continue uninterrupted, are auto-tagged with an "Offline" ribbon and unique ID, and resynchronize to the central database with zero data loss once the connection returns.

Fragmented fiscal compliance

Each of the 12 countries needed different tax-authority rules (e.g., ZIMRA in Zimbabwe, MRA in Malawi) without fragmenting the group Chart of Accounts. We designed a legal entity → dealer → site architecture that layers country-specific fiscal localization onto a standardized, mergeable Chart of Accounts, with "Fast Launch" and "Full MVP Launch" tracks.

/ Product screens

The delivered experience.

The Odoo interface Puma's teams actually use.

Puma Energy Odoo interface, Site-Aware POS/01Site-Aware POS
Puma Energy Odoo interface, Loyalty & eWallet/02Loyalty & eWallet
Puma Energy Odoo interface, Split-Tender Payments/03Split-Tender Payments
Puma Energy Odoo interface, Fuel Sale Capture/04Fuel Sale Capture
Puma Energy Odoo interface, POS Product Catalog/05POS Product Catalog
Puma Energy Odoo interface, Fuel Details Entry/06Fuel Details Entry
Puma Energy Odoo interface, Loyalty Redemption/07Loyalty Redemption
Puma Energy Odoo interface, Multi-Method Checkout/08Multi-Method Checkout
Puma Energy Odoo interface, Payment Confirmation/09Payment Confirmation

/ The results

What changed, in numbers.

87.5% Faster onboarding Onboarding a new dealer or branch dropped from roughly two hours to about fifteen minutes.
~95% POS uptime Around 95% POS uptime maintained during network outages, with no lost sales.
700+ Sites targeted A target of 700+ sites live across 12 countries, being achieved on a rolling basis with client support.
Fewer Configuration errors Faster, more consistent go-lives across all 12 countries with fewer configuration errors.

/ Next step

Ready to standardize your multi-country retail operations?

Partner with Brainvire for Odoo implementation that unifies dealer onboarding, POS, and ERP across your legal-entity, dealer, and site network. A thirty-minute working session, no sales deck.

Book a Working Session →