Hi, I'm not sure if this is making things too complicated for users, but the idea sounds good - it is a bit irritating that currently items appear in the basket without any notice ;-)
Since this might make the ordering process more complicated, it would be good if the merge would be optional (e.g. if you could configure this in the admin and select whether to never merge, always merge, show a notice or ask the user what to merge). Another thought: if you allow the user to merge the baskets, then it would be neat if the user could select which products to merge into the basket, and which products to put on the notice list (if it is activated in the shop). I believe Amazon offers the option of moving things between the notice list and the basket in the basket overview. Beste Grüße aus Dortmund! Robert Rosendahl | Entwicklung u. Support -- anzido GmbH Kirchhörder Str. 12 44229 Dortmund Tel.: 0231 - 60 71 079 Fax.: 0231 - 60 71 081 Mobil:0176 - 8325 1488 Email: [email protected] Web: http://www.anzido.com/ (http://www.anzido.com) USt-ID: DE257982972 Geschäftsführung: Andreas Ziethen Amtsgericht Dortmund HRB 20883 -----Ursprüngliche Daten----- Datum: 23.06.2011 15:32:20 Von: Mavydas Skuodas <[email protected]> An: <[email protected]> Betreff: Re: [oxid-dev-general] Merging old and current baskets Vorgang: T-1KW022X2HH-26 > Hi, > > This feature is nice to have, but it has to be more intelligent, more > customizable by shop owners. User scenario should look like this: > > If user logs in and currently donrsquot have anything in the basket, Oxid > should show message (at notice level) that user have had some basket items > before. if user reacts to that notice, he have few options to choose: > > review all content of that basket, (in that window he could add some of the > items of that basket) continue using old basket discard all items. > > If user have something in the basket, oxid should show also the message in > notice, but this time if some items are the same, message text differs, and > says something like ldquoPreviously you also added item X and other N items, > Merge? rdquo. Notice level is important that user will not be distracted from > buying that he is planning to do now (he is in 2 step to the complete order). > Dialog should suggest the same options as before: > > review all content of that basket, (in that window he could add some of the > items of that basket) add most popular item (in Oxid case, this should be > extendable very easily as it depends on shop owner business logic ) discard > all items. > > Mavydas > > From: [email protected] (Dainius Bigelis) > > Sent: Thursday, June 23, 2011 3:33 PM > > To: [email protected] > > Subject: [oxid-dev-general] Merging old and current baskets > > Hi, > > Currently welsquore considering about concept, how to handle basket saved for > user from previous session (when user not finishes the order, so itlsquos > stored to DB). > > One of the ideas is written in the bugtrack entry: > > https://bugs.oxid-esales.com/view.php?id=2260 > > hellip that baskets from the previous session and current order would be > merged using simple rule. > > Though tjungl (see comments from him next to the bug entry) is right that > this concept still would be confusing for customer as some stuff may occur in > the current basket unexpectedly. > > So suggestion is to ask user if he want to merge baskets or no. > > Going further ndash would be even better to give user possibility to choose > which of the products should be merged, which not. The vision is like > displaying content of two baskets and moving it between right <-> left -> or > cancel some. Or just display popup with content of previous basket and > checkboxes for products, which should be merged. > > Anyway such feature would be additional stuff to the order processing area. > > But ndash what are your ideas about that: > > - Do we need such feature at all? Would it be useful? > > - Or better just apply some simple rule for merging and inform about changes > done? > > - Would it affect/reduce the conversion rate (by adding more complex content > to critical place)? > > - Or maybe you have better ideas how to handle that in the simpler way? > > Best regards, > > Dainius Bigelis > > _______________________________________________ > dev-general mailing list > [email protected] > http://dir.gmane.org/gmane.comp.php.oxid.general > > _______________________________________________ > dev-general mailing list [email protected] > http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
