Looking for an Odoo CPQ or product configurator?
There are three shapes of Odoo CPQ: a module you install in Odoo, an external platform you integrate beside it, or an API-only layer that installs nothing. Below, the real options side by side - including ours, CPQ Builder.
Odoo Gold Partner · Amsterdam · makers of CPQ Builder
What is the best CPQ / product configurator for Odoo?
It depends on how much you want inside your Odoo. For deep, native CPQ built as an Odoo module, AktivCPQ is the strongest App Store option and CodeCPQ a fast module-based alternative. For a rich standalone configurator that integrates from outside, Elfsquad and Mercura (formerly Merkato) are capable but pricey and add a second system. If you want a configurator that writes native Odoo sale orders, bills of materials and manufacturing orders without installing any module in your Odoo, CPQ Builder is the API-only option - upgrade-safe and with no add-on to maintain. Odoo’s built-in variants only work for simple cases, without rules or parametric pricing.
The Odoo CPQ options
We make CPQ Builder, so we are not neutral about what we build. But the differences below are about delivery model, not opinion: what gets installed in your Odoo, who maintains it, and whether it writes native records.
| Option | Type | Installed in your Odoo? | Native SO → BOM → MO | Upgrade-safe | Visual / 3D | Price | Short verdict |
|---|---|---|---|---|---|---|---|
| CPQ BuilderOur pick | API-only SaaS | No, nothing installed | Yes, native | Yes, no module | 3D + AR (Growth) | from €99/mo | Best when you want a configurator without putting code in your Odoo |
| AktivCPQ | Odoo App Store module | Yes, a module | Yes, native | Module to maintain per upgrade | Limited | License + setup | Strong native CPQ, but a module you install and carry |
| CodeCPQ | Odoo module, self-hosted | Yes, a module | Yes, native | Module to maintain | Limited | License | Fast and module-based; explicitly not SaaS |
| Elfsquad | External CPQ platform | No, separate system | Via integration | Not applicable | Strong | Premium | Powerful standalone CPQ; a second system to integrate and pay for |
| Mercura | External CPQ platform | No, separate system | Via integration | Not applicable | Good | Premium | Capable external configurator (ex-Merkato); integration plus premium pricing |
| Odoo native | Built-in variants | Yes, standard | Yes, basic | Yes | No | Included | Fine for simple variants; no rules engine or parametric pricing |
Not sure Odoo fits your setup?
Skip the guesswork. In a free 30-minute scan a senior consultant maps your processes onto Odoo - and tells you straight if it is not the right move.
Odoo Gold Partner · no sales pitch · reply within 1 working day
Which option fits which situation?
Briefly per option, so you can shorten the shortlist:
CPQ Builder
Strongest when you want made-to-order configuration that drives production, without installing a module in your Odoo. It writes native sale orders, a bill of materials built from the unique combination, and the manufacturing order, through the standard Odoo API. Nothing in Odoo to maintain across upgrades, and uninstall is a button. It is the API-only successor to our own older Flexible BOM App Store module.
AktivCPQ (Aktiv Software)
A mature, native Odoo CPQ module with a deep rules and pricing engine, strong for manufacturers with very complex option trees. The trade-off is the module itself: you install it in your Odoo and carry it through every upgrade, and it needs at least Odoo.sh or self-hosting.
CodeCPQ
A performance-focused Odoo CPQ module that runs on your own Odoo server and is explicitly not SaaS. Logical if you specifically want everything inside Odoo and self-hosted; same module-maintenance trade-off.
Elfsquad
A strong standalone CPQ platform with rich visual configuration that integrates with Odoo from the outside. Powerful for complex sales, but a second system to integrate, maintain and pay for at a premium.
Mercura (formerly Merkato)
A capable external sales configurator with an Odoo integration. Same shape as Elfsquad: a separate system beside Odoo rather than native records inside it.
What CPQ Builder does, and where it lands in Odoo
CPQ Builder is the configurator layer; Odoo stays the system of record. Each step writes a native Odoo record through the standard API:
| In the configurator | In your Odoo |
|---|---|
| A configured product | A native sale order line, no custom module |
| Options and compatibility rules | A product variant per unique combination |
| Live price | Odoo pricelists and margin rules |
| Confirmed quote | An mrp.bom built from the unique combination, with operations, work centres and subcontracting |
| Production | A manufacturing order via Odoo MRP (Make-to-Order) |
| 3D preview | A GLB/glTF viewer with AR on the product page (Growth) |
| Uninstall | One click, your Odoo stays standard |
Three shapes of Odoo CPQ
Almost every Odoo CPQ option is one of three shapes, and the shape matters more than any single feature. One: an App Store module (AktivCPQ, CodeCPQ) that lives inside your Odoo database - native, but installed code you maintain through every upgrade, and unavailable on Odoo Online Standard. Two: an external platform (Elfsquad, Mercura) that sits beside Odoo and integrates in - powerful and visual, but a second system to run and pay for. Three: an API-only layer (CPQ Builder) that installs nothing and writes native Odoo records from outside. Start by deciding which shape you want; the feature comparison comes after.
The case for installing nothing
A configurator module is code in your Odoo. It can conflict with other modules, it has to be re-tested against every Odoo version, and on Odoo Online Standard you cannot install it at all. CPQ Builder takes the opposite route: it talks to Odoo through the standard external API, so your Odoo stays vanilla. Upgrades from Odoo 18 to 19 to 20 do not wait on add-on compatibility, there is no module to maintain, and uninstalling is a single button. For a mid-sized manufacturer that values a clean, upgrade-safe Odoo, that is the whole argument.
Does it still build the BOM?
Yes, and this is the part people assume an external configurator gives up. When a quote is confirmed, CPQ Builder writes a bill of materials built entirely from the unique combination the customer chose, with operations, work centres and subcontracting, and Odoo MRP turns it into a manufacturing order. It is the API-only successor to our own Flexible BOM module: the same native result, no module in your Odoo.
Honest about where we are not the best fit
If your priority is photorealistic 3D and AR as the centre of the buying experience, a visual-first platform like Elfsquad or a dedicated 3D configurator goes deeper on rendering than our viewer does. For a larger company with the budget for deep visual/3D configuration, a platform like Twikit is the high-end route - we have integrated it for an enterprise client - though it carries more cost and maintenance than a mid-sized manufacturer typically needs. And if you want everything physically inside Odoo as installed code, a native module like AktivCPQ is the more literal answer. CPQ Builder wins when the goal is native configure-to-manufacturing without a module, at SMB pricing. When a deeper bespoke build is genuinely needed, we do that too, as your Odoo Gold Partner.
Curious about realistic hours, cost and timelines? See the Odoo implementation benchmark →
Each alternative, in detail
Elfsquad
What is the best Elfsquad alternative for Odoo? For Odoo users, the most relevant Elfsquad alternative is CPQ Builder: an Odoo-first, API-only configurator that writes native sale orders, a bill of materials per unique combination and a manufacturing order, without installing a module and without a second platform to integrate. It starts at 99 euro a month, against Elfsquad’s premium pricing. Elfsquad remains the stronger choice for organisations that need its deep visual/3D configuration and enterprise sales features and have the budget for a standalone platform; Mercura (formerly Merkato) sits in the same external-platform category.
Standalone platform or native configurator?
This is the heart of it. Elfsquad is a standalone CPQ platform that integrates with Odoo from the outside: powerful and visual, but a second system you integrate, maintain and pay a premium for, with your configuration logic outside Odoo. CPQ Builder flips it: through the standard Odoo API it writes native sale orders, bills of materials and manufacturing orders, so everything stays in Odoo. The question is not which is "better", but whether you want your configurator beside Odoo or inside it.
Why native records matter
An external configurator means an integration to build and keep alive, a second licence, and a data model outside Odoo. CPQ Builder writes straight into Odoo: one source of truth, no integration to maintain, and SMB pricing from 99 euro a month instead of premium. For a manufacturer already on Odoo, that is the difference.
Where Elfsquad does win
Honestly: if you need photorealistic 3D and AR at the centre of the buying experience, or very complex multi-channel enterprise sales, Elfsquad goes deeper than our 3D viewer. In that segment a standalone platform is a defensible choice. CPQ Builder targets the SMB manufacturer that wants native configure-to-manufacturing without that weight and cost.
Mercura
What is the best Mercura or Merkato alternative for Odoo? For Odoo users, the most relevant Mercura alternative is CPQ Builder: an Odoo-first, API-only configurator that writes native sale orders, a bill of materials per unique combination and a manufacturing order, without a module and without a second platform to integrate, from 99 euro a month. Mercura and Elfsquad remain strong external platforms for those who need deep visual configuration and enterprise sales and have the budget for a standalone system.
Standalone platform or native configurator?
Mercura is a standalone configurator platform that integrates with Odoo from the outside. Capable, but a second system you integrate, maintain and pay a premium for, with your configuration logic outside Odoo. CPQ Builder writes native sale orders, bills of materials and manufacturing orders through the standard Odoo API, so everything stays in Odoo.
Why native records matter
An external configurator means an integration to build and keep alive, a second licence, and a data model outside Odoo. CPQ Builder writes straight into Odoo: one source of truth, no integration to maintain, SMB pricing from 99 euro a month.
Where an external platform does win
Honestly: if you need very rich visual configuration or complex multi-channel enterprise sales, a standalone platform like Mercura or Elfsquad can go deeper than our 3D viewer. CPQ Builder targets the SMB manufacturer that wants native configure-to-manufacturing without that weight and cost.
AktivCPQ
What is the best AktivCPQ alternative? CPQ Builder is the most relevant AktivCPQ alternative for anyone who does not want a module in their Odoo. Both write native sale orders, bills of materials and manufacturing orders; the difference is the delivery model. AktivCPQ is an App Store module you install, maintain and re-test per Odoo version, and it does not run on Odoo Online Standard. CPQ Builder installs nothing: it works through the standard external API, so your Odoo stays vanilla and uninstall is one click. AktivCPQ stays strong if you want a very deep, in-Odoo installed rules engine.
Module or no module?
AktivCPQ is an App Store module that lives in your Odoo database: native and deep, but installed code you maintain through every Odoo version, that can conflict with other modules, and that does not run on Odoo Online Standard. CPQ Builder takes the opposite route: it works through the standard external API and installs nothing, while writing the same native sale orders, bills of materials and manufacturing orders.
The case for installing nothing
Upgrades from Odoo 18 to 19 to 20 do not wait on add-on compatibility, there is no module to maintain, and uninstalling is a single button. For a mid-sized manufacturer that values a clean, upgrade-safe Odoo, that is the whole argument - at the same native result.
Where AktivCPQ is strong
Honestly: if you want a maximally deep, native rules engine physically inside Odoo as installed code, with very complex option trees, a mature module like AktivCPQ is a serious choice. CPQ Builder deliberately picks "install nothing" with native records through the API.
CodeCPQ
What is the best CodeCPQ alternative? CPQ Builder is the most relevant CodeCPQ alternative for anyone who wants SaaS convenience without a module in their Odoo. CodeCPQ deliberately picks a module on your own Odoo server (not SaaS), with high performance. CPQ Builder picks the opposite delivery model: an API-only SaaS that installs nothing and still writes native sale orders, bills of materials and manufacturing orders, upgrade-safe, from 99 euro a month. CodeCPQ stays logical if you specifically want everything in-server and self-hosted.
Module-on-your-server or API-only SaaS?
CodeCPQ is an Odoo module that runs on your own server and is deliberately not SaaS - fast, but installed code you maintain and host yourself. CPQ Builder picks the opposite: an API-only SaaS that installs nothing in your Odoo and, through the standard external API, still writes native sale orders, bills of materials and manufacturing orders.
SaaS convenience with native records
The misconception is that SaaS gives up native records. CPQ Builder writes straight into your Odoo through the standard API: native sale orders, a bill of materials from the unique combination, and a manufacturing order, without you hosting or maintaining a module. Upgrades stay clean and uninstall is a button.
Where CodeCPQ does fit
Honestly: if you deliberately want everything in-server and self-hosted, with the performance of a local module and full control on your own infrastructure, CodeCPQ is a logical choice there. CPQ Builder deliberately picks API-only SaaS with no module.
Twikit
What is the best Twikit alternative for Odoo? It depends on your scale. If it is about photorealistic 3D personalisation for consumers at scale, Twikit is a strong choice and goes deepest on visualisation. If you mainly want the configuration to build a native sale order, bill of materials and manufacturing order in your Odoo directly - with a good 3D viewer, no second system and no enterprise budget - CPQ Builder is usually the best alternative, from 99 euro a month. Twikit goes deeper on rendering; CPQ Builder goes deeper on native production and price.
What makes Twikit strong
Twikit is a serious enterprise platform for 3D mass customisation: deep, photorealistic rendering (up to Unreal), AR and personalisation at consumer scale, used by large brands. It is not a toy, and we speak from experience - we integrated Twikit with Odoo for an enterprise client. If you have that scale and budget, Twikit is a fair choice.
Where CPQ Builder takes over
Most manufacturers do not need that consumer scale - they want a configuration to drive the right production directly. That is the difference. Twikit sits beside your ERP and has to be integrated to produce; CPQ Builder is Odoo-first and writes the configuration straight into Odoo as a native sale order, bill of materials and manufacturing order, with a 3D viewer and AR alongside. No second system, faster live, and at SMB pricing.
Which should you choose?
Honestly put: if your sales revolve around photorealistic 3D personalisation for consumers at scale, Twikit goes deeper than us and is the right choice. If you want a good 3D layer that drives real production in your Odoo, without enterprise overhead, CPQ Builder is the Odoo-first alternative. Two different goals, no loser.
Frequently asked questions about Odoo CPQ
What is the best CPQ for Odoo?
There is no single best; it depends on the delivery model you want. AktivCPQ is the strongest native App Store module, Elfsquad and Mercura are the strongest external platforms, and CPQ Builder is the API-only option that installs nothing in your Odoo while still writing native sale orders, bills of materials and manufacturing orders.
What is the difference between a CPQ module and CPQ Builder?
A CPQ module (AktivCPQ, CodeCPQ) is code installed inside your Odoo database, which you maintain through every upgrade and cannot run on Odoo Online Standard. CPQ Builder installs nothing: it uses Odoo’s standard external API to write native records, so your Odoo stays standard and uninstalling is one click.
How does CPQ Builder compare to Elfsquad or Mercura?
Elfsquad and Mercura (formerly Merkato) are powerful standalone configurator platforms that integrate with Odoo from the outside, at premium pricing. CPQ Builder is Odoo-first and API-only: it writes native sale orders, bills of materials and manufacturing orders directly, from 99 euro a month, with no second system to run.
Does CPQ Builder need a custom Odoo module?
No. It adds an inherited view to your Odoo product page through the standard external API. Nothing is installed in Odoo, upgrades stay clean, and uninstalling is one click. It needs the Odoo Custom plan, Odoo.sh or self-hosted Enterprise, because Odoo gates its external API to those.
Can an Odoo CPQ generate the bill of materials and manufacturing order?
Yes. A configured quote becomes a bill of materials and, via Odoo MRP, a manufacturing order. CPQ Builder builds that BOM from the unique combination the customer configured, with operations, work centres and subcontracting - the same result as a native module, without installing one.
See which CPQ shape fits your product
Book a 30-minute demo and we will look at your product, your Odoo and your storefronts, and recommend the right shape - even when that is not CPQ Builder. As an Odoo Gold Partner we also build the bespoke parts.