Char. and options not behaving as expected

  • Posts: 52
  • Thank you received: 0
10 years 3 months ago #202663

-- HikaShop version -- : 2.4.0
-- Joomla version -- : 3.4.1
-- PHP version -- : 5.5.24
-- Browser(s) name and version -- : Chrome is best
-- Error-message(debug-mod must be tuned on) -- : No error message.

We are very pleased so far with Hikashop, it provides more and more possibilities. Currently we have a need to offer options with our products. This must be done in such a way that each product can have a different subset of values for a characteristic. Unwanted values need to be deleted. Also, the values can come with different product-specific pricing, depending on what product they are for.

Hikashop seems able to partly do this, there are two (partial) ways we have found. In the product attributes page:
1. Using the "Options" section: the standard values and pricing is used, all values are presented, but it is not possible to have other pricing or to delete unwanted values from the list.
2. Using the "Characteristics" section: here, after adding the characteristics, the values are created with a product-specific code. It is therefore possible to delete unwanted values. It is also possible to add other prices. However, the prices are not visible in the drop menu on the front end. And the calculations result in strange effects on the product page, wrong pricing for the main product, wrong calculation of total.
Please see the images supplied.

How can we achieve the best of these 2 world. Our products need:
A. Only the values relevant for the product should be visible.
B. The prices of the product-specific-values which can be selected should be visible in the drop menu.
C. The calculations should be correct and visible on the front end, with the price of the basic guitar remaining visible.

Can you help with this? If you like, we can give direct access to that you can see the workings directly.

Kind regards,
Marjoline

Attachments:
Last edit: 10 years 3 months ago by Marjoline. Reason: Making the description clearer.

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

  • Posts: 84304
  • Thank you received: 13699
  • MODERATOR
10 years 3 months ago #202671

Hi,

Characteristics can be used to handle products with variants. For example, shirts of different colors/sizes.
When you set the price of a variant of the product, you enter the price of that variant of the colors/sizes of the product.
So for example, you'll enter the price of the blue XL shirt, and another one for the red S shirt.
You won't enter the price of red, or blue, or S or XL.
So first, you don't see prices in the characteristic dropdown because it's not possible for the system to display one as you didn't set any for the characteristic value, only for the variants of the product.
And second, you don't see the price of the main product as the price of the variants override the price of the main product instead of adding up to it.
That's totally normal and the way it should be. It's just that it's not what you want to use for what you're trying to do.

What you want is to use options. If you need different prices/choices for different products, it will require that you create different options and add the corresponding one for each product. You can't have a global option to add to all the products in that case.

The following user(s) said Thank You: Marjoline

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

  • Posts: 52
  • Thank you received: 0
10 years 3 months ago #204155

Ok, thanks.
I was under the impression that there is a very solid underlying datamodel, which is excellent. And that this datamodel allowed for having an option, say in the case of guitar: finishing in gold, silver or bronze, which will differ in price depending on the type of guitar, for instance bass or electric, electric or acoustic. And many other options such as type of hardware, pickups, etc. And the only think differing is the price. It would be so much less maintenance if I had been able to only register the gold, silver and bronze finish once, and add the say 100 guitars once. And that the options when used for a particular type of guitar just got a different price. That way I would only need to add those three options, and 100 guitars, and add the price only to that relationship. If I understand you correctly, I will now need to create 300 options instead of 3. Namely gold-guitar-1, silver-guitar-1, bronze-guitar-1... then gold-guitar-2, silver-guitar-s, bronze-guitar-2, each time with the prices. So I will have 100 guitar products and 300 options to maintain, instead of 100 guitar products and 3 options.
This creates a tremendous amount of work, I hope you can have a look to see if this can be looked into to simplify this so that instead of maintaining 300 options here, we can just revert back to maintaining the three options with the price being determined on the relationship between guitar and finish-option.
Alas, for now I will have to do it the cumbersome way I fear. :(
Thanks for advising.
Cheers,
Marjoline

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

  • Posts: 84304
  • Thank you received: 13699
  • MODERATOR
10 years 3 months ago #204183

Hi,

Well that's how the system works. For you, it's cumbersome to set different options with different prices for different products. For others, it's a good way to have the same option used for all their products without having to set the prices for each one since they are all the same.

Of course, there is always the possibility to have only the options you need and then calculate the price of the option based on the main product. That can be done with a custom price calculation override plugin. so it requires some development since everyone has different rules for the prices calculations but it's totally possible.
You can find a simple example of price override with our donation plugin:
demo.hikashop.com/index.php/en/hikashop/...t-page/donation-page
If you're a developer it should not be too complex to do that.
Otherwise, you would have to hire one.

The following user(s) said Thank You: Marjoline

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

Time to create page: 0.051 seconds
Powered by Kunena Forum