A build-to-order front-end configurator that embeds guided, step-by-step configuration and live pricing directly on your Odoo eCommerce product page. Shoppers self-configure made-to-order products, validate compatibility in real time, and check out — or request a quote — with full option detail carried through to the sale order. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $449.00 USD; request a quote for a scoped proposal.

A build-to-order front-end configurator that embeds guided, step-by-step configuration and live pricing directly on your Odoo eCommerce product page. Shoppers self-configure made-to-order products, validate compatibility in real time, and check out — or request a quote — with full option detail carried through to the sale order.
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
Selling configurable or made-to-order products online usually breaks down at the product page. Odoo's native website_sale handles product variants and simple attribute selection well, but it was never designed for guided configuration: it has no concept of steps, no dependency logic between options, no real-time compatibility validation, and no way to recompute an itemized price as a shopper mixes and matches. Once your catalog has options that depend on each other, add-ons priced per unit, or combinations that must be blocked, teams fall back on pre-building every variant (an explosion of thousands of product.product records), long email threads, or a static "contact us" form that kills self-service conversion. That is where the native model runs out of road.
Front-end step-by-step configurator rendered in OWL/QWeb and embedded directly on the `website_sale` product page, not a separate microsite
Server-authoritative live price recalculation over a JSON-RPC/`http.route` AJAX endpoint — options recompute without a page reload and browser input is never trusted for pricing
Visual option selection via image swatches, cards, and dropdowns, each bound to dependency rules stored as ORM records
Real-time compatibility validation that disables incompatible options and blocks any invalid configuration from reaching the cart
Itemized configured-product summary with per-option pricing computed via `@api.depends`, shown before checkout
Save-and-share configuration link (tokenized) so shoppers can resume later or forward the exact configuration to a colleague
We build a clean-room front-end configurator that lives directly on the eCommerce product page and drives configuration through a guided, step-by-step OWL/QWeb interface. As the shopper picks options via image swatches, cards, or dropdowns, the front end calls a JSON-RPC/http.route controller endpoint that recomputes price server-side and returns the itemized breakdown over AJAX — no page reload, no client-trusted math. Option relationships are modeled as ORM records (models.Model with dependency and constraint fields) so the same rules govern what is shown, what is disabled, and what is blocked. A compute layer (@api.depends) rolls per-option prices, per-option stock, and lead times into a live summary, and real-time compatibility validation prevents an invalid configuration from ever reaching the cart. Because the rules and constraints engine is shared with the Sales-side CPQ app, quotes built by your sales team and configurations built by a shopper resolve against one source of truth.
The build carries the full configuration through the whole order flow, not just the storefront. When a shopper adds a configured product, every chosen option is serialized onto the sale.order.line and flows through to the invoice and any QWeb documents, so fulfillment and finance see exactly what was ordered. A save/share link lets a shopper resume later or forward the configuration to a colleague; an optional 2D image-layering preview updates as options change; and a "Request a quote" fallback catches configurations above a price or complexity threshold and routes them to your team instead of forcing a checkout. The UI inherits your active website theme and is fully mobile-responsive. Security is enforced properly with ir.model.access.csv and record rules, and all pricing logic is server-authoritative so nothing can be tampered with from the browser. The build targets Odoo 17.0, 18.0, and 19.0 and works on both Community and Enterprise (Enterprise-only dependencies, where relevant to your edition, are confirmed during scoping).
Because this is made to order, nothing ships as an instant download. After you request a quotation we run a short scoping call, confirm your option model, pricing rules, theme, and edition, and then build, install, and support it. Typical delivery is 2 to 4 weeks from confirmed scope, with UAT on a staging database before anything touches production. Pricing starts from $449 (indicative, single-company base scope); the depth of your dependency/constraint rules, number of configurable product families, 2D preview and image-layering complexity, multi-company or multi-website rollout, and any data migration of existing variant catalogs increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.
Owns the online storefront for made-to-order or highly-optioned products and needs true self-service configuration on the product page so shoppers can build, price, and buy without an email thread — while invalid combinations are blocked automatically.
Wants the storefront and the sales desk to quote from one rules engine so a shopper-built configuration and a rep-built quote never disagree, and wants a clean 'request a quote' path for large or complex orders instead of lost carts.
Maintains the catalog and dreads the variant explosion of pre-building every combination. Needs options and dependencies modeled as maintainable ORM records with proper access control, not thousands of `product.product` rows.
Needs every chosen option to arrive intact on the sale order and invoice with accurate per-option stock and lead times, so production and shipping work from exactly what the customer configured.
Buy the license on ecosire.com and download the CPQ Website Product Configurator for eCommerce module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for CPQ Website Product Configurator for eCommerce, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Delivery model | Build-to-order for your version; scoped, built, installed, supported | You brief and manage an internal or freelance build | Instant download, one-size-fits-all | |
| Guided step-by-step UI | OWL/QWeb wizard embedded on the product page | Possible but you design and build the flow | Often a fixed layout you can't restructure | |
| Live AJAX pricing | Server-authoritative recompute, no reload | Depends on your engineering effort | Usually present but logic is a black box | |
| Dependency & compatibility rules | Shared CPQ rules engine, blocks invalid combos | Hand-rolled logic to build and maintain | Basic exclusions, not a true rules engine | |
| Config detail on order/invoice | Full options serialized to `sale.order.line` and QWeb docs | You implement the serialization | Varies; often summary text only | |
| Stock & lead time per option | Live per-option stock and lead time from inventory | Custom inventory wiring required | Rarely surfaced per option | |
| Request-a-quote fallback | Threshold-based routing to your sales team | Build it yourself | Typically absent — checkout only | |
| Source, docs & handover | Full source, docs, training, git repo, support window | Whatever your team documents | Encrypted/OPL code, limited to changelogs |
No. This is a build-to-order engagement, not an existing apps.odoo.com download. After you request a quotation we scope your option model, pricing rules, theme, and Odoo edition, then build, install, and support the configurator for your instance. You receive installable source code for your version at handover.
Typical delivery is 2 to 4 weeks from confirmed scope. The timeline depends on how deep your dependency/constraint rules go, how many configurable product families are involved, and whether you need the 2D image-layering preview or a multi-website rollout. We agree on the schedule in writing after the scoping call and validate everything on staging before production.
Pricing starts from $449 as an indicative, single-company base-scope figure. The final number depends on rule complexity, number of product families, preview/image-layering needs, multi-company or multi-website rollout, and any migration of your existing variant catalog. After a short scoping call we send a fixed quote — you approve it before we build, so there are no surprise invoices.
We build for Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise. Some features may rely on edition-specific dependencies; we confirm exactly what applies to your edition during scoping so nothing is assumed.
Every chosen option is serialized onto the `sale.order.line` and flows through cart, sale order, invoice, and QWeb documents. Pricing is computed server-side (never trusted from the browser), so fulfillment and finance always see the exact configuration and the correct total.
Yes. The configurator is rendered in OWL/QWeb and inherits your active website theme's colors and typography, and the UI is fully mobile-responsive. It embeds directly on the standard `website_sale` product page rather than living on a separate site.
You get a post-go-live support window for defect fixes and questions, plus a git repository handover with full history so your team (or ours) can extend it later. Version upgrades or new configurable product families beyond the delivered scope are quoted as follow-on work.
A build-to-order front-end configurator that embeds guided, step-by-step configuration and live pricing directly on your Odoo eCommerce product page. Shoppers self-configure made-to-order products, validate compatibility in real time, and check out — or request a quote — with full option detail carried through to the sale order.