Page 1 of 1

Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 9:37 am
by ZLA
What is the current practice to let multiple products make use of the same set of options? I saw this thread: viewtopic.php?f=45&t=8936&hilit=common+options which would require code changes to do this using options.

But that link also suggested using kits. In reviewing kits, it looks like they are product specific. Can someone point me in the right direction?

Thanks.

Re: Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 9:54 am
by Logan Rhodehamel
Kit components can be shared between products. To see how it works, make a kit. Then from the catalog copy the kit. You will see both your copy and your original use the same kit components. Changing the kit component in one will also change it in the other.

In past versions we had a way for you to attach existing kit components to a product. I don't see this in 7.0.3. I am going to log a bug for the ability to be re-established.

Re: Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 10:23 am
by ZLA
I hope you don't mind a lot of questions but the online help is woefully lacking when it comes to kits / bundles. Searching just brings up the version 5 info. The online help would be much more helpful if the subject entries include the versions they applied to. Even better would be if you could search by version. Until help is overhauled, the forums have to provide many of the basic questions as well. Fortunately, all of you at Able Commerce are willing to help beyond belief. Keep up the good work!
Logan_AbleCommerce wrote:Kit components can be shared between products. To see how it works, make a kit. Then from the catalog copy the kit. You will see both your copy and your original use the same kit components. Changing the kit component in one will also change it in the other.

In past versions we had a way for you to attach existing kit components to a product. I don't see this in 7.0.3. I am going to log a bug for the ability to be re-established.
  • Is the above true for 7.0.2 or only 7.0.3? It looks like kitting had some major changes recently. My client is currently on 7.0.2.
  • Why don't kits exist on their own? It looks like I have to create a product first and then add the kitting choices.
  • Once I add the kitting choices, can I use them in another product in AC 7.0.2?
  • Is there swatch-like support in kits? Or is that only available for variants?
  • Is the online demo now version 7.0.3? Or is it still 7.0.2?
Thanks.

Re: Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 10:36 am
by kastnerd
What about product templates?

Re: Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 10:54 am
by ZLA
Templates may work but most likely would require a lot more work than just providing a way to make a copy of an option from one product to another. Options provide built in support for swatches and images. They also provide for multiple SKUs and inventory control as well as price variations. None of that is built into product templates as far as I know.

It would be great if product templates includes an input type of "Option / Variant". But that will have to be another day.

Logan, please let me know if I'm wrong and also address my other questions about common options vs. kits. Thanks.

Re: Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 11:05 am
by Logan Rhodehamel
ZLA wrote:Is the above true for 7.0.2 or only 7.0.3? It looks like kitting had some major changes recently. My client is currently on 7.0.2.
This has always been true, even in AC7.0.0. It was one of the major upgrades from AC55 as merchants complained maintaining kits was very repetitive.
ZLA wrote:Why don't kits exist on their own? It looks like I have to create a product first and then add the kitting choices.
It's how they were originally designed. We refer to the "master" product as the one with the kit choices. This was the simplest way to integrate with our catalog for the kit item, to include it in searches, sorting, pricing rules, etc. I am not sure if we will adjust this in the future.
ZLA wrote:Once I add the kitting choices, can I use them in another product in AC 7.0.2?
Yes. In fact it's easier than in 7.0.3. When you click to add a new kit component, it's not very visible but there is a "click here" link that asks if you want to attach an existing component. You can search existing components and attach them to the kit. Then the choices are shared among the products.
ZLA wrote:Is there swatch-like support in kits? Or is that only available for variants?
Only in variants.
ZLA wrote:Is the online demo now version 7.0.3? Or is it still 7.0.2?
As of this writing 7.0.2, but new demo stores will be 7.0.3 after this weekend.

Re: Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 11:07 am
by ZLA
Thanks Logan. I really appreciate the detailed point by point answers. -- ZLA

Re: Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 11:44 am
by compunerdy
Logan_AbleCommerce wrote: It's how they were originally designed. We refer to the "master" product as the one with the kit choices. This was the simplest way to integrate with our catalog for the kit item, to include it in searches, sorting, pricing rules, etc. I am not sure if we will adjust this in the future.
This really should be changed. Having it set this way forces merchants to create bogus (master) items. Designing it from ground up this way would simplify exporting, inventory, sales reporting, etc.. issues.

You cant use a real product for the parent item in most cases from what I have seen. For instance..
If you use a real item as the master item then..
-you cant sell that same item by itself as well
-If you put a price on the master item then pricing display issues arrise

Re: Standard practice for Common Options / Kits

Posted: Thu Jun 11, 2009 12:17 pm
by Logan Rhodehamel
compunerdy wrote:This really should be changed. Having it set this way forces merchants to create bogus (master) items. Designing it from ground up this way would simplify exporting, inventory, sales reporting, etc.. issues.
We will probably have to have a new kind of catalog object, a redesigned bundle that isn't a product. We can't reform kits outright because some people are using the existng features of the product.

I did some work on this experimentally before altering kits for 7.0.3. The project timeframe would not support the complete redesign.

Re: Standard practice for Common Options / Kits

Posted: Sun Aug 09, 2009 3:52 pm
by Mike718NY
Logan_AbleCommerce wrote: In past versions we had a way for you to attach existing kit components to a product. I don't see this in 7.0.3. I am going to log a bug for the ability to be re-established.
I"m using the current demo and there is no option to even copy a component.
But "attach and copy" do work: I can access that screen by changing the query string to:

Admin/Products/Kits/AttachComponent.aspx?ProductId=57

It's just not showing the
"Define a new component to this kitted product using the form below. If you wish to attach an existing component to this kit, click here.
"
link that the previous version has.
Is this option still available in 7.0.3?