Furniture makers who take custom orders live in a gap Odoo core never fully closes. Every quotation is really an engineering exercise: a customer wants a 2,300 mm oak sideboard in a specific stain with brass hardware, and someone has to translate that into a bill of materials, a cut list, a route through the workshop, and a price that reflects the labour and offcut waste. Stock Odoo mrp assumes you already know the BoM before the sale — it is built around repeatable products with fixed components. When the product is only defined at quote time, teams fall back to spreadsheets for costing, re-key everything into a manufacturing order by hand, and lose the traceable link between what was quoted and what was actually built. Product variants and configurator options help for simple option matrices, but they break the moment dimensions drive material consumption or a finish adds hours of labour.

This build-to-order configuration is the workshop-specific layer we design and install on top of native sale, mrp, and stock. Technically it is a proper Odoo module: new models extending models.Model for a made-to-order specification (dimensions, material, finish, edge profile, hardware) that hangs off the sale order line, with @api.depends compute methods that size a parametric bill of materials and derive linear-metre or board-foot quantities from the entered measurements. Costing fields roll material, labour, and a configurable waste allowance into an indicative sell price on the quotation, and on order confirmation an automated action (or stock.rule route) generates the manufacturing order with the components and operations already populated — no re-keying. Because dimensional data flows through, report_xxx QWeb templates can print a shop-floor cut list and a customer-facing spec sheet from the same record.

Everything is scoped to your process. Security is enforced with ir.model.access.csv plus record rules so the workshop, sales, and costing roles each see the right data; views are delivered as XML (with OWL components where an interactive configurator adds value); and the specification and cost data are exposed over the XML-RPC/JSON-RPC API so a website product configurator, a CAD hand-off, or a pricing sheet can read and write it. We target Odoo 17.0, 18.0, and 19.0, and we are explicit about Community vs Enterprise: the module runs on Community, and where a feature leans on Enterprise-only apps (such as advanced MRP work-order tablet views, Studio, or Documents) we tell you before the build so the scope reflects your edition.

Because this is build-to-order, nothing is downloaded and switched on today. After you request a quotation we run a short scoping call, agree the exact models, fields, costing formula, and reports, and then build, test on a staging database, and install the version tuned to your workflow — typically 2–4 weeks from confirmed scope. Pricing starts from $349 (indicative, single-company base scope); multi-company setups, deeper localization, e-commerce or CAD integrations, and migrating historical order/BoM data increase the quoted scope. You get a fixed quote after the scoping call, never a surprise on the invoice.