Khichdi InfoTech
Skip to content

Odoo Manufacturing · advanced · 11 min read

Configurable Products vs Standard Variants

When to use Odoo product variants versus configurators and custom BoM explosion for made-to-order manufacturing — without SKU explosion or broken MOs.

Last reviewed 2026-07-30 · Estimated effort: 6+ weeks for multi-team change

Table of contents

Standard variants in Odoo model finite attribute combinations — each variant can carry its own BoM, price, and stock. They work when options are predictable and count stays in the hundreds, not millions.

Configurable products (native product configurator or custom modules) build BoM lines and pricing from rules at quotation time — required when dimensions, materials, or logic branches change components per order.

Wrong choice produces either unmanageable SKU lists or MOs that do not match what sales promised. Furniture and quote-to-subcontract businesses often need Customization or Development for configurator-to-MO handoff.

Sales teams love unlimited customization; ERP teams need finite master data. The tension shows up on the first big quote when someone asks why Odoo created four thousand variants overnight.

This article compares variants, standard configurators, and custom CPQ patterns for manufacturing handoff.

Use variants when attributes are discrete (color, size tier, voltage) and each combination is a repeatable SKU you might stock or forecast. Each variant gets a BoM if components differ.

Variant grids stay maintainable when engineering can sign off on a bounded matrix and marketing is not adding ad hoc line items per deal.

  • Attribute values with controlled lists
  • Per-variant BoM where components change by option
  • MTO or MTS per variant without dynamic rules
  • Pricelist rules keyed to variant attributes

Choose configurators when options interact — length drives material quantity, finish excludes hardware, or structural rules add/remove BoM lines. Native Odoo configurators attach optional products and can drive BoM templates in supported setups.

Heavy engineer-to-order often needs Customization to persist configured BoM snapshots on the sales order and pass them to MO creation without manual re-entry.

Variants use pricelist rules and product list prices. Configurators sum option surcharges and calculated quantities — ensure tax, discount, and revision rules match what finance expects.

Lock configured BoM on SO confirmation so engineering changes mid-build do not silently alter margin on open MOs.

The sales order must create or reference the BoM variant the MO will consume. Gap here is the top failure mode: quote shows one bill, MO explodes another.

Subcontract steps triggered by configuration need resupply rules tested per option path. Link Development when external CPQ feeds Odoo via API.

Prefer variants if you can inventory-plan per SKU and BoM differences are attribute-driven. Prefer configurators if most orders are unique dimensions or rule-heavy ETO.

Hybrid models use variants for base platform and configurator for add-ons — document which layer owns master data to avoid duplicate products.

  • Count potential variant combinations before enabling attribute explosion.
  • Prototype one complex quote path through SO confirm and MO creation.
  • Store configured BoM snapshot on the order when rules are dynamic.
  • Train sales on which options are variant versus free-text (avoid free-text for manufacturing).
  • Cross-link Customization for quote-to-subcontract and dimension-driven BoMs.
  • Cross-link Development when integrating external configurators.

  • !Generating all variant combinations when most are never sold.
  • !Using optional products on SO without BoM linkage for manufacturing.
  • !Letting sales edit MO components instead of fixing configurator output.
  • !Mixing imperial and metric dimensions without UoM conversion on rules.
  • !Configurator adds products purchase has never set up as storable items.
  • !No revision lock between quote approval and MO release.

Variants scale bounded option grids; configurators carry engineer-to-order logic — align choice with how unique each order really is.

Next, stress-test your hardest quote through SO confirmation and MO explosion before committing to master data structure.

Variants vs configurator vs custom module trade-offs.
OptionBest whenTrade-off
ConfigureStandard Odoo covers the needLimited uniqueness
CustomizeDifferentiating workflowUpgrade cost
IntegrateExternal system of recordSync complexity
Quote options → SO BoM snapshot → MO components.
1

Quote / order

Sales confirms demand.

2

Engineer / BoM

Configurable or standard.

3

MO create

Manufacturing order.

4

Deliver

FG to customer or stock.

Finite matrix vs dynamic rules decision path.
Standard fit?

Configure and train

Odoo covers ≥80% of the process

Unique process?

Custom module

Competitive advantage depends on it

External master?

Integrate

Another system owns the data

Unclear ROI?

Defer / pilot

Scope is speculative

Frequently asked questions

Does Odoo have a built-in product configurator?

Yes in supported editions — optional products and configurators on sales can drive line composition. Complex ETO often still needs Customization for BoM persistence and subcontract rules.

Can one template use both variants and configurator?

Possible in hybrid setups but increases testing surface. Document which attributes create variants versus runtime options.

How do configurators affect procurement?

Dynamic BoM lines drive component demand at SO or MO confirmation. Long-lead options must appear early in the quote so purchase can buy before production slot.

What about retail-style option swatches on a manufacturing site?

Website configurators feeding MTO manufacturing need the same BoM snapshot discipline as inside sales — see retail portfolio patterns only when ecommerce drives production.

Designing configurable manufacturing in Odoo?

Share sample quotes and option rules — we will recommend variants, configurator, or custom CPQ path.

Business technology and software delivery