If your catalog uses configurable products — fabric grades, dimensions, material thickness, finishes, or capacity tiers — Odoo's native variant pricing quickly runs out of road. Out of the box, each product.template.attribute.value carries a single fixed price_extra that is added linearly to the template list price. That covers a flat "leather +$40" surcharge, but it cannot express "price scales with square-metre area," "premium finish adds 18% rather than a flat amount," "this size costs base × 1.4," or a surplus whose value depends on another chosen attribute. Teams end up maintaining hundreds of hand-keyed extra prices per template, and they drift out of sync the moment a raw-material cost moves.

Advanced Variant Prices is a build-to-order Odoo module that replaces manual per-variant maintenance with a rules engine over attribute coefficients and surpluses. We model the pricing factors — a multiplicative coefficient, an additive surplus, or a formula combining several attributes — on the attribute values themselves via new fields on product.template.attribute.value (and, where you need per-template overrides, on product.template.attribute.line). Each variant's sales price is then produced by a stored compute on product.product declared with @api.depends on product_template_attribute_value_ids and the factor fields, so recomputation is automatic and cache-consistent whenever a coefficient changes. The engine walks the variant's selected attribute values, applies each factor in the precedence you define (for example multipliers before surpluses, or a custom sequence), and writes an auditable computed price plus a stored breakdown you can display on the product form, the sale order line, and QWeb quotation/invoice reports.

Technically the module is delivered as a proper addon: a versioned __manifest__.py depending on sale (and sale_management/stock where your flow needs them), ORM models with the coefficient/surplus fields and the compute methods, OWL/XML form and list views for maintaining the pricing rules, ir.model.access.csv plus record rules so only your pricing managers can edit factors, and optional automated actions or a scheduled recompute for bulk cost updates. Because the computed price is a real stored field, it is available to Odoo's standard XML-RPC/JSON-RPC API, so an external PIM, e-commerce front end, or CPQ tool reads the same authoritative variant price your salespeople see. We build against your target — Odoo 17.0, 18.0, or 19.0 — and confirm Community vs Enterprise behaviour, since some pricing surfaces (like the product configurator UX) differ between editions.

Delivery is build-to-order, not an instant download: after a short scoping call we lock the exact factor model, precedence rules, rounding, and report placement, then build and unit-test the module, run UAT with you on a staging database, and deploy to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, depending on how many attribute-driven formulas and integrations are in play. Pricing starts from $249 (indicative, single-company base scope); multi-company pricing, deep formula logic across many attributes, e-commerce/CPQ integration, localization, or migration of existing per-variant price data increases the quoted scope.