I created a very simple product with variants on demo4.4.tryton.org
called 'PRESTO 605 sur plage'.
The variants are 'Eau froid' and 'Eau chaude'.
I created two suppliers each providing both products.
Unfortunately the suppliers codes seem to always map to the first variant
'Eau froid' so it is quite apparent that there should be a means to
relate the suppliers products to the correct product variant.
Though it seems that it has been mentioned before, there is a missing variant
specific name needed, though the description seems somewhat there.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
Not a bug, it is how product supplier is designed. It links the template and not the product. This is the pattern in Tryton to define on template by default and allow customization at the product level.
Indeed I think a good solution will be to add on the product supplier a second optional field for the variant (aka product). Of course both values should be kept coherent with a domain constraint.
On the variant (aka product), we should add a product_suppliers field which use this new field and add a product_supplier_used property (like for accounting) which return the product values if not empty or the template values not linked to another product.
The only thing is that by default the supplier should use the 'default' product which today should probably always be the first product [variant] (OpenERP had a sequence?).
That is, of course, only until another product is specifically selected.
Here is review66551002 which implement design of msg36116
On the way, the refactoring of selecting the product supplier fixed an uncertainty in sale_supply_drop_shipment.
Cédric Krieradded 1 deleted label and removed 1 deleted label
It would be nice to add a "variant" column in the supplier_product view in the template form because we couldn't distinct between a supplier_product on the variant and a supplier_product on the template.