Product Builder

[whiplash13]

In the PC Configurator thread many people have put money together to have a mod build to allow a product to sub categories that contain a list of products that can be added to the main product.  Since this is no longer just a PC Configurator and has been renamed Product Builder, on Mark's request I have created a new thread to track interest and progress on this mod.  Mark has graciously agreed to look at this project and is currently coming up with a game plan on how it will be designed.  The original thread is http://forum.virtuemart.net/index.php?topic=15492.0. If you would like to contribute please add the details of your contribution in this thread.  As of right now we have $400 dollars to contribute to the devleoper.

[whiplash13]

My last post in the old thread:

For us that will be using this for pc configuration, asking a customer to remove the item from their cart and rebuilding it would be a chore when there can be up to 20 items to configure.  It would definatly be key to have the ability to edit a configuraton once in the shopping cart.  Also could you add the ability to add a picture (if desired) for each option (not each item in the list just the subcategory item as an attribute just as you have title description, display type, etc...)?  While this may not be so important to those of us using this as a pc configurator, it could be important in other applications.  Seems like this wouldn't take much effort to add but will increase the value for some people. 

I would also like to formally thank Mark for attempting to take on this project that so many of us have been chomping at the bit for.

[macallf]

Hi Whiplash13,

Adding a picture as in for normal categories should not be a problem. But layout maybe! I might need to implement a type of flypage or pages to layout the build!

As to editing the cart directly this would be a nightmare. The only idea I have at present is to have an edit button that takes you back to the detail page, where you can edit your current build and update the cart with the new info.

This, as far as I am concerned, will be the best workaround.

Update

I have an important job on at the moment, but should be able to start at the weekend.

[whiplash13]

I think that is a perfectly acceptable workaround from my point of view for editing a product in the cart.  Like I said the image thing would be a nice to have for me but not a must have.  For others this may be more important. 

John

Hi Whiplash13,

Adding a picture as in for normal categories should not be a problem. But layout maybe! I might need to implement a type of flypage or pages to layout the build!

As to editing the cart directly this would be a nightmare. The only idea I have at present is to have an edit button that takes you back to the detail page, where you can edit your current build and update the cart with the new info.

This, as far as I am concerned, will be the best workaround.

Update

I have an important job on at the moment, but should be able to start at the weekend.

[macallf]

A definite list of must haves or likes before I start in earnest will be good idea. It will give me more of an idea of how to design it and what functionality is required.

[MichaelSHiltz]

Mark and contributors,

Thanks again.

Look forward to this mod.

[dustundag]

It would be also great to bundle the items from the admin panel as a bundle or a complete kit under a seperate product number other then just
creating a new product by product builder from the front page by users.

[macallf]

The idea is to create a new product as normal and have a tick box to select it as a build product.

Once saved you will then have an option beside it like parent child items do e.g.

Build Product [categories]

Clicking on categories will then bring up a new page where you can add edit remove categories and beside each will be link to the products in that category e.g.

Motherboards [products]
Processors [products]
Memory [products]

etc.

I hope that explains how the backend will work

[whiplash13]

I agree all the contributors should come up with their must haves and likes for the project.  I think I have pretty much said my peace but I think everyone else needs to ring in.

Mark,
Only issue with that design is if you are not building in dependencies, how does one know they can only select AMD processors if they select an AMD motherboard.  In this case I guess you would have to create a category called AMD Motherboards and Intel Motherboards using your example unless you are saying that you can select the products to fall under this category for this particular product.

Dustundag,
Are you saying that the product should either be configurable by the user or by the store owner as a seperate product #?  or are you saying that it should only be configurable by the store owner?  In my applicaton I definaly want the user to cinfgure the product and would probably never have a use for the latter other than suggesting a configuration that they could then modify if they so choose.

A definite list of must haves or likes before I start in earnest will be good idea. It will give me more of an idea of how to design it and what functionality is required.

[whiplash13]

Also there would obviously be default selections for each category, that can then be edited by the end user, to build a base configuraton.

The idea is to create a new product as normal and have a tick box to select it as a build product.

Once saved you will then have an option beside it like parent child items do e.g.

Build Product [categories]

Clicking on categories will then bring up a new page where you can add edit remove categories and beside each will be link to the products in that category e.g.

Motherboards [products]
Processors [products]
Memory [products]

etc.

I hope that explains how the backend will work

[macallf]

This is how I see it.

The category would define the title, how the products are displayed, images , quantity box style etc.

The products would have options for default product as well as the ability to have a none or null defined. How the price is to be calculated e.g. use full price or a price modifier.

e.g.
Graphics Card
graphics card 64MB, default, price 0
graphics card 128MB, , price +30
graphics card 256MB,, price  (actual-default)

Extra Drives
none, default
dvd rom,,(actual price)
dvd rw,,(actual price)

[whiplash13]

I completely agree with that but if I add the motherboards category do I have to include all motherboards from that category or can I choose specific "product(s)" from this category to include in the overall product?

So for instance if I have 14 motherboard  (8 AMD and 6 Intel) but only want the 8 AMD ones to be configurable for this motherboard is that possible?  or would I have to create seperate product categories for AMD and Intel motherboards?

This is how I see it.

The category would define the title, how the products are displayed, images , quantity box style etc.

The products would have options for default product as well as the ability to have a none or null defined. How the price is to be calculated e.g. use full price or a price modifier.

e.g.
Graphics Card
graphics card 64MB, default, price 0
graphics card 128MB, , price +30
graphics card 256MB,, price  (actual-default)

Extra Drives
none, default
dvd rom,,(actual price)
dvd rw,,(actual price)

[macallf]

The category is not related to any VM category. It is a category for the product builder only.

You add whatever products you want to each category, these can come from any VM category.

e.g. you could have VM sub_categories of manufacturer_a(6), manufacturer_b(4), manufacturer_c(10) (the brackets denote the amount of products) etc but only have one category in the builder "Main Product". Then within this builder category you could have 2 products from manufacturer_a,1 from manufacturer_c etc.

This would make it totally configurable to the way you wish to work or sell products

[whiplash13]

That works.  Will be a little more work to set up but will allow ultimate configuration without a dependability feature.

The category is not related to any VM category. It is a category for the product builder only.

You add whatever products you want to each category, these can come from any VM category.

e.g. you could have VM sub_categories of manufacturer_a(6), manufacturer_b(4), manufacturer_c(10) (the brackets denote the amount of products) etc but only have one category in the builder "Main Product". Then within this builder category you could have 2 products from manufacturer_a,1 from manufacturer_c etc.

This would make it totally configurable to the way you wish to work or sell products

[dustundag]

Iimagine  a  campaign for a typical sets /bundle valid for that set and campaign only. So this would probably mean the capability of the store owner appointing a temporary or parmanent  part number or a bundle name and locking the default selection to the users  . (This would mean that
it is a products ready for a sale like chiled /parent items on the standard VM categories under trims or assemblies categories)   
Surely the default selections for each builder category is a must and a user friendly time saving feature . So we are infact on the same boat!

Dustundag,
Are you saying that the product should either be configurable by the user or by the store owner as a seperate product #?  or are you saying that it should only be configurable by the store owner?  In my applicaton I definaly want the user to cinfgure the product and would probably never have a use for the latter other than suggesting a configuration that they could then modify if they so choose.