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.

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 one working week from confirmed scope, with UAT on a staging database before anything touches production. Pricing starts from $999 (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.