Tag Info

New answers tagged

0

I guess this is the taskflow As is -> Select design -> Add to Cart -> Payment gateway Custom -> Fill form -> Mail receipt -> Manual payment You need shopping cart only for the As is section. What you need for custom order is an order history page. But since your requirement is for customers to keep track of both in a same section, this is my suggestion ...


0

Why not delay customization options until the shopping cart is finalized...e.g. you press the checkout option. You'd press checkout, pay for any as-is items in the cart... then get the options for the custom items. If you don't pay for the as-is items, you don't get the ability to order custom items..but it beats having a split order (I see you ordered an ...


0

I would recommend a split layout. Distinguish the process using colors, icons and context. You don't have to add the custom design to cart. The custom design is a group/set of data that the designer would use to make the product. Therefore you can treat it like sending an email. You could include a product reference number in the bespoke design that's from a ...


0

Sounds like you have two channels. 1) manual payment for custom, 2) paypal for as-is. The first option doesn't really need a cart. It's not like customers are going to be filling up their virtual cart with lots of custom products. Even if they do want to order more than one thing, it sounds like this channel will be best served with a landing page that ...


2

You do not need to add customized product into cart since the payment will be done later manually. Cart approach is for payment at the end but you can use another metaphor which is highly accepted in service and customized product sector: inquiry You can create an inquiry section for customized orders with a suggestive price indication. Due to the ...


0

You don't need two separate shopping carts. Your shopping cart is just a generic collection. It can contain any product(s) for that matter. In your case you can specify whether the product is "as is" or a "customizable" one (You can put a flag on the product to say whether this product is customizable. Based on this flag you can enable/disable a ...


1

I understand that you need most logged customers. However, as @ChrisF said, it's not a good practice to force registration. As pointed out in the recent NNG article, if you need the user to register, highlight the benefits of registration from the users’ perspective and not the company’s perspective when asking users to register. NNG had also done a ...


0

It's great to create an account together with the purchase. But instead of sending an automatically generated password sending a link asking the user to create a new password would be appropriate. You can also provide a link to discard the account if they don't want to have an account. If it's an automatically generated password some may use it for the very ...


3

You should only create an account when it's strictly necessary and then only if the user wants to make an account. If possible you should allow users to complete a transaction as a "guest" whereby they enter all their details but these are only stored with the current order and not used to create an account. You can suggest to the user that they create an ...


1

Just change the text of the button to 'Add Another' or 'Add More' to indicate user has already bought this item and he can add more such items if he prefers. I think ebay or amazon has this type of shopping cart.



Top 50 recent answers are included