Inventory Kit Builder:
• The kit product will display it's assigned Main Image on Category Pages, however once on the Product Page the only images that are displayed are the Main Images of the kit's parts. (bug or feature?)
- If feature, is there a way to display the kit's main image in addition to the images of it's components on the Product Page?
• After being added to the cart, the image used on the Basket Page is the product image of one of the assigned kit components, not the main image of the kit product itself.
- Basket Page image should show the Kit Product’s Main image.
• When an order containing a kit is imported into ShipStation, ShipStation shows the image of the kit's component instead of the kit's actual product image, but even worse, it shows the component's SKU instead of the SKU for the kit itself. This is causing a lot of confusion for order pullers. (Surely a bug, not a feature.)
- ShipStation should display the image and SKU of the kit product, not of a component.
I've found that this problem exists in both our stores - one running Miva 9 and one running Miva 10.
• The kit product will display it's assigned Main Image on Category Pages, however once on the Product Page the only images that are displayed are the Main Images of the kit's parts. (bug or feature?)
- If feature, is there a way to display the kit's main image in addition to the images of it's components on the Product Page?
• After being added to the cart, the image used on the Basket Page is the product image of one of the assigned kit components, not the main image of the kit product itself.
- Basket Page image should show the Kit Product’s Main image.
• When an order containing a kit is imported into ShipStation, ShipStation shows the image of the kit's component instead of the kit's actual product image, but even worse, it shows the component's SKU instead of the SKU for the kit itself. This is causing a lot of confusion for order pullers. (Surely a bug, not a feature.)
- ShipStation should display the image and SKU of the kit product, not of a component.
I've found that this problem exists in both our stores - one running Miva 9 and one running Miva 10.
Comment