A made-to-order Odoo module that prices product variants from attribute-level coefficients, multipliers, and fixed surpluses instead of hand-keyed per-variant extra prices. ECOSIRE builds it to your rules, installs it, and supports it after you confirm scope. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A made-to-order Odoo module that prices product variants from attribute-level coefficients, multipliers, and fixed surpluses instead of hand-keyed per-variant extra prices. ECOSIRE builds it to your rules, installs it, and supports it after you confirm scope.
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
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.
New coefficient (multiplier) and surplus (additive) fields on `product.template.attribute.value`, so pricing factors live on the attribute data rather than on each variant
Stored `@api.depends` compute on `product.product` that recomputes the variant sales price automatically when any factor or selected attribute value changes
Configurable factor precedence — apply multiplicative coefficients before additive surpluses, or a custom evaluation sequence you specify per template
Formula-style surpluses whose value can depend on another chosen attribute (e.g. finish surcharge scales with size class)
Optional per-template overrides via fields on `product.template.attribute.line` so one attribute value can price differently across templates
Stored price-breakdown field showing base price plus each applied coefficient and surplus, for transparency on the product form
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.
Makes made-to-measure goods (furniture, windows, signage, industrial equipment) where price scales with dimensions, material, and finish. Needs formula-driven variant pricing instead of thousands of hand-entered extra prices.
Owns margins across a large variant catalog and needs one place to change a coefficient and have every affected variant, quotation, and invoice reprice automatically and auditably.
Runs the company's Odoo and wants a clean, upgrade-safe addon with proper security, stored computes, and API-readable prices rather than brittle manual maintenance or an unmaintained third-party module.
Wants quotes generated with correct variant prices and a visible breakdown on the order line and PDF, so reps stop overriding prices by hand and margins stay consistent.
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Advanced Variant Prices モジュールの ZIP をダウンロードします。
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「Advanced Variant Prices」を検索し、「インストール」を押します。
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Pricing logic | Coefficients, surpluses, and cross-attribute formulas built to your rules | Whatever you code in-house, if you have the ORM depth | Fixed patterns exposed by a generic module | |
| Maintenance effort | Change one coefficient; every variant reprices via stored compute | Depends on your design; often reinvented per project | Config-bound; edge cases need forked code | |
| Fit to your catalog | Scoped to your attributes, precedence, rounding, and reports | Fully custom but you own all the design decisions | Generic; you adapt your process to the module | |
| Version support | Built and tested for your 17.0 / 18.0 / 19.0 target | You maintain across upgrades | Depends on the vendor's release cadence | |
| Security & access | `ir.model.access.csv` + record rules scoping factor edits to pricing managers | As designed; easy to under-specify | Standard groups, rarely tailored | |
| Integration | Stored fields exposed via `XML-RPC`/`JSON-RPC` for PIM/e-commerce/CPQ | Possible with extra work | Varies; may not expose computed values cleanly | |
| Support & ownership | Post-go-live support window + full git repo handover | Your team owns it entirely | Vendor support terms, shared codebase | |
| Delivery model | Build-to-order, 2–4 weeks from confirmed scope, fixed quote after scoping | Open-ended internal timeline | Instant download, but you fit yourself to it |
No. It is build-to-order. ECOSIRE builds the module to your exact pricing rules, installs it, and supports it. You are commissioning a productized service, not buying an off-the-shelf download.
Typical delivery is 2–4 weeks from confirmed scope. Simple single-company coefficient/surplus models land toward the shorter end; many attribute-driven formulas, e-commerce/CPQ integration, or data migration push toward the longer end.
Pricing starts from $249 (indicative, single-company base scope). We hold a short scoping call to lock the factor model, precedence, rounding, reports, and integrations, then give you a fixed written quote before any build work begins.
Every build includes a post-go-live support window for defect fixes and questions. We build for your target major version (17.0, 18.0, or 19.0), and forward-porting to a newer Odoo release is available as a separate scoped engagement.
Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. We confirm edition-specific behaviour — for example configurator UX differences — during scoping so the build matches your environment.
Yes. The variant price is a real stored field, so it is readable via the standard `XML-RPC`/`JSON-RPC` API. External PIM, e-commerce, or CPQ tools read the same authoritative price your salespeople see.
Yes, as an optional deliverable. We can build an idempotent migration that converts existing `price_extra` values into equivalent coefficients and surpluses, with a mapping report you review before it runs on production.
A made-to-order Odoo module that prices product variants from attribute-level coefficients, multipliers, and fixed surpluses instead of hand-keyed per-variant extra prices. ECOSIRE builds it to your rules, installs it, and supports it after you confirm scope.