← All posts

Odoo Product Variants: Retire Options Without Losing Context

Short answer: Review existing variants and their business use before removing an Odoo product attribute or retiring an option. A catalogue edit can affect record identity as well as presentation. I treat a discontinued option as a lifecycle decision involving stock, orders and integrations, not just a cleaner product form.

Applies to

Odoo 19 product variants in Sales, Inventory and related catalogue applications across editions. Odoo 20 documentation changes attribute navigation and eCommerce presentation fields. The Odoo 19 removal behaviour discussed here should be reviewed in the installed release before changing an established catalogue.

What does retiring an option actually mean?

An option may be unavailable for new orders while existing stock is still sold, or it may be withdrawn entirely. Customers may still need returns, warranty support or replacement parts for products already purchased. Define those requirements before changing the catalogue structure.

A variant is a distinct product combination with its own operational history. Removing a colour from a website selection is not necessarily the same as removing the attribute that helped create the product records. The chosen change should match the business intention.

Ask who still refers to the variant. Warehouse labels, supplier catalogues, customer quotations and external shops may all use its reference. A change that looks harmless to the website editor can disrupt another workflow if those dependencies are not considered.

What does Odoo document about attribute removal?

The Odoo 19 documentation explains that removing attributes affects variants already created. Variants used in orders can be archived, while unused variants can be deleted and recreated with the new attributes. It warns that customisations associated with deleted variants can be lost.

This makes a structural attribute change different from a simple description edit. Review the existing combinations and their use before confirming the new structure. Keep a record of the identifiers and important settings that other systems depend on.

The documentation also warns that an attribute’s variant creation mode cannot be edited once it has been added to a product. Choose between the documented creation modes based on the actual catalogue model. A later operational problem may require a planned redesign rather than a quick toggle.

How should remaining stock and open orders be handled?

Identify stock on hand, reserved quantities and open commercial commitments for the retiring variants. Decide whether the business will fulfil existing orders, offer alternatives or agree cancellations. Those decisions should not be left to whichever employee first notices that a product is no longer selectable.

Review purchasing and replenishment too. A variant can disappear from the sales catalogue while an old supplier rule or open purchase still refers to it. The lifecycle plan should identify which replenishment decisions remain valid and which should stop.

For external stores or connectors, agree the mapping change with the integration owner. Do not assume that an archived or recreated Odoo variant is automatically represented correctly elsewhere. Confirm how the external product reference, stock feed and order import should behave during the transition.

Worked example: a skincare pack size is discontinued

Imagine an illustrative skincare business discontinuing one pack size while continuing two others. Some stock remains, and wholesale customers already have confirmed orders. The team wants the discontinued size removed from new promotional offers but still needs its history for fulfilment and returns.

The catalogue owner reviews whether a targeted lifecycle change can meet that need without removing the entire size attribute. Warehouse and sales agree how the remaining stock will be used. Purchasing stops unnecessary replenishment through the appropriate process, and the online store owner reviews the customer facing offer.

The integration owner preserves the relationship between historic external orders and the original variant. The business can explain the discontinued product without presenting it as a newly created item with a different identity. The change follows the commercial decision rather than forcing the business to adapt to an accidental catalogue rebuild.

When it fits and when it doesn’t

This approach fits established catalogues, seasonal ranges and businesses with several sales channels. It is especially important where variants carry external identifiers or customised settings.

A brand new unused catalogue may be simpler to redesign, but the team should still understand which records will be recreated. Conversely, a legally required product withdrawal can involve additional specialist procedures beyond catalogue retirement. The product configuration is only one part of that wider operational response.

Common mistakes

Removing an attribute to hide one option. Check the effect on every variant combination first.

Ignoring unused variant customisations. Deletion and recreation can lose settings even when no order history exists.

Forgetting external mappings. Coordinate catalogue changes with connected shops and import processes.

Treating retirement as cancellation. Review open orders and supplier commitments separately.

What should the catalogue owner retain?

Keep the reason for the change, the affected variants and the agreed treatment of stock and open work. Record which external channels were updated and who confirmed the result.

A later support or purchasing employee should be able to understand why a product is no longer offered and where its history belongs. That continuity is the real goal of a controlled retirement. A smaller catalogue is useful only if the remaining records still explain the business accurately.

Read Product Variants and Optional Products in Odoo Sales for the connected workflow.

Official references

  1. Product variants

How this article was checked: official Odoo 19 documentation was reviewed in October 2026. Odoo 20 references were also checked; material differences or moved pages are identified above. Examples are illustrative business scenarios, not client results or tests on a live database.

If you need help translating these decisions into your own workflow, see my Odoo consulting services.

? Frequently asked questions

Can removing an attribute affect existing variants?

Yes. Odoo documents that removing attributes can archive used variants or delete and recreate unused variants, potentially losing customisations.

Can a variant creation mode always be changed later?

The documentation warns that an attribute creation mode cannot be edited once the attribute has been added to a product. Decide the model before widespread use.

Ask about this guide