Yes, Odoo can handle custom prices and configurable products, and it can go a lot further than most people expect. The question is where standard variants stop being enough and a real configurator starts earning its keep. This guide draws that line.
Where standard Odoo is enough
Odoo handles product variants and price lists in the standard product. If your catalogue has a manageable set of options, sizes, colours, a few add-ons, and pricing follows clear rules, you don’t need anything custom. Set up the variants and the price lists and you’re done. Per-customer and quantity-based pricing are standard too, so a lot of “we have complicated pricing” turns out to be configuration, not custom code.
The signs you need a real configurator
You’ve outgrown standard variants when:
- Options interact, picking A rules out B, or makes C mandatory.
- The number of valid combinations is too large to list as variants.
- Pricing depends on the configuration, not a fixed list.
- Quotes need engineering input, so they take days and tie up scarce people.
- The price book lives in spreadsheets and one expert’s memory.
If two or more of those are true, you’re paying for slow, error-prone quoting whether you see it on an invoice or not.
What a CPQ configurator actually does
CPQ stands for Configure, Price, Quote. Step by step:
- Configure - the user picks options through a decision tree; invalid combinations are blocked at the point of selection, so a quote can’t be wrong by construction.
- Price - pricing updates inline as options are chosen, with discount tiers and margin floors per product family, and an approval step for anything below margin.
- Quote - a PDF offer is generated with a visual summary, and the same choices output a bill of materials and engineering notes for production.
We built exactly this as the Updoo Configurator for a manufacturer of custom industrial equipment that had 40+ option dimensions and a price book spread across three spreadsheets and one engineer’s head. Quotes used to take a week, often arriving after the prospect had moved on.
The outcome: 85% less time per quote, an 18% higher quote-to-order rate, and zero pricing errors in six months. Under the hood it’s Odoo Studio plus a custom Python rules engine, an OWL component for the configurator interface, and QWeb templates for the PDF.
The same idea, facing the customer
A configurator doesn’t have to be an internal sales tool. The same logic can sit on your webshop so the customer clicks together a made-to-order product and sees the right price on the spot. We built that for Odoo eCommerce, and it runs at cpqbuilder.com for less than a tenth of what a comparable third-party platform had cost a client the year before. That drop in cost is the whole story of why custom software became affordable. More on how it works and how it compares to other options: the Odoo product configurator and Odoo CPQ options compared.
The honest line
Don’t build a rules engine you don’t need. Standard variants for simple catalogues; a configurator when the combinations and pricing rules have outgrown what anyone can track by hand. The test is whether your quotes are slow and occasionally wrong, that’s the pain a configurator removes, not the existence of options as such.
Want a sense of the investment? See what Odoo customisation costs, or start a free Odoo scan.