I don't think that the solution provided by ProductFacility will offer a good solution. I will - again - require a field to be added to the entity. And user would need to propagate the value to field for each product-facility combo. Consider Multiple store, multiple warehouse.... a big burden on the adopter's employees. And it does not give store defaults.
We also have to keep in mind that this requirement is at a higher level, namely at agreement/order level. There the details must be captured, because - when agreed upon - they provide the particulars at a binding contract, that will propagate into lower level (namely receipt of the goods returned). And yes, the settings at store/product level (should) feed into orders, but agreement (when established with long-term contract partners) details may/must override those store/product settings. As always, ad-hoc business decisions may override long-standing (technical) terms in store, product and agreement. Giving a customer a few more days than the default, may lead to having the company retain the customer than sticking to dogmas. And even then product warranty laws may prevail. 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 Sat, Mar 9, 2019 at 1:15 PM Arun Patidar <[email protected]> wrote: > We can use ProductFacility entity for storing number of days and can copy > to it to OrderItem during order creation. > > > Kind Regards, > *Arun Patidar* | Manager, Enterprise Development > HotWax Systems <http://www.hotwaxsystems.com/> > Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, > Indore, M.P. 452010 > Linkedin: *Arun Patidar* <https://www.linkedin.com/in/arunpatidar> > > > > On Sat, Mar 9, 2019 at 4:37 PM Rishi Solanki <[email protected]> > wrote: > > > +1 for having this. The only thing I would like to add go for global > > setting which should be overridden by product level setting. For > example; A > > site may deal in industry which may require different number of days for > > the different products. > > Also agree with Pierre on point we should be aware of the fact that > > unnecessary data model extension should be avoided. > > > > Question: how should we manage if we would like to have two store and for > > both stores we want to have different number of days limit for return. > > My Answer: While configuring the store the System property should be > > configured against prefix/suffix of store id. > > > > Please feel free to add more details or alternative way for handling > this. > > > > Best Regards, > > -- > > Rishi Solanki > > Sr Manager, Enterprise Software Development > > HotWax Systems Pvt. Ltd. > > Direct: +91-9893287847 > > http://www.hotwaxsystems.com > > www.hotwax.co > > > > > > On Sat, Mar 9, 2019 at 1:20 PM Suraj Khurana <[email protected]> > > wrote: > > > > > Hello, > > > > > > In OFBiz, we can create a return for order without checking when that > > order > > > is placed, it might be years long. > > > IMO, we should have a field something like daysToReturn at product > store > > > level to allow creating return till after that much days of order > > > completion. > > > > > > I could not find anything else relevant to this and this is a very > common > > > e-commerce scenario for any business. > > > > > > Am I missing something? > > > Please share your thoughts on the same. > > > > > > -- > > > Best Regards > > > Suraj Khurana > > > TECHNICAL CONSULTANT > > > mobile: +91 9669750002 > > > email: [email protected] > > > www.hotwax.co > > > > > >
