Both Product Price by Formula Calculator and Website Price by Formula Calculator let you build price calculators from your own option fields and formulas, and both drive backend Sales and eCommerce simultaneously from a single rule engine. The difference is which context they lead with — and that turns out to matter less than most buyers expect.
The shared engine
Everything below is present in both products:
- Custom formulas with
+,-,*,/, parentheses and functions. - Unlimited option fields per rule: number, text, text area, select, radio, checkbox, multi-select — with images available on radio options.
- Conditional formula groups that switch the formula based on user input or on running results.
- Any unit of measurement: kilogram, metre, square metre, cubic yard and so on.
- Rounding control — round, round up, round down, with custom precision.
- Rules applied to multiple products or categories, with as many rules as your catalogue needs.
- A backend preview before exposing a calculator to customers.
- Selected options carried through to cart, checkout, order and the printed PDF.
Both depend on sale_management and website_sale, and both are maintained for Odoo 18.0 and 19.0.
Where they differ
The difference is one of emphasis. Product Price by Formula leads with the backend: the calculator dialog on quotation and order lines is the primary experience, with the eCommerce calculator alongside it. Website Price by Formula leads with the storefront: the live calculator on the product page is the primary experience, with the backend dialog alongside it.
Because both ship both contexts, the choice is about which documentation, defaults and product positioning match how you think about your pricing — not about which capabilities you get.
How to choose
- Your sales team quotes first, the website is secondary. Start with Product Price by Formula.
- Customers configure and buy online, quotes are the exception. Start with Website Price by Formula.
- Both matter equally. Either works. Pick on price and read both product pages.
You do not need both. They cover the same engine, and installing two calculators on one database creates ambiguity about which rule applies.
What actually determines success
Not the module — the formula design. Three things decide whether a calculator works in production:
- Field count. Every extra option field costs conversion. Ask only for what genuinely changes the price.
- Rounding policy. Decide early whether you round up on partial units. Changing it later means explaining price changes to existing customers.
- Formula readability. Use conditional formula groups for tiers instead of one enormous nested expression. The person maintaining it in a year will not be you, or will not remember.
A worked example
See how to sell by square metre, weight or custom dimensions in Odoo eCommerce for a full walkthrough with fields, formula and rounding on a real pricing case.
Next steps
Compare both on the shop, or describe your pricing and we will tell you which one fits.
Frequently asked questions
Do I need both modules?
No. They cover the same formula engine and both drive backend Sales and eCommerce. Installing both would create ambiguity about which rule applies.
Does either work without an eCommerce site?
Both depend on website_sale, so the eCommerce stack is installed either way. The backend calculator works regardless, but you will be installing website sales alongside it.
Can the price change depending on what the customer selects?
Yes, in both. Conditional formula groups switch the formula based on user input or on running results.
Do the selected options appear on the order and the PDF?
Yes, in both. Options follow through cart, checkout, order and the printed document.
Which Odoo versions are supported?
Odoo 18.0 and Odoo 19.0 for both.