| Discussion Forum: Thread 220027 |
|
 |
| | | Author: | EJFJCorp  | | Posted: | May 2, 2017 20:13 | | Subject: | Automatic management of wishlists... | | Viewed: | 73 times | | Topic: | Suggestions | | Status: | Open | | Vote: | [Yes|No] | |
|
| Some improvements are required, according to EJFJ Contextual computing :
- wishlists should be sortable, to put up the very important wishlists, and organize
them according to the priority of fullfilling them...
- commands should be doable from many wishlists, and when pieces are commanded
and not paid one icon should appear saying this piece is reserved in one shop
(with the number of such pieces in the same color) and when the command is paid
another icon should illustrate the piece will be delivered (with the mouseover,
the number of command and few informations should be shown) and when the command
is declared as arrived, the pieces should automatically shown as owned in the
wishing list, showing to the user how to split them all in the different wishlists
(as you did with Apply Order link, but automatizing this, allowing the user processing
when and how he wants, without any obligation...). There are problems not recommanding
many times the same pieces, those which are not used in wishlists should be immediately
put as soldable (if the user has a shop and if the pieces are not put in the
special "reserved wish list"). You should use aliases for everything, allowing
users to rename default wishlist and other special items as aliases of official
sets/parts/...
- Colors should illustrate in any shop the importance of buying such pieces according
to the number of items in the wishlist and the percentage reached by this wishlist
and its priority position in the wishlist queue! Informations should be given
according to the number of such items being commanded and to be paid and those
beings delivered and those already received and not attributed to a specific
wishlist (a button should allow to immediately make the transfer of these pieces
in the reserved wishlist, to a specific buying model wishlist, based on priority!)
- Only the best is legal, you command system is very nice, but with Mail Direct
International PSC, any transporter should own the pieces and any step should
be viewable to the final owner of the pieces, and if some are used by someone
else, other pieces are delivered from another shop (automatically!). Please make
things easier for users and more effectiver for all human beings, sparing risks
of any mistake... Put reminders and inform what is being done and how to proceed
to solve any problem (unavailable pieces commanded should be commanded from another
shop having same or lower price)... Delivery should be quite free (because of
Mail Direct International PSC international reference norms!) based on Bill !T
automatic retribution of any convenient act! Thank you...
|
|
|
| | | | | |
| | | | | Author: | Brettj666 | | Posted: | May 3, 2017 09:50 | | Subject: | Re: Automatic management of wishlists... | | Viewed: | 32 times | | Topic: | Suggestions | |
|
| I look forward to your purchasing Bricklink and making these changes.
There is also no such thing as "free" mail, unless you're petitioning every
country to run a mail service out of the goodness of their hearts.
In Suggestions, EJFJCorp writes:
| | Some improvements are required, according to EJFJ Contextual computing :
- wishlists should be sortable, to put up the very important wishlists, and organize
them according to the priority of fullfilling them...
- commands should be doable from many wishlists, and when pieces are commanded
and not paid one icon should appear saying this piece is reserved in one shop
(with the number of such pieces in the same color) and when the command is paid
another icon should illustrate the piece will be delivered (with the mouseover,
the number of command and few informations should be shown) and when the command
is declared as arrived, the pieces should automatically shown as owned in the
wishing list, showing to the user how to split them all in the different wishlists
(as you did with Apply Order link, but automatizing this, allowing the user processing
when and how he wants, without any obligation...). There are problems not recommanding
many times the same pieces, those which are not used in wishlists should be immediately
put as soldable (if the user has a shop and if the pieces are not put in the
special "reserved wish list"). You should use aliases for everything, allowing
users to rename default wishlist and other special items as aliases of official
sets/parts/...
- Colors should illustrate in any shop the importance of buying such pieces according
to the number of items in the wishlist and the percentage reached by this wishlist
and its priority position in the wishlist queue! Informations should be given
according to the number of such items being commanded and to be paid and those
beings delivered and those already received and not attributed to a specific
wishlist (a button should allow to immediately make the transfer of these pieces
in the reserved wishlist, to a specific buying model wishlist, based on priority!)
- Only the best is legal, you command system is very nice, but with Mail Direct
International PSC, any transporter should own the pieces and any step should
be viewable to the final owner of the pieces, and if some are used by someone
else, other pieces are delivered from another shop (automatically!). Please make
things easier for users and more effectiver for all human beings, sparing risks
of any mistake... Put reminders and inform what is being done and how to proceed
to solve any problem (unavailable pieces commanded should be commanded from another
shop having same or lower price)... Delivery should be quite free (because of
Mail Direct International PSC international reference norms!) based on Bill !T
automatic retribution of any convenient act! Thank you...
|
|
|
|
|
|
|
|
Switzerland, Vaud
Canada, Ontario