Product Varients/Options Best Practice

  • Posts: 127
  • Thank you received: 8
8 years 1 month ago #251610

-- HikaShop version -- : 2.6.4
-- Joomla version -- : 3.6.2
-- PHP version -- : 7.0.11
-- Browser(s) name and version -- : Firefox 49.0.1

Hi,

We are doing a restructure of a clients existing hikashop store. The client sells 'weighted' blankets and other products aimed primarily for children and adults with special needs. Currently the store is massive with over 10000 product variants and we are trying to decide the best way to go about structuring the store as one of the main requests made by the client is to simplify the adding and adjusting of prices for the products. The store sells the following different types of blankets:

  • single
  • king single
  • double
  • medium
  • large

Each type of blanket can be sold with a different weight starting from 2kg up to 8kg. This has been created as a product variant selected by the customer (characteristic) and increases in 0.5kg increments. specific products are restricted in weights i.e single blankets are only 2-4kg, while double are 4-8kg. Each increment of weigh (0.5kg) of the blanket changes the cost of the product by a set amount ~ $5.
  • 2.0 +$0
  • 2.5 +$5
  • 3.0 +$10
  • 3.5 +$15 etc
  • ...
  • 7.5
  • 8.0

A blanket product has a specific range of fabrics that the customer can select from, each type of blanket has generic, boy and girl fabrics that the client would like to keep separated from each other. Currently there nearly 300 unique fabrics split among these 3 types.

Currently the system has been set up with ~ 15 different blanket products (Generic, Boy & Girl) X (Single, King Single etc) doing this has led to over 1500 variants of each product. Each product includes a weight range characteristic and a fabric characteristic

100 fabrics X 5 weight increments (2.0-4.0) this is then duplicated for the generic, boys and girls fabrics.

As you can imagine managing this system currently is far too time consuming and requires mass actions and exporting the hikashop database to update product variant pricing and images. The client and they would like to change the system so that they can more easily manage prices, images and other products details without repeating the process more than once (updating the same characteristic across multiple variants).

My question is what would be the best way to implement this structure? Any advice would be welcome.
Cheers

Please Log in or Create an account to join the conversation.

  • Posts: 82863
  • Thank you received: 13372
  • MODERATOR
8 years 1 month ago #251641

Hi,

On the page:
products/blankets/custom-blankets/nanas-generic-blankets/custom-single-bed-blanket
I see that you have two characteristics attached to the product.
One for the fabric and one for the weight.
Regarding the weight, I would actually not use a characteristic but an option product.
That way, you wouldn't have to configure the different prices for each variant.
You would have only one price in the main product, with one set of variants (with one image each) and you would configure the price increments in the variants of the weight option product.
The system would then calculate the total on the product page based on the price of the main product and the selected variant option.
That way, it would make it easier to manage prices since the base price would be in each product only once, and the increment prices would be only in the variants option product, and changing it once there, would reflect in all the products using the option.
It would be easier to configure the images too, since you wouldn't have to configure them for each weight anymore.
I think that just that change would already help a lot.

Please Log in or Create an account to join the conversation.

  • Posts: 127
  • Thank you received: 8
8 years 1 month ago #252196

Hi Nicolas,

Thanks for the response, I think what you described is the way we will move forward.

With the fabric characteristic is it possible to assign a different image to each characteristic without going through the process of creating a set of variants and then assigning an image for each product variant? Either way using product options should help reduce the workload dramatically.

Cheers

Please Log in or Create an account to join the conversation.

  • Posts: 82863
  • Thank you received: 13372
  • MODERATOR
8 years 1 month ago #252209

Hi,

Besides the import of a CSV with the variants and the images set thanks to that in each variant, I don't see a way to automate that.

Please Log in or Create an account to join the conversation.

  • Posts: 127
  • Thank you received: 8
8 years 1 month ago #252417

Hi Nicolas,

I'd rather not rely on using CSV imports as we're trying to make the system as easy as possible for the client to update.

I've created a separate option product for fabrics with the different designs as a characteristic, I've assigned this option product to the main product with the intention or removing the need to create any variants of the main product (saving time to configure the same set of 100+ fabric images for each product). Is it possible update the main product image displayed with the image of the selected product option? Would this require editing the show_default or option view?

I did a search and came across this topic,
www.hikashop.com/forum/product-category-...ions-part-image.html
Does this advice still stand?

Cheers

Please Log in or Create an account to join the conversation.

  • Posts: 82863
  • Thank you received: 13372
  • MODERATOR
8 years 1 month ago #252434

Hi,

If you're talking about the advice that I wrote on this post ( www.hikashop.com/forum/product-category-...rt-image.html#159478 ), then yes, it's still the same. So as you can read there, it would still require modifying heavily the show_img_block view file.

Please Log in or Create an account to join the conversation.

Time to create page: 0.064 seconds
Powered by Kunena Forum