Webstore - ability to set limit on quantity

This is a forum to suggest new features for mojoPortal. 

This thread is closed to new posts. You must sign in to post in the forums.
7/1/2012 3:39:10 AM
Total Posts 537
feet planted firmly on the ground

Webstore - ability to set limit on quantity

I have a store where I would like to limit each purchase to one only.   I cannot see any way to achieve this (looking at the config of the offers and products). Context - the purchase is an entry for a race.

I see that an offer can comprise specific numbers of products, but there doesn't seem to be a way of saying the user can only buy 1 (or perhaps not more than 2 etc) of the offer.

Could there be some control over this on the Offer configuration?

e.g. one setting 

Maximum # in basket =   (where leaving it empty means unlimited, or up to max # in stock)

If this is set to 1, then the Quantity field should be disappeared or disabled in the Cart.

Of course the user could come back for another go, and ideally this should then cross-check what they have already purchased, but this would be the icing on the cake.

PS my need for this ties in closely with recent discussions/requests (e.g. this thread) for the ability to add custom fields or a survey to the ordering process, to collect some customer information at the time of purchase.  Because we cannot do this at present, I'm collecting this information via registration (custom profile), but allowing the user to make more than one purchase subverts this.


7/5/2012 11:14:56 AM
Total Posts 18439

Re: Webstore - ability to set limit on quantity

I have logged this request but honestly I don't expect to get to it any time soon.

Even if we enforce this at the cart nothing prevents a user from making multiple purchase transactions. Even if we were to keep track of previous orders someone could use a different user account. So to really enforce it is not trivial and 100% enforcement is not feasible.

WebStore is a very basic ecommerce feature and I don't expect to evolve it much until after I complete more of my planned add on products. I built it to support my needs and I share it as it is in case others may find it useful. I do plan to evolve it but its a lower priority vs other things I need to complete to keep my business model viable. Possibly I may try to figure out a way to plug in additional functionality so that I can sell the advanced functionality as add on extensions for WebStore.

I also don't want to make it compete against my other products, ie I think Event Calendar Pro is a closer match for a race entry scenario though it may not have everything you need. But it would be bad for my business model to make improvements to WebStore to support event registration kinds of ecommerce scenarios. Ultimately I have to make a living from my work if I'm to continue doing the work, so I can't do everything as free features.



You must sign in to post in the forums. This thread is closed to new posts.