Customer goes to page for a product and chooses color and other attributes, adds to cart. Customer while in cart decides to change the color and clicks on the product name,picture or description in the cart. Customer is taken back to the product page but none of the options previously selected are there as is the norm for carts.


Is this by design?

Chris, I'd prefer then to see the image and description isn't clickable at all. An edit button would also be nice...as a shopper that's what I'm accustomed too.

Hello,
I posted about a year ago that BVC needed an edit button in the cart, the same as other carts that have functionality to edit options. The feedback was that everyone agreed, but nothing was done.
Clicking a picture is not intuitive to edit options.
As the original post here indicates, when someone wants to edit an existing option that is in the cart all those options should show when going back to do the edits. This is how all other carts work. This is very important for products with many text field options. Not sure if C saw the problem with text fields or just drop-down options.
I thought it used to do this-maintain options when updating.
Unfortunately, I can't test anymore since I don't use the cart due to the delay in kitting.


Bob

BV 2004 product template.

You can check it out on any product.

Just checked ours with the BVC5 template...does the same thing. Is this a change in Sp3 ?

Totally understood...I wasn't even sure it was a problem. Apparently it's something else not quite right.

Justin, stock 3 or 3B2 stores have the same bug.

Create a product, custom url, minimum quantity, 1 product modifier which is color with options red and blue
Go to product page, add it to the cart with Blue selected (red is first on the list). Once in the cart click on the product, you get dropped back on the product page with no information carried back.

I'm sure it's the same in Sp 3.1

Absolutely stock installs, fresh DB, brand new test stores...so it's not something we've done, it's stock behavior. I think most all of us would consider this a major bug.

Everything is lost. It loses track of anything entered into text area boxes as we use those fields. A week or so ago we had people clicking back and forth and we couldn't figure out why. What they end up doing is abandoning the cart entirely. Some of our products require 5-7 selections. Right now stock bvc5 forces a customer to:

1. recognize that this cart functions differently than what they are acccustomed to at amazon, target etc and does not carry back the selections when they click on the item
2. In recognizing 1 the customer has to go to the cart page by finding the cart icon and DELETE the product they may just want to change one item on
3. Navigate back to the page of the product they like
4. Re-input all the information to just change something as simple as a color.

In short 99% of your customers will just leave and go somewhere else. We had no idea this was going on until a trusted long term customer pointed it out as a major usability issue. It explains a lot of wasted CPC conversions 10-15 days ago. We could literally watch people via chat going back and forth between pages 4 or 5 times, then they'd just leave. They shouldn't have to spend 3 minutes deleting and clicking just to change a shirt from red to yellow...this is silly.

I'm confused as to what the purpose of having the items in the cart being clickable.

I have not tested but others tell me 2004 was not like this and functioned properly.


Bob to be concise, clicking the picture or text doesn't matter, it still just dumps the customer back to a blank product page with no options carried back.

Justin, you didn't test it with a rewritten/custom url. I just ran the tests on Sp3.1 fails every time on every selector if the url is specified on the product page. Remove and let the program decide the url and it's fine and even Bob's text fields work fine.

This is a major bug, please get out a hotfix next week if at all possible.

Thanks

We browsed some of your stores last night with custom urls and choices/modifiers, in every case the problem was duplicated so it's a bug. The key is a custom url.