Case Studies

A 150+ Merchant Payments Platform on Odoo

Merchants 150+
Odoo 13 Community
Ongoing 6+ years
Product insight iPos

Insight Technologies SAS is a digital payment provider in the Republic of Congo, and our oldest and longest-running client: we have built and supported their product, insight iPos, for around six years, and the work is ongoing. It is the deepest test of Odoo as a product that we know.

We built and operate the multi-tenant platform behind insight iPos on Odoo 13 Community, serving more than 150 merchants from one standardised, heavily customised system. Karan told this story on stage at Odoo Experience 2023: Unleashing Business Growth, a digital payment provider’s success story from the Republic of Congo.

What this looks like in practice

  • Six years, and counting. insight iPos is our longest relationship: roughly six years of building, customising and supporting the platform for Insight Technologies SAS, still ongoing. That depth is only earned by staying with a system through everything real operation throws at it.
  • 150+ merchants on one platform. More than 150 merchants served from one standardised multi-tenant platform, the point at which every manual process you didn’t automate becomes a daily tax and every shortcut becomes a fleet-wide fault.
  • Built on Odoo 13 Community. The platform runs on Odoo 13 Community extended with a large body of custom development, which is proof that the free edition plus serious engineering can carry a live, revenue-bearing product at scale.
  • Isolation and provisioning. Tenant isolation and automated provisioning, so merchants are independent and onboarding doesn’t depend on manual setup, because at 150-plus tenants manual is neither fast enough nor reliable enough. See multi-tenant deployment.
  • Public proof, on stage. The story was presented at Odoo Experience 2023, a digital payment provider’s growth built on this platform. It’s public proof, not a private claim.

What this means for your build

  1. Depth you can draw on. These systems exist because we went deep on hard problems, and that experience is what you’re buying, not a slide deck of logos.
  2. Engineering, not reselling. The value is the judgement to avoid expensive wrong turns, which only comes from having built the difficult version before.
  3. Scoped to your reality. We’d map your specific problem and scope it with an hours breakdown, rather than assume your situation matches the reference.
  4. Built to survive upgrades. Work built with the framework rather than against it, so it ports across Odoo versions rather than breaking, as the WIP work across v15 to v19 shows.
  5. One accountable partner. Senior oversight from our UK base, with delivery supported by our India team, on the hook for the outcome.

Common questions

What does 150-plus merchants teach that 10 doesn't?
That automation and isolation aren't optional: at fleet scale every manual gap compounds into a daily tax or an outage. Six years at this scale is where that discipline was learned. See the multi-tenant guide.
Odoo 13 Community for a payment platform, really?
Yes, and the platform is the evidence: Community plus substantial custom development has carried a live, multi-merchant payments product for years. The edition was never the limit; the engineering is.
Could we build a platform like this?
If you're turning a solution into a product (SaaS, franchise or merchant platform), the pattern transfers. We'd scope the isolation model and provisioning first, as the guide describes.

Not sure where to start? Book a free discovery call and we’ll map your current setup, or request a free Odoo health check if you’re already running Odoo.

Next step

Ready to fix your ops?

Book a free discovery call. We'll look at your current setup and tell you honestly whether Odoo is the right move and what it would involve.

Book a Discovery Call Get a Free Odoo Health Check