The verdict, up front. There’s no single “Odoo CPQ” module to buy. Odoo’s Sales app already includes all three pieces the acronym stands for — a product configurator, rule-based pricing, and a quotation flow — without buying anything extra. You need a dedicated CPQ add-on if your sales team quotes complex products through a multi-step approval process, with pricing that depends on more than a pricelist rule can express. Odoo’s native tools are enough if customers or reps pick options, the price follows automatically, and no one needs a sign-off step before a quote goes out. Skip the CPQ conversation entirely if you sell simple, unconfigurable products — there’s nothing here to configure, price, or quote.
This closes out a three-part series built around one client’s actual Odoo ecommerce implementation: the product configurator that let customers build a compatible gate kit, and the phantom bill-of-materials structure underneath it that tracked what those kits actually contained. This piece covers the third leg: pricing those configured kits, and whether that requires “CPQ software” as its own purchase.
Key takeaways
- “Odoo CPQ” isn’t a built-in module. What people mean by it is a combination of three things Odoo’s Sales app already includes — a product configurator, pricelist rules, and the quotation flow — sometimes packaged into a paid add-on that layers a formal approval step on top.
- This client’s build used only the native configurator and standard pricelists. No CPQ add-on, no quote-approval workflow. Their catalogue didn’t need one.
- The dividing line isn’t complexity of the product — it’s complexity of the sale. A configurator plus pricing rules handles complex products. Dedicated CPQ software earns its cost when the sales process around the quote gets complex: approvals, multi-currency quote documents, reps who need guardrails.
- A market of paid Odoo CPQ apps exists specifically for the businesses that do need that layer — it’s a real and reasonable purchase for the right sales process, not a sign that Odoo is missing something.
- CPQ tooling isn’t priced separately in an implementation — it’s scoped the same way configurator and BOM work is, inside the standard range.
What “Odoo CPQ” actually refers to
CPQ stands for configure, price, quote. Search for “Odoo CPQ” and you’ll find several paid marketplace apps using that exact name, plus a steady stream of agency blog posts explaining what CPQ means in an Odoo context. What you won’t find is a module called CPQ inside standard Odoo. There isn’t one.
What Odoo ships natively, across the Sales app, is the three pieces the acronym stands for, unbundled: a product configurator for letting a customer or rep select compatible options (the subject of our first piece in this series), pricing through pricelist rules that can vary by customer, quantity, or option selected, and a standard quotation document and approval flow through Sales Orders. For a large share of businesses, running those three natively, connected but not formally packaged as “CPQ,” is functionally the same outcome a dedicated CPQ app sells as a single branded product.
The paid CPQ apps on Odoo’s marketplace exist because some businesses need more than that: a distinct quote-approval workflow with sign-off stages, guided selling scripts for reps handling unfamiliar product lines, or quote documents with layouts and logic too specific for a standard pricelist. That’s a real, legitimate need — it’s just a different problem than most ecommerce catalogues actually have.
What this client’s build actually used
Our client’s gate and access-control kits are genuinely complex to configure — that’s the whole reason the configurator existed. But once a customer had selected a valid combination, pricing it was not a hard problem. Standard Odoo pricelists calculated the total from the selected options, the same way they would for any product with priced variants. There was no separate approval step, no sales rep sign-off, no quote document requiring custom logic beyond what Odoo’s standard Sales Order template already produces.
That is worth stating plainly rather than dressing up: this client did not need CPQ software, and we didn’t build or install any. The complexity in this build lived entirely in the configurator and the underlying phantom BOM structure, not in the sale itself. A customer configuring a gate kit online never needed a human to review and approve the price before checkout — the price was deterministic the moment the configuration was valid.
That’s not a limitation of the platform. It’s what it looks like when a business’s actual sales process is simpler than the acronym implies.
When native configurator-plus-pricing is enough, and when it isn’t
The dividing line has nothing to do with how complicated the product is. A gate kit with dozens of compatible option combinations is genuinely complex, and standard Odoo handled it. The dividing line is whether the sale requires more than “select options, see price.”
| What’s actually happening | What you need |
|---|---|
| Price follows automatically from selected options, no human review | Native configurator + pricelist rules — no CPQ add-on |
| Reps need a guided script to configure products they don’t know well | A CPQ app, or a more built-out configurator with validation rules |
| Quotes above a threshold need a manager’s sign-off before sending | A CPQ app with approval workflows, or a custom Sales Order automation |
| Pricing depends on negotiated, deal-specific terms rather than rules | A CPQ app built for negotiated enterprise sales |
| You sell a fixed catalogue with no configuration at all | Neither — there’s nothing to configure or quote |
Most ecommerce catalogues, even genuinely complex ones like this client’s, land in the first row. Approval workflows and negotiated pricing are B2B sales-team problems more than they are ecommerce catalogue problems — which is also why the general “CPQ software” market is priced and marketed toward enterprise sales teams rather than online storefronts.
What this adds to implementation cost
Same answer as the rest of this series: it isn’t a separate line item. It’s scoped inside the same $5,000 to $50,000 (USD) range that covers an Odoo ecommerce implementation, and in this client’s case it added close to nothing beyond the configurator and pricelist work already accounted for — because no CPQ add-on was purchased or built.
Where the number moves: if your sales process genuinely needs an approval workflow or a paid CPQ app, that’s additional configuration (and sometimes license cost for the add-on itself) on top of the configurator and BOM work. It’s worth scoping that honestly rather than assuming “CPQ” is a checkbox every configurable-product business needs to tick.
When this isn’t the right answer
If your sales process already runs through a dedicated CPQ platform you’re happy with, integrating it with Odoo rather than replacing it is often the lower-risk move — several of the marketplace apps referenced above exist specifically for that integration. And if you don’t sell configurable products at all, none of this series applies: a single fixed-price SKU doesn’t need a configurator, a BOM, or a pricing conversation more complex than a price tag.
Frequently asked questions
Does Odoo have CPQ?
Not as a single named module. Odoo’s Sales app natively includes the three components the acronym stands for: a product configurator, pricelist-based pricing, and a standard quotation flow. Several paid third-party apps on Odoo’s marketplace package additional CPQ-specific functionality, like formal approval workflows, on top of that base.
What is CPQ in Odoo?
In practice, “CPQ in Odoo” usually means one of two things: the native combination of Odoo’s product configurator, pricelists, and Sales Order quotations, or a paid add-on app that adds a dedicated approval workflow and guided-selling layer on top of that native base. Which one you need depends on your sales process, not your product’s complexity.
Did this client’s implementation use a CPQ app?
No. Their kits were priced using standard Odoo pricelist rules tied to the configurator, with no separate approval step or CPQ add-on. Their sales process didn’t require one, pricing was deterministic once a configuration was valid.
When do I actually need dedicated CPQ software?
When your sales process, not your product, is complex: quotes that need manager approval before they go out, reps who need a guided script for unfamiliar product lines, or pricing that depends on negotiated terms a pricelist rule can’t express. If price follows automatically from selected options with no review step, native Odoo is typically enough.
How much does CPQ software add to an Odoo implementation?
If you don’t need a dedicated CPQ add-on, close to nothing beyond configurator and pricing work already scoped into the standard $5,000-$50,000 (USD) implementation range. If your sales process does need one, add the app’s own licensing plus the configuration to connect its approval workflow to your Sales Orders.
Is a product configurator the same thing as CPQ?
No, though they overlap. A configurator handles the “configure” step, letting a customer or rep pick valid options. CPQ, as a category, adds pricing rules and a formal quote process around it, sometimes with approval workflows. You can have a configurator without full CPQ, which is exactly what this client’s build was.
Thinking through your own sales process?
Whether you need a dedicated CPQ app or just Odoo’s native configurator and pricing depends on how quotes actually move through your sales process today — not on whether your products are complex to configure.
Talk to us about your Odoo ecommerce build →
About the author
Nguyen Tran is the founder of Ministers.io. He has spent five years working on Odoo ERP implementations — five delivered directly and more than twenty advised on — across ecommerce, retail, manufacturing, and maintenance, repair and operations (MRO).
