Community: CMS / eCommerce Experts mailing list archives


Product Variants :: Question (bug?)

Antiun Ingeniería S.L., Rafael Blasco
- 29/01/2015 13:50:24

Hi all,


I would like to rescue this thead.


It’s clear about how and why Odoo implemented variants in product. Easy to understand.


1 - What I don’t understand  (maybe is a bug) is why in the variants, description_sale in product.product is propagated to all variants and to the template.


For example: you have t-shit (red, green)


description for Green: This is a Green T-shirt like a tree

description for Red: This is a Red T-Shirt like a tomatoes


The second description you write will propagate and over write the actual description eventhough is a description_sale of product.product.


This means that Variants are not usefull in the e-commerce side, because clients will see a photo of a Grenn T-shirt but a descripción like “This is a Red T-Shirt like a tomatoes”


Any of you have this same problem? I’m using SAAS Odoo.


2 – Has any sense that 2 different Manufacturing processes produce 2 different variants from the same product?



Re: Product Variants :: Question

By Fabien Pinckaers (fp) - 2014-07-16 08:05:24




No, several variants of the same template are really different products,

with different prices, pictures, internal codes, EAN, stock levels. What

we call a 'product' is actually a specific variant of a template.



But, even if they are different products, variants of the same template

share a lot of attributes between each others: suppliers, base price,

description, base name, etc.


Starting from version 8, a user:

  - create/edit products from the template view

  - can drill down to variants, but it's not mandatory as we designed

    the system so that you just need to work on the template form if you

    do not use variants.

 - selects variants of a template if working on a sale order/picking


Since a lot of attributes are shared between variants, a good practice

is to use variants for products that have nearly all attributes in

common and differ slightly by just a few characteristics (color, size)


We wanted to put most characteristics on the template otherwise it's too

complex for the end-user to create a new product. (having to create a

template then zoom to the variant just to set the cost price is too complex)


The supplier price is on the template but can be different from one

product to another since pricelists use products, not templates. (not

ideal but it works).


For the cost price, it may be a good idea to be able to overwrite it on

the variant, but it's not the case for now on. (maybe a community module?)






On 07/16/2014 09:32 AM, Daniel Reis wrote:

>> May I broaden this question on what fields are variant sensitive? And

>> add the question if the present set of fields is sensible?

>> e.g. Image, Internal Ref, EAN (?) can receive different values, but as

>> said above, procurement costs cannot.


> AFAIK, the point for "variants" is to let the same "Product" (same Ref,

> EAN, Cost,...) have different characteristics such as colour and size.


> If you need different EAN's or Cost for "variants", then probably you

> want to have different "Products" instead of one product with variants.


> /DR


> --

> Daniel Reis Sent by Odoo Inc.  using OpenERP

> . Access your messages and documents in Odoo






Fabien Pinckaers

Odoo Founder


Phone: +


Twitter: @fpodoo


Instant Demo: