New here and trying to figure out how Odoo inventory handles parent items with child skus?
I see the product variants but what I can't figure out is how variant skus connect to a non-inventory parent (catalog) item.
For example, a sized T-shirt, item T01 in sizes Small through XL where T01 is the catalog parent item, and T01S, T01M, T01L and T01X are the child stock units being tracked and sold.
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Boekhouding
- Voorraad
- PoS
- Project
- MRP
Deze vraag is gerapporteerd
1
Beantwoorden
1248
Weergaven
Correct, the (Internal) Reference field (or default_code as it is called in the database) is meant to be an unique identifier on a Product.
Now, here 'Product' can mean two things:
- a Product (Template) (technical name product.template) without Variants
- a (Product) Variant (technical name product.product) itself
It's important to note that every Product Template has at least on Product Variant. In other words, a product.template record is either directly linked to a single product.product record (=> a Product without Variants) or to multiple product.product records (=> a Product with Variants); In return, each Product Variant is definitely linked to one Product Template.
In the light of calling '(Internal) Reference' a 'SKU' this makes actually sense, since you don't keep track of the stock of what all a product could be (Product Template with multiple Variants) but rather what it actually is (a Product Template representing just one Variant or the different Variants of a Product Template).
From a more technical point of view, the behavior of what a Product Template's Reference is, is defined here: https://github.com/odoo/odoo/blob/18.0/addons/product/models/product_template.py#L423-L428
This section basically says that when there's just a single Variant, the Variant's Reference is applicable to the Template as well, otherwise it isn't (this then is combined with some view logic of whether or not to show the field).
This is also true for other fields, such as for example the weight of a Product - again, here you would be interested in the physical item rather than the 'definition container' or 'group' (aka Product Template) when dealing with different Variants.
Geniet je van het gesprek? Blijf niet alleen lezen, doe ook mee!
Maak vandaag nog een account aan om te profiteren van exclusieve functies en deel uit te maken van onze geweldige community!
Aanmelden| Gerelateerde posts | Antwoorden | Weergaven | Activiteit | |
|---|---|---|---|---|
|
1
jul. 25
|
2126 | ||
|
1
okt. 25
|
394 | ||
|
1
jul. 25
|
1395 | ||
|
0
sep. 24
|
1191 | ||
|
0
jul. 24
|
1378 |
I'm unsure of what kind of answer your looking for. Product variants are for example described in https://www.odoo.com/documentation/18.0/applications/sales/sales/products_prices/products/variants.html - 'Inventory: inventory is counted for each individual product variant. On the product template form, the inventory reflects the sum of all variants, but the actual inventory is computed by individual variants.'
To clarify, what I was looking for is how to structure product codes ( I think it's Internal Reference) in Odoo.
I see that on a single product I can have an Internal Reference product code.
But on a product with variants, only the variants seem to have a product code.
In the T-shirt example, the main item would be product code T01 but in Odoo I can only provide T01S to the variant size small but I can't assign T01 to the main item.
Does that make sense?
Correct, you cannot have an Internal Product Reference (T01) for the T-shirt, but if you searched for "T01" products you would see T01S, T01M, T01L and T01X. That makes sense because you can't buy or sell T01, you have to select a size.
Additionally, this app - https://apps.odoo.com/apps/modules/18.0/product_dynamic_code - may help configure internal references to reflect the hierarchical nature of Odoo's products.