Posted by
Rishi Solanki on
Dec 04, 2018; 8:39am
URL: http://ofbiz.116.s1.nabble.com/Maximum-order-quantity-of-a-product-tp4729076p4729104.html
Hi Deepak,
Generally these kind of requirement temporary at any ecommerce site. Either
business wants to sale limited edition initially or want to give discount
on maximum X quantity.
If you are looking for the second option that is, discount on maximum X
quantity then it can be achievable thru promotion by setting quantity rules
and use limit per order etc.
In other case where business wants to sale limited edition and limit the
purchase quantity per person then in general it should have some time frame
and after that no limit on quantity should be applicable. So I consider it
specific requirement for time and business.
I second with Pierre's suggestion that instead of modifying existing model
should utilize the entity attributes. Also as shared in original email by
Deepak MINIMUM_ORDER_PRICE can go with the MAX_ORDER_PRICE and it won't
affect the existing model. But for this particular requirement I think we
can go with entity attributes and may also think of using it for minimum
order quantity.
@Pritam IMO, as we already have the rules engine for price, IMO adding one
more for quantity not worth enough. And agree on the fact no existing
support available on such requirement OOTB.
Finally, my suggestion is to go with attributes or similar model for
maximum quantity and we can change the minimum logic as well if all agree
ootb.
Brainstorming done in the past for minimum quantity as well -
https://issues.apache.org/jira/browse/OFBIZ-3633But now I think if something can be easily handle using attributes then why
to go for complex calculation done in the past. Attributes seems to better
way to go with.
Thanks!
Best Regards,
--
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.comwww.hotwax.co
On Mon, Dec 3, 2018 at 4:18 PM Pritam Kute <
[hidden email]>
wrote:
> Hello Deepak,
>
> As far as I know, there is no direct support available in OFBiz for your
> requirement. But it would be a good addition to the codebase if we can
> design full features around quantity rules, in a similar fashion as "Price
> Rules".
>
> There can be the multiple cases around quantity which we can handle such as
> 1. Min/Max product quantity to be ordered.
> 2. Rule-based product quantity handling such as based on already added
> products in the cart.
>
> Just a thought!
>
> Thanks and Regards
> --
> Pritam Kute
>
>
> On Mon, Dec 3, 2018 at 3:38 PM Pierre Smits <
[hidden email]>
> wrote:
>
> > Hi Deepak,
> >
> > Instead of modifying the model for the entity such a parameter could be
> set
> > as an attribute of the product. IMO, we have dozens of *Attr entities
> that
> > are greatly under-utilised in favour of adding fields to their associated
> > parent entity.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > *Apache Trafodion <
https://trafodion.apache.org>, Vice President*
> > *Apache Directory <
https://directory.apache.org>, PMC Member*
> > Apache Incubator <
https://incubator.apache.org>, committer
> > *Apache OFBiz <
https://ofbiz.apache.org>, contributor (without
> privileges)
> > since 2008*
> > Apache Steve <
https://steve.apache.org>, committer
> >
> >
> > On Mon, Dec 3, 2018 at 9:43 AM Deepak Nigam <
[hidden email]>
> > wrote:
> >
> > > Hello all,
> > >
> > > I need to set the maximum order quantity for a particular product for
> the
> > > e-commerce site. I have provided the client-side validation for the
> same
> > > but it is easily breakable using request interceptors. Also, I don't
> want
> > > to hardcode it at the backend, considering multiple clients of the ERP
> > > solution.
> > >
> > > As far as I know, we can set the minimum order quantity using product
> > price
> > > type "MINIMUM_ORDER_PRICE". Is there a way by which we can set the
> > maximum
> > > order quantity of a given product (both from front-end and backend)?
> > >
> > > Thanks & Regards
> > > --
> > > Deepak Nigam
> > > HotWax Systems Pvt. Ltd
> > >
> >
>