Community: Inventory and MRP mailing list archives

Re: configurable products

- 06/05/2015 09:28:41

In your message you reference a "car".  Has Odoo actually begun to look at automotive?  I have been pushing the concept of an open source Dealership Management System (DMS) for several years with OpenERP/Odoo as the base application (see 

The example you used is a good one - typically the attributes are: Year, Make, Model, Package.  For example:  2016, Toyota, Camry, SE.  Extensive detail can be referenced in the notes are.  In this case the inventory is serialized.

In a parts department - which is more like what others are referencing, as you mention each variation has a unique part number, with one caveat.  Sometimes the same part is manufactured by different vendors.  In these cases typically they are handled by adding a suffix to the base number.  For example lets say you have two vendors making a gasket - The "Apple" (A) and the "Baker" (B) manufacturers.  Lets say the gasket is part number 1250390.  So the "Apple" number would be 1250390-A, and the "Baker" one would be 1250390-B.  Some manufacturers use dashes and some don't - which is a particular headache for the programmers to address.

Sometimes there is a need for "configurable products".  In the automotive world the most likely parallel scenario would be "parts kits".  A good example is a kit for an "Oil Change".  This could be VIN driven or more generic.  For example you would need - an oil filter, oil, and shop supplies at a minimum.  You have different types of oil filters and different types/quantities of oil (based on the engine/vehicle).  There are sub-applications that can deal with this; but, "Kits" (giving a bundled set of numbers a unique part number) is the most common.

Hopefully the above is useful...

On 6/5/2015 7:10 AM, Gustavo Marino wrote:
<blockquote cite="" type="cite">
Based on the ideas of the attached document, we are generating a hierarchy of products with inheritance of product attributes.

The idea is to share attibutes as much as possible, modelling the reality in a way similar to prototype object systems. Let say for example you define a car, with atributtes like motor type or number of passengers, sharing this attributes in all cars.

Additionally, products attributes could be declare in a higher point in the hierarchy, but concrete defined in leaf products. Using the cars example, at the car level you can define a brand attribute, that will be defined in the specific cars low in the tree

This could be very helpful in large collections, where the attribute values are defined once and in only one place for many products, like for example colours for t-shirts.

I am attaching the module, since it is not published till now. Any comment or suggestion will be appreciated


Gustavo Adrian Marino


Mobile:  +54 911 5498 2515


Skype: gustavo.adrian.marino


<img border="0" width="213" height="94" src="cid:image001.jpg@01CC37F5.99B4CD20" alt="Descripción: Numa Logo V 1-0">

2015-06-05 7:24 GMT-03:00 Peter van Montfort <>:
At this moment we are building a product configuration module !!
Peter van Montfort
Senior Consultant

<IMG src="cid:em6cfdb3b3-9aa9-40c2-8280-fd71f242e4e2@peter-hp" width=16 height=12> +31 88 627 0429
<IMG src="cid:em73f4ac73-1fea-40c6-a00c-553cab5e9d7d@peter-hp" width=16 height=12> +31 6 2412 9003
<IMG src="cid:emb8cf83fc-5db0-44c8-8bbe-cec8639cf23d@peter-hp" width=16 height=12> p.vanmontfort
<IMG src="cid:em0e907aa1-729a-4ac6-86f4-8be19a23c712@peter-hp" width=16 height=12>

Onestein B.V.
<IMG src="cid:embf000974-7f8e-4d37-b1b4-9147601f1078@peter-hp" width=16 height=12> +31 88 627 0400
<IMG src="cid:em4ea16636-2f00-4227-b61b-d02422653333@peter-hp" width=16 height=12>
<IMG src="cid:emf7ff5082-cd64-4ba9-bf65-614b4cd9fa82@peter-hp" width=16 height=12> onestein_erp
<IMG src="cid:eme38a43ab-674c-4d42-b651-b7c777a30351@peter-hp" width=16 height=12> onestein

<IMG src="cid:emf9c144c7-93b2-4f7c-be91-2b8431693316@peter-hp" width=16 height=12> Amsterdam - Keizersgracht 62-64
<IMG src="cid:em580d4c4c-5c2a-42e1-9cda-3fc545268a4b@peter-hp" width=16 height=12> Oosterhout - Beneluxweg 37
<IMG src="cid:em3be0fc7c-3651-413f-b243-29ec2863993f@peter-hp" width=16 height=12> Antwerpen - Brusselsestraat 51

<IMG src="cid:em65a771d6-8680-4323-b97a-7f901e99feae@peter-hp" width=183 height=60>
------ Origineel bericht ------
Van: "Johan Van Hirtum" <>
Aan: "Community: Inventory and MRP" <>
Verzonden: 5-6-2015 11:58:39
Onderwerp: RE: configurable products
<BLOCKQUOTE class=cite2 cite=zarafa.5571716d.2c2c.24f98b5713da7bb2@zarafa type="cite">



I have the same problem ( our products are windows, doors, solar protection systems, shutters,… ).

When someone has started some development in this area, we want to cooperate.



With kind regards,



Van Hirtum Johan


Van: Arjan Duijs []
Verzonden: vrijdag 5 juni 2015 1:30
Aan: Community: Inventory and MRP
Onderwerp: configurable products



I am buying and selling products that have various options.

For example office chairs. They have a model (the product) and various options to enhance the product.

leather seat (6 leathers), imitation leather (12 leathers) 4d arm-pads, seat in color (30+ colors), polished aluminium base, counter seat version etc etc, can be up to approx 15 options.

I have searched the forum and the documentation, but cant find a clear explanation on how to configure this in Odoo.

Product variants isnt really an option imo since it would mean thousands of variants with all the seat types and a pain in the ass to add one to an order.

on the forum Luke pointed me towards

but after installing that it doesnt seem to make a difference.

In other words, i probably have no clue how that works :)


anyone a suggestion on how to do a product configurator/generator. (conditional would be even better.. a chair can not have a colored seat, leather seat AND an imitation leather seat.





Post to:

Post to:

Dave Nelson
m. 512.627.3164
o. 512.703.0448

Avast logo

This email has been checked for viruses by Avast antivirus software.