Kitted Product Price Displays as $0.00

[rdevarona]

Hi all,

I'm using the kit feature to provide a way for customers to buy either an individual piece or a case of multiple pieces. I've set the "Master" product to not have a price and then added a component that has two radio button options. These are either a single "Child" product with the standard child product's price and weight, or the same component with the case quantity (in this case 60pcs) in for Kit Quantity.

My issue is that in all of the places that this item shows up, the price is listed as $0.00. Is there any way to show the minimum, or the "Selected" option price instead? Here's a summary of the Kit/Bundle Screen for this component:

Qty:1, Item: Single Piece, Price$8.33, Selected: True
Qty:60, Item: Case of 60, Price$417.00, Selected:

Any help would be greatly appreciated.

Regards,

Ray

[Will]

We ran into a somewhat simliar situation. We sell a product in either a 1-pound package or a 5-pound package.

If you put all of your pricing in kit items, your main product price lists as $0 -- both on the product page and the category page. This also happens if you put all of your pricing into options and variants.

We ended up creating them as product options (variants), rather than a kit.

Product looked like this:

Base product
- base price: $10
- base shipping weight: 1.3 pounds
- base SKU

1-pound bag option
- price modifier: none
- shipping weight modifier: none
- SKU modifier: -1P

5-pound bag option
- price modifier: $40 (override)
- shipping weight modifier: 6 pounds (override)
- SKU modifier: -5P

Hope this helps.

[compunerdy]

In my opinion this is a bug. The parent kit item should show the minimum price of the kit. This should be an option at the very least.

The way I worked around it was to add up all the default items in the kit and set the parent item to that price. Then I made any of the kit items that when select would add to the price to just add the difference between its price and the already accounted for default items price. Its a pain but it worked for me.

[rdevarona]

We ended up creating them as product options (variants), rather than a kit.

I played around with this method, too, but I much prefer having the radio button options explicitly listed instead of having a drop down for pack size. I'll try to look through the control to see if it can be changed easily. Will keep you guys posted.

Thanks for the help,

Ray De Varona

[danielb]

In my opinion this is a bug. The parent kit item should show the minimum price of the kit. This should be an option at the very least.

The way I worked around it was to add up all the default items in the kit and set the parent item to that price. Then I made any of the kit items that when select would add to the price to just add the difference between its price and the already accounted for default items price. Its a pain but it worked for me.

I have this problem too.. Is there a fix/work-around for this problem?

[compunerdy]

Nothing yet. I use kits for many items in my store and would love to discuss how these where designed to work with someone like Logan. They did a good job to start but these could be designed to work a bit better.

[danielb]

As a quick fix for this, this should do it.

in file
\CorLib\Utility\ProductPrice.ascx.cs
in method
Page_Render( ... )

change this

Code: Select all

                ProductCalculator pcalc = ProductCalculator.LoadForProduct(_Product.ProductId, 1, _OptionList, _SelectedKitProducts);
                if (!_Product.HidePrice)
                {
                    //PRICE IS VISIBLE, NO POPUP
                    phPricePopup.Visible = false;
                    Price.Text = pcalc.Price.ToString("ulc");

to

Code: Select all

                ProductCalculator pcalc = ProductCalculator.LoadForProduct(_Product.ProductId, 1, _OptionList, _SelectedKitProducts);
                if (!_Product.HidePrice)
                {

                    LSDecimal result = 0;

                    if (_Product.ProductKitComponents.Count > 0 && Request.QueryString["ProductId"] == null)
                    {
                        Kit kit = new Kit(_Product);
                        result = kit.DefaultPrice;
                    }
                    else
                    {
                        result = pcalc.Price;
                    }

                    Price.Text = result.ToString("ulc");

                    //PRICE IS VISIBLE, NO POPUP
                    phPricePopup.Visible = false;
                    //Price.Text = pcalc.Price.ToString("ulc");

This falls back to the Kit's default price if you don't look at a product display page and the product in the list is a Kit.

Thus, if you have a "sidebar" visible on a "product display page" - prices there would show up as before... but this works in my senario since we don't show products on the sidebar when we're displaying a single product.

[AbleMods]

I've debated this with Able in the past. The issue isn't exclusive to kits - same thing happens with products that have variants/options assigned to them.

No storefront software should ever show a visitor a $0.00 price for a real product. It only encourages an atmosphere of misrepresentation in an environment where people are already leary of being ripped off.

[danielb]

I've debated this with Able in the past. The issue isn't exclusive to kits - same thing happens with products that have variants/options assigned to them.

No storefront software should ever show a visitor a $0.00 price for a real product. It only encourages an atmosphere of misrepresentation in an environment where people are already leary of being ripped off.

I totally agree! But this is the best i could do right now, not having the full source makes it hard to guess what's under the hood in some components. Guess I have to watch the prices too when we start to add up variants then.. thanks for the warning.

[AbleMods]

Wait'll you figure out that adding a variant product to the basket doesn't show the variant image in the basket. It shows the main product image in the basket instead.

Kind of confusing for a customer to order a "Red" polo shirt but have the basket constantly showing the "Green" polo shirt. I modified my code to fix this as well.

[danielb]

Great! now I really feel like this is the commerce solution i want to put my money on!

[AbleMods]

Great! now I really feel like this is the commerce solution i want to put my money on!

Look at this way. For every 1 thing someone doesn't like about AC7, there are 9 other things about it they love. Plus, it's still a "release candidate" of a .0 version. Able made *huge* improvements over 5.5, so there's bound to be some things that still need a little polish.

Let's try a different approach. Go into the "helpful Topics" forum and read my post on how to leverage the Order Status. Truly an ingenious design for order management Able has implemented.

Or better yet, setup some variants on a product, all with respective inventory values. Then turn off the backorder flag on the master product record and reset a particular variant inventory value to 0. Make sure you pulled the product up in a seperate window BEFORE you do all of this.

Now click the Add-to-Cart button on the product page. Not only doesn't AC7 know the item is no longer backorder-able, it knows it's out of stock and automatically removes it from the basket AND tells you why. Now that's slick.

It is hard to please everyone all the time. The gripes I have are signficant to me, but others may not care at all. That's the mark of a truly good product design because it means the product has enough flexibility to apply to a variety of online store needs. Not to mention like 9 different payment gateways supported out-of-box, or 5 integrated shipping carriers. That stuff isn't easy.

[compunerdy]

I agree with Joe. There wouldnt be tons of us on here griping about our small issues if we all where not happy with how the program is setup overall. That doesnt mean I will stop whining anytime soon