CODEerts
Case study: Insurance
Quoting rules that non-technical staff can change
An insurance brokerage running across two markets quoted out of spreadsheets, where every rate change was a developer request. We built the platform and handed the rating rules back to the business.
Industry
Insurance and brokerage
Region
United States and the Caribbean
Odoo
Version 17 on Odoo.sh
Scope
Platform build, quoting engine, portal
The challenge
What was not working.
Quoting ran on legacy spreadsheets with rating rules buried in formulas that only technical staff could safely touch. Every product or rate adjustment became a development ticket. There was no unified system across the two territories, no customer self-service, and no reliable record of how a given quote had been produced.
What we built
The work, in detail.
One platform across both territories
We migrated the legacy spreadsheet workflows into a single digital system covering both operating regions, so quotes, policies and customers live in one place.
A dynamic formula engine
The core of the build. Non-technical staff author and manage quoting rules themselves through a formula engine, which turned rating logic from code into configuration.
Public website and customer portal
We delivered the marketing site, a self-service customer portal and the core backend modules as one solution, rather than a backend-only implementation.
The result
What changed.
Quoting moved off spreadsheets into a governed system
Rate and product changes no longer require a developer
Both regions operate on one platform
Customers self-serve through the portal
Stack
What it runs on.
- Odoo 17 on Odoo.sh
- Custom quoting and formula engine
- Website
- Customer portal
- Multi-region
Modules behind this
Productised from real work.
Work from engagements like this one becomes a published module, so the next client installs it instead of paying to build it again.
Questions
About work like this.
Can Odoo handle insurance quoting?
Odoo has no insurance rating engine out of the box, so this is a custom build on top of it. What Odoo gives you is the surrounding platform, meaning customers, documents, accounting and portal, which is most of the work.
Why let business users edit rating rules?
Because otherwise every rate change queues behind a developer. A formula engine with validation lets the people who own the product change the numbers, while the structure stays under control.
Can one Odoo instance serve two countries?
Yes. Multi-company handles separate books, currencies and compliance per territory while keeping one customer and product view across the group.
More work
Other things we have shipped.
Every engagement below was delivered by the same certified Odoo team.
From overselling to zero stock conflicts
Multi-company Odoo behind several WooCommerce storefronts, with shipping, tax and card payments automated end to end.
Read the case study Finance & AccountingReplacing the settlement spreadsheet
Vendor invoices parsed straight out of email, and multi-tier franchise payouts calculated inside Odoo instead of Excel.
Read the case study RetailOne stock position across every branch
Central warehouse, live branch stock, cross-store pickup, POS and compliant e-invoicing in one connected system.
Read the case studyReady to make Odoo work the way your business does?
Book a free call
CODEerts
CODEerts is a team of certified Odoo experts and full-stack engineers. We implement, customise and support Odoo ERP, then build the software around it.
