Hello, we’re encountering a design problem of or NOP DB and have a relative urgent question.
The context:
Most of our products have several variants like 300mg, 600mg and some have no variant. The products are mostly pills or liquids.
We are in the migration process towards NOP and imported already a few thousand products into the new database structure. Currently we are using attribute combinations to distinguish the different variants of each product.
The problem:
Now were adding features like order processing which needs us to relate each product-variant to one supplier (or more) and also to different stock levels etc. The current solution by using attribute combinations does not support all these product based relations and therefore requires some extension.
The question:
Can we continue with our current approach to use attribute combinations to distinguish product variants or should we change to use the product group feature and each single product is its own variant?
Thank you very much for your help or advise.
Advise: Grouped products or attribute combinations for variants
MVP
認定開発者
- 558
- 6401
- 2011/07/29
- United Kingdom
ldenkewi wrote:
Unless you want to implement the additional functionality yourself I'd say it would be easier to switch to individual products. For the 2 features you mention:
1. Manufacturer mapping only exists for products (not product attribute combinations) which you might be able to equate with suppliers.
2. Stock levels exist for product attribute combinations but if you need multiple stock levels per product (one for each supplier) then the closest thing that nop offers is multiple warehouses per product. So each warehouse would represent one supplier and allow you to maintain individual stock levels per supplier. Again, this is only available to individual products, not product attribute combinations.
One thing to bear in mind is that although the presentation of grouped products with variants is significantly different to individual products with combinations in the default nop theme it's relatively easy to alter the theme views to make the page layouts more similar if that's the presentation you prefer.
The context:
Most of our products have several variants like 300mg, 600mg and some have no variant. The products are mostly pills or liquids.
We are in the migration process towards NOP and imported already a few thousand products into the new database structure. Currently we are using attribute combinations to distinguish the different variants of each product.
The problem:
Now were adding features like order processing which needs us to relate each product-variant to one supplier (or more) and also to different stock levels etc. The current solution by using attribute combinations does not support all these product based relations and therefore requires some extension.
The question:
Can we continue with our current approach to use attribute combinations to distinguish product variants or should we change to use the product group feature and each single product is its own variant?
Most of our products have several variants like 300mg, 600mg and some have no variant. The products are mostly pills or liquids.
We are in the migration process towards NOP and imported already a few thousand products into the new database structure. Currently we are using attribute combinations to distinguish the different variants of each product.
The problem:
Now were adding features like order processing which needs us to relate each product-variant to one supplier (or more) and also to different stock levels etc. The current solution by using attribute combinations does not support all these product based relations and therefore requires some extension.
The question:
Can we continue with our current approach to use attribute combinations to distinguish product variants or should we change to use the product group feature and each single product is its own variant?
Unless you want to implement the additional functionality yourself I'd say it would be easier to switch to individual products. For the 2 features you mention:
1. Manufacturer mapping only exists for products (not product attribute combinations) which you might be able to equate with suppliers.
2. Stock levels exist for product attribute combinations but if you need multiple stock levels per product (one for each supplier) then the closest thing that nop offers is multiple warehouses per product. So each warehouse would represent one supplier and allow you to maintain individual stock levels per supplier. Again, this is only available to individual products, not product attribute combinations.
One thing to bear in mind is that although the presentation of grouped products with variants is significantly different to individual products with combinations in the default nop theme it's relatively easy to alter the theme views to make the page layouts more similar if that's the presentation you prefer.