We have a prospective client who sells cleaning products to trade. He's looking to sell them online both to the general public and his existing trade customers.
His existing trade customers all have their own prices for some or all of his products, which he can export as a csv (contain columns for customer id, sku, price)
We usually use cs-cart, but this type of task would be a nightmare in that. I'm thinking it might be more do-able in lemonstand.
I'm thinking we could do something like the following:
All products would be added as normal, along with their standard prices for regular uses
We'd then create a new table (using a custom module) for the custom prices which contains fields for customer id, sku and price. The client could upload a new csv to be imported into this table whenever his prices changed or he got a new product (the table would be just be emptied and reset with the new records each time).
On the front end, whenever a customer was logged in as a wholesaler we'd need to join on customer id with this new table for all product lists, details, or whenever a product was displayed. If there was a value in the price field of the new table then output that, otherwise output the normal price.
Does this sound feasible, and the right kind of way to go about it. Can you forsee any problems, either with the functionality or with performace, and would there likely be any issues with the discount system (say if he wanted to set up a voucher code, or give users a discount on products in a particular category).
Page 1 of 1
Custom prices for each product for each wholesale customer
#2
Posted 09 September 2010 - 04:00 PM
Hi!
Your solution looks good. There should not be issues with discounts, because if you use the shop:onGetCartItemPrice event (http://lemonstandapp...onstand_events/) for overriding cart item prices, the Discount Engine will use the updated prices in the internal calculations.
I don't see possible issues with the offered approach. Let me know if you need any help.
Thanks
Your solution looks good. There should not be issues with discounts, because if you use the shop:onGetCartItemPrice event (http://lemonstandapp...onstand_events/) for overriding cart item prices, the Discount Engine will use the updated prices in the internal calculations.
I don't see possible issues with the offered approach. Let me know if you need any help.
Thanks
#3
Posted 10 September 2010 - 01:54 AM
Great - sounds good.
Another feature the client would like is the ability for customers to re-place old orders. Lots of his customers order the same kind of thing over and over again, so it would be great if he could go into a past order and add it all to the cart (while updating with the latest prices, displaying any out of stock notices, applying any new discounts etc).
Do you know what might be the best way to go about this, and if it might be tricky to implement?
We're just at the proposal stage at the moment so I don't want you to spend any time looking at this, but it would be good to know if its likely to be something that might take a while for us to do and whether we should factor in a fair bit of custom work for it.
Another feature the client would like is the ability for customers to re-place old orders. Lots of his customers order the same kind of thing over and over again, so it would be great if he could go into a past order and add it all to the cart (while updating with the latest prices, displaying any out of stock notices, applying any new discounts etc).
Do you know what might be the best way to go about this, and if it might be tricky to implement?
We're just at the proposal stage at the moment so I don't want you to spend any time looking at this, but it would be good to know if its likely to be something that might take a while for us to do and whether we should factor in a fair bit of custom work for it.
#4
Posted 10 September 2010 - 06:33 PM
Hi!
Re-placing orders is not a difficult task. This store http://lemonstandapp...doorstep_dairy/ creates orders periodically (the feature is called "standing order"). The implementation took only a few hours. Another customer asked us to develop a module which splits orders into 2 new orders, basing on the original order content. So, manipulating with order contents and creating new orders is not a complicated task with LemonStand API. I will provide you with necessary information when you are ready.
Thanks
Re-placing orders is not a difficult task. This store http://lemonstandapp...doorstep_dairy/ creates orders periodically (the feature is called "standing order"). The implementation took only a few hours. Another customer asked us to develop a module which splits orders into 2 new orders, basing on the original order content. So, manipulating with order contents and creating new orders is not a complicated task with LemonStand API. I will provide you with necessary information when you are ready.
Thanks
#5
Posted 13 September 2010 - 01:12 AM
Great - thanks for the info.
I'll let you know if anything comes of our proposal.
I'll let you know if anything comes of our proposal.
Share this topic:
Page 1 of 1

Help












